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 027721FF13C for ; Thu, 30 Apr 2026 13:49:34 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EF7F93895; Thu, 30 Apr 2026 13:49:30 +0200 (CEST) From: Dominik Rusovac To: pve-devel@lists.proxmox.com Subject: [PATCH pve-ha-manager v3 5/6] api: status: add load imbalance to status Date: Thu, 30 Apr 2026 13:48:44 +0200 Message-ID: <20260430114845.151174-6-d.rusovac@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260430114845.151174-1-d.rusovac@proxmox.com> References: <20260430114845.151174-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: 1777549630835 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.382 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: QASH6AJTLLXRSCM6EMZ7RDOTUTYRFTNJ X-Message-ID-Hash: QASH6AJTLLXRSCM6EMZ7RDOTUTYRFTNJ 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 a very basic measure to enable users to detect the prevailing load imbalance in the UI, which atm reveals nothing about the latter. Load imbalance should appear in status if CRS mode is not basic and auto-rebalance is enabled. imo, enabling users to track how the load imbalance changed over time (using RRD graphs, for example) should be considered, in the long run. Signed-off-by: Dominik Rusovac --- Notes: changes since v2: * correct extra_status handling * check definedness of imbalance src/PVE/API2/HA/Status.pm | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/src/PVE/API2/HA/Status.pm b/src/PVE/API2/HA/Status.pm index 4894f3b..feb1419 100644 --- a/src/PVE/API2/HA/Status.pm +++ b/src/PVE/API2/HA/Status.pm @@ -199,8 +199,15 @@ __PACKAGE__->register_method({ } my $datacenter_config = eval { cfs_read_file('datacenter.cfg') } // {}; if (my $crs = $datacenter_config->{crs}) { - $extra_status .= " - $crs->{ha} load CRS" - if $crs->{ha} && $crs->{ha} ne 'basic'; + my $mode = $crs->{ha}; + + if ($mode && $mode ne 'basic') { + $extra_status .= " - $mode load CRS "; + + my $imbalance = $status->{imbalance}; + $extra_status .= sprintf("(load imbalance: %.2f", 100 * $imbalance) . "%)" + if $crs->{'ha-auto-rebalance'} && defined($imbalance); + } } my $time_str = localtime($status->{timestamp}); my $status_text = "$master ($status_str, $time_str)$extra_status"; -- 2.47.3