Back to bug 1042179

Who When What Removed Added
RHOS Integration 2013-12-12 21:17:32 UTC Keywords FutureFeature
Whiteboard upstream_milestone_icehouse-1 upstream_status_implemented
Red Hat Bugzilla 2013-12-12 21:17:32 UTC Doc Type Bug Fix Enhancement
John Skeoch 2014-01-13 01:15:53 UTC CC hateya
Stephen Gordon 2014-01-23 20:47:52 UTC Status NEW POST
RHOS Integration 2014-02-19 22:26:33 UTC Target Release 5.0 ---
Whiteboard upstream_milestone_icehouse-1 upstream_status_implemented upstream_milestone_icehouse-1 upstream_status_implemented upstream_definition_approved
RHEL Program Management 2014-02-19 22:57:15 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 16:03:06 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 17:20:23 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 17:54:25 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 18:22:54 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 21:48:55 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 22:16:56 UTC Target Release --- 5.0
Scott Lewis 2014-03-26 18:41:38 UTC CC sbaker, sdake, shardy
Component RFEs openstack-heat
Steven Dake 2014-04-08 17:10:00 UTC Priority unspecified medium
Doc Text Feature:
Allow build information for heat to be queried via the rest API.

Reason:
Cloud deployers may want to know the version of heat engine or heat api they are communicating with when accessing customer support.

Result (if any):
The build information can be presented to the user. For security reasons, the build information must be manually set!
Scott Lewis 2014-07-07 13:41:35 UTC Target Milestone Upstream M1 rc
Scott Lewis 2014-07-07 13:53:01 UTC Target Milestone rc ga
Scott Lewis 2014-07-22 19:08:59 UTC Status POST CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-07-22 15:08:59 UTC
Martin Lopes 2014-07-23 04:24:12 UTC CC mlopes
Doc Text Feature:
Allow build information for heat to be queried via the rest API.

Reason:
Cloud deployers may want to know the version of heat engine or heat api they are communicating with when accessing customer support.

Result (if any):
The build information can be presented to the user. For security reasons, the build information must be manually set!
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.

Back to bug 1042179