Bug 1190312

Summary:	[RFE][horizon]: Report the heat engines under horizon system information panel
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aortega, athomas, ddomingo, markmc, mrunge, nbarcet, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/heat-engine-status-report
Whiteboard:	upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:	python-django-horizon-2015.1.0-7.el7ost	Doc Type:	Enhancement
Doc Text:	You can now view details about Orchestration service hosts through the dashboard. To do so, go to 'Admin > System > System Information > Orchestration Services'. This page is only available if the Orchestration service is deployed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:21:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2015-02-07 05:06:24 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/heat-engine-status-report.

Description:

Heat is implemented with feature for reporting the deployed heat-engines in a given openstack deployment. The corresponding heat spec is https://review.openstack.org/#/c/122597/. It provides required REST API for retrieving the engines details. 

 This blue print is submitted to report the heat-engines under admin->system info panel by consuming the new REST API provided in heat as part of above mentioned blue print.

NOTE: This is similar to how horizon reports nova compute nodes, cinder volume nodes, etc.

Specification URL (additional information):

None

Comment 6 errata-xmlrpc 2015-08-05 13:21:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548