generate wiki output file mappings automatically

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

diff --git a/ha-manager.adoc b/ha-manager.adoc
index cef806d7af723599410a96f8c8a9a7b41e38b206..570b282fdaf17cf7241a30944492bd48d3a73203 100644 (file)
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -1,15 +1,16 @@
-[[chapter-ha-manager]]
+[[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[]
@@ -17,13 +18,14 @@ include::ha-manager.1-synopsis.adoc[]
 DESCRIPTION
 -----------
 endif::manvolnum[]
-
 ifndef::manvolnum[]
 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,
@@ -122,6 +124,7 @@ Requirements
 * optional hardware fencing devices
 
 
+[[ha_manager_resources]]
 Resources
 ---------
 
@@ -311,6 +314,7 @@ the update process can be too long which, in the worst case, may result in
 a watchdog reset.
 
 
+[[ha_manager_fencing]]
 Fencing
 -------
 
@@ -380,6 +384,7 @@ That minimizes the possibility of an overload, which else could cause an
 unresponsive node and as a result a chain reaction of node failures in the
 cluster.
 
+[[ha_manager_groups]]
 Groups
 ------
 
@@ -422,13 +427,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