remove empty line between heading and attribute definition, fix man titles

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

diff --git a/ha-manager.adoc b/ha-manager.adoc
index a3cb91cd0704658154ee9b0a434b0c93554b1ed3..18b745f87f844972da249afa70534a31b0af7f3a 100644 (file)
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -1,15 +1,16 @@
 [[chapter-ha-manager]]
 ifdef::manvolnum[]
-PVE({manvolnum})
-================
+ha-manager(1)
+=============
 include::attributes.txt[]
+:pve-toplevel:
 
 NAME
 ----
 
 ha-manager - Proxmox VE HA Manager
 
-SYNOPSYS
+SYNOPSIS
 --------
 
 include::ha-manager.1-synopsis.adoc[]
@@ -23,7 +24,9 @@ High Availability
 =================
 include::attributes.txt[]
 endif::manvolnum[]
-
+ifdef::wiki[]
+:pve-toplevel:
+endif::wiki[]
 
 Our modern society depends heavily on information provided by
 computers over the network. Mobile devices amplified that dependency,
@@ -409,10 +412,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::
 
@@ -421,13 +425,14 @@ The resource won't automatically fail back when a more preferred node
   Examples;;
   * You need to migrate a service to a node which hasn't the highest priority
   in the group at the moment, to tell the HA manager to not move this service
-  instantly back set the nofailnback option and the service will stay on
+  instantly back set the 'nofailback' option and the service will stay on
+  the current node.
 
-  * A service was fenced and he got recovered to another node. The admin
-  repaired the node and brang it up online again but does not want that the
+  * A service was fenced and it got recovered to another node. The admin
+  repaired the node and brought it up online again but does not want that the
   recovered services move straight back to the repaired node as he wants to
   first investigate the failure cause and check if it runs stable. He can use
-  the nofailback option to achieve this.
+  the 'nofailback' option to achieve this.
 
 
 Start Failure Policy