From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id D52181FF138 for ; Wed, 22 Jul 2026 10:49:34 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 2F85B215D4; Wed, 22 Jul 2026 10:48:38 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs v3 14/16] ha-manager: rules: improve resource affinity rule short description Date: Wed, 22 Jul 2026 10:48:22 +0200 Message-ID: <20260722084824.108350-15-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260722084824.108350-1-d.kral@proxmox.com> References: <20260722084824.108350-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: 1784710083143 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.110 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) 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: 76XNWXZZVGWVW6FHFKFJH32TYOCR5EI7 X-Message-ID-Hash: 76XNWXZZVGWVW6FHFKFJH32TYOCR5EI7 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 CC: David Riley 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 Reviewed-by: David Riley --- changes since v2: - none ha-manager.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 2433796..58d50ed 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