From: "Daniel Kral" <d.kral@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 2/5] ha: rules: update about mixed usage of node and resource affinity rules
Date: Tue, 05 Aug 2025 09:15:38 +0200 [thread overview]
Message-ID: <DBUB5AMTW7MT.ILL024L6LLCB@proxmox.com> (raw)
In-Reply-To: <DBTQLBHFU8BX.3O5D8A59YSVPJ@proxmox.com>
Hey Hannes,
thanks for the quick review!
On Mon Aug 4, 2025 at 5:09 PM CEST, Hannes Duerr wrote:
> On Mon Aug 4, 2025 at 4:11 PM CEST, Daniel Kral wrote:
>> +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/
ACK!
>> +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.
Thanks, will change that with slightly more emphasis that the rules will
be disabled and not the HA resources.
>> +section about xref:ha_manager_rule_conflicts[rule conflicts and errors] below.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-08-05 7:14 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 ` [pve-devel] [PATCH docs 2/5] ha: rules: update about mixed usage of node and resource affinity rules Daniel Kral
2025-08-04 15:09 ` Hannes Duerr
2025-08-05 7:15 ` Daniel Kral [this message]
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=DBUB5AMTW7MT.ILL024L6LLCB@proxmox.com \
--to=d.kral@proxmox.com \
--cc=pve-devel-bounces@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox