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 E329F1FF185 for ; Mon, 4 Aug 2025 16:10:43 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C0EC333346; Mon, 4 Aug 2025 16:12:11 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Date: Mon, 4 Aug 2025 16:11:40 +0200 Message-ID: <20250804141204.207216-2-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250804141204.207216-1-d.kral@proxmox.com> References: <20250804141204.207216-1-d.kral@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754316709270 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.014 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 Subject: [pve-devel] [PATCH docs 2/5] ha: rules: update about mixed usage of node and resource affinity rules X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" As HA resources can be part of node and resource affinity rules at the same time in simpler cases, update the relevant sections about specific interactions and restrictions. Signed-off-by: Daniel Kral --- ha-manager.adoc | 29 +++++++++++++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index d6ac75d..5d75287 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -837,6 +837,23 @@ Two or more HA resources cannot be kept on the same node and separated on different nodes at the same time. For more information on these cases, see the section about xref:ha_manager_rule_conflicts[rule conflicts and errors] below. +Interactions between Node and Positive Resource Affinity Rules +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + +If there are HA resources in a node affinity rule, which are also part of a +positive resource affinity rules, then all the other HA resources in the +positive resource affinity rule inherit the node affinity rule as well. + +For example, if the HA resources `vm:100`, `vm:101`, and `vm:102` are in a +positive resource affinity rule, and `vm:102` is in a node affinity rule, which +restricts `vm:102` to be only on `node3`, then `vm:100` and `vm:101` are +restricted to be only on `node3` as well. + +Note that if there are two or more HA resources of a positive resource affinity +rules, which are in different node affinity rules, then those will be disabled +as it is currently not supported. For more information on these cases, see the +section about xref:ha_manager_rule_conflicts[rule conflicts and errors] below. + Resource Affinity Rule Properties +++++++++++++++++++++++++++++++++ @@ -866,8 +883,16 @@ Currently, HA rules are checked for the following feasibility tests: resources as a negative HA resources affinity rule. That is, two or more HA resources cannot be kept together and separate at the same time. -* A HA resource can only be part of either a HA node affinity rule or HA - resource affinity rules, but not both at the same time. +* An HA resource can only be part of a HA node affinity rule and a HA resource + affinity rule at the same time, if the HA node affinity rule has a single + priority class. + +* The HA resources of a positive HA resource affinity rule can only be part of + a single HA node affinity rule at most. + +* The HA resources of a negative HA resource affinity rule cannot be restricted + to less nodes than HA resources by their node affinity rules. Otherwise, the + HA resources do not have enough nodes to be separated. [[ha_manager_fencing]] Fencing -- 2.47.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel