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 1E44F1FF13F for ; Thu, 09 Apr 2026 13:42:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7C49D1D3E; Thu, 9 Apr 2026 13:42:53 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs 13/18] ha-manager: crs: reword the rebalance on start scheduling point Date: Thu, 9 Apr 2026 13:41:39 +0200 Message-ID: <20260409114224.323102-14-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260409114224.323102-1-d.kral@proxmox.com> References: <20260409114224.323102-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1775734880143 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.081 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: 4XIE5ZPRLMOTTDJUCLG6JD6CBMEW6R7N X-Message-ID-Hash: 4XIE5ZPRLMOTTDJUCLG6JD6CBMEW6R7N X-MailFrom: d.kral@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: 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 rules: rule, the HA stack will use the CRS algorithm to ensure that these HA resources are moved to separate nodes. -HA resources stopped -> start transition (opt-in) -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +HA resource rebalance on start (opt-in) +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Requesting that a stopped HA resource should be started is an good opportunity -to check for the best suited node as per the CRS algorithm, as moving stopped -HA resources is cheaper to do than moving them started, especially if their -disk volumes reside on shared storage. You can enable this by setting the -**`ha-rebalance-on-start`** CRS option in the datacenter config. You can change -that option also in the Web UI, under `Datacenter` -> `Options` -> `Cluster -Resource Scheduling`. +When starting an HA resource with rebalance on start enabled, the CRS will +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. + +This setting can be enabled with the CRS option `ha-rebalance-on-start` in the +web interface under `Datacenter` -> `Options` -> `Cluster Resource Scheduling`. ifdef::manvolnum[] include::pve-copyright.adoc[] -- 2.47.3