Bug 1042091 - [RFE][horizon]: Heat template validation view
Summary: [RFE][horizon]: Heat template validation view
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Matthias Runge
QA Contact: yeylon@redhat.com
URL: https://blueprints.launchpad.net/hori...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:54 UTC by RHOS Integration
Modified: 2016-11-02 04:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-15 15:06:20 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 20:54:13 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/heat-template-choices.

Description:

Currently, when we load a template in the orchestration view, the second panel project/stacks/select_template provides a form which can be modified. The issue is that we can modify value, but we have to check the template for the correct name i.e image_id.  This is problematic because if one error is made we have to resubmit the form.

In addition Heat already provides all the options which can be modified with the template_validate method. This method return JSON datas which can be used for creating multi-choices in the form.

The goal of this blueprint is to build an html template based on the JSON provided by the valid template method of Heat.
Use select instead of input, to reduce the possibility of errors.

Specification URL (additional information):

None

Comment 2 George 2015-03-25 15:08:55 UTC
I've contributed to the upstream blueprint. Looks like the feature is feature complete. Is there anything else needed to be done to close the bug?

Comment 4 Matthias Runge 2015-12-15 10:30:41 UTC
George, do you think the feature is really complete? If yes, we should mark it as complete upstream and write something up for a doc text.

Comment 5 George 2015-12-15 15:06:20 UTC
The solution has 2 parts: 
1) Needed to fix a bug in Heat to return correct values when using parameters with constraints.
https://review.openstack.org/#/c/91179/

2) The template form now generated drop down list to parameters with constraints. 
https://review.openstack.org/#/c/90614/


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