Promotable clone resources
Promotable clone resources have the promotable meta attribute set to true and operate in two modes: promoted and unpromoted. When an instance starts, it must initialize in the Unpromoted state.
The Promoted and Unpromoted role names are the functional equivalent of the Master and Slave Pacemaker roles in previous RHEL releases.
Create a promotable clone resource Copy linkLink copied!
Configure a promotable clone resource to manage services that run in different modes, such as active and passive. You can create a new promotable resource or convert an existing resource or group to support promoted and unpromoted roles.
Procedure Copy linkLink copied!
Promotable resource constraints Copy linkLink copied!
You can determine the behavior of a promotable resource in a cluster by configuring constraints for that resource. For general information about resource constraints, see Configuring cluster resources.
Promotable resource location constraints
In most cases, a promotable resource will have a single copy on each active cluster node. If this is not the case, you can indicate which nodes the cluster should preferentially assign copies to with resource location constraints. These constraints are written no differently than those for regular resources. For information about location constraints, see Determining which node a resource can run on.
Promotable resource colocation constraints
You can create a colocation constraint which specifies whether the resources are operating in a promoted or unpromoted role. The following command creates a resource colocation constraint:
# pcs constraint colocation add [promoted|unpromoted] source_resource with [promoted|unpromoted] target_resource [score] [options]
For information about colocation constraints, see Colocating cluster resources.
Promotable resource ordering constraints
When configuring an ordering constraint that includes promotable resources, one of the actions that you can specify for the resources is promote, indicating that the resource be promoted from unpromoted role to promoted role. Additionally, you can specify an action of demote, indicated that the resource be demoted from promoted role to unpromoted role.
The command for configuring an order constraint is as follows:
# pcs constraint order [action] resource_id then [action] resource_id [options]
Demote a promoted resource on failure Copy linkLink copied!
Configure a promotable resource so that when a promote or monitor action fails, or the partition loses quorum, the resource is demoted rather than fully stopped. This prevents manual intervention in scenarios where fully stopping the resource requires manual action.