public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Severen Redwood <severen.redwood@sitehost.co.nz>,
	pve-devel@lists.proxmox.com
Cc: t.lamprecht@proxmox.com
Subject: Re: [pve-devel] [PATCH container v3] api: record CT ID as used after a container is destroyed
Date: Tue, 5 Nov 2024 16:49:13 +0100	[thread overview]
Message-ID: <fda21eda-689b-481d-a4c7-ea200ad66238@proxmox.com> (raw)
In-Reply-To: <20241105020054.215734-3-severen.redwood@sitehost.co.nz>

beside one small nit that could be cleaned up in a follow-up,

consider this:

Tested-By: Aaron Lauterer <a.lauterer@proxmox.com>
Reviewed-By: Aaron Lauterer <a.lauterer@proxmox.com>


On  2024-11-05  03:00, Severen Redwood wrote:
> After a container is destroyed, record that its ID has been used via the
> `PVE::UsedVmidList` module so that the `/cluster/nextids` endpoint can
> later optionally avoid suggesting previously used IDs.
> 
> Co-authored-by: Daniel Krambrock <krambrock@hrz.uni-marburg.de>
> Signed-off-by: Severen Redwood <severen.redwood@sitehost.co.nz>
> ---
> Changed since v2 is the addition of the use statement for `PVE::UsedVmidList`.
> 
>   src/PVE/API2/LXC.pm | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
> index 213e518..cc47c5c 100644
> --- a/src/PVE/API2/LXC.pm
> +++ b/src/PVE/API2/LXC.pm
> @@ -28,6 +28,7 @@ use PVE::API2::LXC::Config;
>   use PVE::API2::LXC::Status;
>   use PVE::API2::LXC::Snapshot;
>   use PVE::JSONSchema qw(get_standard_option);
> +use PVE::UsedVmidList qw(add_vmid);

adding the `qw(add_vmid)` here is not strictly necessary, AFAIU. We call 
the function with the full PVE::UsedVmidList:: prefix anyway.

>   use base qw(PVE::RESTHandler);
>   
>   BEGIN {
> @@ -794,7 +795,9 @@ __PACKAGE__->register_method({
>   		}
>   	    }
>   
> -	    # only now remove the zombie config, else we can have reuse race
> +	    # only now mark the CT ID as previously used and remove the zombie
> +	    # config, else we can have reuse race
> +	    PVE::UsedVmidList::add_vmid($vmid);
>   	    PVE::LXC::Config->destroy_config($vmid);
>   	};
>   



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2024-11-05 15:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  1:58 [pve-devel] [PATCH SERIES v3] Add ability to prevent suggesting previously used VM/CT IDs Severen Redwood via pve-devel
2024-11-05  2:00 ` [pve-devel] [PATCH manager v3 1/2] close #4369: api: optionally only suggest unique IDs Severen Redwood via pve-devel
     [not found] ` <20241105020054.215734-1-severen.redwood@sitehost.co.nz>
2024-11-05  2:00   ` [pve-devel] [PATCH manager v3 2/2] close #4369: ui: add datacenter option for unique VM/CT IDs Severen Redwood via pve-devel
2024-11-05  2:00   ` [pve-devel] [PATCH container v3] api: record CT ID as used after a container is destroyed Severen Redwood via pve-devel
2024-11-05  2:00   ` [pve-devel] [PATCH qemu-server v3] api: record VM ID as used after a virtual machine " Severen Redwood via pve-devel
2024-11-05  2:00   ` [pve-devel] [PATCH cluster v3 5/6] cluster files: add used_vmids.list Severen Redwood via pve-devel
2024-11-05  2:00   ` [pve-devel] [PATCH cluster v3 6/6] datacenter config: add unique-next-id to schema Severen Redwood via pve-devel
     [not found]   ` <20241105020054.215734-3-severen.redwood@sitehost.co.nz>
2024-11-05 15:49     ` Aaron Lauterer [this message]
     [not found]   ` <20241105020054.215734-4-severen.redwood@sitehost.co.nz>
2024-11-05 15:50     ` [pve-devel] [PATCH qemu-server v3] api: record VM ID as used after a virtual machine is destroyed Aaron Lauterer
2024-11-05 15:53   ` [pve-devel] [PATCH manager v3 1/2] close #4369: api: optionally only suggest unique IDs Aaron Lauterer

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=fda21eda-689b-481d-a4c7-ea200ad66238@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=severen.redwood@sitehost.co.nz \
    --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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal