From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 14D1A1FF0B6 for ; Thu, 12 Nov 2026 10:45:46 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id AEED421760; Thu, 12 Nov 2026 10:44:52 +0100 (CET) From: Dominik Rusovac To: pve-devel@lists.proxmox.com Subject: [PATCH pve-cluster v2 10/19] fix #7993: datacenter config: ad ha-{cpu,mem}-weight crs options Date: Thu, 12 Nov 2026 10:44:28 +0100 Message-ID: <20261112094437.1951271-11-d.rusovac@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261112094437.1951271-1-d.rusovac@proxmox.com> References: <20261112094437.1951271-1-d.rusovac@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794476685946 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.041 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: DBHLFAUZXTLAX3LZEJCEQL2HNHUWW45T X-Message-ID-Hash: DBHLFAUZXTLAX3LZEJCEQL2HNHUWW45T 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: add weights controlling how much balancing the CPU load, respectively the memory usage, of nodes is prioritized relative to each other by the static and dynamic scheduling modes the weights are not specific to automatic rebalancing, as they are also used when selecting a node to start or recover a resource on, so they do not require 'ha-auto-rebalance' if neither weight is set, the previous behavior is kept: selecting a node and the TOPSIS method favor memory usage 5 times over CPU load, while the bruteforce method weighs both equally. if only one weight is set, the other one defaults to 1 Signed-off-by: Dominik Rusovac --- Notes: changes since v1: * rename ha-auto-rebalance-{cpu,mem}-weight, as the weights are not auto-rebalance specific * add verbose_description * reword commit src/PVE/DataCenterConfig.pm | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/src/PVE/DataCenterConfig.pm b/src/PVE/DataCenterConfig.pm index 004122e..a678838 100644 --- a/src/PVE/DataCenterConfig.pm +++ b/src/PVE/DataCenterConfig.pm @@ -78,6 +78,34 @@ EODESC description => "The minimum relative improvement in cluster node imbalance," . " in percent, to commit to a resource balancing migration.", }, + 'ha-cpu-weight' => { + type => 'integer', + optional => 1, + minimum => 0, + default => 1, + description => "How much balancing the CPU load of nodes is prioritized, relative to" + . " 'ha-mem-weight'. Used for the 'static' and 'dynamic' scheduler modes.", + verbose_description => "How much balancing the CPU load of nodes is prioritized," + . " relative to 'ha-mem-weight'. Used for the 'static' and 'dynamic' scheduler" + . " modes, both for selecting a node to start or recover a resource on and for" + . " the automatic rebalancing. Only the ratio of the weights matters. If" + . " neither weight is set, selecting a node to start or recover a resource on and" + . " the 'topsis' rebalancing method prioritize memory usage 5 times over CPU load.", + }, + 'ha-mem-weight' => { + type => 'integer', + optional => 1, + minimum => 0, + default => 1, + description => "How much balancing the memory usage of nodes is prioritized, relative" + . " to 'ha-cpu-weight'. Used for the 'static' and 'dynamic' scheduler modes.", + verbose_description => "How much balancing the memory usage of nodes is prioritized," + . " relative to 'ha-cpu-weight'. Used for the 'static' and 'dynamic' scheduler" + . " modes, both for selecting a node to start or recover a resource on and for" + . " the automatic rebalancing. Only the ratio of the weights matters. If" + . " neither weight is set, selecting a node to start or recover a resource on and" + . " the 'topsis' rebalancing method prioritize memory usage 5 times over CPU load.", + }, }; my $migration_format = { -- 2.47.3