From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <proxmox@elchaka.de>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id CE2D79EA3A
 for <pve-user@lists.proxmox.com>; Fri,  3 Nov 2023 00:23:10 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id A7493162CE
 for <pve-user@lists.proxmox.com>; Fri,  3 Nov 2023 00:22:40 +0100 (CET)
Received: from taris.securewebs.net (taris.securewebs.net [185.3.234.240])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS
 for <pve-user@lists.proxmox.com>; Fri,  3 Nov 2023 00:22:36 +0100 (CET)
X-PDA-ORIGIN: taris.securewebs.net
Received: (qmail 19314 invoked from network); 2 Nov 2023 23:15:14 -0000
Received: by simscan 1.4.0 ppid: 19303, pid: 19309, t: 0.2943s
 scanners: clamav: 0.103.8/m:62/d:27080
Received: from unknown (HELO ?127.0.0.1?) (mt@elchaka.de@176.198.200.40)
 by 0 with ESMTPS (TLS_AES_128_GCM_SHA256 encrypted); 2 Nov 2023 23:15:14 -0000
Date: Fri, 03 Nov 2023 00:15:11 +0100
From: proxmox@elchaka.de
To: uwe.sauter.de@gmail.com, Proxmox VE user list <pve-user@lists.proxmox.com>
User-Agent: K-9 Mail for Android
Reply-to: proxmox@elchaka.de
In-Reply-To: <7fb6b78c-8a6d-496f-ac3e-89910c34b6d3@gmail.com>
References: <7fb6b78c-8a6d-496f-ac3e-89910c34b6d3@gmail.com>
Message-ID: <ADB562A5-6601-4D0C-8464-D41E91DCC6AE@elchaka.de>
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results:  0
 AWL 1.673 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 HTML_MESSAGE            0.001 HTML included in message
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery
 methods
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_NONE                0.001 SPF: sender does not publish an SPF Record
 T_SCC_BODY_TEXT_LINE    -0.01 -
 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See
 http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more
 information. [proxmox.com]
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
Subject: Re: [PVE-User] Question regarding resource pools and assigning not
 yet used IDs
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 02 Nov 2023 23:23:10 -0000

As far as i know you can just define=20

Start id
End id

Via datacenter - options - next free vmid=2E=2E=2E

This is valid for a cluster or a single mode installation if i am not wron=
g

Hth
Mehmet

Am 23=2E Oktober 2023 23:17:23 MESZ schrieb Uwe Sauter <uwe=2Esauter=2Ede@=
gmail=2Ecom>:
>Hi all,
>
>reading the documentation about user management [1] and especially about =
resource pools I keep wondering if there is a way to pre-assign IDs to reso=
urce pools so that a group with the necessary permissions can create new VM=
s within the pre-assigned ID range=2E
>
>E=2Eg=2E I have two groups, let's call them A and B=2E In order to keep o=
rder in the Proxmox cluster, I'd like to give each group a certain ID range=
 within they can manage (and create) their one VMs, say
>
>A -> IDs 300-349
>B -> IDs 350-379
>
>As far as I understand the documentation (and please correct me if I'm wr=
ong) there is no way to do this=2E What I understand is that once a VM is c=
reated and has an ID assigned some admin with higher privileges needs to as=
sign said VM to a resource pool so that it than can be managed by the respe=
ctive group=2E
>
>If this is correct the concept of resource pools seems to be lacking an i=
mportant feature to lower the administrative burden=2E
>
>The WebUI also shows no way to define such a range=2E When I browse to da=
tacenter -> resource pool -> mypool and try to add a VM I can only select e=
xisting ones=2E
>(What I also noticed is that you cannot add containers to a pool=E2=80=A6=
 though I don't know if that would make sense=2E)
>
>
>Thanks,
>
>	Uwe
>
>
>[1] https://pve=2Eproxmox=2Ecom/pve-docs/chapter-pveum=2Ehtml
>
>_______________________________________________
>pve-user mailing list
>pve-user@lists=2Eproxmox=2Ecom
>https://lists=2Eproxmox=2Ecom/cgi-bin/mailman/listinfo/pve-user