Utilizing Role Base Access Control for managing Multi-tenancy

Bug #1567446 reported by Adam Young
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Expired
Wishlist
Unassigned

Bug Description

After creating a new project and allocating some amount of resources, we should be able to create a hierarchy of users like Project Manager (PM) having complete view of the project usage, then PM should be able to allocate resources to different sub-teams (like Dev, QA, Prod, etc), each sub-team leads having access to their allocated resources and able to manage the resources at their level with approval from the PM. All the users will be AD authenticated ones.

Changed in keystone:
assignee: nobody → Prosunjit Biswas (prosun-csedu)
assignee: Prosunjit Biswas (prosun-csedu) → nobody
Revision history for this message
navdeep (navdeepniku) wrote :

I'm trying to do similar thing for my project. Hoping to resolve in future versions of Openstack.

Revision history for this message
Dolph Mathews (dolph) wrote :

I'm leaving this as incomplete, because it's not clear what part of this use case is missing / broken in keystone, and it's obviously spec-level work anyway. I'd suggest proposing a well-defined problem description to the spec backlog.

Changed in keystone:
importance: Undecided → Wishlist
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Identity (keystone) because there has been no activity for 60 days.]

Changed in keystone:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.