Role-based Access Control for QoS policies
The cloud admin needs to have the ability to share Neutron QoS policies between subsets of tenants instead of the all-or-nothing choice he has now.
For example, there is no way for a cloud admin to define a "platinum" policy (e.g. guaranteed BW, low latency) and making it available only for certain tenants (the ones who actually paid for it) applying it to their ports/networks.
Blueprint information
- Status:
- Complete
- Approver:
- Miguel Angel Ajo
- Priority:
- Low
- Drafter:
- Miguel Angel Ajo
- Direction:
- Approved
- Assignee:
- Haim Daniel
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-rc1
- Started by
- Armando Migliaccio
- Completed by
- Armando Migliaccio
Related branches
Sprints
Whiteboard
Mar-11-2016(armax): doc change: https:/
Mar-7-2016(
Jan-27-
Jan-24-2016(armax): spec merged, unclear the status of the code, testing and documentation. Candidate for removal out of Mitaka.
Dec-15-2015(armax): spec needs revision, code is in progress.
Addressed by: https:/
Role-based Access Control for QoS Policies
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
[WIP] Qos policy RBAC DB setup and migraition
Addressed by: https:/
update blueprint rbac-qos documentation status
