5.3. Resource Properties

These values tell the cluster which resource agent to use for the resource, where to find that resource agent and what standards it conforms to.

Table 5.1. Properties of a Primitive Resource

Field	Description
`id`	Your name for the resource
`class`	The standard the resource agent conforms to. Allowed values: `lsb`, `nagios`, `ocf`, `service`, `stonith`, `systemd`, `upstart`
`type`	The name of the Resource Agent you wish to use. E.g. `IPaddr` or `Filesystem`
`provider`	The OCF spec allows multiple vendors to supply the same resource agent. To use the OCF resource agents supplied by the Heartbeat project, you would specify `heartbeat` here.

The XML definition of a resource can be queried with the crm_resource tool. For example:

# crm_resource --resource Email --query-xml

might produce:

Example 5.1. A system resource definition

<primitive id="Email" class="service" type="exim"/>

Note

One of the main drawbacks to system services (LSB, systemd or Upstart) resources is that they do not allow any parameters!

Example 5.2. An OCF resource definition

<primitive id="Public-IP" class="ocf" type="IPaddr" provider="heartbeat">
   <instance_attributes id="Public-IP-params">
      <nvpair id="Public-IP-ip" name="ip" value="192.0.2.2"/>
   </instance_attributes>
</primitive>