Difference between revisions of "DynamicPolicies"
(→Dynamic Policies) |
(→Roadmap) |
||
| Line 31: | Line 31: | ||
=== US 1 - As a cloud admin, I want to manage Policies via API === | === US 1 - As a cloud admin, I want to manage Policies via API === | ||
| − | + | '''Depends On:''' None | |
| − | + | <br /> | |
| − | |||
Description Bla ... | Description Bla ... | ||
| Line 44: | Line 43: | ||
*** [https://review.openstack.org/#/c/184903/ Basic API spec for managing Policy rules in a database] | *** [https://review.openstack.org/#/c/184903/ Basic API spec for managing Policy rules in a database] | ||
*** [https://review.openstack.org/#/c/185126/ Policy Mapping API] | *** [https://review.openstack.org/#/c/185126/ Policy Mapping API] | ||
| + | |||
=== US 2 - As a cloud admin, I want to have services using the Policies I have defined via API === | === US 2 - As a cloud admin, I want to have services using the Policies I have defined via API === | ||
| − | Depends On: US 1 - As a cloud admin, I want to manage Policies via API | + | '''Depends On:''' US 1 - As a cloud admin, I want to manage Policies via API |
| − | + | <br /> | |
Description Bla ... | Description Bla ... | ||
| Line 56: | Line 56: | ||
=== As a domain admin, I want to define roles that are meaningful to my business === | === As a domain admin, I want to define roles that are meaningful to my business === | ||
| + | |||
| + | '''Depends On:''' None | ||
| + | <br /> | ||
Description Bla ... | Description Bla ... | ||
| Line 62: | Line 65: | ||
** [https://review.openstack.org/#/c/133855/ Add support for domain specific roles. (Name-spaced Roles)] | ** [https://review.openstack.org/#/c/133855/ Add support for domain specific roles. (Name-spaced Roles)] | ||
| − | === As a user, I want to delegate | + | === US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles === |
| + | |||
| + | '''Depends On:''' None | ||
| + | <br /> | ||
Description Bla ... | Description Bla ... | ||
| Line 69: | Line 75: | ||
** [https://review.openstack.org/#/c/125704/ Hierarchical Roles] | ** [https://review.openstack.org/#/c/125704/ Hierarchical Roles] | ||
| − | === As a deployer, I want to have better default policies, distinguishing different admin scopes === | + | === US 4 - As a deployer, I want to have better default policies, distinguishing different admin scopes === |
| + | |||
| + | '''Depends On:''' US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles | ||
| + | <br /> | ||
Description Bla ... | Description Bla ... | ||
Revision as of 13:32, 16 June 2015
Contents
- 1 Dynamic Policies
- 1.1 Weekly Meeting
- 1.2 Background
- 1.3 Evolution
- 1.4 Roadmap
- 1.4.1 US 1 - As a cloud admin, I want to manage Policies via API
- 1.4.2 US 2 - As a cloud admin, I want to have services using the Policies I have defined via API
- 1.4.3 As a domain admin, I want to define roles that are meaningful to my business
- 1.4.4 US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles
- 1.4.5 US 4 - As a deployer, I want to have better default policies, distinguishing different admin scopes
Dynamic Policies
Improving Access Control on OpenStack
Weekly Meeting
TBD
Background
OpenStack uses a Role-Based Access Control mechanism to manage authorization, which defines if a user is able to perform actions on resources based on the roles he has assigned on them. Resources include VMs, volumes, networks, etc and are organized into projects, which are owned by domains. Users have roles assigned on domains or projects.
Users get domain or project scoped tokens, which contains the roles the user has assigned on them, and pass this token along to services in requests to perform actions on resources. The services check the roles and the scope from the token against the rules defined for the requested action on the policy.json file to determine if the user has enough privileges.
Evolution
- How to evolve the policies management mechanism, which currently uses an out-of-band mechanism to update the policy.json files ?
- How to improve delegation mechanism, allowing users to only delegate a subset of their roles, which may be customized per domain ?
- How to provide better default policies, fixing the bug in which an admin anywhere is admin everywhere ?
Roadmap
US 1 - As a cloud admin, I want to manage Policies via API
Depends On: None
Description Bla ...
- Specs
- Policy Management API
- TODO: Create Spec
- Policy Storage Backend
- Policy Management API
US 2 - As a cloud admin, I want to have services using the Policies I have defined via API
Depends On: US 1 - As a cloud admin, I want to manage Policies via API
Description Bla ...
As a domain admin, I want to define roles that are meaningful to my business
Depends On: None
Description Bla ...
US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles
Depends On: None
Description Bla ...
- Specs
US 4 - As a deployer, I want to have better default policies, distinguishing different admin scopes
Depends On: US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles
Description Bla ...
- Specs
- Improve Default Policies
- TODO: Create Spec
- Improve Default Policies
