ha-manager.adoc: simplify language, provide command line example

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

diff --git a/ha-manager.adoc b/ha-manager.adoc
index c7c65f4fe2772548f211caf39314c3d52a681a1d..cef806d7af723599410a96f8c8a9a7b41e38b206 100644 (file)
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -396,9 +396,9 @@ available. If more nodes are in the highest priority class the services will
 get distributed to those node if not already there. The priorities have a
 relative meaning only.
   Example;;
-  You want to run all services from a group on node1 if possible, if this node
-  is not available you want them to run equally splitted on node2 and node3 and
-  if those fail it should use the other group members.
+  You want to run all services from a group on `node1` if possible. If this node
+  is not available, you want them to run equally splitted on `node2` and `node3`, and
+  if those fail it should use `node4`.
   To achieve this you could set the node list to:
 [source,bash]
   ha-manager groupset mygroup -nodes "node1:2,node2:1,node3:1,node4"
@@ -409,10 +409,11 @@ Resources bound to this group may only run on nodes defined by the
 group. If no group node member is available the resource will be
 placed in the stopped state.
   Example;;
-  A Service can run just on a few nodes, as he uses resources from only found
-  on those, we created a group with said nodes and as we know that else all
-  other nodes get implicitly added with lowest priority we set the restricted
-  option.
+  Lets say a service uses resources only available on `node1` and `node2`,
+  so we need to make sure that HA manager does not use other nodes.
+  We need to create a 'restricted' group with said nodes:
+[source,bash]
+  ha-manager groupset mygroup -nodes "node1,node2" -restricted 
 
 nofailback::