From: Philipp Hufnagl <p.hufnagl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager v3 0/2] fix #474: allow transfer from container/vms
Date: Wed, 9 Aug 2023 16:49:02 +0200 [thread overview]
Message-ID: <20230809144904.1359074-1-p.hufnagl@proxmox.com> (raw)
changes to v3:
fix subject typo
at version log
changes to v2:
split patch in front and backend
When a member of 2 pools wants to transfer a
vm/container to an other pool they can not do that. The vm/container would
have first to be removed form the current pool resulting in a loss of
privileges of the pool member for this vm/contianer. This feature introduces
a way to transfer a vm between pools, guarded by a checkbox from accidental
transfers
Philipp Hufnagl (2):
fix #474: backend allow transfer from container/vms
fix #474: backend allow transfer from container/vms
PVE/API2/Pool.pm | 15 +++++++++++++--
www/manager6/grid/PoolMembers.js | 17 ++++++++++++++---
2 files changed, 27 insertions(+), 5 deletions(-)
--
2.39.2
next reply other threads:[~2023-08-09 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 14:49 Philipp Hufnagl [this message]
2023-08-09 14:49 ` [pve-devel] [PATCH manager v3 1/2] fix #474: backend: " Philipp Hufnagl
2023-08-09 14:49 ` [pve-devel] [PATCH manager v3 2/2] fix #474: frontend: " Philipp Hufnagl
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=20230809144904.1359074-1-p.hufnagl@proxmox.com \
--to=p.hufnagl@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