openstack/openstack-manuals
Code Issues Proposed changes

changed al-pacemaker cleanup

Browse Source 
removed extra -
corrected run on sentence
added "the" before Corosync
changed "an" to a before default

Change-Id: I3e5996049e859d7ab5fb108ddcfe3a5435b7dc7c
This commit is contained in:
Shilla Saebi 2014-02-17 12:18:24 -05:00
parent 88d7e271cd
commit df9791128b
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/high-availability-guide/ap-pacemaker.txt
View File

@ -4,12 +4,12 @@
OpenStack infrastructure high availability relies on the
http://www.clusterlabs.org[Pacemaker] cluster stack, the
state-of-the-art high availability and load balancing stack for the
Linux platform. Pacemaker is storage- and application-agnostic, and is
Linux platform. Pacemaker is storage and application-agnostic, and is
in no way specific to OpenStack.
Pacemaker relies on the http://www.corosync.org[Corosync] messaging
layer for reliable cluster communications. Corosync implements the
Totem single-ring ordering and membership protocol and provides UDP
Totem single-ring ordering and membership protocol. It also provides UDP
and InfiniBand based messaging, quorum, and cluster membership to
Pacemaker.
@ -107,7 +107,7 @@ usually named +corosync+:
* +start corosync+ (upstart)
* +systemctl start corosync+ (systemd)
You can now check Corosync connectivity with two tools.
You can now check the Corosync connectivity with two tools.
The +corosync-cfgtool+ utility, when invoked with the +-s+ option,
gives a summary of the health of the communication rings:
@ -151,7 +151,7 @@ that the cluster is communicating properly, it is safe to start
* +start pacemaker+ (upstart)
* +systemctl start pacemaker+ (systemd)
Once Pacemaker services have started, Pacemaker will create an default
Once Pacemaker services have started, Pacemaker will create a default
empty cluster configuration with no resources. You may observe
Pacemaker's status with the +crm_mon+ utility: