[pve-devel] [RFC PATCH-SERIES ha-manager 0/2] Negative Node Affinity Rules

[Daniel Kral]

For larger HA clusters, specifying the nodes in simple* node affinity
rules as opt-out (negative) instead of opt-in (positive) can make the
rule set easier to follow and implement by users.

* simple = without priority groups


There's no web interface integration yet, because I'm not entirely sure
yet how to integrate it with the concept of priority groups for positive
node affinity rules, which do not make sense in this context as the
specified nodes will be removed from the effective node set.

As the conversion is pretty straightforward, we could even allow users
to convert between positive and negative node affinity rules (e.g. when
switching the affinity type in the web interface?).


Negative node affinity rules can be declared manually in the rules.cfg
now with these two small patches:


node-affinity: ha-rule-name
	affinity negative
	nodes node1,node2
	resources vm:100,vm:101

In a cluster with node1,...,node5 this will result in the identical
positive node affinity rule:

node-affinity: ha-rule-name-dual
	affinity positive
	nodes node3,node4,node5
	resources vm:100,vm:101


Daniel Kral (2):
  rules: node affinity: add affinity property to node affinity rules
  rules: node affinity: implement negative node affinity rules

 src/PVE/HA/Groups.pm                          |  1 +
 src/PVE/HA/HashTools.pm                       | 20 ++++++
 src/PVE/HA/Rules.pm                           |  2 +
 src/PVE/HA/Rules/NodeAffinity.pm              | 64 +++++++++++++++++++
 .../defaults-for-node-affinity-rules.cfg      | 23 +++++--
 ...efaults-for-node-affinity-rules.cfg.expect | 62 +++++++++++++++++-
 ...nt-node-resource-affinity-rules.cfg.expect |  3 +
 ...ositive-resource-affinity-rules.cfg.expect |  4 ++
 ...ty-with-resource-affinity-rules.cfg.expect |  2 +
 ...rce-refs-in-node-affinity-rules.cfg.expect |  3 +
 10 files changed, 179 insertions(+), 5 deletions(-)

-- 
2.47.3