From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] User permissions for some hosts
Date: Thu, 03 Sep 2020 14:14:41 +0200 [thread overview]
Message-ID: <1599134462.pm42d9isdh.astroid@nora.none> (raw)
In-Reply-To: <88f905da-f9cc-4636-3f54-c653f48b78c4@ecos.de>
On September 3, 2020 12:36 pm, Tobias Guth wrote:
> Hi,
>
> I have posted some issue on the pve forum regarding user permissions on
> some pve hosts.
> (https://forum.proxmox.com/threads/permission-set-for-specific-hosts.75138/)
>
> but no answer so far.
>
> I try to give some usergroup the permission to create/delete/modify
> virtual machines on just 2 hosts of our cluster.
> But I have no luck to configure the right permissions that this group
> can not modify or delete virtual machines on the hosts.
> There is no namespace like /vms/nodes or /vms/node1, just /vms.
permissions don't work on that level. you might be able to somewhat work
around it (e.g., with a storage that is only available on a subset of
nodes), but that is more of a hack than anything else.
> Is there any way to configure this ?
>
> And one more question. Was exatly does the propagade option with
> permissions ?
> Does it mean to propagade given permissions through out the cluster ?
propagate means set this role on subpaths as well, unless they have a
more specific role set.
e.g., if you give some role A to user X on path /vms with propagate set,
and additionally give role B to user X on path /vms/123, user X is 'A'
for all VMs except 123, where they are 'B'. on recent PVE versions, you
can use 'pveum user permissions' to get a list of effective permissions,
either for all paths with an ACL (also available as button in the User
management GUI), or for a specific path.
parent reply other threads:[~2020-09-03 12:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <88f905da-f9cc-4636-3f54-c653f48b78c4@ecos.de>]
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=1599134462.pm42d9isdh.astroid@nora.none \
--to=f.gruenbichler@proxmox.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 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.