ocf_heartbeat_LVM-activate(7)

1OCF_HEARTBEAT_LVM-A(7)        OCF resource agents       OCF_HEARTBEAT_LVM-A(7)
2
3
4

NAME

6       ocf_heartbeat_LVM-activate - This agent activates/deactivates logical
7       volumes.
8

SYNOPSIS

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

DESCRIPTION

13       This agent manages LVM activation/deactivation work for a given volume
14       group.
15
16       It supports the following modes, controlled by the vg_access_mode
17       parameter:
18
19       * lvmlockd * system_id * clvmd * tagging
20
21       Notes:
22
23       1. There are two possible configuration combinations:
24       lvmlockd+LVM-activate and clvm+LVM-activate. However, it is not
25       possible to use both at the same time!
26
27       2. Put all "lvmlockd"/"clvmd" volume groups into auto management by the
28       agent if using the cluster to manage at least one of them. If you
29       manage some manually, the stop action of the lvmlockd agent may fail
30       and the node may get fenced, because some DLM lockspaces might be in
31       use and cannot be closed automatically.
32

SUPPORTED PARAMETERS

34       vgname
35           The volume group name.
36
37           (unique, required, string, no default)
38
39       lvname
40           If set, only the specified LV will be activated.
41
42           (optional, string, no default)
43
44       vg_access_mode
45           This option decides which solution will be used to protect the
46           volume group in cluster environment. Optional solutions are:
47           lvmlockd, clvmd, system_id and tagging.
48
49           (required, string, no default)
50
51       activation_mode
52           The activation mode decides the visibility of logical volumes in
53           the cluster. There are two different modes: "shared" for cluster
54           filesystem and "exclusive" for local filesystem. With "shared", an
55           LV can be activated concurrently from multiple nodes. With
56           "exclusive", an LV can be activated by one node at a time.
57
58           This option only has effect on "lvmlockd"/"clvmd" vg_access_mode.
59           For "system_id" and "tagging", they always mean exclusive
60           activation.
61
62           (optional, string, default "exclusive")
63
64       tag
65           The tag used for tagging activation mode.
66
67           (optional, string, default "pacemaker")
68

SUPPORTED ACTIONS

70       This resource agent supports the following actions (operations):
71
72       start
73           Starts the resource. Suggested minimum timeout: 90s.
74
75       stop
76           Stops the resource. Suggested minimum timeout: 90s.
77
78       monitor
79           Performs a detailed status check. Suggested minimum timeout: 90s.
80           Suggested interval: 30s.
81
82       meta-data
83           Retrieves resource agent metadata (internal use only). Suggested
84           minimum timeout: 10s.
85
86       validate-all
87           Performs a validation of the resource configuration. Suggested
88           minimum timeout: 20s.
89

EXAMPLE CRM SHELL

91       The following is an example configuration for a LVM-activate resource
92       using the crm(8) shell:
93
94           primitive p_LVM-activate ocf:heartbeat:LVM-activate \
95             params \
96               vgname=string \
97               vg_access_mode=string \
98             op monitor timeout="90s" interval="30s" depth="0"
99

EXAMPLE PCS

101       The following is an example configuration for a LVM-activate resource
102       using pcs(8)
103
104           pcs resource create p_LVM-activate ocf:heartbeat:LVM-activate \
105             vgname=string \
106             vg_access_mode=string \
107             op monitor timeout="90s" interval="30s" depth="0"
108

AUTHOR

113       ClusterLabs contributors (see the resource agent source for information
114       about individual authors)
115
116
117
118resource-agents UNKNOWN           03/15/2019            OCF_HEARTBEAT_LVM-A(7)