Chapter 3. Configuration Explained

Table of Contents

3.1. Resource Meta-Attributes for Guest Nodes
3.2. Connection Resources for Remote Nodes
3.3. Environment Variables for Daemon Start-up
3.4. Removing Remote Nodes and Guest Nodes

The walk-through examples use some of these options, but don’t explain exactly what they mean or do. This section is meant to be the go-to resource for all the options available for configuring pacemaker_remote-based nodes.

3.1. Resource Meta-Attributes for Guest Nodes

When configuring a virtual machine as a guest node, the virtual machine is created using one of the usual resource agents for that purpose (for example, ocf:heartbeat:VirtualDomain or ocf:heartbeat:Xen), with additional metadata parameters.

No restrictions are enforced on what agents may be used to create a guest node, but obviously the agent must create a distinct environment capable of running the pacemaker_remote daemon and cluster resources. An additional requirement is that fencing the host running the guest node resource must be sufficient for ensuring the guest node is stopped. This means, for example, that not all hypervisors supported by VirtualDomain may be used to create guest nodes; if the guest can survive the hypervisor being fenced, it may not be used as a guest node.

Below are the metadata options available to enable a resource as a guest node and define its connection parameters.

Table 3.1. Meta-attributes for configuring VM resources as guest nodes

Option	Default	Description
`remote-node`	none	The node name of the guest node this resource defines. This both enables the resource as a guest node and defines the unique name used to identify the guest node. If no other parameters are set, this value will also be assumed as the hostname to use when connecting to pacemaker_remote on the VM. This value must not overlap with any resource or node IDs.
`remote-port`	3121	The port on the virtual machine that the cluster will use to connect to pacemaker_remote.
`remote-addr`	value of `remote-node`	The IP address or hostname to use when connecting to pacemaker_remote on the VM.
`remote-connect-timeout`	60s	How long before a pending guest connection will time out.