From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 1/3] qemu: create: add checkbox for creating HA resource upon VM creation
Date: Tue, 07 Oct 2025 11:52:46 +0200 [thread overview]
Message-ID: <DDBZXX7ETTOV.HF8RDKL9FBZP@proxmox.com> (raw)
In-Reply-To: <74d35ac2-091f-4c2f-a98d-be6e87c0c14b@proxmox.com>
On Mon Oct 6, 2025 at 7:29 PM CEST, Thomas Lamprecht wrote:
> Am 06.10.25 um 17:52 schrieb Michael Köppl:
>> The new checkbox allows users to create a HA resource for the VM right
>> away. The 'state' of the HA resource will match the value of the "Start
>> after creation" checkbox.
>
> The idea for the start-after-create is that it's only affecting
> run state, but no config and is often decided last, that's why I
> put that flag in the docked section of the wizard.
>
> Adding to HA affects a config, not just runtime state, and it
> probably is often decided upfront if a guest should be HA or
> not; so that option *might* better fit into the general section,
> would also avoid making the docked section to crowded.
>
> And then it might be also nice to show "HA Managed: Yes" in the
> summary grid of the confirmation step.
>
> What do you think?
Thanks for the feedback! I'm a bit conflicted regarding this one. The
reason I thought it might fit better into the Confirm section is that,
while it does affect *a* config, it does not affect the config of the
VM/CT (and I don't think it should). That's also why I thought
displaying the value of ha-managed in the summary grid might be a bit
misleading, since this value will not be in the VM's/CT's config. But
it might also be that my mental model of this dialog is too strict in
assuming that everything that comes before the Confirm step is strictly
related to the config of the guest?
I would of course be open to moving the checkbox, just wanted to provide
some rationale for why I put it there. If I moved it, I think it would
make sense to move it to the Advanced section of the General tab?
_______________________________________________
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-10-07 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 15:52 [pve-devel] [PATCH container/manager/qemu-server 0/5] add option to create HA resource upon guest create or restore Michael Köppl
2025-10-06 15:52 ` [pve-devel] [PATCH qemu-server 1/1] api: create/store: allow adding VM as HA resource after creation Michael Köppl
2025-10-06 17:23 ` Thomas Lamprecht
2025-10-06 17:24 ` Thomas Lamprecht
2025-10-06 15:52 ` [pve-devel] [PATCH container 1/1] api: create/store: allow adding CT " Michael Köppl
2025-10-06 17:22 ` [pve-devel] applied: " Thomas Lamprecht
2025-10-06 15:52 ` [pve-devel] [PATCH manager 1/3] qemu: create: add checkbox for creating HA resource upon VM creation Michael Köppl
2025-10-06 17:29 ` Thomas Lamprecht
2025-10-07 9:52 ` Michael Köppl [this message]
2025-10-07 10:26 ` Thomas Lamprecht
2025-10-07 11:46 ` Michael Köppl
2025-10-07 12:42 ` Michael Köppl
2025-10-06 15:52 ` [pve-devel] [PATCH manager 2/3] lxc: create: add checkbox for creating HA resource upon CT creation Michael Köppl
2025-10-06 15:52 ` [pve-devel] [PATCH manager 3/3] ui: restore: add checkbox for adding HA resource upon restore of guest 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=DDBZXX7ETTOV.HF8RDKL9FBZP@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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