Add separated policy rule for each v3 api

Registered by Alex Xu

We prefer provide policy rule for each api in v3 api. There are two reason for this.
1. provide finer permission control, that is same reason with this bp https://blueprints.launchpad.net/nova/+spec/aggregate-api-policy
2. there are some extension only have one rule for all the API, and some extension is not. This is hard for operator to know how to write policy for an api. We can just provide policy rule for each API, then operator can easy to how to write policy for an api, because all the policy follow the pattern 'compute:v3:[extension]:[action]'

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Alex Xu
Direction:
Needs approval
Assignee:
Alex Xu
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/is,n,z

Addressed by: https://review.openstack.org/92326
    Add separated policy rule for each v3 api

Spec not approved yet, un-targeting blueprint from juno-1 --johnthetubaguy (28th May 2014)

You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.

Addressed by: https://review.openstack.org/127863
    Add separated policy rule for each v2.1 api

Gerrit topic: https://review.openstack.org/#q,topic:bp/v3-api-policy,n,z

Addressed by: https://review.openstack.org/128560
    The end goal of Nova API policy improvement

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.