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 groupadd* `<group> --nodes <string>` `[OPTIONS]`
45 Create a new HA group.
47 `<group>`: `<string>` ::
49 The HA group identifier.
51 `--comment` `<string>` ::
55 `--nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
57 List of cluster node names with optional priority.
59 `--nofailback` `<boolean>` ('default =' `0`)::
61 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.
63 `--restricted` `<boolean>` ('default =' `0`)::
65 Resources bound to restricted groups may only run on nodes defined by the group.
71 *ha-manager groupconfig*
75 *ha-manager groupremove* `<group>`
77 Delete ha group configuration.
79 `<group>`: `<string>` ::
81 The HA group identifier.
83 *ha-manager groupset* `<group>` `[OPTIONS]`
85 Update ha group configuration.
87 `<group>`: `<string>` ::
89 The HA group identifier.
91 `--comment` `<string>` ::
95 `--delete` `<string>` ::
97 A list of settings you want to delete.
99 `--digest` `<string>` ::
101 Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
103 `--nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
105 List of cluster node names with optional priority.
107 `--nofailback` `<boolean>` ('default =' `0`)::
109 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.
111 `--restricted` `<boolean>` ('default =' `0`)::
113 Resources bound to restricted groups may only run on nodes defined by the group.
115 *ha-manager help* `[OPTIONS]`
117 Get help about specified command.
119 `--extra-args` `<array>` ::
121 Shows help for a specific command
123 `--verbose` `<boolean>` ::
125 Verbose output format.
127 *ha-manager migrate* `<sid> <node>`
129 Request resource migration (online) to another node.
131 `<sid>`: `<type>:<name>` ::
133 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).
135 `<node>`: `<string>` ::
139 *ha-manager relocate* `<sid> <node>`
141 Request resource relocatzion to another node. This stops the service on the
142 old node, and restarts it on the target node.
144 `<sid>`: `<type>:<name>` ::
146 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).
148 `<node>`: `<string>` ::
152 *ha-manager remove* `<sid>`
154 Delete resource configuration.
156 `<sid>`: `<type>:<name>` ::
158 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).
160 *ha-manager set* `<sid>` `[OPTIONS]`
162 Update resource configuration.
164 `<sid>`: `<type>:<name>` ::
166 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).
168 `--comment` `<string>` ::
172 `--delete` `<string>` ::
174 A list of settings you want to delete.
176 `--digest` `<string>` ::
178 Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
180 `--group` `<string>` ::
182 The HA group identifier.
184 `--max_relocate` `<integer> (0 - N)` ('default =' `1`)::
186 Maximal number of service relocate tries when a service failes to start.
188 `--max_restart` `<integer> (0 - N)` ('default =' `1`)::
190 Maximal number of tries to restart the service on a node after its start failed.
192 `--state` `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::
194 Requested resource state.
196 *ha-manager status* `[OPTIONS]`
198 Display HA manger status.
200 `--verbose` `<boolean>` ('default =' `0`)::
202 Verbose output. Include complete CRM and LRM status (JSON).