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
10 specific name, separated with colon (example: vm:100 / ct:100). For virtual
11 machines and containers, you can simply use the VM or CT id as a shortcut
14 `-comment` `string` ::
20 The HA group identifier.
22 `-max_relocate` `integer (0 - N)` (default=`1`)::
24 Maximal number of service relocate tries when a service failes to start.
26 `-max_restart` `integer (0 - N)` (default=`1`)::
28 Maximal number of tries to restart the service on a node after its start
31 `-state` `(disabled | enabled)` (default=`enabled`)::
35 `-type` `(ct | vm)` ::
41 *ha-manager config* `[OPTIONS]`
45 `-type` `(ct | vm)` ::
47 Only list resources of specific type
52 *ha-manager disable* `<sid>`
54 Disable a HA resource.
56 `<sid>` `<type>:<name>` ::
58 HA resource ID. This consists of a resource type followed by a resource
59 specific name, separated with colon (example: vm:100 / ct:100). For virtual
60 machines and containers, you can simply use the VM or CT id as a shortcut
65 *ha-manager enable* `<sid>`
69 `<sid>` `<type>:<name>` ::
71 HA resource ID. This consists of a resource type followed by a resource
72 specific name, separated with colon (example: vm:100 / ct:100). For virtual
73 machines and containers, you can simply use the VM or CT id as a shortcut
79 *ha-manager groupadd* `<group> -nodes <string>` `[OPTIONS]`
81 Create a new HA group.
85 The HA group identifier.
87 `-comment` `string` ::
91 `-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
93 List of cluster node names with optional priority. We use priority '0' as
94 default. The CRM tries to run services on the node with highest priority
95 (also see option 'nofailback').
97 `-nofailback` `boolean` (default=`0`)::
99 The CRM tries to run services on the node with the highest priority. If a
100 node with higher priority comes online, the CRM migrates the service to
101 that node. Enabling nofailback prevents that behavior.
103 `-restricted` `boolean` (default=`0`)::
105 Services on unrestricted groups may run on any cluster members if all group
106 members are offline. But they will migrate back as soon as a group member
107 comes online. One can implement a 'preferred node' behavior using an
108 unrestricted group with one member.
116 *ha-manager groupconfig*
122 *ha-manager groupremove* `<group>`
124 Delete ha group configuration.
126 `<group>` `string` ::
128 The HA group identifier.
132 *ha-manager groupset* `<group>` `[OPTIONS]`
134 Update ha group configuration.
136 `<group>` `string` ::
138 The HA group identifier.
140 `-comment` `string` ::
144 `-delete` `string` ::
146 A list of settings you want to delete.
148 `-digest` `string` ::
150 Prevent changes if current configuration file has different SHA1 digest.
151 This can be used to prevent concurrent modifications.
153 `-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
155 List of cluster node names with optional priority. We use priority '0' as
156 default. The CRM tries to run services on the node with highest priority
157 (also see option 'nofailback').
159 `-nofailback` `boolean` (default=`0`)::
161 The CRM tries to run services on the node with the highest priority. If a
162 node with higher priority comes online, the CRM migrates the service to
163 that node. Enabling nofailback prevents that behavior.
165 `-restricted` `boolean` (default=`0`)::
167 Services on unrestricted groups may run on any cluster members if all group
168 members are offline. But they will migrate back as soon as a group member
169 comes online. One can implement a 'preferred node' behavior using an
170 unrestricted group with one member.
175 *ha-manager help* `[<cmd>]` `[OPTIONS]`
177 Get help about specified command.
183 `-verbose` `boolean` ::
185 Verbose output format.
190 *ha-manager migrate* `<sid> <node>`
192 Request resource migration (online) to another node.
194 `<sid>` `<type>:<name>` ::
196 HA resource ID. This consists of a resource type followed by a resource
197 specific name, separated with colon (example: vm:100 / ct:100). For virtual
198 machines and containers, you can simply use the VM or CT id as a shortcut
203 The cluster node name.
207 *ha-manager relocate* `<sid> <node>`
209 Request resource relocatzion to another node. This stops the service on the
210 old node, and restarts it on the target node.
212 `<sid>` `<type>:<name>` ::
214 HA resource ID. This consists of a resource type followed by a resource
215 specific name, separated with colon (example: vm:100 / ct:100). For virtual
216 machines and containers, you can simply use the VM or CT id as a shortcut
221 The cluster node name.
225 *ha-manager remove* `<sid>`
227 Delete resource configuration.
229 `<sid>` `<type>:<name>` ::
231 HA resource ID. This consists of a resource type followed by a resource
232 specific name, separated with colon (example: vm:100 / ct:100). For virtual
233 machines and containers, you can simply use the VM or CT id as a shortcut
238 *ha-manager set* `<sid>` `[OPTIONS]`
240 Update resource configuration.
242 `<sid>` `<type>:<name>` ::
244 HA resource ID. This consists of a resource type followed by a resource
245 specific name, separated with colon (example: vm:100 / ct:100). For virtual
246 machines and containers, you can simply use the VM or CT id as a shortcut
249 `-comment` `string` ::
253 `-delete` `string` ::
255 A list of settings you want to delete.
257 `-digest` `string` ::
259 Prevent changes if current configuration file has different SHA1 digest.
260 This can be used to prevent concurrent modifications.
264 The HA group identifier.
266 `-max_relocate` `integer (0 - N)` (default=`1`)::
268 Maximal number of service relocate tries when a service failes to start.
270 `-max_restart` `integer (0 - N)` (default=`1`)::
272 Maximal number of tries to restart the service on a node after its start
275 `-state` `(disabled | enabled)` (default=`enabled`)::
282 *ha-manager status* `[OPTIONS]`
284 Display HA manger status.
286 `-verbose` `boolean` (default=`0`)::
288 Verbose output. Include complete CRM and LRM status (JSON).