From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v2] ui: node: use plug icon for node shutdown
Date: Tue, 15 Jul 2025 21:50:40 +0200 [thread overview]
Message-ID: <82578bf3-0d7d-459a-8096-7cc7215605d3@proxmox.com> (raw)
In-Reply-To: <f4ed2805-e3ef-4245-837f-ae68fca743c0@proxmox.com>
Am 14.07.25 um 12:48 schrieb Dominik Csapak:
> I don't think we'll prevent all users from mis-clicking the button with this change,
> but having a different Icon can probably avoid *some* confusion.
>
> I don't really like that this icon would imply we 'pull the plug',
> but there is sadly not really a better icon that is different from
> the shutdown one.
>
> I'm a bit unsure myself, but *if* we want to have a different icon here than for
> the guest shutdown, consider this patch:
Checking this out I'm also not sure about this.
IMO it might be a better option to have different confirmation
prompts, where the one for the node has some more info, like the
amount of running guests that might be affected, or a hint that the
cluster might loose quorum if that nodes is shutdown, like if in a
three node cluster one node is already unavailable and then the user
continues to shutdown another one - can be fine, but would not hurt
to get some extra hint about implications.
Yet another thing might be offering to optionally give a shutdown
reason, i.e. some predefined (appllying updates, maintenance) and
a free form one. A bit like what windows server does, and while I
normally really do not want to take that as prime example for good
UX, it might have some value for orgs with multiple admins to see
the original reason behind a shutdown or reboot.
Maybe there is more, but that's implementation details, having
any of that info there would make the dialogue much more visual
distinct and informational compared to a slightly different button
icon, especially for users with (slightly) impaired visual senses.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-15 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 9:52 Aaron Lauterer
2025-07-14 10:48 ` Dominik Csapak
2025-07-15 19:50 ` Thomas Lamprecht [this message]
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=82578bf3-0d7d-459a-8096-7cc7215605d3@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=d.csapak@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