[PATCH docs v2 17/19] ha-manager: crs: add dynamic load scheduler section

[Daniel Kral <d.kral@proxmox.com>]

For pve-ha-manager >= 5.2.0, the HA Manager also has a dynamic-load
scheduler mode.

Signed-off-by: Daniel Kral <d.kral@proxmox.com>
Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>
---
changes v1 -> v2:
- add 'section' to the end of the patch subject

 ha-manager.adoc | 21 +++++++++++++++------
 1 file changed, 15 insertions(+), 6 deletions(-)

diff --git a/ha-manager.adoc b/ha-manager.adoc
index c5c7f20..0421b86 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -1453,6 +1453,14 @@ Static usage information from active guests on each node is used to choose the
 best-fitting node for an HA resource. This includes the configured CPU and
 memory quotas for the active guests.
 
+[[_dynamic_scheduler]]
+Dynamic-Load Scheduler
+^^^^^^^^^^^^^^^^^^^^^^
+
+Dynamic usage information from active guests on each node is used to choose the
+best-fitting node for an HA resource. This includes the average CPU and memory
+usage as well as the configured CPU and memory quotas for the active guests.
+
 [[ha_manager_crs_scheduling_points]]
 CRS Scheduling Points
 ~~~~~~~~~~~~~~~~~~~~~
@@ -1499,8 +1507,9 @@ the current node, the HA resource will be migrated to the selected node.
 For the xref:_basic_scheduler[basic scheduler mode], the node with the least
 resources count is considered as the best suited node.
 
-For the xref:_static_scheduler[static-load scheduler mode], each node in turn
-is considered as if the HA resource was already running on it, using CPU and
+For the xref:_static_scheduler[static] and
+xref:_dynamic_scheduler[dynamic-load scheduler mode], each node in turn is
+considered as if the HA resource was already running on it, using CPU and
 memory usage from the associated guest configuration. Then for each such
 alternative, CPU and memory usage of all nodes are considered, with memory
 being weighted much more, because it's a truly limited resource. For both, CPU
@@ -1512,10 +1521,10 @@ considered.
 This setting can be enabled with the CRS option `ha-rebalance-on-start` in the
 web interface under `Datacenter` -> `Options` -> `Cluster Resource Scheduling`.
 
-IMPORTANT: For the static-load scheduler mode, this functionality is still in
-technology preview. The more HA resources the more possible combinations there
-are, so it's currently not recommended to use it if you have thousands of HA
-resources.
+IMPORTANT: For the static-load and dynamic-load scheduler mode, this
+functionality is still in technology preview. The more HA resources the more
+possible combinations there are, so it's currently not recommended to use it if
+you have thousands of HA resources.
 
 ifdef::manvolnum[]
 include::pve-copyright.adoc[]
-- 
2.47.3