Difference between revisions of "Horizon/DomainSupport"
< Horizon
Dan Nguyen (talk | contribs) m (→Domain Admins and Project Admins should be mutually exclusive.) |
Dan Nguyen (talk | contribs) m (→Domain Support (Work In Progress)) |
||
| Line 1: | Line 1: | ||
| − | == | + | == (Work In Progress) == |
=== Use Cases === | === Use Cases === | ||
| Line 71: | Line 71: | ||
- persona driven workflows | - persona driven workflows | ||
- keystone changes | - keystone changes | ||
| + | - quota inheritance | ||
Revision as of 01:25, 1 May 2015
Contents
- 1 (Work In Progress)
- 1.1 Use Cases
- 1.2 Best Practices
- 1.2.1 Keystone v3 policy files
- 1.2.2 An new admin domain should be created
- 1.2.3 Project Admin should be deprecated
- 1.2.4 Domain Admins and Project Admins should be mutually exclusive.
- 1.2.5 Domain Admins and Project Members should be mutually exclusive.
- 1.2.6 Only Cloud Admin(s) should have a role on an admin domain
- 1.3 Definitions
(Work In Progress)
Use Cases
- LDAP, AD, MySQL support
Best Practices
Keystone v3 policy files
Horizon should use the same keystone v3 policy file as the keystone API
An new admin domain should be created
Cloud Admin should have an admin role in a domain specifically created for Identity management of the system.
Project Admin should be deprecated
Cloud Admin and Domain Admin are the preferred "admin" personas in the context of domains
Domain Admins and Project Admins should be mutually exclusive.
Domain Admin + Project Admin is not recommended
Domain Admins and Project Members should be mutually exclusive.
Domain Admin + Project Member is not recommended (even in the same domain)
Only Cloud Admin(s) should have a role on an admin domain
Non-Cloud Admin users should not have a role on the default admin domain
Definitions
User Types / Personas
Cloud Admin
domain-scoped token, scoped to the ‘default’ domain. This is assuming that user have the ‘admin’ role assigned to him for the ‘default’ domain.
Domain Admin
domain-scoped token, scoped to the given domain. This is assuming that user have the ‘admin’ role assigned to him for the given domain. Cloud Admin is also the Domain Admin for the ‘default’ domain.
Project Admin
project-scoped token, scoped to the given project. This is assuming that user have the ‘admin’ role assigned to him for the given project.
Project User
project-scoped token, scoped to the given project. This is assuming that user have at least one role assigned to him for the given project. Project User is also Project Admin only if user also have the ‘admin’ role assigned to him for the given project.
Note:
Domain-scoped token should NOT have access to Nova. Only project-scoped token have access to the services. Cloud Admin and Domain Admin are Keystone-specific personas and therefore only have access to Keystone APIs.
Known Issues
- Mixing Domain Admin + Project Admin - Creating Members in the Default Admin domain - Project Admin, hide Admin Dash on purpose
Horizon Bugs
- luigi (project member, invalid Catalog Service:compute) - list_role_assignments (pure domain admin) - Group manange members (pure domain admin) - Project details (pure project admin, member) - checkboxes and actions when no actions available (member)
Next Steps
- DOA patch - Keystone patch - Fix Horzon Bugs - UX/UI - project picker, set domain context changes
Test Cases
Future
- angular goodness - persona driven workflows - keystone changes - quota inheritance
