33 lines
1.8 KiB
XML
Raw Normal View History

<chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xi="http://www.w3.org/2001/XInclude"
version="5.0" xml:id="ch-pacemaker">
<info>
<title>The Pacemaker cluster stack</title>
</info>
<simpara>OpenStack infrastructure high availability relies on the
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.clusterlabs.org">Pacemaker</link> 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
in no way specific to OpenStack.</simpara>
<simpara>Pacemaker relies on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.corosync.org">Corosync</link> messaging
layer for reliable cluster communications. Corosync implements the
Totem single-ring ordering and membership protocol. It also provides UDP
and InfiniBand based messaging, quorum, and cluster membership to
Pacemaker.</simpara>
<simpara>Pacemaker interacts with applications through <emphasis>resource agents</emphasis> (RAs),
of which it supports over 70 natively. Pacemaker can also easily use
third-party RAs. An OpenStack high-availability configuration uses
existing native Pacemaker RAs (such as those managing MySQL
databases or virtual IP addresses), existing third-party RAs (such as
for RabbitMQ), and native OpenStack RAs (such as those managing the
OpenStack Identity and Image Services).</simpara>
<xi:include href="./pacemaker/section_install_packages.xml"/>
<xi:include href="./pacemaker/section_set_up_corosync.xml"/>
<xi:include href="./pacemaker/section_starting_corosync.xml"/>
<xi:include href="./pacemaker/section_start_pacemaker.xml"/>
<xi:include href="./pacemaker/section_set_basic_cluster_properties.xml"/>
</chapter>