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 E2E891FF13A for ; Wed, 15 Apr 2026 11:17:11 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 22E29A830; Wed, 15 Apr 2026 11:16:48 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2 07/19] ha-manager: crs: remove note about manual changes to datacenter config Date: Wed, 15 Apr 2026 11:15:34 +0200 Message-ID: <20260415091635.162224-8-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260415091635.162224-1-d.kral@proxmox.com> References: <20260415091635.162224-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776244521931 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: 25UM6MYZ4QWZGWABT66G2TKS6IL6G4OE X-Message-ID-Hash: 25UM6MYZ4QWZGWABT66G2TKS6IL6G4OE 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: It is generally discouraged to change the datacenter configuration manually, so it should not be mentioned in the admin guide. If there is a CLI utility to change these options in the future it can be added here. Signed-off-by: Daniel Kral Reviewed-by: Michael Köppl --- changes v1 -> v2: - none I didn't go for adding the pvesh command after all since it hindered simplifying the paragraph's flow in the following patches, especially with adding additional text about that the option also controls the functionality described in other chapters... And as mentioned by Shannon, users that really want to change it that way probably will already figure it out through the API viewer documentation. ha-manager.adoc | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index aa2d362..07f6958 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1415,11 +1415,7 @@ Cluster Resource Scheduling The cluster resource scheduler (CRS) mode controls how HA selects nodes for the recovery of a service as well as for migrations that are triggered by a shutdown policy. The default mode is `basic`, you can change it in the Web UI -(`Datacenter` -> `Options`), or directly in `datacenter.cfg`: - ----- -crs: ha=static ----- +(`Datacenter` -> `Options`). [thumbnail="screenshot/gui-datacenter-options-crs.png"] -- 2.47.3