network: adapt apply config section to PVE 7

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

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 2162d25ea0e64db8561375e9a9fe85d43a0b63d9..54db2a50f13409b24b4e7efe5075807ec705f475 100644 (file)
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -243,7 +243,7 @@ the current manager status file and executes the respective commands.
 
 `pve-ha-crm`::
 
-The cluster resource manager (CRM), which makes the cluster wide
+The cluster resource manager (CRM), which makes the cluster-wide
 decisions. It sends commands to the LRM, processes the results,
 and moves resources to other nodes if something fails. The CRM also
 handles node fencing.
@@ -307,10 +307,20 @@ LRM that the service is running.
 
 fence::
 
-Wait for node fencing (service node is not inside quorate cluster
-partition). As soon as node gets fenced successfully the service will
-be recovered to another node, if possible
-(see xref:ha_manager_fencing[Fencing]).
+Wait for node fencing as the service node is not inside the quorate cluster
+partition (see xref:ha_manager_fencing[Fencing]).
+As soon as node gets fenced successfully the service will be placed into the
+recovery state.
+
+recovery::
+
+Wait for recovery of the service. The HA manager tries to find a new node where
+the service can run on. This search depends not only on the list of online and
+quorate nodes, but also if the service is a group member and how such a group
+is limited.
+As soon as a new available node is found, the service will be moved there and
+initially placed into stopped state. If it's configured to run the new node
+will do so.
 
 freeze::
 
@@ -321,9 +331,8 @@ node, or when we restart the LRM daemon
 ignored::
 
 Act as if the service were not managed by HA at all.
-Useful, when full control over the service is desired temporarily,
-without removing it from the HA configuration.
-
+Useful, when full control over the service is desired temporarily, without
+removing it from the HA configuration.
 
 migrate::
 
@@ -347,7 +356,7 @@ Local Resource Manager
 ~~~~~~~~~~~~~~~~~~~~~~
 
 The local resource manager (`pve-ha-lrm`) is started as a daemon on
-boot and waits until the HA cluster is quorate and thus cluster wide
+boot and waits until the HA cluster is quorate and thus cluster-wide
 locks are working.
 
 It can be in three states: