Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ocf_heartbeat_lvm(7) [centos man page]

OCF_HEARTBEAT_LVM(7)						OCF resource agents					      OCF_HEARTBEAT_LVM(7)

NAME
ocf_heartbeat_LVM - Controls the availability of an LVM Volume Group SYNOPSIS
LVM [start | stop | status | monitor | meta-data | validate-all] DESCRIPTION
Resource script for LVM. It manages an Linux Volume Manager volume (LVM) as an HA resource. SUPPORTED PARAMETERS
volgrpname The name of volume group. (required, string, no default) exclusive If set, the volume group will be activated exclusively. This option works one of two ways. If the volume group has the cluster attribute set, then the volume group will be activated exclusively using clvmd across the cluster. If the cluster attribute is not set, the volume group will be activated exclusively through the use of the volume_list filter in lvm.conf. In the filter scenario, the LVM agent verifies that pacemaker's configuration will result in the volume group only being active on a single node in the cluster and that the local node's volume_list filter will prevent the volume group from activating outside of the resource agent. On activation this agent claims the volume group through the use of a unique tag, and then overrides the volume_list field in a way that allows the volume group to be activated only by the agent. To use exclusive activation without clvmd, the volume_list in lvm.conf must be initialized. If volume groups exist locally that are not controlled by the cluster, such as the root volume group, make sure those volume groups are listed in the volume_list so they will be allowed to activate on bootup. (optional, boolean, default false) tag If "exclusive" is set on a non clustered volume group, this overrides the tag to be used. (optional, string, default "pacemaker") partial_activation If set, the volume group will be activated even only partial of the physical volumes available. It helps to set to true, when you are using mirroring logical volumes. (optional, string, default "false") SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 30. stop Stops the resource. Suggested minimum timeout: 30. status Performs a status check. Suggested minimum timeout: 30. monitor Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10. methods Suggested minimum timeout: 5. 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: 5. EXAMPLE
The following is an example configuration for a LVM resource using the crm(8) shell: primitive p_LVM ocf:heartbeat:LVM params volgrpname=string op monitor depth="0" timeout="30" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/LVM_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_LVM(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 | reload | 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. SUPPORTED PARAMETERS
state Location to store the resource state in. (optional, string, default /var/run/resource-agents/Dummy-{OCF_RESOURCE_INSTANCE}.state) 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 example_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 1.0.3 07/05/2010 OCF_HEARTBEAT_DUMMY(7)
Man Page

Featured Tech Videos