Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ocf_pacemaker_dummy(7) [centos man page]

OCF_PACEMAKER_DUMMY(7)					      Pacemaker Configuration					    OCF_PACEMAKER_DUMMY(7)

NAME
ocf_pacemaker_Dummy - Example stateless resource agent SYNOPSIS
OCF_RESKEY_state=string [OCF_RESKEY_fake=string] OCF_RESKEY_op_sleep=string Dummy [start | stop | monitor | reload | migrate_to | migrate_from | validate-all | meta-data] DESCRIPTION
This is a Dummy Resource Agent. It does absolutely nothing except keep track of whether its running or not. Its purpose in life is for testing and to serve as a template for RA writers. NB: Please pay attention to the timeouts specified in the actions section below. They should be meaningful for the kind of resource the agent manages. They should be the minimum advised timeouts, but they shouldn't/cannot cover _all_ possible resource instances. So, try to be neither overly generous nor too stingy, but moderate. The minimum timeouts should never be below 10 seconds. SUPPORTED PARAMETERS
OCF_RESKEY_state = string [/Dummy-{OCF_RESOURCE_INSTANCE}.state] State file Location to store the resource state in. OCF_RESKEY_fake = string [dummy] Fake attribute that can be changed to cause a reload Fake attribute that can be changed to cause a reload OCF_RESKEY_op_sleep = string [0] Operation sleep duration in seconds. Number of seconds to sleep during operations. This can be used to test how the cluster reacts to operation timeouts. AUTHOR
Andrew Beekhof <andrew@beekhof.net> Author. Pacemaker Configuration 06/10/2014 OCF_PACEMAKER_DUMMY(7)

Check Out this Related Man Page

OCF_HEARTBEAT_DUMMY(7)						OCF resource agents					    OCF_HEARTBEAT_DUMMY(7)

NAME
ocf_heartbeat_Dummy - Example stateless resource agent SYNOPSIS
Dummy [start | stop | monitor | migrate_to | migrate_from | meta-data | validate-all] DESCRIPTION
This is a Dummy Resource Agent. It does absolutely nothing except keep track of whether its running or not. Its purpose in life is for testing and to serve as a template for RA writers. NB: Please pay attention to the timeouts specified in the actions section below. They should be meaningful for the kind of resource the agent manages. They should be the minimum advised timeouts, but they shouldn't/cannot cover _all_ possible resource instances. So, try to be neither overly generous nor too stingy, but moderate. The minimum timeouts should never be below 10 seconds. This resource agent may be configured for native migration if available in the cluster manager. For Pacemaker, the allow-migrate="true" meta attribute enables native migration. SUPPORTED PARAMETERS
state Location to store the resource state in. (unique, optional, string, default "/var/run/resource-agents/Dummy-default.state") fake Fake attribute that can be changed to cause a reload (optional, string, default "dummy") SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 20. stop Stops the resource. Suggested minimum timeout: 20. monitor Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10. reload Suggested minimum timeout: 20. migrate_to Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 20. migrate_from Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 20. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 20. EXAMPLE
The following is an example configuration for a Dummy resource using the crm(8) shell: primitive p_Dummy ocf:heartbeat:Dummy meta allow-migrate="true" op monitor timeout="20" interval="10" depth="0" SEE ALSO
http://www.linux-ha.org/wiki/Dummy_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_DUMMY(7)
Man Page

Featured Tech Videos