From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 4F2881FF13F for ; Thu, 09 Apr 2026 13:44:11 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9CBD02C95; Thu, 9 Apr 2026 13:43:33 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs 12/18] ha-manager: crs: use headings for the scheduling points Date: Thu, 9 Apr 2026 13:41:38 +0200 Message-ID: <20260409114224.323102-13-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260409114224.323102-1-d.kral@proxmox.com> References: <20260409114224.323102-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1775734880088 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.081 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: H3V563HT6EO6UKEVYZ7QA33ICASL2OFQ X-Message-ID-Hash: H3V563HT6EO6UKEVYZ7QA33ICASL2OFQ X-MailFrom: d.kral@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: This is in preparation to be able to extend the existing entries with more information and allows users to make permalinks to the specific scheduling points. Signed-off-by: Daniel Kral --- ha-manager.adoc | 61 +++++++++++++++++++++++++++---------------------- 1 file changed, 34 insertions(+), 27 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 716e77e..7d4bc44 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1474,38 +1474,45 @@ CRS Scheduling Points In every HA Manager round, the CRS checks whether any HA resources need a new node placement, which can be caused by any of the following scheduling points: -- HA resource recovery (always active). When a node with active HA resources - fails, all its HA resources need to be recovered to other nodes. The CRS - algorithm will be used here to balance that recovery over the remaining nodes. +HA resource recovery (always active) +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -- HA rule config changes (always active). If a rule emposes different - constraints on the HA resources, the HA stack will use the CRS algorithm to - find a new target node for the HA resources affected by these rules depending - on the type of the new rules: +When a node with active HA resources fails, all its HA resources need to be +recovered to other nodes. The CRS algorithm will be used here to balance that +recovery over the remaining nodes. -** Node affinity rules: If a node affinity rule is created or HA resources/nodes - are added to an existing node affinity rule, the HA stack will use the CRS - algorithm to ensure that these HA resources are assigned according to their - node and priority constraints. +HA rule config changes (always active) +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -** Positive resource affinity rules: If a positive resource affinity rule is - created or HA resources are added to an existing positive resource affinity - rule, the HA stack will use the CRS algorithm to ensure that these HA - resources are moved to a common node. +If a rule emposes different constraints on the HA resources, the HA stack will +use the CRS algorithm to find a new target node for the HA resources affected +by these rules depending on the type of the new rules: -** Negative resource affinity rules: If a negative resource affinity rule is - created or HA resources are added to an existing negative resource affinity - rule, the HA stack will use the CRS algorithm to ensure that these HA - resources are moved to separate nodes. +- Node affinity rules: If a node affinity rule is created or HA resources/nodes + are added to an existing node affinity rule, the HA stack will use the CRS + algorithm to ensure that these HA resources are assigned according to their + node and priority constraints. -- HA resources stopped -> start transition (opt-in). Requesting that a stopped - HA resource should be started is an good opportunity to check for the best - suited node as per the CRS algorithm, as moving stopped HA resources is - cheaper to do than moving them started, especially if their disk volumes - reside on shared storage. You can enable this by setting the - **`ha-rebalance-on-start`** CRS option in the datacenter config. You can - change that option also in the Web UI, under `Datacenter` -> `Options` -> - `Cluster Resource Scheduling`. +- Positive resource affinity rules: If a positive resource affinity rule is + created or HA resources are added to an existing positive resource affinity + rule, the HA stack will use the CRS algorithm to ensure that these HA + resources are moved to a common node. + +- Negative resource affinity rules: If a negative resource affinity rule is + created or HA resources are added to an existing negative resource affinity + rule, the HA stack will use the CRS algorithm to ensure that these HA + resources are moved to separate nodes. + +HA resources stopped -> start transition (opt-in) +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Requesting that a stopped HA resource should be started is an good opportunity +to check for the best suited node as per the CRS algorithm, as moving stopped +HA resources is cheaper to do than moving them started, especially if their +disk volumes reside on shared storage. You can enable this by setting the +**`ha-rebalance-on-start`** CRS option in the datacenter config. You can change +that option also in the Web UI, under `Datacenter` -> `Options` -> `Cluster +Resource Scheduling`. ifdef::manvolnum[] include::pve-copyright.adoc[] -- 2.47.3