Policy Default Refresh

Registered by Ghanshyam Mann on 2019-03-21

Ideally most operators should be able to run without modifying policy, as
such we need to have richer defaults.

When operators must modify the policy, or need to audit the defaults, they are
thinking about API operations what policy to change, so the policy should
always clearly relate to the API node the code.

To improve the Nova policies in term of self-service and rich defaults roles, we need multiple updates :
1. making the policy rules granular to add scope_type and new defaults roles - https://blueprints.launchpad.net/nova/+spec/granular-api-policy

2. scope - Adding the correct scope_type with global and project access

3. Defaults roles, keystone now has new defaults roles like reader, admin, member which can be applied with each scope_type.

More details in spec.

Blueprint information

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

Related branches

Sprints

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.