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>` ::
37 *ha-manager config* `[OPTIONS]`
41 `--type` `<ct | vm>` ::
43 Only list resources of specific type
48 *ha-manager groupadd* `<group> --nodes <string>` `[OPTIONS]`
50 Create a new HA group.
52 `<group>`: `<string>` ::
54 The HA group identifier.
56 `--comment` `<string>` ::
60 `--nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
62 List of cluster node names with optional priority.
64 `--nofailback` `<boolean>` ('default =' `0`)::
66 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.
68 `--restricted` `<boolean>` ('default =' `0`)::
70 Resources bound to restricted groups may only run on nodes defined by the group.
78 *ha-manager groupconfig*
84 *ha-manager groupremove* `<group>`
86 Delete ha group configuration.
88 `<group>`: `<string>` ::
90 The HA group identifier.
94 *ha-manager groupset* `<group>` `[OPTIONS]`
96 Update ha group configuration.
98 `<group>`: `<string>` ::
100 The HA group identifier.
102 `--comment` `<string>` ::
106 `--delete` `<string>` ::
108 A list of settings you want to delete.
110 `--digest` `<string>` ::
112 Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
114 `--nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
116 List of cluster node names with optional priority.
118 `--nofailback` `<boolean>` ('default =' `0`)::
120 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.
122 `--restricted` `<boolean>` ('default =' `0`)::
124 Resources bound to restricted groups may only run on nodes defined by the group.
129 *ha-manager help* `[<cmd>]` `[OPTIONS]`
131 Get help about specified command.
133 `<cmd>`: `<string>` ::
137 `--verbose` `<boolean>` ::
139 Verbose output format.
144 *ha-manager migrate* `<sid> <node>`
146 Request resource migration (online) to another node.
148 `<sid>`: `<type>:<name>` ::
150 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).
152 `<node>`: `<string>` ::
154 The cluster node name.
158 *ha-manager relocate* `<sid> <node>`
160 Request resource relocatzion to another node. This stops the service on the
161 old node, and restarts it on the target node.
163 `<sid>`: `<type>:<name>` ::
165 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).
167 `<node>`: `<string>` ::
169 The cluster node name.
173 *ha-manager remove* `<sid>`
175 Delete resource configuration.
177 `<sid>`: `<type>:<name>` ::
179 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).
183 *ha-manager set* `<sid>` `[OPTIONS]`
185 Update resource configuration.
187 `<sid>`: `<type>:<name>` ::
189 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).
191 `--comment` `<string>` ::
195 `--delete` `<string>` ::
197 A list of settings you want to delete.
199 `--digest` `<string>` ::
201 Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
203 `--group` `<string>` ::
205 The HA group identifier.
207 `--max_relocate` `<integer> (0 - N)` ('default =' `1`)::
209 Maximal number of service relocate tries when a service failes to start.
211 `--max_restart` `<integer> (0 - N)` ('default =' `1`)::
213 Maximal number of tries to restart the service on a node after its start failed.
215 `--state` `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::
217 Requested resource state.
222 *ha-manager status* `[OPTIONS]`
224 Display HA manger status.
226 `--verbose` `<boolean>` ('default =' `0`)::
228 Verbose output. Include complete CRM and LRM status (JSON).