apache:2
.
OCF_RESKEY_CRM_meta_clone_max
environment variable and which copy it is by examining OCF_RESKEY_CRM_meta_clone
.
OCF_RESKEY_CRM_meta_clone
) about which copies are active. In particular, the list of active copies will not always be an unbroken sequence, nor always start at 0.
notify
action to be implemented. Once supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it.
Table 10.4. Environment variables supplied with Clone notify actions
Variable | Description |
---|---|
OCF_RESKEY_CRM_meta_notify_type
| |
OCF_RESKEY_CRM_meta_notify_operation
| |
OCF_RESKEY_CRM_meta_notify_start_resource
| |
OCF_RESKEY_CRM_meta_notify_stop_resource
| |
OCF_RESKEY_CRM_meta_notify_active_resource
| |
OCF_RESKEY_CRM_meta_notify_inactive_resource
| |
OCF_RESKEY_CRM_meta_notify_start_uname
| |
OCF_RESKEY_CRM_meta_notify_stop_uname
| |
OCF_RESKEY_CRM_meta_notify_active_uname
| |
OCF_RESKEY_CRM_meta_notify_inactive_uname
|
OCF_RESKEY_CRM_meta_notify_start_resource
and OCF_RESKEY_CRM_meta_notify_start_uname
and should be treated as an array of whitespace separated elements.
clone:0
will be started on sles-1
, clone:2
will be started on sles-3
, and clone:3
will be started on sles-2
, the cluster would set
Example 10.6. Example notification variables
OCF_RESKEY_CRM_meta_notify_start_resource="clone:0 clone:2 clone:3" OCF_RESKEY_CRM_meta_notify_start_uname="sles-1 sles-3 sles-2"