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 DAF261FF13F for ; Thu, 09 Apr 2026 13:43:14 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 189C0235A; Thu, 9 Apr 2026 13:43:05 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs 11/18] ha-manager: crs: remove HA group config from scheduling points list Date: Thu, 9 Apr 2026 13:41:37 +0200 Message-ID: <20260409114224.323102-12-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: 1775734880033 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.082 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: YAEFHKJ4UCFCT4QRYESA4JKQNLOJGWN6 X-Message-ID-Hash: YAEFHKJ4UCFCT4QRYESA4JKQNLOJGWN6 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: For Proxmox VE 9 and onwards, HA groups are deprecated and automatically migrated to HA node affinity rules. This is already noted for the still existing HA group section, such that referencing here is only duplicate and outdated information. Signed-off-by: Daniel Kral --- ha-manager.adoc | 5 ----- 1 file changed, 5 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index d7412f2..716e77e 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1478,11 +1478,6 @@ node placement, which can be caused by any of the following scheduling points: 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 group config changes (always active). If a node is removed from a group, - or its priority is reduced, the HA stack will use the CRS algorithm to find a - new target node for the HA resources in that group, matching the adapted - priority constraints. - - 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 -- 2.47.3