From: Daniel Krambrock via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Daniel Krambrock <krambrock@hrz.uni-marburg.de>
Subject: [pve-devel] [PATCH container] close #4369: make VMID suggestion strategy configurable
Date: Wed, 22 May 2024 14:05:52 +0200 [thread overview]
Message-ID: <mailman.226.1716379935.319.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <20240522120553.49114-1-krambrock@hrz.uni-marburg.de>
[-- Attachment #1: Type: message/rfc822, Size: 4483 bytes --]
From: Daniel Krambrock <krambrock@hrz.uni-marburg.de>
To: pve-devel@lists.proxmox.com
Subject: [PATCH container] close #4369: make VMID suggestion strategy configurable
Date: Wed, 22 May 2024 14:05:52 +0200
Message-ID: <20240522120553.49114-4-krambrock@hrz.uni-marburg.de>
on container deletion the VMID is added to the list of previously used
VMIDs
Signed-off-by: Daniel Krambrock <krambrock@hrz.uni-marburg.de>
---
src/PVE/API2/LXC.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index 138288c..f71f005 100644
--- a/src/PVE/API2/LXC.pm
+++ b/src/PVE/API2/LXC.pm
@@ -799,6 +799,7 @@ __PACKAGE__->register_method({
my $realcmd = sub { PVE::LXC::Config->lock_config($vmid, $code); };
+ PVE::UsedVmidList::add_vmid($vmid);
return $rpcenv->fork_worker('vzdestroy', $vmid, $authuser, $realcmd);
}});
--
2.39.2
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
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:[~2024-05-22 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240522120553.49114-1-krambrock@hrz.uni-marburg.de>
2024-05-22 12:05 ` [pve-devel] [PATCH manager] " Daniel Krambrock via pve-devel
2024-05-22 12:05 ` [pve-devel] [PATCH cluster] " Daniel Krambrock via pve-devel
2024-05-22 12:05 ` Daniel Krambrock via pve-devel [this message]
2024-05-22 12:05 ` [pve-devel] [PATCH qemu] " Daniel Krambrock via pve-devel
2024-06-05 8:56 ` [pve-devel] (no subject) Shannon Sterz
[not found] ` <20240522120553.49114-2-krambrock@hrz.uni-marburg.de>
2024-06-05 8:57 ` [pve-devel] [PATCH manager] close #4369: make VMID suggestion strategy configurable Shannon Sterz
[not found] ` <20240522120553.49114-3-krambrock@hrz.uni-marburg.de>
2024-06-05 8:57 ` [pve-devel] [PATCH cluster] " Shannon Sterz
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=mailman.226.1716379935.319.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=krambrock@hrz.uni-marburg.de \
/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