10.2.4. Clone Options

⁠10.2.4. Clone Options

Options inherited from primitive resources: priority, target-role, is-managed

Table 10.3. Clone-specific configuration options

Field	Default	Description
`globally-unique`	false	If `true`, each clone instance performs a distinct function
`clone-max`	number of nodes in cluster	The maximum number of clone instances that can be started across the entire cluster
`clone-node-max`	1	If `globally-unique` is `true`, the maximum number of clone instances that can be started on a single node
`clone-min`	0	Require at least this number of clone instances to be runnable before allowing resources depending on the clone to be runnable. A value of 0 means require all clone instances to be runnable.
`notify`	false	Call the resource agent’s `notify` action for all active instances, before and after starting or stopping any clone instance. The resource agent must support this action. Allowed values: `false`, `true`
`ordered`	false	If `true`, clone instances must be started sequentially instead of in parallel Allowed values: `false`, `true`
`interleave`	false	When this clone is ordered relative to another clone, if this option is `false` (the default), the ordering is relative to all instances of the other clone, whereas if this option is `true`, the ordering is relative only to instances on the same node. Allowed values: `false`, `true`
`promotable`	false	If `true`, clone instances can perform a special role that Pacemaker will manage via the resource agent’s `promote` and `demote` actions. The resource agent must support these actions. Allowed values: `false`, `true`
`promoted-max`	1	If `promotable` is `true`, the number of instances that can be promoted at one time across the entire cluster
`promoted-node-max`	1	If `promotable` is `true` and `globally-unique` is `false`, the number of clone instances can be promoted at one time on a single node

For backward compatibility, master-max and master-node-max are accepted as aliases for promoted-max and promoted-node-max, but are deprecated since 2.0.0, and support for them will be removed in a future version.