ClusterLabs/pacemaker — pull request #348 by davidvossel (2013-08-30 22:00:12+00:00)
Title: Initial baremetal remote-node support

Integrating a remote node is a simple as issuing the following pcs command.

'pcs resource create mynode remote'

As long as 'mynode' is a reachable hostname that has a machine running pacemaker_remoted on it, that command should be all that is required. Once integrated into the cluster, resources can be placed on the remote-node as if it was a normal cluster node. The only difference between a cluster node and a baremetal remote-node is that the remote-nodes do not take place in quorum and can not run fencing devices.

Baremetal remote-node fencing works the nearly the same way regular cluster node fencing works. The only difference is that a remote-node will never be responsible for fencing a node, only cluster nodes are capable of actually initiating a fencing request. Other than that, if a fencing device is capable of fencing a remote-node, it will work as long as the cluster-nodes maintain quorum.