From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 45ACD1FF13A for ; Wed, 15 Apr 2026 11:18:36 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6B3D0B7BD; Wed, 15 Apr 2026 11:17:18 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2 10/19] ha-manager: crs: generalize the description for basic and static load modes Date: Wed, 15 Apr 2026 11:15:37 +0200 Message-ID: <20260415091635.162224-11-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260415091635.162224-1-d.kral@proxmox.com> References: <20260415091635.162224-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776244522102 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: P6T2YVG7BUTB2REUAEMY4ZCID42FA7EV X-Message-ID-Hash: P6T2YVG7BUTB2REUAEMY4ZCID42FA7EV 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: The CRS mode does choose the best-fitting node for HA resources in many more scenarios than just HA resource recovery. Therefore, make the text reflect this behavior better. Signed-off-by: Daniel Kral Reviewed-by: Michael Köppl --- changes v1 -> v2: - none ha-manager.adoc | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index b7e0d9b..d7412f2 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1441,16 +1441,19 @@ the future. Basic Scheduler ^^^^^^^^^^^^^^^ -The number of active HA resources on each node is used to choose a recovery -node. Non-HA-managed resources are currently not counted. +The number of active HA resources on each node is used to choose the +best-fitting node for an HA resource. Non-HA-managed resources are currently +not counted. Static-Load Scheduler ^^^^^^^^^^^^^^^^^^^^^ IMPORTANT: The static mode is still a technology preview. -Static usage information from HA resources on each node is used to choose a -recovery node. Usage of non-HA-managed resources is currently not considered. +Static usage information from HA resources 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 HA resources. Usage of non-HA-managed resources is +currently not considered. For this selection, 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 -- 2.47.3