Incorrect description of Active/Passive for Stateless, and other HA guide issues.

Bug #1352053 reported by Doug Baer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
High
Doug Baer

Bug Description

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

Tags: ha-guide
tags: added: ha-guide
Revision history for this message
Doug Baer (dbaer-2) wrote :

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-availability-guide.pdf file with comments/annotations and text highlights. If these do not come through, please let me know and I will try to find an alternate mechanism.

Revision history for this message
Tom Fifield (fifieldt) wrote :

Thanks Doug.

We know there are a ton of issues with the guide as it is and would really appreciate the help.

summary: - Incorrect description of Active/Passive for Stateless ?
+ Incorrect description of Active/Passive for Stateless, and other HA
+ guide issues.
Changed in openstack-manuals:
status: New → Triaged
importance: Undecided → High
milestone: none → juno
Revision history for this message
Doug Baer (dbaer-2) wrote :

Tom, I'm happy to help. I will assign the doc bug to myself and get the update submitted the proper way.

Changed in openstack-manuals:
assignee: nobody → Doug Baer (dbaer-2)
Changed in openstack-manuals:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/114338
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=0cd5218f50be4697a43f393036f6c70af0a9a98b
Submitter: Jenkins
Branch: master

commit 0cd5218f50be4697a43f393036f6c70af0a9a98b
Author: Doug Baer <email address hidden>
Date: Thu Aug 14 12:36:29 2014 -0700

    Corrects typos and provide clarification

    Closes-Bug: #1352053
    Minor ormatting, capitalization and verb tense corrections
    Corrections to IP addresses in some examples and replacing "VIP" with "virtual IP" for simplicity.
    Calling out split-brain possibility in 2-node cluster with required quorum override
    Amended with feedback from Andreas Jaeger and Christian Berendt on patch set 1 and 2

    Change-Id: I1cc532d73483ad82d1ceaec92a8caf11071a7d0e

Changed in openstack-manuals:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-manuals 15.0.0

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.