From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container/manager/qemu-server 0/5] add option to create HA resource upon guest create or restore
Date: Mon, 6 Oct 2025 17:52:28 +0200 [thread overview]
Message-ID: <20251006155233.267374-1-m.koeppl@proxmox.com> (raw)
This patch series aims to make the creation of a HA resource for a new
or restored guest easier for users by adding a parameter to the API that
allows adding the guest as a HA resource right away. In the web GUI, a
checkbox is added to the CreateWizard and Restore dialogs. Note that
the state of the resulting HA resource will match the value of the
'start' parameter, i.e. if 'Start after creation' is set to true, the
state of the resource will be 'started', otherwise 'stopped'. This is
done to avoid unexpected behavior for users, where 'Start after
creation' was set to false, but the default 'started' state of the HA
resource would start the VM anyway.
qemu-server:
Michael Köppl (1):
api: create/store: allow adding VM as HA resource after creation
src/PVE/API2/Qemu.pm | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
pve-container:
Michael Köppl (1):
api: create/store: allow adding CT as HA resource after creation
src/PVE/API2/LXC.pm | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
pve-manager:
Michael Köppl (3):
qemu: create: add checkbox for creating HA resource upon VM creation
lxc: create: add checkbox for creating HA resource upon CT creation
ui: restore: add checkbox for adding HA resource upon restore of guest
www/manager6/lxc/CreateWizard.js | 17 ++++++++++++++---
www/manager6/qemu/CreateWizard.js | 17 ++++++++++++++---
www/manager6/window/Restore.js | 12 ++++++++++++
3 files changed, 40 insertions(+), 6 deletions(-)
Summary over all repositories:
5 files changed, 81 insertions(+), 6 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-10-06 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 15:52 Michael Köppl [this message]
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
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=20251006155233.267374-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