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 829A81FF185 for ; Mon, 4 Aug 2025 17:07:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 29E30353FB; Mon, 4 Aug 2025 17:09:14 +0200 (CEST) Mime-Version: 1.0 Date: Mon, 04 Aug 2025 17:09:11 +0200 Message-Id: Cc: "pve-devel" From: "Hannes Duerr" To: "Proxmox VE development discussion" X-Mailer: aerc 0.20.0 References: <20250804141204.207216-1-d.kral@proxmox.com> <20250804141204.207216-2-d.kral@proxmox.com> In-Reply-To: <20250804141204.207216-2-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754320132601 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.074 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [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" On Mon Aug 4, 2025 at 4:11 PM CEST, Daniel Kral wrote: > 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 s/rules/rule/ > +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 Please note that if there are two or more HA resources in a positive resource affinity rule and in different node affinity rules, these will be disabled, as this is not currently supported. > +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 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel