From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager v2 07/12] ui: ha: node affinity: allow setting affinity for node affinity rules
Date: Tue, 2 Jun 2026 12:01:11 +0200 [thread overview]
Message-ID: <20260602100226.180071-8-d.kral@proxmox.com> (raw)
In-Reply-To: <20260602100226.180071-1-d.kral@proxmox.com>
Since the node affinity rules can be either 'positive' or 'negative'
now, allow users to define either affinity type for the node affinity
rules in the web interface as well.
Since the priority field does not have any semantic value for negative
node affinity rules, do not use the field for the negative affinity
type.
As the affinity type is switched from positive to negative and vice
versa, the node selection is inverted to make the (lossy) conversion
easier. The column widths are changed to minimize movement while
switching between the affinity types.
The inversion is not done if the selection is empty, as preferring all
nodes is rather uselessly verbose and avoiding all nodes is disallowed
as this rule would not satisfiable.
Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
changes since v1:
- new
www/manager6/ha/NodePrioritySelector.js | 65 ++++++++++++++++++-
www/manager6/ha/rules/NodeAffinityRuleEdit.js | 25 +++++++
www/manager6/ha/rules/NodeAffinityRules.js | 5 ++
3 files changed, 92 insertions(+), 3 deletions(-)
diff --git a/www/manager6/ha/NodePrioritySelector.js b/www/manager6/ha/NodePrioritySelector.js
index ec6ac02a..b58b0ada 100644
--- a/www/manager6/ha/NodePrioritySelector.js
+++ b/www/manager6/ha/NodePrioritySelector.js
@@ -10,6 +10,16 @@ Ext.define('PVE.forms.NodePrioritySelector', {
selectAll: false,
isFormField: true,
+ config: {
+ useNodePriority: null,
+ },
+
+ publishes: ['useNodePriority'],
+
+ viewModel: {
+ showNodePriority: null,
+ },
+
store: {
autoLoad: true,
fields: ['node', 'cpu', 'mem', 'priority'],
@@ -28,7 +38,7 @@ Ext.define('PVE.forms.NodePrioritySelector', {
columns: [
{
header: gettext('Node'),
- flex: 1,
+ width: 150,
dataIndex: 'node',
},
{
@@ -42,7 +52,7 @@ Ext.define('PVE.forms.NodePrioritySelector', {
header: gettext('CPU usage'),
renderer: Proxmox.Utils.render_cpu,
sortable: true,
- width: 150,
+ flex: 1,
dataIndex: 'cpu',
},
{
@@ -56,6 +66,14 @@ Ext.define('PVE.forms.NodePrioritySelector', {
minValue: 0,
maxValue: 1000,
isFormField: false,
+ bind: {
+ hidden: '{!showNodePriority}',
+ disabled: '{!showNodePriority}',
+ },
+ },
+ bind: {
+ hidden: '{!showNodePriority}',
+ disabled: '{!showNodePriority}',
},
},
],
@@ -74,6 +92,39 @@ Ext.define('PVE.forms.NodePrioritySelector', {
},
},
+ invertCheckboxSelection: function () {
+ let me = this;
+
+ let sm = me.getSelectionModel();
+
+ let allNodeModels = new Set(sm.getStore().getData().items ?? []);
+ let selectedNodeModels = new Set(sm.getSelection() ?? []);
+
+ if (!allNodeModels.size || !selectedNodeModels.size) {
+ return;
+ }
+
+ sm.deselectAll();
+ sm.select([...allNodeModels.difference(selectedNodeModels)]);
+ },
+
+ applyUseNodePriority: function (newValue) {
+ let me = this;
+
+ let oldValue = me.getViewModel().get('showNodePriority');
+
+ if (newValue !== oldValue) {
+ me.getViewModel().set('showNodePriority', newValue);
+
+ // Prevent inverting the selection during component initialization
+ if (oldValue !== null) {
+ me.invertCheckboxSelection();
+ }
+ }
+
+ return newValue;
+ },
+
getSubmitData: function () {
let me = this;
let res = {};
@@ -91,7 +142,15 @@ Ext.define('PVE.forms.NodePrioritySelector', {
let sm = me.getSelectionModel();
let selectedNodeModels = sm.getSelection() ?? [];
let nodes = selectedNodeModels
- .map(({ data }) => data.node + (data.priority ? `:${data.priority}` : ''))
+ .map(({ data }) => {
+ let nodeEntry = data.node;
+
+ if (me.useNodePriority && data.priority) {
+ nodeEntry += `:${data.priority}`;
+ }
+
+ return nodeEntry;
+ })
.join(',');
return nodes;
diff --git a/www/manager6/ha/rules/NodeAffinityRuleEdit.js b/www/manager6/ha/rules/NodeAffinityRuleEdit.js
index 77da18b1..aecaa276 100644
--- a/www/manager6/ha/rules/NodeAffinityRuleEdit.js
+++ b/www/manager6/ha/rules/NodeAffinityRuleEdit.js
@@ -1,6 +1,15 @@
Ext.define('PVE.ha.rules.NodeAffinityInputPanel', {
extend: 'PVE.ha.RuleInputPanel',
+ viewModel: {
+ data: {
+ affinity: 'positive',
+ },
+ formulas: {
+ isPositiveNodeAffinity: (get) => get('affinity') === 'positive',
+ },
+ },
+
initComponent: function () {
let me = this;
@@ -18,6 +27,19 @@ Ext.define('PVE.ha.rules.NodeAffinityInputPanel', {
uncheckedValue: 0,
defaultValue: 0,
},
+ {
+ xtype: 'proxmoxKVComboBox',
+ name: 'affinity',
+ fieldLabel: gettext('Affinity'),
+ allowBlank: false,
+ comboItems: [
+ ['positive', gettext('Prefer Nodes')],
+ ['negative', gettext('Avoid Nodes')],
+ ],
+ bind: {
+ value: '{affinity}',
+ },
+ },
];
me.columnB = [
@@ -25,6 +47,9 @@ Ext.define('PVE.ha.rules.NodeAffinityInputPanel', {
xtype: 'pveNodePrioritySelector',
name: 'nodes',
allowBlank: false,
+ bind: {
+ useNodePriority: '{isPositiveNodeAffinity}',
+ },
},
];
diff --git a/www/manager6/ha/rules/NodeAffinityRules.js b/www/manager6/ha/rules/NodeAffinityRules.js
index 6fc42799..089dece8 100644
--- a/www/manager6/ha/rules/NodeAffinityRules.js
+++ b/www/manager6/ha/rules/NodeAffinityRules.js
@@ -11,6 +11,11 @@ Ext.define('PVE.ha.NodeAffinityRulesView', {
stateId: 'grid-ha-node-affinity-rules',
columns: [
+ {
+ header: gettext('Affinity'),
+ width: 75,
+ dataIndex: 'affinity',
+ },
{
header: gettext('Strict'),
width: 75,
--
2.47.3
next prev parent reply other threads:[~2026-06-02 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 10:01 [PATCH-SERIES docs/ha-manager/manager v2 00/12] Negative Node Affinity Rules Daniel Kral
2026-06-02 10:01 ` [PATCH ha-manager v2 01/12] rules: node affinity: add affinity property to node affinity rules Daniel Kral
2026-06-02 10:01 ` [PATCH ha-manager v2 02/12] rules: rename ambiguous argument nodes to cluster nodes Daniel Kral
2026-06-02 10:01 ` [PATCH ha-manager v2 03/12] rules: node affinity: implement negative node affinity rules Daniel Kral
2026-06-02 10:01 ` [PATCH manager v2 04/12] ui: ha: node affinity: handle non-existent nodes Daniel Kral
2026-06-02 10:01 ` [PATCH manager v2 05/12] ui: ha: node affinity: do update node selection all at once Daniel Kral
2026-06-02 10:01 ` [PATCH manager v2 06/12] ui: ha: node affinity: move node priority selector into separate component Daniel Kral
2026-06-02 10:01 ` Daniel Kral [this message]
2026-06-02 10:01 ` [PATCH manager v2 08/12] ui: ha: node affinity: do not send default node affinity rule values Daniel Kral
2026-06-02 10:01 ` [PATCH docs v2 09/12] ha-manager: rules: use the correct article for terms starting with HA Daniel Kral
2026-06-02 10:01 ` [PATCH docs v2 10/12] ha-manager: rules: improve resource affinity rule short description Daniel Kral
2026-06-02 10:01 ` [PATCH docs v2 11/12] ha-manager: rules: adapt rule configuration examples Daniel Kral
2026-06-02 10:01 ` [PATCH docs v2 12/12] ha-manager: rules: add negative node affinity rule descriptions 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=20260602100226.180071-8-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox