More granular permissions (and documentation about it)
Bug #1949901 reported by
Garrett Neugent
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Medium
|
Bill Wear | ||
Bug Description
Hello,
I was hoping to:
1) learn more information about the different permissions levels in MAAS, and
2) also request that more granular control be made available.
During a cloud handover, we have two teams that are working on separate clouds within a single datacenter. We originally tried to have one team retain admin access, but the second team was not able to add new KVMs, even on machines that they had acquired, and were shown as being owned by them in the CLI/UI.
This is a bit of a duplicate of LP#1714106, but I'm hoping that it can also be used as a request to update the documentation [0] with more information for future readers.
Thanks for your time!
Revision history for this message
| Björn Tillenius (bjornt) wrote | #1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: doc |
Revision history for this message
| Jerzy Husakowski (jhusakowski) wrote | #2 |
| Changed in maas: | |
| assignee: | nobody → Bill Wear (billwear) |
| importance: | High → Medium |
| milestone: | none → 3.4.0 |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.4.x |
To post a comment you must log in.
The way we do granular access is through our RBAC services, which is available to paying support customers.
It may or not do what you need. I'm keeping this bug open, since we still need to document the RBAC service and the permissions it provides.