From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id CC4091FF09C for ; Mon, 21 Sep 2026 17:55:03 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 0EBD62165C; Mon, 21 Sep 2026 17:54:27 +0200 (CEST) From: =?UTF-8?q?Michael=20K=C3=B6ppl?= To: pve-devel@lists.proxmox.com Subject: [PATCH pve-cluster v5 2/7] datacenter config: add unique-next-id to schema Date: Mon, 21 Sep 2026 17:54:05 +0200 Message-ID: <20260921155410.938337-3-m.koeppl@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260921155410.938337-1-m.koeppl@proxmox.com> References: <20260921155410.938337-1-m.koeppl@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1790006059155 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.551 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: HCEX2HGSD3A74XRD5BTSNAPNRPT2KXZN X-Message-ID-Hash: HCEX2HGSD3A74XRD5BTSNAPNRPT2KXZN X-MailFrom: m.koeppl@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Severen Redwood Add the `unique-next-id` property to the datacenter config schema to track whether only unique (ie. neither currently nor previously in use) VM/CT IDs should be suggested by the `/cluster/nextid` API endpoint. Co-authored-by: Daniel Krambrock Signed-off-by: Severen Redwood [MK: use datacenter in commit message instead of datacentre] Signed-off-by: Michael Köppl --- src/PVE/DataCenterConfig.pm | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/PVE/DataCenterConfig.pm b/src/PVE/DataCenterConfig.pm index 004122e..54f9c10 100644 --- a/src/PVE/DataCenterConfig.pm +++ b/src/PVE/DataCenterConfig.pm @@ -415,6 +415,12 @@ my $datacenter_schema = { format => $next_id_format, description => "Control the range for the free VMID auto-selection pool.", }, + 'unique-next-id' => { + optional => 1, + type => 'boolean', + description => + "Only suggest VMIDs that are neither currently in use nor have previously been used.", + }, migration => { optional => 1, type => 'string', -- 2.47.3