Product SiteDocumentation Site

5.4. Integrate Remote Node into Cluster

Integrating a remote node into the cluster is achieved through the creation of a remote node connection resource. The remote node connection resource both establishes the connection to the remote node and defines that the remote node exists. Note that this resource is actually internal to Pacemaker’s controller. A metadata file for this resource can be found in the /usr/lib/ocf/resource.d/pacemaker/remote file that describes what options are available, but there is no actual ocf:pacemaker:remote resource agent script that performs any work.
Define the remote node connection resource to our remote node, remote1, using the following command on any cluster node.
# pcs resource create remote1 ocf:pacemaker:remote
That’s it. After a moment you should see the remote node come online.
Cluster name: mycluster
Stack: corosync
Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum
Last updated: Fri Jan 12 17:13:09 2018
Last change: Fri Jan 12 17:02:02 2018

3 nodes configured
1 resources configured

Online: [ node1 node2 ]
RemoteOnline: [ remote1 ]

Full list of resources:

 remote1 (ocf::pacemaker:remote):       Started node1

Daemon Status:
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/enabled