[rdo-users] Newbie question: CentOS Cloud SIG vs RDO vs "centos-release-openstack-xxx"
Haïkel Guémar
hguemar at redhat.com
Fri Jan 26 23:48:33 UTC 2018
On 01/26/2018 06:21 PM, Javier Pena wrote:
> Hi Jan,
>
> ------------------------------------------------------------------------
>
> On 26 January 2018 at 18:24, Haïkel Guémar <hguemar at redhat.com
> <mailto:hguemar at redhat.com>> wrote:
>
> On 01/26/2018 05:07 PM, Jan Gutter wrote:
>
> First RHOSP and RDO are different distros, RDO is to RHOSP what
> Fedora is to RHEL.
> RDO follows the same lifecycle as upstream OpenStack, RHOSP
> lifecycle is defined by Red Hat product management.
>
>
> Ah thanks, I realised that there's a fork there, but somehow I
> thought it was later. I presume there's no distro that has a similar
> relationship to RHOSP as CentOS has with RHEL.
>
> As for Newton, it's not EOL yet despite what website says. This
> month, we had a Nova, puppet modules and TripleO updates.
>
>
> I think the TripleO update pulled in the accidental depency that's
> needed:
>
> It seems that the RPM for puppet-tripleo includes this commit:
> https://github.com/openstack/puppet-tripleo/commit/547d96d70db6e88eb2de44ac8212ed5dd5864692#diff-24e7008c99ef5f420d7457a0cfe16cd9
> (note the cross-dependency)
>
> However, the package puppet-pacemaker for newton RPM doesn't include
> the corresponding commit:
> https://github.com/openstack/puppet-pacemaker/commit/d7f4f9a08ae6f685058e78075060ee03c5de7cf1#diff-f04b36a70bfe6061dab388d183c1c716
>
> This means that pacemaker setups break during deploy. I tested
> with puppet-pacemaker-0.6.0-1.e0f9c42git.el7.noarch.rpm from the
> pike repo and it seems to work.
>
> I think I found the reason for this. Looking at rdoinfo (the source of
> information for what we build in RDO) I found this: [1]. The tags in the
> YAML file mean that we are building puppet-pacemaker 0.4.0 in RDO
> Newton, and 0.5.0 in Ocata. It looks like the patch you need in
> puppet-pacemaker is already available in 0.5.0, see [2].
>
> To make things more interesting, the RDO Trunk builds use the same
> stable branch for both Newton and Ocata, and it's stable/0.6.x. This
> branch is more recent than what we ship in RDO.
>
> So, TL;DR: we can propose two different fixes here:
>
> a) For a quick fix, you can use
> https://trunk.rdoproject.org/centos7-newton/current-passed-ci/puppet-pacemaker-0.6.1-0.20171124095858.5f56a96.el7.centos.noarch.rpm
> to replace your current puppet-pacemaker package.
> b) For a stable fix, we should at least bump the puppet-pacemaker
> version we are shipping in Newton to 0.5.0, to match the Ocata version
> and fix the deployment issue.
>
> Haikel, what do you think?
>
> Regards,
> Javier
>
+2 if that's what trunk builds are already using, I have no objections
to bump stable packages to 0.5.0 or 0.6.0
>
> [1] -
> https://github.com/redhat-openstack/rdoinfo/blob/master/rdo.yml#L1275-L1293
> [2] - https://review.openstack.org/422484
>
> RDO stable builds == CentOS Cloud SIG OpenStack builds
>
>
> Thanks, that finally clicks. As I was reading your mail I found a
> link that also cleared it up: https://www.rdoproject.org/what/repos/
>
> Well, that's something we can consider but it has to be
> discussed with puppet modules maintainers. But updating newton
> by using the pike version of the packages implies to update it
> in Ocata too. Otherwise we break the upgrade path.
>
>
> Ah, good point. I didn't check if Ocata had the corresponding
> puppet-tripleo commit.
>
> --
> Jan Gutter
> Embedded Networking Software Engineer
>
> Netronome | First Floor Suite 1, Block A, Southdowns Ridge Office Park,
> Cnr Nellmapius and John Vorster St, Irene, Pretoria, 0157
> Phone: +27 (12) 665-4427 | Skype: jangutter | www.netronome.com
> <http://www.netronome.com>
>
>
> _______________________________________________
> users mailing list
> users at lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/users
>
> To unsubscribe: users-unsubscribe at lists.rdoproject.org
>
>
More information about the users
mailing list