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:

  1. Mount the filesystems (serviced-isvcs and serviced-volumes)
  2. Start the serviced logical volume.
  3. Manage serviced storage.
  4. Enable the virtual IP address of the cluster.
  5. Start Docker.
  6. Start NFS.
  7. 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.

  1. Log in to the primary node as root, or as a user with superuser privileges.
  2. Create the Control Center resource group.
    pcs resource group add serviced-group \
      serviced-isvcs serviced-volumes \
      serviced-lvm serviced-storage \
      VirtualIP docker nfs \
  3. Define constraints for the Control Center resource group.
    Pacemaker resource constraints control when and where resources are deployed in a cluster.
    1. Ensure that serviced-group runs on the same node as DFSMaster.
      pcs constraint colocation add serviced-group with DFSMaster \
        INFINITY with-rsc-role=Master
    2. Ensure that serviced-group is only started after DFSMaster is started.
      pcs constraint order promote DFSMaster then \
        start serviced-group