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 CB7111FF141 for ; Tue, 02 Jun 2026 12:03:01 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B65F2DF09; Tue, 2 Jun 2026 12:02:52 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2 10/12] ha-manager: rules: improve resource affinity rule short description Date: Tue, 2 Jun 2026 12:01:14 +0200 Message-ID: <20260602100226.180071-11-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260602100226.180071-1-d.kral@proxmox.com> References: <20260602100226.180071-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: 1780394515802 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.075 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: VJWQNUS465UUE6TCVBZ2RO6CQKAWL2IP X-Message-ID-Hash: VJWQNUS465UUE6TCVBZ2RO6CQKAWL2IP 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: For conciseness, make the following improvements to the resource affinity rule short description in a single patch: - Add newline to separate most important information from additional nice-to-have information. - Use the same order of affinity types as in the separate "Resource affinity rules" section. - Use the word 'must' to highlight that resource affinity rules are currently always strict. Signed-off-by: Daniel Kral --- changes since v1: - new ha-manager.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index d34916e..479b539 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -709,10 +709,11 @@ include::generated/ha-rules-opts.adoc[] | HA Rule Type | Description | `node-affinity` | Places affinity from one or more HA resources to one or more nodes. -| `resource-affinity` | Places affinity between two or more HA resources. The -affinity `negative` specifies that HA resources are to be kept on separate -nodes, while the affinity `positive` specifies that HA resources are to be kept -on the same node. +| `resource-affinity` | Places affinity between two or more HA resources. + +The affinity `positive` specifies that HA resources must be kept on the same +node, while the affinity `negative` specifies that HA resources must be kept on +separate nodes. |=========================================================== [[ha_manager_node_affinity_rules]] -- 2.47.3