Add audio device documentation

[pve-docs.git] / ha-manager.1-synopsis.adoc

diff --git a/ha-manager.1-synopsis.adoc b/ha-manager.1-synopsis.adoc
index 7394c5d25303608fe44a94a6cee63e416b599366..f91530df2f66c0b75e0f0c3ea3f7d5372bcd1b2d 100644 (file)
--- a/ha-manager.1-synopsis.adoc
+++ b/ha-manager.1-synopsis.adoc
@@ -32,8 +32,6 @@ Requested resource state.
 
 Resource type.
 
-
-
 *ha-manager config* `[OPTIONS]`
 
 List HA resources.
@@ -42,9 +40,6 @@ List HA resources.
 
 Only list resources of specific type
 
-
-
-
 *ha-manager groupadd* `<group> --nodes <string>` `[OPTIONS]`
 
 Create a new HA group.
@@ -73,14 +68,10 @@ Resources bound to restricted groups may only run on nodes defined by the group.
 
 Group type.
 
-
-
 *ha-manager groupconfig*
 
 Get HA groups.
 
-
-
 *ha-manager groupremove* `<group>`
 
 Delete ha group configuration.
@@ -89,8 +80,6 @@ Delete ha group configuration.
 
 The HA group identifier.
 
-
-
 *ha-manager groupset* `<group>` `[OPTIONS]`
 
 Update ha group configuration.
@@ -123,24 +112,18 @@ The CRM tries to run services on the node with the highest priority. If a node w
 
 Resources bound to restricted groups may only run on nodes defined by the group.
 
-
-
-
-*ha-manager help* `[<cmd>]` `[OPTIONS]`
+*ha-manager help* `[OPTIONS]`
 
 Get help about specified command.
 
-`<cmd>`: `<string>` ::
+`--extra-args` `<array>` ::
 
-Command name
+Shows help for a specific command
 
 `--verbose` `<boolean>` ::
 
 Verbose output format.
 
-
-
-
 *ha-manager migrate* `<sid> <node>`
 
 Request resource migration (online) to another node.
@@ -151,9 +134,7 @@ HA resource ID. This consists of a resource type followed by a resource specific
 
 `<node>`: `<string>` ::
 
-The cluster node name.
-
-
+Target node.
 
 *ha-manager relocate* `<sid> <node>`
 
@@ -166,9 +147,7 @@ HA resource ID. This consists of a resource type followed by a resource specific
 
 `<node>`: `<string>` ::
 
-The cluster node name.
-
-
+Target node.
 
 *ha-manager remove* `<sid>`
 
@@ -178,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* `<sid>` `[OPTIONS]`
 
 Update resource configuration.
@@ -216,9 +193,6 @@ Maximal number of tries to restart the service on a node after its start failed.
 
 Requested resource state.
 
-
-
-
 *ha-manager status* `[OPTIONS]`
 
 Display HA manger status.
@@ -228,5 +202,3 @@ Display HA manger status.
 Verbose output. Include complete CRM and LRM status (JSON).
 
 
-
-