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 C838B1FF141 for ; Mon, 13 Apr 2026 17:52:28 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 41EE9423B; Mon, 13 Apr 2026 17:53:11 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 13 Apr 2026 17:52:35 +0200 Message-Id: Subject: Re: [PATCH docs 12/18] ha-manager: crs: use headings for the scheduling points From: =?utf-8?q?Michael_K=C3=B6ppl?= To: "Daniel Kral" , X-Mailer: aerc 0.21.0 References: <20260409114224.323102-1-d.kral@proxmox.com> <20260409114224.323102-13-d.kral@proxmox.com> In-Reply-To: <20260409114224.323102-13-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776095481018 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.101 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: CXNFO36HHUS37HVEFTP4KU7A5KF5QBKE X-Message-ID-Hash: CXNFO36HHUS37HVEFTP4KU7A5KF5QBKE X-MailFrom: m.koeppl@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: noticed 2 typos, mentioned inline On Thu Apr 9, 2026 at 1:41 PM CEST, Daniel Kral wrote: > 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 p= oints: > =20 > -- HA resource recovery (always active). When a node with active HA resou= rces > - fails, all its HA resources need to be recovered to other nodes. The C= RS > - algorithm will be used here to balance that recovery over the remainin= g nodes. > +HA resource recovery (always active) > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > =20 > -- HA rule config changes (always active). If a rule emposes different s/emposes/imposes > - constraints on the HA resources, the HA stack will use the CRS algorit= hm to > - find a new target node for the HA resources affected by these rules de= pending > - 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. > =20 > -** Node affinity rules: If a node affinity rule is created or HA resourc= es/nodes > - are added to an existing node affinity rule, the HA stack will use th= e CRS > - algorithm to ensure that these HA resources are assigned according to= their > - node and priority constraints. > +HA rule config changes (always active) > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > =20 > -** Positive resource affinity rules: If a positive resource affinity rul= e is > - created or HA resources are added to an existing positive resource af= finity > - 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 stac= k will s/emposes/imposes > +use the CRS algorithm to find a new target node for the HA resources aff= ected > +by these rules depending on the type of the new rules: [snip]