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` ::
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)` (default=`enabled`)::
31 `-type` `(ct | vm)` ::
37 *ha-manager config* `[OPTIONS]`
41 `-type` `(ct | vm)` ::
43 Only list resources of specific type
48 *ha-manager disable* `<sid>`
50 Disable a HA resource.
52 `<sid>` `<type>:<name>` ::
54 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).
58 *ha-manager enable* `<sid>`
62 `<sid>` `<type>:<name>` ::
64 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).
69 *ha-manager groupadd* `<group> -nodes <string>` `[OPTIONS]`
71 Create a new HA group.
75 The HA group identifier.
77 `-comment` `string` ::
81 `-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
83 List of cluster node names with optional priority. We use priority '0' as default. The CRM tries to run services on the node with highest priority (also see option 'nofailback').
85 `-nofailback` `boolean` (default=`0`)::
87 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.
89 `-restricted` `boolean` (default=`0`)::
91 Services on unrestricted groups may run on any cluster members if all group members are offline. But they will migrate back as soon as a group member comes online. One can implement a 'preferred node' behavior using an unrestricted group with one member.
99 *ha-manager groupconfig*
105 *ha-manager groupremove* `<group>`
107 Delete ha group configuration.
109 `<group>` `string` ::
111 The HA group identifier.
115 *ha-manager groupset* `<group>` `[OPTIONS]`
117 Update ha group configuration.
119 `<group>` `string` ::
121 The HA group identifier.
123 `-comment` `string` ::
127 `-delete` `string` ::
129 A list of settings you want to delete.
131 `-digest` `string` ::
133 Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
135 `-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
137 List of cluster node names with optional priority. We use priority '0' as default. The CRM tries to run services on the node with highest priority (also see option 'nofailback').
139 `-nofailback` `boolean` (default=`0`)::
141 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.
143 `-restricted` `boolean` (default=`0`)::
145 Services on unrestricted groups may run on any cluster members if all group members are offline. But they will migrate back as soon as a group member comes online. One can implement a 'preferred node' behavior using an unrestricted group with one member.
150 *ha-manager help* `[<cmd>]` `[OPTIONS]`
152 Get help about specified command.
158 `-verbose` `boolean` ::
160 Verbose output format.
165 *ha-manager migrate* `<sid> <node>`
167 Request resource migration (online) to another node.
169 `<sid>` `<type>:<name>` ::
171 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).
175 The cluster node name.
179 *ha-manager relocate* `<sid> <node>`
181 Request resource relocatzion to another node. This stops the service on the
182 old node, and restarts it on the target node.
184 `<sid>` `<type>:<name>` ::
186 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).
190 The cluster node name.
194 *ha-manager remove* `<sid>`
196 Delete resource configuration.
198 `<sid>` `<type>:<name>` ::
200 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 *ha-manager set* `<sid>` `[OPTIONS]`
206 Update resource configuration.
208 `<sid>` `<type>:<name>` ::
210 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).
212 `-comment` `string` ::
216 `-delete` `string` ::
218 A list of settings you want to delete.
220 `-digest` `string` ::
222 Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
226 The HA group identifier.
228 `-max_relocate` `integer (0 - N)` (default=`1`)::
230 Maximal number of service relocate tries when a service failes to start.
232 `-max_restart` `integer (0 - N)` (default=`1`)::
234 Maximal number of tries to restart the service on a node after its start failed.
236 `-state` `(disabled | enabled)` (default=`enabled`)::
243 *ha-manager status* `[OPTIONS]`
245 Display HA manger status.
247 `-verbose` `boolean` (default=`0`)::
249 Verbose output. Include complete CRM and LRM status (JSON).