Back to bug 1042203
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHOS Integration | 2013-12-12 21:21:51 UTC | Keywords | FutureFeature | |
| Whiteboard | upstream_milestone_icehouse-2 upstream_status_started | |||
| Red Hat Bugzilla | 2013-12-12 21:21:51 UTC | Doc Type | Bug Fix | Enhancement |
| John Skeoch | 2014-01-13 01:15:59 UTC | CC | hateya | |
| RHOS Integration | 2014-01-15 16:58:53 UTC | Whiteboard | upstream_milestone_icehouse-2 upstream_status_started | upstream_milestone_icehouse-2 upstream_status_good-progress |
| RHOS Integration | 2014-01-22 05:05:45 UTC | Target Release | 5.0 | --- |
| Target Milestone | Upstream M2 | Upstream M3 | ||
| Whiteboard | upstream_milestone_icehouse-2 upstream_status_good-progress | upstream_milestone_icehouse-3 upstream_status_good-progress | ||
| RHEL Program Management | 2014-01-22 05:21:03 UTC | Target Release | --- | 5.0 |
| RHOS Integration | 2014-02-19 22:28:04 UTC | Target Release | 5.0 | --- |
| Whiteboard | upstream_milestone_icehouse-3 upstream_status_good-progress | upstream_milestone_icehouse-3 upstream_status_good-progress upstream_definition_approved | ||
| RHEL Program Management | 2014-02-19 22:55:38 UTC | Target Release | --- | 5.0 |
| RHOS Integration | 2014-02-20 16:04:03 UTC | Target Release | 5.0 | --- |
| RHEL Program Management | 2014-02-20 17:19:07 UTC | Target Release | --- | 5.0 |
| RHOS Integration | 2014-02-20 17:54:55 UTC | Target Release | 5.0 | --- |
| RHEL Program Management | 2014-02-20 18:21:04 UTC | Target Release | --- | 5.0 |
| RHOS Integration | 2014-02-20 21:50:06 UTC | Target Release | 5.0 | --- |
| RHEL Program Management | 2014-02-20 22:15:29 UTC | Target Release | --- | 5.0 |
| RHOS Integration | 2014-02-26 05:05:13 UTC | Status | NEW | POST |
| Whiteboard | upstream_milestone_icehouse-3 upstream_status_good-progress upstream_definition_approved | upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved | ||
| Scott Lewis | 2014-03-26 18:41:41 UTC | CC | sbaker, sdake, shardy | |
| Component | RFEs | openstack-heat | ||
| Steven Dake | 2014-04-08 17:21:39 UTC | Priority | unspecified | high |
| Doc Text | Feature: From a UI perspective, it may be desireable to group parameters and order them. Reason: A UI ideally presents parameters in a specific order in specific groups. Result (if any): The UI could parse the template and use the information for better presentation. From a Heat perspective, all that is done is the adding of the top level sections and validation to ensure the content is valid HOT format. |
|||
| Scott Lewis | 2014-07-07 13:41:42 UTC | Target Milestone | Upstream M3 | rc |
| Scott Lewis | 2014-07-07 13:53:10 UTC | Target Milestone | rc | ga |
| Scott Lewis | 2014-07-22 19:08:58 UTC | Status | POST | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-07-22 15:08:58 UTC | |||
| Deepti Navale | 2014-07-23 05:19:59 UTC | CC | dnavale | |
| Doc Text | Feature: From a UI perspective, it may be desireable to group parameters and order them. Reason: A UI ideally presents parameters in a specific order in specific groups. Result (if any): The UI could parse the template and use the information for better presentation. From a Heat perspective, all that is done is the adding of the top level sections and validation to ensure the content is valid HOT format. | Currently, Orchestration returns the parameters from the template in an unorganized manner. This can result in important parameters being randomly pushed towards the bottom as well as logical groupings of parameters being random. With this update, the UI presents parameters in a specific order in specific groups. As a result, the UI can parse the template and use the information for better presentation. This is achieved by adding of the top level sections and validation to ensure the content is valid HOT format. |
||
| Don Domingo | 2014-09-23 03:24:44 UTC | CC | ddomingo | |
| Doc Text | Currently, Orchestration returns the parameters from the template in an unorganized manner. This can result in important parameters being randomly pushed towards the bottom as well as logical groupings of parameters being random. With this update, the UI presents parameters in a specific order in specific groups. As a result, the UI can parse the template and use the information for better presentation. This is achieved by adding of the top level sections and validation to ensure the content is valid HOT format. | Previously, Orchestration returns the parameters from the template in an unorganized manner. This can result in important parameters being randomly pushed towards the bottom as well as logical groupings of parameters being random. With this update, the UI presents parameters in a specific order in specific groups. As a result, the UI can parse the template and use the information for better presentation. This is achieved by adding of the top level sections and validation to ensure the content is valid HOT format. |
Back to bug 1042203