Management API
As an administrator of a Heat system, I should be able to pull certain information from the Heat API that is relevant to the system as a whole, or aggregate information across multiple tenants. As a system administrator, I should have the ability to restrict access to some of this information such that a general tenant (user) must not be able to access it. Note that some of this information may also be nice to expose to normal individual tenants of the system. Either using Heat configuration files, or a proxy such as REPOSE, I would like the ability to configure what keystone roles have permission to access which pieces of information.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Baker
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- andersonvom
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Steve Baker
- Completed by
- andersonvom
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
DRAFT: Management API - Proof of Concept
(shardy): I've been looking at the request scoping aspects of this, and have added a dep on keystone service-scoped token, and request-
(dolph): this bp should really not be blocked on "service-
Addressed by: https:/
Add filter and pagination to stack_get_all
Addressed by: https:/
Unscoped List Stacks
Gerrit topic: https:/
Addressed by: https:/
Add tenant to unscoped stack list response
Addressed by: https:/
Alter stack_count_
Addressed by: https:/
Replace stack_get_
Addressed by: https:/
Refactor Stack timestamps
Addressed by: https:/
Fix stack_get_all call on stack watcher
Addressed by: https:/
Change Resource timestamps to save correct info
Work Items
Dependency tree
* Blueprints in grey have been implemented.
