From: Severen Redwood via pve-devel <pve-devel@lists.proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Severen Redwood <severen.redwood@sitehost.co.nz>
Subject: Re: [pve-devel] [PATCH cluster v4 1/2] cluster files: add used_vmids.list
Date: Fri, 28 Mar 2025 10:02:23 +1300 [thread overview]
Message-ID: <mailman.284.1743109368.359.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <ac5ac659-a5be-4e83-a6fe-c1e01b43fc44@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 4475 bytes --]
From: Severen Redwood <severen.redwood@sitehost.co.nz>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH cluster v4 1/2] cluster files: add used_vmids.list
Date: Fri, 28 Mar 2025 10:02:23 +1300
Message-ID: <441cec36-60f0-45ab-841f-e85d2949a063@sitehost.co.nz>
On 26/03/2025 20:22, Thomas Lamprecht wrote:
> Am 26.03.25 um 04:51 schrieb Severen Redwood:
>> No problem, I've changed it to `/etc/pve/used-ids` now. Slightly more generic than `used-vmids` since there are also container IDs.
>
> Hmm, I see where you come from, but that's IMO making it a bit overly
> generic, there are many IDs in a Proxmox VE system.
>
> So let's go for something a bit more specific while still ensuring it's
> not suggesting that this is purely for VMs, like e.g. `used-guest-ids`
> as we normally use virtual guest in places where we talk about both, CTs
> and VMs.
This makes sense to me. I will post the updated patches today with that filename :)
[-- 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:[~2025-03-27 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 1:44 [pve-devel] [PATCH SERIES v4] Add ability to prevent suggesting previously used VM/CT IDs Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH manager v4 1/2] close #4369: api: optionally only suggest unique IDs Severen Redwood via pve-devel
2025-01-27 12:16 ` Fabian Grünbichler
2025-03-26 3:50 ` Severen Redwood via pve-devel
[not found] ` <20241108014620.73352-1-severen.redwood@sitehost.co.nz>
2024-11-08 1:46 ` [pve-devel] [PATCH manager v4 2/2] close #4369: ui: add datacenter option for unique VM/CT IDs Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH cluster v4 1/2] cluster files: add used_vmids.list Severen Redwood via pve-devel
2025-01-27 12:18 ` Fabian Grünbichler
2025-01-28 14:57 ` Thomas Lamprecht
2025-03-26 3:51 ` Severen Redwood via pve-devel
[not found] ` <fd441572-6c7c-4b62-bdef-0d738ac699fb@sitehost.co.nz>
2025-03-26 7:22 ` Thomas Lamprecht
2025-03-27 21:02 ` Severen Redwood via pve-devel [this message]
2024-11-08 1:46 ` [pve-devel] [PATCH cluster v4 2/2] datacenter config: add unique-next-id to schema Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH qemu-server v4] api: record VM ID as used after a virtual machine is destroyed Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH container v4] api: record CT ID as used after a container " Severen Redwood via pve-devel
2025-01-27 12:16 ` Fabian Grünbichler
2025-03-26 3:51 ` Severen Redwood via pve-devel
2024-12-03 21:43 ` [pve-devel] [PATCH SERIES v4] Add ability to prevent suggesting previously used VM/CT IDs Severen Redwood via pve-devel
[not found] ` <d39f8d05-d5a6-48c9-996a-dca751f62ff3@sitehost.co.nz>
2025-01-19 22:01 ` Severen Redwood via pve-devel
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.284.1743109368.359.pve-devel@lists.proxmox.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal