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).
-`-comment` `<string>` ::
+`--comment` `<string>` ::
Description.
-`-group` `<string>` ::
+`--group` `<string>` ::
The HA group identifier.
-`-max_relocate` `<integer> (0 - N)` ('default =' `1`)::
+`--max_relocate` `<integer> (0 - N)` ('default =' `1`)::
Maximal number of service relocate tries when a service failes to start.
-`-max_restart` `<integer> (0 - N)` ('default =' `1`)::
+`--max_restart` `<integer> (0 - N)` ('default =' `1`)::
Maximal number of tries to restart the service on a node after its start failed.
-`-state` `<disabled | enabled>` ('default =' `enabled`)::
+`--state` `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::
-Resource state.
+Requested resource state.
-`-type` `<ct | vm>` ::
+`--type` `<ct | vm>` ::
Resource type.
List HA resources.
-`-type` `<ct | vm>` ::
+`--type` `<ct | vm>` ::
Only list resources of specific type
-*ha-manager disable* `<sid>`
-
-Disable a HA resource.
-
-`<sid>`: `<type>:<name>` ::
-
-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).
-
-
-
-*ha-manager enable* `<sid>`
-
-Enable a HA resource.
-
-`<sid>`: `<type>:<name>` ::
-
-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).
-
-
-
-
-*ha-manager groupadd* `<group> -nodes <string>` `[OPTIONS]`
+*ha-manager groupadd* `<group> --nodes <string>` `[OPTIONS]`
Create a new HA group.
The HA group identifier.
-`-comment` `<string>` ::
+`--comment` `<string>` ::
Description.
-`-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
+`-
-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
-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').
+List of cluster node names with optional priority.
-`-nofailback` `<boolean>` ('default =' `0`)::
+`--nofailback` `<boolean>` ('default =' `0`)::
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.
-`-restricted` `<boolean>` ('default =' `0`)::
+`--restricted` `<boolean>` ('default =' `0`)::
-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.
+Resources bound to restricted groups may only run on nodes defined by the group.
-`-type` `<group>` ::
+`--type` `<group>` ::
Group type.
The HA group identifier.
-`-comment` `<string>` ::
+`--comment` `<string>` ::
Description.
-`-delete` `<string>` ::
+`--delete` `<string>` ::
A list of settings you want to delete.
-`-digest` `<string>` ::
+`--digest` `<string>` ::
Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
-`-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
+`-
-nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
-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').
+List of cluster node names with optional priority.
-`-nofailback` `<boolean>` ('default =' `0`)::
+`--nofailback` `<boolean>` ('default =' `0`)::
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.
-`-restricted` `<boolean>` ('default =' `0`)::
+`--restricted` `<boolean>` ('default =' `0`)::
-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.
+Resources bound to restricted groups may only run on nodes defined by the group.
Command name
-`-verbose` `<boolean>` ::
+`--verbose` `<boolean>` ::
Verbose output format.
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).
-`-comment` `<string>` ::
+`--comment` `<string>` ::
Description.
-`-delete` `<string>` ::
+`--delete` `<string>` ::
A list of settings you want to delete.
-`-digest` `<string>` ::
+`--digest` `<string>` ::
Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
-`-group` `<string>` ::
+`--group` `<string>` ::
The HA group identifier.
-`-max_relocate` `<integer> (0 - N)` ('default =' `1`)::
+`--max_relocate` `<integer> (0 - N)` ('default =' `1`)::
Maximal number of service relocate tries when a service failes to start.
-`-max_restart` `<integer> (0 - N)` ('default =' `1`)::
+`--max_restart` `<integer> (0 - N)` ('default =' `1`)::
Maximal number of tries to restart the service on a node after its start failed.
-`-state` `<disabled | enabled>` ('default =' `enabled`)::
+`--state` `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::
-Resource state.
+Requested resource state.
Display HA manger status.
-`-verbose` `<boolean>` ('default =' `0`)::
+`--verbose` `<boolean>` ('default =' `0`)::
Verbose output. Include complete CRM and LRM status (JSON).
projects / pve-docs.git / blobdiff