The goal here is to use the Foreman which is part of RHOS to deploy the core OpenStack controller services (and their dependencies) such that they will be highly available. This includes the following tasks from https://home.corp.redhat.com/wiki/rdo-usability-sprint -Use Foreman to deploy RDO with load balanced services and HAProxy/keepalived (creation of LB Host Group) -Use Foreman to deploy RDO with highly available mysql using Pacemaker/Corosync -Use Foreman to deploy RDO with highly available qpid
Since this is 3 separate deliverables on the sprint, would it make more sense to list each of them in their own BZs?
This describes the desired end-state. The sprints are a function of breaking it apart at a technical level so each individual piece can be completed and confirmed on a unit level. NOTE: There is still some debate on the qpid HA so for beta we will limit to the first two (lb + ha/mysql).
Load Balancer and HA/mysql are in this release
Jason, can u plz provide more info on the implementation (i.e. gerrit link etc.)
Ami, we have not been using gerrit for anything to date, but the 2 host groups (HA Mysql and Load Balancer) merely need to be applied to a couple of nodes - note load balancer is not yet itself HA. Overview can be found starting here: http://openstack.redhat.com/Deploying_RDO_Using_Foreman#Load_Balancer Let me know if you have more specific questions I can assist with.
*** Bug 1027535 has been marked as a duplicate of this bug. ***
I dont see a need for a doc text here. This is more of a Feature that can/will be documented in official documentation vs notes on the BZ.
Let's limit the scope on this one to explicitly test the LB via haproxy for services on the controller node. We'll track qpid ha in 1049122 and the ha/mysql setup in 1049121
Verified with: openstack-foreman-installer-1.0.3-1.el6ost.noarch (puddle 2014-01-16.1) /var/log/messages: Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy ceilometer-api started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy cinder-api started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy glance-api started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy glance-registry started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy heat-api started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy horizon started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy keystone-admin started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy keystone-public started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy nova-compute started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy nova-ec2 started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy nova-metadata started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy stats started. Jan 19 17:37:09 cougar14 haproxy[3263]: Proxy swift-proxy started. [root@cougar14]# /etc/init.d/haproxy status haproxy (pid 3264) is running...
I still don't see a reason for doc text here, as I mentioned in Comment #10
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2014-0046.html