Red Hat Bugzilla – Bug 1259599
[RFE] [Undercloud] Undercloud High Availability
Last modified: 2018-01-20 21:52:00 EST
1. Bug Overview:
a) Description of bug report:
[RHEL-OSP 7.0]: Undercloud high availability
b) Bug Description:
Currently RHEL OSP Director does not provide a way
to make the Undercloud high availability
Version-Release number of selected component:
RHEL OSP Director 7.0 GA
2. Bug Details:
I would like to know how to make the Undercloud high availability
The Undercloud is an OpenStack instance. Therefore following
documents may be helpful as references.
OpenStack High Availability Guide
High availability with Red Hat Enterprise Linux OpenStack Platform 4
But I am not sure these are enough for the undercloud
and could recommend them to our customers.
According to the roadmap of the Director, Red Hat seems to have
a plan of high availability Undercloud. I guess it because
3 nodes are figured for the Undercloud nodes. (See p.32, p.39)
RHEL OpenStack Platform director Overview and Roadmap
If Red Hat has the plan and it is realized in a short term,
we can recommend customers to wait for updating the Director.
If it takes time that the Director supports the Undercloud
high availability, alternative way should be presented to customers.
3. Business Justification
Generally speaking, production environments always require
high availability composition to remove SPOF.
The Undercloud node can be an SPOF.
4. Primary contact at Red Hat, email, phone (chat)
email@example.com (Yo kawada)
5. Primary contact at Partner, email, phone (chat)
firstname.lastname@example.org (Takashi Aosawa)
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
*** Bug 1337935 has been marked as a duplicate of this bug. ***
Other partner also need to track this feature and requested to make this visible for them.
I believe this BZ doesn't contain confidential information, but I'd like to ask you if you can make this RFE public or make this RFE visible from other partner.
Thank you for your comment via email.
Now I made this one as public RFE.
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Agree with Fabio. This task most likely fits with the Deployment framework DFG.
Some general thoughts here on the approach we take to implement this. I would not recommend using instack-undercloud as a basis. I would much rather see us leveral some of the new containers deployment bits with Ansible to drive a multi-node undercloud installer.
The new tripleo-heat-templates underclouds gets us part of the way here. This along with deployed-server and some ansible orchestration around it could do the trick I think quite nicely. There are some up-front network considerations that need to be worked out for VIPs, etc (and perhaps we will consult PIDONE for these details) but in general I think most of this is deployment architecture work.
Moving out of OSP13. Delivering containerized undercloud is having higher priority.