From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 0/2] refresh affinity rules on edit to display conflicts
Date: Fri, 1 Aug 2025 18:58:43 +0200 [thread overview]
Message-ID: <20250801165845.97353-1-m.koeppl@proxmox.com> (raw)
The goal of this is to refresh both affinity rules stores to
immediately display any conflicts. Without this change, users have to
refresh the page to see conflicts on resource affinity rules after they
added a node affinity rule that was in conflict (and vice-versa).
The second patch is formatting through `make tidy`.
pve-manager:
Michael Köppl (2):
ui: ha: refresh rules lists on edit to display conflicts immediately
run make tidy
www/manager6/ha/Rules.js | 118 ++++++++++++++++++++++++---------------
1 file changed, 73 insertions(+), 45 deletions(-)
Summary over all repositories:
1 files changed, 73 insertions(+), 45 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-08-01 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 16:58 Michael Köppl [this message]
2025-08-01 16:58 ` [pve-devel] [PATCH manager 1/2] ui: ha: refresh rules lists on edit to display conflicts immediately Michael Köppl
2025-08-01 16:58 ` [pve-devel] [PATCH manager 2/2] run make tidy Michael Köppl
2025-08-02 12:51 ` Thomas Lamprecht
2025-08-02 17:31 ` [pve-devel] [PATCH manager 0/2] refresh affinity rules on edit to display conflicts Thomas Lamprecht
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=20250801165845.97353-1-m.koeppl@proxmox.com \
--to=m.koeppl@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