public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Question regarding resource pools and assigning not yet used IDs
Date: Mon, 23 Oct 2023 23:17:23 +0200	[thread overview]
Message-ID: <7fb6b78c-8a6d-496f-ac3e-89910c34b6d3@gmail.com> (raw)

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



             reply	other threads:[~2023-10-23 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 21:17 Uwe Sauter [this message]
2023-11-02 23:15 ` proxmox

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=7fb6b78c-8a6d-496f-ac3e-89910c34b6d3@gmail.com \
    --to=uwe.sauter.de@gmail.com \
    --cc=pve-user@lists.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