Red Hat Bugzilla – Bug 1304020
[RFE] Automated Deployment of Instance HA in Director/Openstack
Last modified: 2016-11-16 07:58:08 EST
Automated deployment of Instance HA would be a desirable feature to include in Director/Openstack.
For this customer it was one of their requirements in the initial engagement and is currently automated in Spinal Stack for them. It's of particular interest to obsolete their use of Spinal Stack by building those features into contemporary versions of RHOSP.
Currently OSPd will partially deploy some of instance HA; however pacemaker remote requires additional manual configuration to complete the setup.
It would be highly desirable if this could be defined, and the conducted via the deployment of the overcloud.
Correction on this one. There is a post process script that runs after spinal stack does the deploy that configures pacemaker remote and instance ha for them. Director does in fact partially deploy some of this but it would be great if it would completely deploy the proper configuration as well as possibly including a test to validate the config or simulate instance fail over.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
On a related note I would like comments on this use case
All documentation states that once isntance HA is turned on upgrades are out of the question. My question is
- Can instance HA be turned off after being turned on ?
Is it possible to follow these steps at all ?
- If I manually turned on Instance HA
- Can manual steps be followed to turn it off ?
- If the above answer is yes, can I then proceed to do an upgrade ?
*** This bug has been marked as a duplicate of bug 1264181 ***