The page (page 2 of the PDF version) indicates:
"Typically, an active/passive installation for a stateless service would maintain a redundant instance that can be brought online when required. Requests are load balanced using a virtual IP address and a load balancer such as HAProxy."
In my experience, Active/Passive configurations do not use a load balancer because the secondary (passive) instance is offline. A load balancer MAY be put in place to make the activation of the passive instance simpler (i.e. all requests continue to use the VIP provided by the load balancer) -- however, this traffic would not be considered "load balanced" because all load is either handled by the active node or the passive node which has been made active when the usual active node has failed.
I suggest the following edit as being more technically correct:
"Typically, an active/passive installation for a stateless service would maintain a redundant instance that can be brought online when required. Requests are SERVICED using a virtual IP address and a load balancer such as HAProxy."
-----------------------------------
Built: 2014-07-31T19:38:00 00:00
git SHA: c00a9a2a4ed0330da6f9eefbaf0153d97f357e56
URL: http://docs.openstack.org/high-availability-guide/content/ap-intro.html
source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/high-availability-guide/ch_intro.xml
xml:id: ap-intro
I have been making my way through this guide and have found it to be very useful. I have some suggestions and possible corrections. Rather than open a bug on each of them, I would like to consolidate them here.
I marked up a copy of the high-availabili