Hi Ilja,
On Mon, 2016-08-15 at 17:08 +0100, Ilja Maslov wrote:
Hi,
I’ve been trying to use centos-release-openstack-mitaka repo to
deploy undercloud, build overcloud images (with some hacks to use the
same repo) and deploy the overcloud.
I think you are running into the same issues we are.
The rationale behind it is to use Centos-provided repos with
production deployment in mind.
rdo-trunk-mitaka-tested repo has many bugs fixed, but I do not think
it can be qualified as production-ready repository.
Agreed, production deployment at the moment with RDO is not a pretty
picture. Sorry to be blunt but this is my experience after around a
year of working with it. We have to pin package versions, mash
repositories together, run deployments from nightly images and the
like. We generally resort to the OSP documentation for a definitive
source.
Long story short, centos-release-openstack-mitaka has os-net-config
package at version 0.2.2-1.el7, which broke Linux Bond configurations
[1].
We also have issues with incorrect galera affecting HA and a bug with
keystone v3 domain support
The issue had been fixed back in April and made it to RHEL OSP
(Liberty), but not to centos-release-openstack-mitaka.
I’m not sure if rdo-list is the best place to ask this question, but
would appreciate if you can point me towards resources describing how
Centos stable repos for OpenStack are maintained, tested and packages
promoted to newer versions.
I would also really appreciate this so there can be a cohesive effort
towards maintaining a stable rdo release.
It feels as if today, one has a choice between a bit outdated Centos
repo and too hot rdo-trunk-tested. Is there anything in between that
can be used for production deployments?
I think the idea with the CentOS repo is that it only gets updated with
when upstream release an update. But there doesn't seem to be any CI
that tests whether this setup actually works.
I have added this as a topic for Wednesday's IRC meeting:
https://etherpad.openstack.org/p/RDO-Meeting
but it is unlikely I will be able to attend this as I will be
travelling.
--
Regards,
Christopher