/ 14.4. Resource Operations
	14.3. Resource Options		14.5. Instance Attributes

Resource Operations

By default, the cluster will not ensure that your resources are still healthy. To instruct the cluster to do this, you need to add a monitor operation to the resource’s deﬁnition. Monitor operations can be added for all classes or resource agents.

Table 14.4. Resource Operations

Operation	Description
`id`	Your name for the action. Must be unique.
`name`	The action to perform. Common values: `monitor`, `start`, `stop`.
`interval`	How frequently to perform the operation. Unit: seconds .
`timeout`	How long to wait before declaring the action has failed.
`requires`	What conditions need to be satisﬁed before this action occurs. Allowed values: `nothing`, `quorum`, `fencing`. The default depends on whether fencing is enabled and if the resource’s class is `stonith`. For STONITH resources, the default is `nothing`.
`on-fail`	The action to take if this action ever fails. Allowed values: `ignore`: Pretend the resource did not fail. `block`: Do not perform any further operations on the resource. `stop`: Stop the resource and do not start it elsewhere. `restart`: Stop the resource and start it again (possibly on a different node). `fence`: Bring down the node on which the resource failed (STONITH). `standby`: Move all resources away from the node on which the resource failed.
`enabled`	If `false`, the operation is treated as if it does not exist. Allowed values: `true`, `false`.