ocf_heartbeat_LVM-activate man page

ocf_heartbeat_LVM-activate ā€” This agent activates/deactivates logical volumes.

Synopsis

LVM-activate [start | stop | monitor | meta-data | validate-all]

Description

This agent manages LVM activation/deactivation work for a given volume group.

It supports the following modes, controlled by the vg_access_mode parameter:

* lvmlockd * system_id * clvmd * tagging

Notes:

1. There are two possible configuration combinations: lvmlockd+LVM-activate and clvm+LVM-activate. However, it is not possible to use both at the same time!

2. Put all "lvmlockd"/"clvmd" volume groups into auto management by the agent if using the cluster to manage at least one of them. If you manage some manually, the stop action of the lvmlockd agent may fail and the node may get fenced, because some DLM lockspaces might be in use and cannot be closed automatically.

Supported Parameters

vgname

The volume group name.

(unique, required, string, no default)

lvname

If set, only the specified LV will be activated.

(optional, string, no default)

vg_access_mode

This option decides which solution will be used to protect the volume group in cluster environment. Optional solutions are: lvmlockd, clvmd, system_id and tagging.

(required, string, no default)

activation_mode

The activation mode decides the visibility of logical volumes in the cluster. There are two different modes: "shared" for cluster filesystem and "exclusive" for local filesystem. With "shared", an LV can be activated concurrently from multiple nodes. With "exclusive", an LV can be activated by one node at a time.

This option only has effect on "lvmlockd"/"clvmd" vg_access_mode. For "system_id" and "tagging", they always mean exclusive activation.

(optional, string, default "exclusive")

tag

The tag used for tagging activation mode.

(optional, string, default "pacemaker")

Supported Actions

This resource agent supports the following actions (operations):

start

Starts the resource. Suggested minimum timeout: 90s.

stop

Stops the resource. Suggested minimum timeout: 90s.

monitor

Performs a detailed status check. Suggested minimum timeout: 90s. Suggested interval: 30s.

meta-data

Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 10s.

validate-all

Performs a validation of the resource configuration. Suggested minimum timeout: 20s.

Example CRM Shell

The following is an example configuration for a LVM-activate resource using the crm(8) shell:

primitive p_LVM-activate ocf:heartbeat:LVM-activate \
  params \
    vgname=string \
    vg_access_mode=string \
  op monitor timeout="90s" interval="30s" depth="0" 

Example PCS

The following is an example configuration for a LVM-activate resource using pcs(8)

pcs resource create p_LVM-activate ocf:heartbeat:LVM-activate \
  vgname=string \
  vg_access_mode=string \
  op monitor timeout="90s" interval="30s" depth="0" 

See Also

http://clusterlabs.org/

Author

ClusterLabs contributors (see the resource agent source for information about individual authors)

Info

04/10/2018 resource-agents UNKNOWN OCF resource agents