Defining the Control Center resource group
The resources in a resource group are started in the order they appear in the group, and stopped in the reverse order they appear in the group. The start order is:
- Mount the filesystems (serviced-isvcs and serviced-volumes)
- Start the serviced logical volume.
- Manage serviced storage.
- Enable the virtual IP address of the cluster.
- Start Docker.
- Start NFS.
- Start Control Center.
In the event of a failover, Pacemaker stops the resources on the failed node in the reverse order they are defined before starting the resource group on the standby node.
- Log in to the primary node as root, or as a user with superuser privileges.
Create the Control Center resource group.
pcs resource group add serviced-group \ serviced-isvcs serviced-volumes \ serviced-lvm serviced-storage \ VirtualIP docker nfs \ serviced
Define constraints for the Control Center resource group.
Pacemaker resource constraints control when and where resources are deployed in a cluster.
Ensure that serviced-group runs on the same node as
pcs constraint colocation add serviced-group with DFSMaster \ INFINITY with-rsc-role=Master
Ensure that serviced-group is only started after
DFSMaster is started.
pcs constraint order promote DFSMaster then \ start serviced-group
- Ensure that serviced-group runs on the same node as DFSMaster.