1 *ha-manager* `<COMMAND> [ARGS] [OPTIONS]`
3 *ha-manager add* `<sid>` `[OPTIONS]`
5 Create a new HA resource.
7 `<sid>`: `<type>:<name>` ::
9 HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
11 `--comment` `<string>` ::
15 `--group` `<string>` ::
17 The HA group identifier.
19 `--max_relocate` `<integer> (0 - N)` ('default =' `1`)::
21 Maximal number of service relocate tries when a service failes to start.
23 `--max_restart` `<integer> (0 - N)` ('default =' `1`)::
25 Maximal number of tries to restart the service on a node after its start failed.
27 `--state` `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::
29 Requested resource state.
31 `--type` `<ct | vm>` ::
35 *ha-manager config* `[OPTIONS]`
39 `--type` `<ct | vm>` ::
41 Only list resources of specific type
43 *ha-manager crm-command migrate* `<sid> <node>`
45 Request resource migration (online) to another node.
47 `<sid>`: `<type>:<name>` ::
49 HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
51 `<node>`: `<string>` ::
55 *ha-manager crm-command node-maintenance disable* `<node>`
57 Change the node-maintenance request state.
59 `<node>`: `<string>` ::
61 The cluster node name.
63 *ha-manager crm-command node-maintenance enable* `<node>`
65 Change the node-maintenance request state.
67 `<node>`: `<string>` ::
69 The cluster node name.
71 *ha-manager crm-command relocate* `<sid> <node>`
73 Request resource relocatzion to another node. This stops the service on the
74 old node, and restarts it on the target node.
76 `<sid>`: `<type>:<name>` ::
78 HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
80 `<node>`: `<string>` ::
84 *ha-manager crm-command stop* `<sid> <timeout>`
86 Request the service to be stopped.
88 `<sid>`: `<type>:<name>` ::
90 HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
92 `<timeout>`: `<integer> (0 - N)` ::
94 Timeout in seconds. If set to 0 a hard stop will be performed.
96 *ha-manager groupadd* `<group> --nodes <string>` `[OPTIONS]`
98 Create a new HA group.
100 `<group>`: `<string>` ::
102 The HA group identifier.
104 `--comment` `<string>` ::
108 `--nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
110 List of cluster node names with optional priority.
112 `--nofailback` `<boolean>` ('default =' `0`)::
114 The CRM tries to run services on the node with the highest priority. If a node with higher priority comes online, the CRM migrates the service to that node. Enabling nofailback prevents that behavior.
116 `--restricted` `<boolean>` ('default =' `0`)::
118 Resources bound to restricted groups may only run on nodes defined by the group.
120 `--type` `<group>` ::
124 *ha-manager groupconfig*
128 *ha-manager groupremove* `<group>`
130 Delete ha group configuration.
132 `<group>`: `<string>` ::
134 The HA group identifier.
136 *ha-manager groupset* `<group>` `[OPTIONS]`
138 Update ha group configuration.
140 `<group>`: `<string>` ::
142 The HA group identifier.
144 `--comment` `<string>` ::
148 `--delete` `<string>` ::
150 A list of settings you want to delete.
152 `--digest` `<string>` ::
154 Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
156 `--nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
158 List of cluster node names with optional priority.
160 `--nofailback` `<boolean>` ('default =' `0`)::
162 The CRM tries to run services on the node with the highest priority. If a node with higher priority comes online, the CRM migrates the service to that node. Enabling nofailback prevents that behavior.
164 `--restricted` `<boolean>` ('default =' `0`)::
166 Resources bound to restricted groups may only run on nodes defined by the group.
168 *ha-manager help* `[OPTIONS]`
170 Get help about specified command.
172 `--extra-args` `<array>` ::
174 Shows help for a specific command
176 `--verbose` `<boolean>` ::
178 Verbose output format.
182 An alias for 'ha-manager crm-command migrate'.
184 *ha-manager relocate*
186 An alias for 'ha-manager crm-command relocate'.
188 *ha-manager remove* `<sid>`
190 Delete resource configuration.
192 `<sid>`: `<type>:<name>` ::
194 HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
196 *ha-manager set* `<sid>` `[OPTIONS]`
198 Update resource configuration.
200 `<sid>`: `<type>:<name>` ::
202 HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
204 `--comment` `<string>` ::
208 `--delete` `<string>` ::
210 A list of settings you want to delete.
212 `--digest` `<string>` ::
214 Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
216 `--group` `<string>` ::
218 The HA group identifier.
220 `--max_relocate` `<integer> (0 - N)` ('default =' `1`)::
222 Maximal number of service relocate tries when a service failes to start.
224 `--max_restart` `<integer> (0 - N)` ('default =' `1`)::
226 Maximal number of tries to restart the service on a node after its start failed.
228 `--state` `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::
230 Requested resource state.
232 *ha-manager status* `[OPTIONS]`
234 Display HA manger status.
236 `--verbose` `<boolean>` ('default =' `0`)::
238 Verbose output. Include complete CRM and LRM status (JSON).