[rdo-users] Newbie question: CentOS Cloud SIG vs RDO vs "centos-release-openstack-xxx"

[Haïkel Guémar]

On 01/26/2018 05:07 PM, Jan Gutter wrote:
> Hi,
> 
> Apologies for asking an obviously newbie question here, but I got a bit 
> confused by the relationship between the CentOS Cloud SIG, RDO and the 
> repos enabled by installing "centos-release-openstack-<x>".
> 
> For example, I'm aware that upstream OpenStack is no longer supporting 
> Newton, but RHEL has support for RHOSP10 (based on Newton). I do see 
> that Newton's still listed on https://trunk.rdoproject.org/
> 

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.

As for Newton, it's not EOL yet despite what website says. This month, 
we had a Nova, puppet modules and TripleO updates.


> Am I correct in assuming that the repos pointed to when a CentOS user 
> installs centos-release-openstack-<x> points to a set of packages that 
> was emitted from the RDO pipeline? Is this process manual or automated 
> to some degree?
> 

RDO packages are built by an automated pipeline through our gerrit/zuul 
instances in review.rdoproject.org.

RDO stable builds == CentOS Cloud SIG OpenStack builds
The only difference lies in the -release packages, the one in CentOS 
extras enables more CentOS repositories for additional features.
rdo-release should be preferred for RHEL users as it enables less 
external repos.

RDO trunk builds are meant to be consumed by CI pipeline or for the more 
adventurous/advanced users (it's also an excellent way to apply 
quickfixes too).

> In a semi-related question: I've hit an issue with an outdated 
> puppet-pacemaker package in the centos-release-openstack-newton repo 
> that prevents deployment. There's an "easy fix" available by promoting 
> the pike version of said package to the same repo, but if Newton's been 
> sunset then this question is moot.
> 

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.

> Apologies for the meandering ramble, if you need more details on the 
> last issue I can provide them.
> 

It's always fine to ask questions :)

Regards,
H.

> -- 
> 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
>