From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <uwe.sauter.de@gmail.com>
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) server-digest SHA256)
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 8AE1D9C337
 for <pve-user@lists.proxmox.com>; Mon, 23 Oct 2023 23:18:04 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 6FAAB18BA6
 for <pve-user@lists.proxmox.com>; Mon, 23 Oct 2023 23:17:34 +0200 (CEST)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com
 [IPv6:2a00:1450:4864:20::22a])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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>; Mon, 23 Oct 2023 23:17:32 +0200 (CEST)
Received: by mail-lj1-x22a.google.com with SMTP id
 38308e7fff4ca-2c5087d19a6so56428181fa.0
 for <pve-user@lists.proxmox.com>; Mon, 23 Oct 2023 14:17:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20230601; t=1698095845; x=1698700645; darn=lists.proxmox.com;
 h=content-transfer-encoding:subject:from:content-language:reply-to:to
 :user-agent:mime-version:date:message-id:from:to:cc:subject:date
 :message-id:reply-to;
 bh=D9w9K4fJ0SI+laiwOdJFqozXbid7LlEy3ZEWwYnZcy4=;
 b=kF8MPLcPgnxhoSSfpYzu58PPLJyHS5/sTGqBRx71jxoUSNslFrz2W8htKxRw9G5MmI
 bvhLvzZ3hSAoJnLZBpsnykNP2QR4QeBhSu6zIqk51reoQL5JAn4or5vF9gQoCOeylGyW
 7mSTXKSpaO2bw+tL/hCak+XyEBNyWAQcRQv6G1ZYM8IYxjz6xMDR5KlxZKHF+3W3Adm0
 9Gj6cO/hi6T6zLnxn3suAy0Ss8O8msDxLKeUo7M7Vr7raKuQSJq2Kh6tCl/YzPp6RgAZ
 YSgcY9uOTrshaaGUul5SJxhHzGVmgjGKgUOQDUh7CvtQASm+jaO57C7FezgIHoYbd5AA
 W2aQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1698095845; x=1698700645;
 h=content-transfer-encoding:subject:from:content-language:reply-to:to
 :user-agent:mime-version:date:message-id:x-gm-message-state:from:to
 :cc:subject:date:message-id:reply-to;
 bh=D9w9K4fJ0SI+laiwOdJFqozXbid7LlEy3ZEWwYnZcy4=;
 b=YY5MRd6AYGwMCt5TeFp63+CoaOwfJU8uz5F5z+TaQ4CjI0RkWq1dCUFOLSTRIeDbNy
 hLWSjOfrtq2zOa0whGXPDh/zWCb+9UVKfyQjOZYTKEJBW01fd6859NOSo/FQprA4HsYk
 mIHFURNoD2SFG8IIzptw1G0msIWHNFsWHHoKCZ3pA0rpvRai533rwGn9RJ/ccKb3eo1E
 wDoP0qgUtmKh6sjthVqcXbUnIRZATnSTpRF2nRFRsol0EGHjt+3dYFTQfeDC2qgpoaPy
 SamVaqaDmFMUCPEFDlh0AYPCAE8fbNzr0ER0lIdobe/tPtobnpEmHshtm7FaDS+5RV6R
 cIMg==
X-Gm-Message-State: AOJu0YwWRFUh+Vzo+GMb7CqCoEeDTok2NTXPcMxCZ7/6a/9AgLXwC7ZF
 NP1PCZvjthvTisgjHMK0vFc08P+UyHE=
X-Google-Smtp-Source: AGHT+IHd9JdBlrXTGiiaIHO6FQoa8PtZCkedv+4cDjrG6VZ43rTcR6wVnKn2N4W+RFsithuB4vCxrg==
X-Received: by 2002:a05:651c:306:b0:2c4:feef:64ee with SMTP id
 a6-20020a05651c030600b002c4feef64eemr6203703ljp.50.1698095844579; 
 Mon, 23 Oct 2023 14:17:24 -0700 (PDT)
Received: from [192.168.49.44] (ip-109-192-041-223.um38.pools.vodafone-ip.de.
 [109.192.41.223]) by smtp.gmail.com with ESMTPSA id
 m16-20020a7bca50000000b00405d9a950a2sm14842797wml.28.2023.10.23.14.17.23
 for <pve-user@lists.proxmox.com>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Mon, 23 Oct 2023 14:17:24 -0700 (PDT)
Message-ID: <7fb6b78c-8a6d-496f-ac3e-89910c34b6d3@gmail.com>
Date: Mon, 23 Oct 2023 23:17:23 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: pve-user@lists.proxmox.com
Reply-To: uwe.sauter.de@gmail.com
Content-Language: de-DE, en-US
From: Uwe Sauter <uwe.sauter.de@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-SPAM-LEVEL: Spam detection results:  0
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DKIM_SIGNED               0.1 Message has a DKIM or DK signature,
 not necessarily valid
 DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
 DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's
 domain
 DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from
 domain DMARC_PASS               -0.1 DMARC pass policy
 FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider
 RCVD_IN_DNSWL_NONE     -0.0001 Sender listed at https://www.dnswl.org/,
 no trust
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
 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]
Subject: [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: Mon, 23 Oct 2023 21:18:04 -0000

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 resource pools so that a group with the necessary permissions can create new VMs within the 
pre-assigned ID range.

E.g. I have two groups, let's call them A and B. In order to keep order 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 wrong) there is no way to do this. What I 
understand is that once a VM is created and has an ID assigned some admin with higher privileges needs to assign said VM 
to a resource pool so that it than can be managed by the respective group.

If this is correct the concept of resource pools seems to be lacking an important feature to lower the administrative 
burden.

The WebUI also shows no way to define such a range. When I browse to datacenter -> resource pool -> mypool and try to 
add a VM I can only select existing ones.
(What I also noticed is that you cannot add containers to a pool… though I don't know if that would make sense.)


Thanks,

	Uwe


[1] https://pve.proxmox.com/pve-docs/chapter-pveum.html