X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=ha-manager.1-synopsis.adoc;h=3071693e775a6b8b5bc59464675285ecd8de4e30;hp=feb156ccf361f01be8b3152139dbaffd18b240b4;hb=a75eeddebed864bde81358463958ed1d166935e1;hpb=013dc89ffce47b8c55412c016a508205768b4fd6 diff --git a/ha-manager.1-synopsis.adoc b/ha-manager.1-synopsis.adoc index feb156c..3071693 100644 --- a/ha-manager.1-synopsis.adoc +++ b/ha-manager.1-synopsis.adoc @@ -8,65 +8,39 @@ Create a new HA resource. 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` `` :: +`--comment` `` :: Description. -`-group` `` :: +`--group` `` :: The HA group identifier. -`-max_relocate` ` (0 - N)` ('default =' `1`):: +`--max_relocate` ` (0 - N)` ('default =' `1`):: Maximal number of service relocate tries when a service failes to start. -`-max_restart` ` (0 - N)` ('default =' `1`):: +`--max_restart` ` (0 - N)` ('default =' `1`):: Maximal number of tries to restart the service on a node after its start failed. -`-state` `` ('default =' `enabled`):: +`--state` `` ('default =' `started`):: -Resource state. +Requested resource state. -`-type` `` :: +`--type` `` :: Resource type. - - *ha-manager config* `[OPTIONS]` List HA resources. -`-type` `` :: +`--type` `` :: Only list resources of specific type - - - -*ha-manager disable* `` - -Disable a HA resource. - -``: `:` :: - -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* `` - -Enable a HA resource. - -``: `:` :: - -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* ` -nodes ` `[OPTIONS]` +*ha-manager groupadd* ` --nodes ` `[OPTIONS]` Create a new HA group. @@ -74,34 +48,30 @@ Create a new HA group. The HA group identifier. -`-comment` `` :: +`--comment` `` :: Description. -`-nodes` `[:]{,[:]}*` :: +`--nodes` `[:]{,[:]}*` :: -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` `` ('default =' `0`):: +`--nofailback` `` ('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` `` ('default =' `0`):: +`--restricted` `` ('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` `` :: +`--type` `` :: Group type. - - *ha-manager groupconfig* Get HA groups. - - *ha-manager groupremove* `` Delete ha group configuration. @@ -110,8 +80,6 @@ Delete ha group configuration. The HA group identifier. - - *ha-manager groupset* `` `[OPTIONS]` Update ha group configuration. @@ -120,48 +88,42 @@ Update ha group configuration. The HA group identifier. -`-comment` `` :: +`--comment` `` :: Description. -`-delete` `` :: +`--delete` `` :: A list of settings you want to delete. -`-digest` `` :: +`--digest` `` :: Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications. -`-nodes` `[:]{,[:]}*` :: +`--nodes` `[:]{,[:]}*` :: -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` `` ('default =' `0`):: +`--nofailback` `` ('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` `` ('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. +`--restricted` `` ('default =' `0`):: +Resources bound to restricted groups may only run on nodes defined by the group. - - -*ha-manager help* `[]` `[OPTIONS]` +*ha-manager help* `[OPTIONS]` Get help about specified command. -``: `` :: +`--extra-args` `` :: -Command name +Shows help for a specific command -`-verbose` `` :: +`--verbose` `` :: Verbose output format. - - - *ha-manager migrate* ` ` Request resource migration (online) to another node. @@ -174,8 +136,6 @@ HA resource ID. This consists of a resource type followed by a resource specific The cluster node name. - - *ha-manager relocate* ` ` Request resource relocatzion to another node. This stops the service on the @@ -189,8 +149,6 @@ HA resource ID. This consists of a resource type followed by a resource specific The cluster node name. - - *ha-manager remove* `` Delete resource configuration. @@ -199,8 +157,6 @@ Delete resource configuration. 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 set* `` `[OPTIONS]` Update resource configuration. @@ -209,45 +165,40 @@ Update resource configuration. 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` `` :: +`--comment` `` :: Description. -`-delete` `` :: +`--delete` `` :: A list of settings you want to delete. -`-digest` `` :: +`--digest` `` :: Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications. -`-group` `` :: +`--group` `` :: The HA group identifier. -`-max_relocate` ` (0 - N)` ('default =' `1`):: +`--max_relocate` ` (0 - N)` ('default =' `1`):: Maximal number of service relocate tries when a service failes to start. -`-max_restart` ` (0 - N)` ('default =' `1`):: +`--max_restart` ` (0 - N)` ('default =' `1`):: Maximal number of tries to restart the service on a node after its start failed. -`-state` `` ('default =' `enabled`):: - -Resource state. - - +`--state` `` ('default =' `started`):: +Requested resource state. *ha-manager status* `[OPTIONS]` Display HA manger status. -`-verbose` `` ('default =' `0`):: +`--verbose` `` ('default =' `0`):: Verbose output. Include complete CRM and LRM status (JSON). - -