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 C20551FF141 for ; Mon, 13 Apr 2026 17:52:20 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E68044096; Mon, 13 Apr 2026 17:53:08 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 13 Apr 2026 17:53:04 +0200 Message-Id: From: =?utf-8?q?Michael_K=C3=B6ppl?= To: "Daniel Kral" , Subject: Re: [PATCH docs 13/18] ha-manager: crs: reword the rebalance on start scheduling point X-Mailer: aerc 0.21.0 References: <20260409114224.323102-1-d.kral@proxmox.com> <20260409114224.323102-14-d.kral@proxmox.com> In-Reply-To: <20260409114224.323102-14-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776095510357 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.102 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: ALIRVVQF2FOXRUWKFBYV5BEGV3FUUTTF X-Message-ID-Hash: ALIRVVQF2FOXRUWKFBYV5BEGV3FUUTTF X-MailFrom: m.koeppl@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: 1 nit inline On Thu Apr 9, 2026 at 1:41 PM CEST, Daniel Kral wrote: > Make the action, which the CRS takes in the transition from the stopped > to request_start state, more apparent in the heading as well describe > what it does achieve in its description. > > The crs option is not stylized as bold anymore, because it distracts > from the rest of the text and is already highlighted by the different > color as well as the use of a monospaced font. > > Signed-off-by: Daniel Kral > --- > ha-manager.adoc | 17 ++++++++--------- > 1 file changed, 8 insertions(+), 9 deletions(-) > > diff --git a/ha-manager.adoc b/ha-manager.adoc > index 7d4bc44..682e254 100644 > --- a/ha-manager.adoc > +++ b/ha-manager.adoc > @@ -1503,16 +1503,15 @@ by these rules depending on the type of the new r= ules: > rule, the HA stack will use the CRS algorithm to ensure that these HA > resources are moved to separate nodes. > =20 > -HA resources stopped -> start transition (opt-in) > -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > +HA resource rebalance on start (opt-in) > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > =20 > -Requesting that a stopped HA resource should be started is an good oppor= tunity > -to check for the best suited node as per the CRS algorithm, as moving st= opped > -HA resources is cheaper to do than moving them started, especially if th= eir > -disk volumes reside on shared storage. You can enable this by setting th= e > -**`ha-rebalance-on-start`** CRS option in the datacenter config. You can= change > -that option also in the Web UI, under `Datacenter` -> `Options` -> `Clus= ter > -Resource Scheduling`. > +When starting an HA resource with rebalance on start enabled, the CRS wi= ll > +select the node best suited for the HA resource. If the selected node is= not > +the current node, the HA resource will be migrate to the selected node. nit: s/migrate/migrated > + > +This setting can be enabled with the CRS option `ha-rebalance-on-start` = in the > +web interface under `Datacenter` -> `Options` -> `Cluster Resource Sched= uling`. > =20 > ifdef::manvolnum[] > include::pve-copyright.adoc[]