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 ha-manager/manager/proxmox-widget-toolkit 0/3] remove
Date: Fri, 19 Sep 2025 16:41:53 +0200 [thread overview]
Message-ID: <DCWUTHDDHUBQ.I004WXSXZD8E@proxmox.com> (raw)
In-Reply-To: <20250919140620.243497-1-m.koeppl@proxmox.com>
On Fri Sep 19, 2025 at 4:06 PM CEST, Michael Köppl wrote:
> Even though groups have been replaced with rules in PVE 9, the guest
> summary still displayed "Groups: none" for VMs and CTs. This patch
> series removes this information from the HA status information and also
> removes the remnants of it in the widget-toolkit and ha-manager.
>
> The patch series does not add information about rules as a replacement
> for the following reasons:
> - There is no 1:1 mapping of resources to groups anymore, so a resource
> could potentially have many rules, cluttering the summary page
> - Finding the rules that reference the given resource adds more
> complexity compared to finding the group for information that can be
> be viewed in a less cluttered manner on the rules page.
Thanks!
The changes look good to me.
Just to link these here, there were two community forum posts [0] and
[1], which added some more viewpoints how HA groups are/were used and
what could still be improved for the HA rules.
The pain points were primarily that users could add/remove HA resources
to/from HA groups directly through the VM/CT in the web interface under
More > Manage HA and then select the assigned HA group there, instead of
going to the Datacenter > HA tab.
For HA node affinity rules, the former isn't possible anymore and the
main workflow is to add the HA resources and then add them to a node
affinity rule in bulk there. I'm not sure how we could improve that yet.
[0] https://forum.proxmox.com/threads/172190/
Anyway:
Reviewed-by: Daniel Kral <d.kral@proxmox.com>
_______________________________________________
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-09-19 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 14:06 Michael Köppl
2025-09-19 14:06 ` [pve-devel] [PATCH manager 1/1] ui: ha: remove group info from HA status string in guest status view Michael Köppl
2025-09-19 14:06 ` [pve-devel] [PATCH widget-toolkit 1/1] remove unused groupText mapping Michael Köppl
2025-09-19 14:06 ` [pve-devel] [PATCH ha-manager 1/1] config: remove groups field from service status data Michael Köppl
2025-09-19 14:41 ` Daniel Kral [this message]
2025-09-19 15:06 ` [pve-devel] [PATCH ha-manager/manager/proxmox-widget-toolkit 0/3] remove Michael Köppl
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=DCWUTHDDHUBQ.I004WXSXZD8E@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 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.