Product SiteDocumentation Site

10.3.3.8. Notifications

Like with clones, supporting notifications requires the 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.9. Environment variables supplied with Master notify actions [11]
Variable Description
OCF_RESKEY_CRM_meta_notify_type Allowed values: pre, post
OCF_RESKEY_CRM_meta_notify_operation Allowed values: start, stop
OCF_RESKEY_CRM_meta_notify_active_resource Resources the that are running
OCF_RESKEY_CRM_meta_notify_inactive_resource Resources the that are not running
OCF_RESKEY_CRM_meta_notify_master_resource Resources that are running in Master mode
OCF_RESKEY_CRM_meta_notify_slave_resource Resources that are running in Slave mode
OCF_RESKEY_CRM_meta_notify_start_resource Resources to be started
OCF_RESKEY_CRM_meta_notify_stop_resource Resources to be stopped
OCF_RESKEY_CRM_meta_notify_promote_resource Resources to be promoted
OCF_RESKEY_CRM_meta_notify_demote_resource Resources to be demoted
OCF_RESKEY_CRM_meta_notify_start_uname Nodes on which resources will be started
OCF_RESKEY_CRM_meta_notify_stop_uname Nodes on which resources will be stopped
OCF_RESKEY_CRM_meta_notify_promote_uname Nodes on which resources will be promoted
OCF_RESKEY_CRM_meta_notify_demote_uname Nodes on which resources will be demoted
OCF_RESKEY_CRM_meta_notify_active_uname Nodes on which resources are running
OCF_RESKEY_CRM_meta_notify_inactive_uname Nodes on which resources are not running
OCF_RESKEY_CRM_meta_notify_master_uname Nodes on which resources are running in Master mode
OCF_RESKEY_CRM_meta_notify_slave_uname Nodes on which resources are running in Slave mode