Role-based Access Control for QoS policies

Registered by Armando Migliaccio on 2015-12-01

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:
milestone icon mitaka-rc1
Started by
Armando Migliaccio on 2015-12-01
Completed by
Armando Migliaccio on 2016-03-11

Related branches

Sprints

Whiteboard

Mar-11-2016(armax): doc change: https://review.openstack.org/#/c/291276/
Mar-7-2016(ihrachys): user visible doc update is needed, everything else landed.
Jan-27-2016(mangelajo): spec merged, two new patch versions submitted addressing all previous comments, under review.
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://review.openstack.org/254224
    Role-based Access Control for QoS Policies

Gerrit topic: https://review.openstack.org/#q,topic:bp/rbac-qos,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bug/1512587,n,z

Addressed by: https://review.openstack.org/250081
    [WIP] Qos policy RBAC DB setup and migraition

Addressed by: https://review.openstack.org/291413
    update blueprint rbac-qos documentation status

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.