[Rdo-list] [Softwarefactory-dev] Gitnetics integration, or how can we automate upstream changes polling

[David Moreau Simard]

+1, let's split OPM into a single package per module (and then a
meta-package to install them all) like we agreed and let it stay
vanilla.

If anything breaks, let's address it.

Until we have a mean to test a vanilla OPM, we do not have a way to
see what is really necessary.
Upstream puppet openstack uses vanilla puppet modules and it works just fine.

If there are downstream patches necessary for RDO Manager or
Packstack, our CI or frequent testing (such as test days) should be
able to identify the issues.


David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]


On Thu, Feb 4, 2016 at 6:31 AM, Haïkel <hguemar at fedoraproject.org> wrote:
> I do not have the whole context, so this is just few comments:
> 1. we're trying to split the OPM behemoth and goal is to converge to
> the point where we don't need any downstream patches.
> 2. until then, we can just use our own mirrors instead of upstream
> 3. depending how much time, it'll take, it would be worth considering
> having vanilla puppet modules packages available for testing
> Moreover associated w/ delorean, it will help us to catch glitches as
> soon as puppet modules gets broken.
> 4. I don't like cherry-pick upstream commits on top of own branches,
> it only encourage us to widen the gap with upstream.
>
> If we aim to be the first (as in excellence) vanilla distribution of
> OpenStack, no exception for puppet modules. If upstream model is
> broken, for us, then fix it.
> We've been working with Emilien (upstream Puppet Module PTL) to fix
> upstream CI w/ RDO, so it's doable.
>
> Regards,
> H.
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe at redhat.com