Comment 5 for bug 1516341

I apologize if I missed something as I'm new to the documents. I pulled from git, built the docs and I see the following:

path: openstack-manuals/doc/ha-guide/build/html/controller-ha-identity.html

It looks like its setting up a single vip(10.0.0.11) configured in pacemaker and has the endpoints and all services pointing to a single vip. I'm not seeing any mention of load balancing on this page. Where does the vip reside?

...

nm, I'm finally see it at https://docs.openstack.org/ha-guide/controller-ha-vip.html . So haproxy is using pacemaker as well? I was reading some haproxy docs earlier and it looks like the creator recommends keepalived for haproxy use for the following reasons:

http://www.formilux.org/archives/haproxy/1003/3259.html

I'm not opposed to pacemaker, but it is a bit of overkill for some of this. We have used it in the public cloud and it always seems to turn out badly. The original builders may know how to use it, but your average tech has a hard time with it. It usually ends up with them getting in and breaking pacemaker in the process of bringing up the services manually. It usually ends up staying in a broken status as no-one wants to take it down while in the process of fixing the cluster to keep SLA.