Bug 1042152 - [RFE][heat]: Management API
Summary: [RFE][heat]: Management API
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/heat...
Whiteboard: upstream_milestone_icehouse-3 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:13 UTC by RHOS Integration
Modified: 2014-09-08 05:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Management features have been added to count stacks, provide pagination, provide Orchestration build information, and request scoping policy. These are fundamental features are required for administering Orchestration.
Clone Of:
Environment:
Last Closed: 2014-07-22 19:09:00 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 21:13:00 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/management-api.

Description:

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.

Specification URL (additional information):

https://etherpad.openstack.org/p/heat-management-api
Note You need to log in before you can comment on or make changes to this bug.