buildsys: switch upload dist over to buster

[pve-docs.git] / ha-resources-opts.adoc

diff --git a/ha-resources-opts.adoc b/ha-resources-opts.adoc
index 50780aea3b4ee9e00019cc3401070f33cf440a99..c0aaf1999b881bb02c5392ad09e586457c4715c7 100644 (file)
--- a/ha-resources-opts.adoc
+++ b/ha-resources-opts.adoc
@@ -14,7 +14,7 @@ Maximal number of service relocate tries when a service failes to start.
 
 Maximal number of tries to restart the service on a node after its start failed.
 
 
 Maximal number of tries to restart the service on a node after its start failed.
 

-`state`: `<disabled | enabled | started | stopped>` ('default =' `started`)::
+`state`: `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::

 
 Requested resource state. The CRM reads this state and acts accordingly.
 Please note that `enabled` is just an alias for `started`.
 
 Requested resource state. The CRM reads this state and acts accordingly.
 Please note that `enabled` is just an alias for `started`.


@@ -37,4 +37,12 @@ The CRM tries to put the resource in `stopped` state, but does not try
 to relocate the resources on node failures. The main purpose of this
 state is error recovery, because it is the only way to move a resource out
 of the `error` state.
 to relocate the resources on node failures. The main purpose of this
 state is error recovery, because it is the only way to move a resource out
 of the `error` state.

++
+`ignored`;;
++
+The resource gets removed from the manager status and so the CRM and the LRM do
+not touch the resource anymore. All {pve} API calls affecting this resource
+will be executed, directly bypassing the HA stack. CRM commands will be thrown
+away while there source is in this state. The resource will not get relocated
+on node failures.