Verifying the Pacemaker configuration

This procedure reviews the resource and property defaults for Pacemaker.

  1. Log in to the primary node as root, or as a user with superuser privileges.
  2. Check resource defaults.
    pcs resource defaults
    Example result:
    resource-stickiness: 100
  3. Check property defaults.
    pcs property
    Example result:
    Cluster Properties:
     cluster-infrastructure: corosync
     cluster-name: serviced-ha
     dc-version: 1.1.12-a14efad
     have-watchdog: false
     no-quorum-policy: ignore
     stonith-enabled: false
  4. Review the resource constraints.
    The ordering constraint should show that serviced-group starts after DFSMaster (the DRBD master). The colocation constraint should show that serviced-group resource and DFSMaster are on the same active cluster node.
    pcs constraint
    Example result:
    Location Constraints:
    Ordering Constraints:
      promote DFSMaster then start serviced-group (kind:Mandatory)
    Colocation Constraints:
      serviced-group with DFSMaster (score:INFINITY) (with-rsc-role:Master)
  5. Review the ordering of the serviced-group resource group.
    pcs resource show --full

    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 correct start order is:

    1. serviced-isvcs
    2. serviced-volumes
    3. serviced-lvm
    4. serviced-storage
    5. VirtualIP
    6. Docker
    7. nfs
    8. serviced