all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/5] ha: rules: update about mixed usage of node and resource affinity rules
Date: Mon,  4 Aug 2025 16:11:40 +0200	[thread overview]
Message-ID: <20250804141204.207216-2-d.kral@proxmox.com> (raw)
In-Reply-To: <20250804141204.207216-1-d.kral@proxmox.com>

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 <d.kral@proxmox.com>
---
 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


  reply	other threads:[~2025-08-04 14:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 14:11 [pve-devel] [PATCH docs 1/5] ha: affinity rules: simplify overly verbose rule conflicts and errors section Daniel Kral
2025-08-04 14:11 ` Daniel Kral [this message]
2025-08-04 15:09   ` [pve-devel] [PATCH docs 2/5] ha: rules: update about mixed usage of node and resource affinity rules Hannes Duerr
2025-08-05  7:15     ` Daniel Kral
2025-08-04 14:11 ` [pve-devel] [PATCH docs 3/5] ha: rules: document crs behavior for split positive resource affinity Daniel Kral
2025-08-05  7:42   ` Michael Köppl
2025-08-05  7:50     ` Daniel Kral
2025-08-04 14:11 ` [pve-devel] [PATCH docs 4/5] ha: mark ha groups as deprecated and note migration to node affinity rules Daniel Kral
2025-08-04 14:11 ` [pve-devel] [PATCH docs 5/5] ha: replace in-text references to ha groups with ha rules Daniel Kral
2025-08-04 15:24   ` Hannes Duerr
2025-08-05  7:39     ` Daniel Kral
2025-08-05  7:41   ` Michael Köppl
2025-08-05  7:47 ` [pve-devel] [PATCH docs 1/5] ha: affinity rules: simplify overly verbose rule conflicts and errors section Michael Köppl
2025-08-05  8:01 ` [pve-devel] applied: " Daniel Kral

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250804141204.207216-2-d.kral@proxmox.com \
    --to=d.kral@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal