Cluster Resource Manager
++ Pacemaker is an Open Source, + High Availability + resource manager suitable for both small and large + clusters. +
+
+
++ "The definitive open-source high-availability stack for the Linux + platform builds upon the Pacemaker cluster resource manager." + -- LINUX Journal, + "Ahead + of the Pack: the Pacemaker High-Availability Stack" ++ + +
+
+ + Pacemaker has been around + since 2004 + and is primarily a collaborative effort + between Red Hat + and SuSE. However, we also + receive considerable help and support from the folks + at LinBit and the community in + general. +
++ The core Pacemaker team is made up of full-time developers from + Australia, the Czech Republic, the USA, and Germany. Contributions to the code or + documentation are always welcome. +
++ Pacemaker ships with most modern Linux distributions and has been + deployed in many critical environments including Deutsche + Flugsicherung GmbH + (DFS) + which uses Pacemaker to ensure + its air traffic + control systems are always available. +
++ Currently Andrew Beekhof is + the project lead for Pacemaker. +
+
+
+ + Stay up to date with the ClusterLabs community by subscribing to our + mailing lists or by following the project development on Github. +
+ +We support many deployment scenarios, from the simplest 2-node standby cluster to a 32-node active/active configuration. We can also dramatically reduce hardware costs by allowing several active/passive clusters to be combined and share a common backup node.
We monitor the system for both hardware and software failures. In the event of a failure, we will automatically recover your application and make sure it is available from one of the remaning machines in the cluster.
After a failure, we use advanced algorithms to quickly determine the optimum locations for services based on relative node preferences and/or requirements to run with other cluster services (we call these "constraints").
At its core, a cluster is a distributed finite state machine capable of co-ordinating the startup and recovery of inter-related services across a set of machines.
System HA is possible without a cluster manager, but you save many headaches using one anyway
Even a distributed and/or replicated application that is able to survive the failure of one or more components can benefit from a higher level cluster:
While SYS-V init replacements like systemd can provide deterministic recovery of a complex stack of services, the recovery is limited to one machine and lacks the context of what is happening on other machines - context that is crucial to determine the difference between a local failure, clean startup or recovery after a total site failure.
The ClusterLabs stack, incorporating Corosync - and Pacemaker defines + and Pacemaker defines an Open Source, High Availability cluster offering suitable for both small and large deployments.
"The definitive open-source high-availability stack for the Linux platform builds upon the Pacemaker cluster resource manager."
-- LINUX Journal, "Ahead of the Pack: the Pacemaker High-Availability Stack"
A Pacemaker stack is built on five core components:
We describe each of these in more detail as well as other optional components such as CLIs and GUIs.
Pacemaker has been around since 2004 and is primarily a collaborative effort between Red Hat and SUSE, however we also receive considerable help and support from the folks at LinBit and the community in general.
"Pacemaker cluster stack is the state-of-the-art high availability and load balancing stack for the Linux platform."
-- OpenStack documentation
Corosync also began life in 2004 but was then part of the OpenAIS project. It is primarily a Red Hat initiative, however we also receive considerable help and support from the folks in the community.
The core ClusterLabs team is made up of full-time developers from Australia, Austria, Canada, China, Czech Repulic, England, Germany, Sweden and the USA. Contributions to the code or documentation are always welcome.
The ClusterLabs stack ships with most modern enterprise distributions and has been deployed in many critical environments including Deutsche Flugsicherung GmbH (DFS) which uses Pacemaker to ensure its air traffic control systems are always available.
At its core, Pacemaker is a distributed finite state machine capable of co-ordinating the startup and recovery of inter-related services across a set of machines.
Pacemaker understands many different resource types (OCF, SYSV, systemd) and can accurately model the relationships between them (colocation, ordering).
It can even use technology such as Docker to automatically isolate the resources managed by the cluster.
Corosync APIs provide membership (a list of peers), messaging (the ability to talk to processes on those peers), and quorum (do we have a majority) capabilities to projects such as Apache Qpid and Pacemaker.
libqb is a library with the primary purpose of providing high performance client server reusable features. It provides high performance logging, tracing, ipc, and poll.
The initial features of libqb come from the parts of corosync that were thought to useful to other projects.
Resource agents are the abstraction that allows Pacemaker to manage services it knows nothing about. They contain the logic for what to do when the cluster wishes to start, stop or check the health of a service.
This particular set of agents conform to the Open Cluster Framework (OCF) specification. A guide to writing agents is also available.
Fence agents are the abstraction that allows Pacemaker to isolate badly behaving nodes. They achieve this by either powering off the node or disabling its access to the network and/or shared storage.
Many types of network power switches exist and you will want to choose the one(s) that match your hardware. Please be aware that some (ones that don't loose power when the machine goes down) are better than others.
Agents are generally expected to expose OCF-compliant metadata.
The original documentation that sparked a lot of this work. Mostly we only use the "RA" specification. Efforts are underway to revive the process for updating and modernizing the spec.
Pacemaker's internal configuration format is XML, which is great for machines but terrible for humans.
The community's best minds have created GUIs and Shells to hide the XML and allow the configuration to be viewed and updated in a more human friendly format.
The original configuration shell for Pacemaker. Written and actively maintained by SUSE, it may be used either as an interactive shell with tab completion, for single commands directly on the shell's command line or as batch mode scripting tool. Documentation for crmsh can be found here.
An alternate vision for a full cluster lifecycle configuration shell and web based GUI. Handles everything from cluster installation through to resource configuration and status.
The original GUI for Pacemaker written in Python by IBM China. Mostly deprecated on SLES in favor of Hawk
Hawk is a web-based GUI for managing and monitoring Pacemaker HA clusters. It is generally intended to be run on every node in the cluster, so that you can just point your web browser at any node to access it. There is a usage guide at hawk-guide.readthedocs.org, and it is documented as part of the SUSE Linux Enterprise High Availability Extension documentation
The Linux Cluster Management Console (LCMC) is a GUI with an inovative approach for representing the status of and relationships between cluster services. It uses SSH to let you install, configure and manage clusters from your desktop.
An alternate vision for a full cluster lifecycle configuration shell and web based GUI. Handles everything from cluster installation through to resource configuration and status.
Striker is the user interface for the Anvil! (virtual) server platform and the ScanCore autonomous self-defence and alert system.
The Booth cluster ticket manager extends Pacemaker to support geographically distributed clustering. It does this by managing the granting and revoking of 'tickets' which authorizes one of the cluster sites, potentially located in geographically dispersed locations, to run certain resources.
SBD provides a node fencing mechanism through the exchange of messages via shared block storage such as for example a SAN, iSCSI, FCoE. This isolates the fencing mechanism from changes in firmware version or dependencies on specific firmware controllers, and it can be used as a STONITH mechanism in all configurations that have reliable shared storage. It can also be used as a pure watchdog-based fencing mechanism.
Recent versions of all major Linux distributions provide Pacemaker as part of their usual repositories, so you can usually just launch your favorite package manager. One exception is Debian 8 ("jessie"), which had packaging issues not resolved by the release deadline. For more information, see the Debian-HA team.
+ The ClusterLabs wiki has + how-to's, tips, and other information that doesn't make it into the project + manuals. +
+ +-The following Pacemaker documentation was generated from the upstream sources. -
- -- - If you're new to Pacemaker or clustering in general, the best - place to start is the Clusters from Scratch guide. This - document walks you step-by-step through the installation and - configuration of a High Availability cluster with Pacemaker. - It even makes the common configuration mistakes so that it can - demonstrate how to fix them. - -
- -- - On the otherhand, if you're looking for an exhaustive reference of - all Pacemaker's options and features, try Pacemaker - Explained. It's dry, but should have the answers you're - looking for. - -
- -- There is also a project wiki with plenty of - examples and - howto guides which - the wider community is encouraged to update and add to. -
- -| Ordering Explained | -[pdf] | -[print] | -
| Colocation Explained | -[pdf] | -[print] | -
| Configuring Fencing with crmsh | -[html] | -|
| ACL Guide | -[html] | -
| '.str_replace("_", " ", $b)." ($lang) | "; - - echo ''; - foreach (glob("$base/$lang/Pacemaker/$version/epub/$b/*.epub") as $filename) { - echo " [epub]"; - } - foreach (glob("$base/$lang/Pacemaker/$version/pdf/$b/*.pdf") as $filename) { - echo " [pdf]"; - } - foreach (glob("$base/$lang/Pacemaker/$version/html/$b/index.html") as $filename) { - echo " [html]"; - } - foreach (glob("$base/$lang/Pacemaker/$version/html-single/$b/index.html") as $filename) { - echo " [html-single]"; - } - foreach (glob("$base/$lang/Pacemaker/$version/txt/$b/*.txt") as $filename) { - echo " [txt]"; - } - echo " |
| Clusters from Scratch - Pacemaker 1.0 & GFS2 | -[pdf] | -
| Clusters from Scratch - Pacemaker 1.0 & OCFS2 | -[pdf] | -
Q: Where can I get Pacemaker?
A: Pacemaker ships as part of most modern distributions, so you can usually just launch your favorite package manager on:
If all else fails, you can try installing from source.
Q: Is there any documentation?
A: Yes. You can find the set relevant to your version in our documentation index.
Q: Where should I ask questions?
A: Often basic questions can be answered on irc, but sending them to the mailing list is always a good idea so that everyone can benefit from the answer.
Q: Do I need shared storage?
A: No. We can help manage it if you have some, but Pacemaker itself has no need for shared storage.
Q: Which cluster filesystems does Pacemaker support?
A: Pacemaker supports the popular OCFS2 and GFS2 filesystems. As you'd expect, you can use them on top of real disks or network block devices like DRBD.
Q: What kind of applications can I manage with Pacemaker?
A: Pacemaker is application agnostic, meaning anything that can be scripted can be made highly available - provided the script conforms to one of the supported standards: - LSB, - OCF, - Systemd, - or Upstart. + LSB, + OCF, + Systemd, + or Upstart.
Q: Can I use Pacemaker with Heartbeat?
A: Yes. Pacemaker started off life as part of the Heartbeat project and continues to support it as an alternative to Corosync. See this documentation for more details
Q: Can I use Pacemaker with CMAN?
A: Yes. Pacemaker added support for CMAN v3 in version 1.1.5 to better integrate with distros that have traditionally shipped and/or supported the RHCS cluster stack instead of Pacemaker. This is particularly relevant for those looking to use GFS2 or OCFS2. See - the documentation + the documentation for more details
Q: Can I use Pacemaker with Corosync 1.x?
A: Yes. You will need to configure Corosync to load Pacemaker's custom plugin to provide the membership and quorum information we require. See - the documentation for more details.
+ the documentation for more details.Q: Can I use Pacemaker with Corosync 2.x?
A: Yes. Pacemaker can obtain the membership and quorum information it requires directly from Corosync in this configuration. See - the documentation for more details.
+ the documentation for more details.Q: Do I need a fencing device?
A: Yes. Fencing is the only 100% reliable way to ensure the integrity of your data and that applications are only active on one host. Although Pacemaker is technically able to function without Fencing, there are a good reasons SUSE and Red Hat will not support such a configuration.
Q: Do I need to know XML to configure Pacemaker?
A: No. Although Pacemaker uses XML as its native configuration format, there exist 2 CLIs and at least 4 GUIs that present the configuration in a human friendly format.
Q: How do I synchronize the cluster configuration?
A: Any changes to Pacemaker's configuration are automatically replicated to other machines. The configuration is also versioned, so any offline machines will be updated when they return.
Q: Should I choose pcs or crmsh?
A: Arguably the best advice is to use whichever one comes with your distro. This is the one that will be tailored to that environment, receive regular bugfixes and feature in the documentation.
Of course, for years people have been side-loading all of Pacemaker onto enterprise distros that didn't ship it, so doing the same for just a configuration tool should be easy if your favorite distro does not ship your favorite tool.
Q: What if my question isn't here?
A: See the getting help section and let us know!
You can stay up to date with the Pacemaker project by subscribing to our news and/or site updates feeds.
A good first step is always to check out the FAQ - and documentation. Otherwise, many + and documentation. Otherwise, many members of the community hang out on irc and are happy to answer questions. We are spread out over many timezones though (and have day jobs), so you may need to be patient when waiting for a reply.
Extended or complex issues might be better sent to the relevant mailing list(s) (you'll need to subscribe in order to send messages). Don't worry if you pick the wrong one, many of us are on multiple lists and someone will suggest a more appropriate forum if necessary.
People new to the project, or Open Source generally, are encouraged to read Getting Answers by Mike Ash from Rogue Amoeba. It provides some very good tips on effective communication with groups such as this one. Following the advice it contains will greatly increase the chance of a quick and helpful reply.
Bugs and other problems can also be reported via Bugzilla.
Or if you already know the solution, submit a patch against our GitHub repository.
The development of most of the ClusterLabs-related projects take place as part of the ClusterLabs organization at Github, and the source code and issue trackers for these projects can be found there.
If you find this project useful, you may want to consider supporting its future development. There are a number of ways to support the project (in no particular order):
Thank you for using Pacemaker
Does your company provide Pacemaker training or support? Let us know!
+ Most of the documentation listed here was generated from the Pacemaker + sources. +
+ ++ If you're new to Pacemaker or clustering in general, the best place to + start is Clusters from Scratch, which walks you step-by-step through + the installation and configuration of a high-availability cluster with + Pacemaker. It even makes common configuration mistakes so that it can + demonstrate how to fix them. +
+ ++ On the other hand, if you're looking for an exhaustive reference of all + of Pacemaker's options and features, try Pacemaker Explained. It's + dry, but should have the answers you're looking for. +
+ ++ There is also a project wiki + with examples, how-to guides, and other information that doesn't make it + into the manuals. +
+ +| Ordering Explained | +[pdf] | +[print] | +
| Colocation Explained | +[pdf] | +[print] | +
| Configuring Fencing with crmsh | +[html] | +|
| ACL Guide | +[html] | +
| '.str_replace("_", " ", $b)." ($lang) | "; + + echo ''; + foreach (glob("$base/$lang/Pacemaker/$version/epub/$b/*.epub") as $filename) { + echo " [epub]"; + } + foreach (glob("$base/$lang/Pacemaker/$version/pdf/$b/*.pdf") as $filename) { + echo " [pdf]"; + } + foreach (glob("$base/$lang/Pacemaker/$version/html/$b/index.html") as $filename) { + echo " [html]"; + } + foreach (glob("$base/$lang/Pacemaker/$version/html-single/$b/index.html") as $filename) { + echo " [html-single]"; + } + foreach (glob("$base/$lang/Pacemaker/$version/txt/$b/*.txt") as $filename) { + echo " [txt]"; + } + echo " |
| Clusters from Scratch - Pacemaker 1.0 & GFS2 | +[pdf] | +
| Clusters from Scratch - Pacemaker 1.0 & OCFS2 | +[pdf] | +
"The definitive open-source high-availability stack for the Linux platform builds upon the Pacemaker cluster resource manager." -- LINUX Journal, "Ahead of the Pack: the Pacemaker High-Availability Stack"
Pacemaker has been around since 2004 and is primarily a collaborative effort between Red Hat and SuSE. However, we also receive considerable help and support from the folks at LinBit and the community in general.
The core Pacemaker team is made up of full-time developers from Australia, the Czech Republic, the USA, and Germany. Contributions to the code or documentation are always welcome.
Pacemaker ships with most modern Linux distributions and has been deployed in many critical environments including Deutsche Flugsicherung GmbH (DFS) which uses Pacemaker to ensure its air traffic control systems are always available.
Currently Andrew Beekhof is the project lead for Pacemaker.
Pacemaker ships as part of the Red Hat High Availability Add-on. The easiest way to try it out on RHEL is to install it from the Scientific Linux or CentOS repositories.
If you are already running CentOS or Scientific Linux, you can skip this step. Otherwise, to teach the machine where to find the CentOS packages, run:
[ALL] # cat <
Next we use yum to install pacemaker and some other necessary packages we will need:
[ALL] # yum install pacemaker cman pcs ccs resource-agents
The supported stack on RHEL6 is based on CMAN, so thats what Pacemaker uses too.
We now create a CMAN cluster and populate it with some nodes. Note that the name cannot exceed 15 characters (we'll use 'pacemaker1').
[ONE] # ccs -f /etc/cluster/cluster.conf --createcluster pacemaker1 [ONE] # ccs -f /etc/cluster/cluster.conf --addnode node1 [ONE] # ccs -f /etc/cluster/cluster.conf --addnode node2
Next we need to teach CMAN how to send it's fencing requests to Pacemaker. We do this regardless of whether or not fencing is enabled within Pacemaker.
[ONE] # ccs -f /etc/cluster/cluster.conf --addfencedev pcmk agent=fence_pcmk [ONE] # ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect node1 [ONE] # ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect node2 [ONE] # ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk node1 pcmk-redirect port=node1 [ONE] # ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk node2 pcmk-redirect port=node2
Now copy /etc/cluster/cluster.conf to all the other nodes that will be part of the cluster.
CMAN was originally written for rgmanager and assumes the cluster should not start until the node has quorum, so before we try to start the cluster, we need to disable this behavior:
[ALL] # echo "CMAN_QUORUM_TIMEOUT=0" >> /etc/sysconfig/cman
Now, on each machine, run:
[ALL] # service cman start [ALL] # service pacemaker start
The original cluster shell (crmsh) is no longer available on RHEL. To help people make the transition there is a quick reference guide for those wanting to know what the pcs equivalent is for various crmsh commands.
With so many devices and possible topologies, it is nearly impossible to include Fencing in a document like this. For now we will disable it.
[ONE] # pcs property set stonith-enabled=false
One of the most common ways to deploy Pacemaker is in a 2-node configuration. However quorum as a concept makes no sense in this scenario (because you only have it when more than half the nodes are available), so we'll disable it too.
[ONE] # pcs property set no-quorum-policy=ignore
For demonstration purposes, we will force the cluster to move services after a single failure:
[ONE] # pcs resource defaults migration-threshold=1
Lets add a cluster service, we'll choose one doesn't require any configuration and works everywhere to make things easy. Here's the command:
[ONE] # pcs resource create my_first_svc Dummy op monitor interval=120s
"my_first_svc" is the name the service will be known as.
"ocf:pacemaker:Dummy" tells Pacemaker which script to use (Dummy - an agent that's useful as a template and for guides like this one), which namespace it is in (pacemaker) and what standard it conforms to - (OCF). + (OCF).
"op monitor interval=120s" tells Pacemaker to check the health of this service every 2 minutes by calling the agent's monitor action.
You should now be able to see the service running using:
[ONE] # pcs status
or
[ONE] # crm_mon -1
We can simulate an error by telling the service to stop directly (without telling the cluster):
[ONE] # crm_resource --resource my_first_svc --force-stop
If you now run crm_mon in interactive mode (the default), you should see (within the monitor interval - 2 minutes) the cluster notice that my_first_svc failed and move it to another node.
Pacemaker ships as part of the Red Hat High Availability Add-on. The easiest way to try it out on RHEL is to install it from the Scientific Linux or CentOS repositories.
If you are already running CentOS or Scientific Linux, you can skip this step. Otherwise, to teach the machine where to find the CentOS packages, run:
[ALL] # cat <
Next we use yum to install pacemaker and some other necessary packages we will need:
[ALL] # yum install pacemaker pcs resource-agents
The supported stack on RHEL7 is based on Corosync 2, so thats what Pacemaker uses too.
First we set up the authentication needed for pcs.
[ALL] # echo CHANGEME | passwd --stdin hacluster [ONE] # pcs cluster auth node1 node2 -u hacluster -p CHANGEME --force
We now create a cluster and populate it with some nodes. Note that the name cannot exceed 15 characters (we'll use 'pacemaker1').
[ONE] # pcs cluster setup --force --name pacemaker1 node1 node2
[ONE] # pcs cluster start --all
With so many devices and possible topologies, it is nearly impossible to include Fencing in a document like this. For now we will disable it.
[ONE] # pcs property set stonith-enabled=false
One of the most common ways to deploy Pacemaker is in a 2-node configuration. However quorum as a concept makes no sense in this scenario (because you only have it when more than half the nodes are available), so we'll disable it too.
[ONE] # pcs property set no-quorum-policy=ignore
For demonstration purposes, we will force the cluster to move services after a single failure:
[ONE] # pcs resource defaults migration-threshold=1
Lets add a cluster service, we'll choose one doesn't require any configuration and works everywhere to make things easy. Here's the command:
[ONE] # pcs resource create my_first_svc Dummy op monitor interval=120s
"my_first_svc" is the name the service will be known as.
"ocf:pacemaker:Dummy" tells Pacemaker which script to use (Dummy - an agent that's useful as a template and for guides like this one), which namespace it is in (pacemaker) and what standard it conforms to - (OCF). + (OCF).
"op monitor interval=120s" tells Pacemaker to check the health of this service every 2 minutes by calling the agent's monitor action.
You should now be able to see the service running using:
[ONE] # pcs status
or
[ONE] # crm_mon -1
We can simulate an error by telling the service to stop directly (without telling the cluster):
[ONE] # crm_resource --resource my_first_svc --force-stop
If you now run crm_mon in interactive mode (the default), you should see (within the monitor interval of 2 minutes) the cluster notice that my_first_svc failed and move it to another node.
Pacemaker ships as part of the SUSE High Availability Extension. To install, follow the provided documentation. It is also available in openSUSE Leap and openSUSE Tumbleweed (for openSUSE, see the SLES 12 Quickstart guide.
The supported stack on SLES11 is based on Corosync/OpenAIS.
To get started, install the cluster stack on all nodes.
[ALL] # zypper install ha-cluster-bootstrap
First we initialize the cluster on the first machine (node1):
[ONE] # ha-cluster-init
Now we can join the cluster from the second machine (node2):
[ONE] # ha-cluster-join -c node1
These two steps create and start a basic cluster together with the HAWK web interface. If given additional arguments, ha-cluster-init can also configure STONITH and OCFS2 as part of initial configuration.
For more details on ha-cluster-init, see the output of ha-cluster-init --help.
For demonstration purposes, we will force the cluster to move services after a single failure:
[ONE] # crm configure property migration-threshold=1
Lets add a cluster service, we'll choose one doesn't require any configuration and works everywhere to make things easy. Here's the command:
[ONE] # crm configure primitive my_first_svc ocf:pacemaker:Dummy op monitor interval=120s
"my_first_svc" is the name the service will be known as.
"ocf:pacemaker:Dummy" tells Pacemaker which script to use (Dummy - an agent that's useful as a template and for guides like this one), which namespace it is in (pacemaker) and what standard it conforms to - (OCF). + (OCF).
"op monitor interval=120s" tells Pacemaker to check the health of this service every 2 minutes by calling the agent's monitor action.
You should now be able to see the service running using:
[ONE] # crm status
We can simulate an error by telling the service stop directly (without telling the cluster):
[ONE] # crm_resource --resource my_first_svc --force-stop
If you now run crm_mon in interactive mode (the default), you should see (within the monitor interval - 2 minutes) the cluster notice that my_first_svc failed and move it to another node.
You can also watch the transition from the HAWK dashboard, by going to https://node1:7630.
Pacemaker ships as part of the SUSE High Availability Extension. To install, follow the provided documentation. It is also available in openSUSE Leap and openSUSE Tumbleweed.
The supported stack on SLES12 is based on Corosync 2.x.
To get started, install the cluster stack on all nodes.
[ALL] # zypper install ha-cluster-bootstrap
First we initialize the cluster on the first machine (node1):
[ONE] # ha-cluster-init
Now we can join the cluster from the second machine (node2):
[ONE] # ha-cluster-join -c node1
These two steps create and start a basic cluster together with the HAWK web interface. If given additional arguments, ha-cluster-init can also configure STONITH, OCFS2 and an administration IP address as part of initial configuration. It is also possible to choose whether to use multicast or unicast for corosync communication.
For more details on ha-cluster-init, see the output of ha-cluster-init --help.
For demonstration purposes, we will force the cluster to move services after a single failure:
[ONE] # crm configure property migration-threshold=1
Lets add a cluster service, we'll choose one doesn't require any configuration and works everywhere to make things easy. Here's the command:
[ONE] # crm configure primitive my_first_svc Dummy op monitor interval=120s
"my_first_svc" is the name the service will be known as.
"Dummy" tells Pacemaker which script to use (Dummy - an agent that's useful as a template and for guides like this one), which namespace it is in (pacemaker) and what standard it conforms to - (OCF). + (OCF).
"op monitor interval=120s" tells Pacemaker to check the health of this service every 2 minutes by calling the agent's monitor action.
You should now be able to see the service running using:
[ONE] # crm status
We can simulate an error by telling the service stop directly (without telling the cluster):
[ONE] # crm_resource --resource my_first_svc --force-stop
If you now run crm_mon in interactive mode (the default), you should see (within the monitor interval - 2 minutes) the cluster notice that my_first_svc failed and move it to another node.
You can also watch the transition from the HAWK dashboard, by going to https://node1:7630.
Ubuntu appears to have switched to Corosync 2 for it's LTS releases.
We use aptitude to install pacemaker and some other necessary packages we will need:
[ALL] # aptitude install pacemaker corosync fence-agents
Since the pcs tool from RHEL does not exist on Ubuntu, we well create the corosync configuration file on both machines manually:
[ALL] # cat <
On each machine, run:
[ALL] # service pacemaker start
With so many devices and possible topologies, it is nearly impossible to include Fencing in a document like this. For now we will disable it.
[ONE] # crm configure property stonith-enabled=false
One of the most common ways to deploy Pacemaker is in a 2-node configuration. However quorum as a concept makes no sense in this scenario (because you only have it when more than half the nodes are available), so we'll disable it too.
[ONE] # crm configure property no-quorum-policy=ignore
For demonstration purposes, we will force the cluster to move services after a single failure:
[ONE] # crm configure property migration-threshold=1
Lets add a cluster service, we'll choose one doesn't require any configuration and works everywhere to make things easy. Here's the command:
[ONE] # crm configure primitive my_first_svc ocf:pacemaker:Dummy op monitor interval=120s
"my_first_svc" is the name the service will be known as.
"ocf:pacemaker:Dummy" tells Pacemaker which script to use (Dummy - an agent that's useful as a template and for guides like this one), which namespace it is in (pacemaker) and what standard it conforms to - (OCF). + (OCF).
"op monitor interval=120s" tells Pacemaker to check the health of this service every 2 minutes by calling the agent's monitor action.
You should now be able to see the service running using:
[ONE] # crm_mon -1
We can simulate an error by telling the service stop directly (without telling the cluster):
[ONE] # crm_resource --resource my_first_svc --force-stop
If you now run crm_mon in interactive mode (the default), you should see (within the monitor interval - 2 minutes) the cluster notice that my_first_svc failed and move it to another node.
