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

Fixed In Version:
Doc Type: Enhancement
Doc Text:
This feature allows Orchestration build information to be queried via the REST API. As a result, administrators are able to determine the version of the Orchestration engine or API they are utilizing when accessing customer support. Consequently, the build information can be presented to the user. For security reasons, it is important to note that the build information must be manually set.
Clone Of:
Environment:
Last Closed: 2014-07-22 19:08:59 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 21:17:27 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/heat-build-info.

Description:

It is useful for system administrators, support users, and possibly regular users to be able to query current build information.  An authenticated user could query /v1/build_info and get information about the current heat build that would be retrieved from a configuration file (e.g. etc/heat/heat.conf).  The response could look like this:

{
  "api": {
    "revision": <api revision>
  },
  "engine": {
    "revision": <engine revision>
  }
}

The full spec contains more details.

Specification URL (additional information):

https://etherpad.openstack.org/p/heat-build-info

Comment 2 Stephen Gordon 2014-01-23 20:47:52 UTC
Moving to POST based on upstream status (Implemented).


Note You need to log in before you can comment on or make changes to this bug.