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 A00E51FF13A for ; Wed, 13 May 2026 15:48:30 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5055FFAEF; Wed, 13 May 2026 15:48:29 +0200 (CEST) From: Dominik Rusovac To: pve-devel@lists.proxmox.com Subject: [PATCH docs] ha-manager: document auto-rebalance property Date: Wed, 13 May 2026 15:48:17 +0200 Message-ID: <20260513134817.1196095-1-d.rusovac@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778680098860 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.336 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: 5FLPFGPMYD3GZXJRX6M2BXHOKUQ72UI6 X-Message-ID-Hash: 5FLPFGPMYD3GZXJRX6M2BXHOKUQ72UI6 X-MailFrom: d.rusovac@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 the documentation part for the recently sent implementation: https://lore.proxmox.com/all/20260513104657.1105858-1-d.rusovac@proxmox.com/ Signed-off-by: Dominik Rusovac --- ha-manager.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ha-manager.adoc b/ha-manager.adoc index 68b8336..5784df4 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1551,6 +1551,12 @@ imbalance by automatically issuing rebalancing migrations. Currently, these migrations are issued only for HA resources and executed sequentially. Furthermore, these migrations always obey the current HA affinity rules. +Disabling `auto-rebalance` for an HA resource prevents the resource from +being part of automatically issued rebalancing migrations. + +NOTE: Any HA resource with a positive affinity for an HA resource with +`auto-rebalance` disabled won't be part of rebalancing migrations either. + The automatic load balancing system can be enabled and configured in the web interface under `Datacenter` -> `Options` -> `Cluster Resource Scheduling`. This allows fine-tuning the various parameters as described in the next -- 2.47.3