1.2. Cluster Creation
- Execute the following command from
z1.example.comto create the two-node cluster
my_clusterthat consists of nodes
z2.example.com. This will propagate the cluster configuration files to both nodes in the cluster. This command includes the
--startoption, which will start the cluster services on both nodes in the cluster.
pcs cluster setup --start --name my_cluster\
z1.example.com z2.example.comz1.example.com: Succeeded z1.example.com: Starting Cluster... z2.example.com: Succeeded z2.example.com: Starting Cluster...
- Enable the cluster services to run on each node in the cluster when the node is booted.
NoteFor your particular environment, you may choose to leave the cluster services disabled by skipping this step. This allows you to ensure that if a node goes down, any issues with your cluster or your resources are resolved before the node rejoins the cluster. If you leave the cluster services disabled, you will need to manually start the services when you reboot a node by executing the
pcs cluster startcommand on that node.
pcs cluster enable --all
pcs cluster statuscommand. Because there may be a slight delay before the cluster is up and running when you start the cluster services with the
--startoption of the
pcs cluster setupcommand, you should ensure that the cluster is up and running before performing any subsequent actions on the cluster and its configuration.
pcs cluster statusCluster Status: Last updated: Thu Jul 25 13:01:26 2013 Last change: Thu Jul 25 13:04:45 2013 via crmd on z2.example.com Stack: corosync Current DC: z2.example.com (2) - partition with quorum Version: 1.1.10-5.el7-9abe687 2 Nodes configured 0 Resources configured