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 3E13D1FF13C for ; Thu, 02 Apr 2026 15:21:42 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CC0121A1DA; Thu, 2 Apr 2026 15:22:11 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 02 Apr 2026 15:21:37 +0200 Message-Id: Subject: Re: [PATCH ha-manager v4 21/28] test: add dynamic automatic rebalancing system test cases From: "Dominik Rusovac" To: "Daniel Kral" , X-Mailer: aerc 0.20.0 References: <20260402124817.416232-1-d.kral@proxmox.com> <20260402124817.416232-22-d.kral@proxmox.com> In-Reply-To: <20260402124817.416232-22-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1775136039501 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.502 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: YZ6AMZJ77L6X4MX5JMGSAVFAZZGJHD4I X-Message-ID-Hash: YZ6AMZJ77L6X4MX5JMGSAVFAZZGJHD4I 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: lgtm, consider this On Thu Apr 2, 2026 at 2:44 PM CEST, Daniel Kral wrote: > These test cases document the basic behavior of the automatic load > rebalancer using the dynamic usage stats. > > As an overview: > > - Case 0: rebalancing system is inactive for no configured HA resources > - Case 1: rebalancing system doesn't trigger any rebalancing migrations > for a single, configured HA resource > - Case 2: rebalancing system triggers migrations if the running HA > resources cause a significant node imbalance and converge if > the imbalance falls below the threshold > - Case 3: rebalancing system triggers migrations if the running HA > resources cause a significant node imbalance through dynamic > changes in their usage > - Case 4: rebalancing system doesn't trigger a migration if the node > imbalance is exceeded once but isn't sustained for at least > the set hold duration > > Signed-off-by: Daniel Kral > --- > changes v3 -> v4: > - case 3 was changed to have an initial imbalance below 0.3 instead of > an imbalance below 0.7 as before > - case 4 was changed to have an imbalance below 0.3 instead of below 0.7 > to not trigger a rebalancing migration inbetween the transient spike > [snip] Reviewed-by: Dominik Rusovac