From: Max Carrara <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/2] pveum: sort roles and privileges alphabetically
Date: Mon, 10 Jul 2023 17:10:13 +0200 [thread overview]
Message-ID: <20230710151013.2348741-2-m.carrara@proxmox.com> (raw)
In-Reply-To: <20230710151013.2348741-1-m.carrara@proxmox.com>
Signed-off-by: Max Carrara <m.carrara@proxmox.com>
---
NOTE: Thought it would make these two little sections a little more
readable if their list items were sorted alphabetically; if that's not
desired, then this commit can be dropped.
pveum.adoc | 48 ++++++++++++++++++++++++------------------------
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/pveum.adoc b/pveum.adoc
index 6a806ef..3ff7f43 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -776,13 +776,13 @@ of predefined roles, which satisfy most requirements.
* `PVEMappingUser`: view and use resource mappings
* `PVEPoolAdmin`: allocate pools
* `PVEPoolUser`: view pools
+* `PVESDNAdmin`: manage SDN configuration
+* `PVESDNUser`: access to bridges/vnets
* `PVESysAdmin`: audit, system console and system logs
* `PVETemplateUser`: view and clone templates
* `PVEUserAdmin`: manage users
* `PVEVMAdmin`: fully administer VMs
* `PVEVMUser`: view, backup, configure CD-ROM, VM console, VM power management
-* `PVESDNAdmin`: manage SDN configuration
-* `PVESDNUser`: access to bridges/vnets
You can see the whole set of predefined roles in the GUI.
@@ -816,46 +816,46 @@ We currently support the following privileges:
Node / System related privileges::
-* `Permissions.Modify`: modify access permissions
-* `Sys.PowerMgmt`: node power management (start, stop, reset, shutdown, ...)
-* `Sys.Console`: console access to node
-* `Sys.Syslog`: view syslog
-* `Sys.Audit`: view node status/config, Corosync cluster config, and HA config
-* `Sys.Modify`: create/modify/remove node network parameters
-* `Sys.Incoming`: allow incoming data streams from other clusters (experimental)
* `Group.Allocate`: create/modify/remove groups
+* `Mapping.Audit`: view resource mappings
+* `Mapping.Modify`: manage resource mappings
+* `Mapping.Use`: use resource mappings
+* `Permissions.Modify`: modify access permissions
* `Pool.Allocate`: create/modify/remove a pool
* `Pool.Audit`: view a pool
-* `Realm.Allocate`: create/modify/remove authentication realms
* `Realm.AllocateUser`: assign user to a realm
-* `User.Modify`: create/modify/remove user access and details.
+* `Realm.Allocate`: create/modify/remove authentication realms
* `SDN.Allocate`: manage SDN configuration
* `SDN.Audit`: view SDN configuration
-* `Mapping.Modify`: manage resource mappings
-* `Mapping.Audit`: view resource mappings
-* `Mapping.Use`: use resource mappings
+* `Sys.Audit`: view node status/config, Corosync cluster config, and HA config
+* `Sys.Console`: console access to node
+* `Sys.Incoming`: allow incoming data streams from other clusters (experimental)
+* `Sys.Modify`: create/modify/remove node network parameters
+* `Sys.PowerMgmt`: node power management (start, stop, reset, shutdown, ...)
+* `Sys.Syslog`: view syslog
+* `User.Modify`: create/modify/remove user access and details.
Virtual machine related privileges::
+* `SDN.Use`: access SDN vnets and local network bridges
* `VM.Allocate`: create/remove VM on a server
-* `VM.Migrate`: migrate VM to alternate server on cluster
-* `VM.PowerMgmt`: power management (start, stop, reset, shutdown, ...)
-* `VM.Console`: console access to VM
-* `VM.Monitor`: access to VM monitor (kvm)
-* `VM.Backup`: backup/restore VMs
* `VM.Audit`: view VM config
+* `VM.Backup`: backup/restore VMs
* `VM.Clone`: clone/copy a VM
-* `VM.Config.Disk`: add/modify/remove disks
* `VM.Config.CDROM`: eject/change CD-ROM
* `VM.Config.CPU`: modify CPU settings
+* `VM.Config.Cloudinit`: modify Cloud-init parameters
+* `VM.Config.Disk`: add/modify/remove disks
+* `VM.Config.HWType`: modify emulated hardware types
* `VM.Config.Memory`: modify memory settings
* `VM.Config.Network`: add/modify/remove network devices
-* `VM.Config.HWType`: modify emulated hardware types
* `VM.Config.Options`: modify any other VM configuration
-* `VM.Config.Cloudinit`: modify Cloud-init parameters
-* `VM.Snapshot`: create/delete VM snapshots
+* `VM.Console`: console access to VM
+* `VM.Migrate`: migrate VM to alternate server on cluster
+* `VM.Monitor`: access to VM monitor (kvm)
+* `VM.PowerMgmt`: power management (start, stop, reset, shutdown, ...)
* `VM.Snapshot.Rollback`: rollback VM to one of its snapshots
-* `SDN.Use`: access SDN vnets and local network bridges
+* `VM.Snapshot`: create/delete VM snapshots
Storage related privileges::
--
2.39.2
next prev parent reply other threads:[~2023-07-10 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 15:10 [pve-devel] [PATCH docs 1/2] pveum: add missing roles and privileges Max Carrara
2023-07-10 15:10 ` Max Carrara [this message]
2023-07-17 14:11 ` [pve-devel] applied: " Thomas Lamprecht
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=20230710151013.2348741-2-m.carrara@proxmox.com \
--to=m.carrara@proxmox.com \
--cc=pve-devel@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