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 A57E91FF133 for ; Mon, 27 Apr 2026 15:21:40 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BE8221ED2F; Mon, 27 Apr 2026 15:21:23 +0200 (CEST) From: Dominik Rusovac To: pve-devel@lists.proxmox.com Subject: [PATCH pve-ha-manager 6/7] api: status: add load imbalance to status Date: Mon, 27 Apr 2026 15:20:30 +0200 Message-ID: <20260427132031.220468-7-d.rusovac@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260427132031.220468-1-d.rusovac@proxmox.com> References: <20260427132031.220468-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: 1777295945431 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.444 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: CFVKNGMLU33C3PFWQBBY7QRV4GC3ZKNL X-Message-ID-Hash: CFVKNGMLU33C3PFWQBBY7QRV4GC3ZKNL 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. 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 --- src/PVE/API2/HA/Status.pm | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/PVE/API2/HA/Status.pm b/src/PVE/API2/HA/Status.pm index 4894f3b..acec78e 100644 --- a/src/PVE/API2/HA/Status.pm +++ b/src/PVE/API2/HA/Status.pm @@ -199,7 +199,9 @@ __PACKAGE__->register_method({ } my $datacenter_config = eval { cfs_read_file('datacenter.cfg') } // {}; if (my $crs = $datacenter_config->{crs}) { - $extra_status .= " - $crs->{ha} load CRS" + $extra_status .= + " - $crs->{ha} load CRS " + . sprintf("(load imbalance: %.2f", 100 * $status->{imbalance}) . "%)" if $crs->{ha} && $crs->{ha} ne 'basic'; } my $time_str = localtime($status->{timestamp}); -- 2.47.3