About Pacemaker Resources and Resource Groups

A Pacemaker resource, at its most basic, is a service managed by Pacemaker. Example of resources include services for the following:

IP address
File system
Website
Database

The resources in the preceding list are known as primitive resources. Primitive resources can be grouped and cloned into more complex resources called groups and clones.

Resource Agents

Each primitive resource is managed by a resource agent script that provides Pacemaker with access to the resource through a standardized interface. Some of the standards compatible with Pacemaker are shown in the following list:

Open Cluster Framework (OCF)
Systemd
System Services
STONITH
Linux Standard Base (LSB)

WARNING:

LSB scripts do not always comply with the standard. See https://clusterlabs.org/ for more information.

To see the resource agents on your system, you can run the pcs resource agents command as shown in the following example (lots of lines have been omitted from the sample output for brevity):

pcs resource agents

.
.
.
apache
.
.
.
IPaddr
IPaddr2
.
.
.
oracle
oralsnr
pacemaker
pacemaker
.
.
.
pcsd
pcsd
.
.
.

To see the interface standards on your system you can run the pcs resource standards command as shown in the following example:

pcs resource standards

lsb
ocf
service
systemd

Resource Properties

Resource properties determine which resource agent manages the resource, where to find that resource agent and which standards it conforms to. The following list describes the properties of a primitive resource:

id

This is the resource name of your choice.

class

The standard the resource agent conforms to.

For example: ocf, stonith, or systemd.

description

Description of the resource agent.

type

The type of the resource agent you need to use.

For example, IPaddr2, Filesystem, or Website.

provider

With OCF agents you can specify the provider to use for a resource (the OCF spec allows multiple vendors to supply the same resource agent).

Example values: heartbeat, pacemaker.