Bug 1156678

Summary: [RFE][horizon]: Heat UI improvement
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: python-django-horizonAssignee: Matthias Runge <mrunge>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aortega, athomas, lbopf, markmc, mrunge, nbarcet, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature, OtherQA
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement
Whiteboard: upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version: python-django-horizon-2015.1.0-9.el7ost Doc Type: Enhancement
Doc Text:
The user interface options available in the dashboard for the OpenStack Orchestration service (heat) have been improved. For example, users can now check, suspend, resume, and preview stacks.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:16:18 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 2014-10-25 04:06:16 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement.

Description:

There is a lot of Heat operations which require Horizon support. It would be nice to provide user with the following actions:

- List resource types (lists the supported template resource types)
- Get stack template
- Preview stack
- Check stack action
- Update an existing stack with modified parameters

The following features are used less often however is should be possible to perform them through Horizon too:

- Suspend stack
- Resume stack
- Adopt stack
- Abandon stack

Specification URL (additional information):

None

Comment 5 errata-xmlrpc 2015-08-05 13:16:18 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