Back to bug 1302810

Who When What Removed Added
Bill Wei 2016-01-28 16:53:02 UTC Status NEW ON_DEV
Assignee gblomqui bilwei
Bill Wei 2016-02-05 19:56:25 UTC Summary Don't show OpenStack resource groups as nested stacks [RFE] Orchestration templates auto collected from provider should be be hidden from Services -> Catalogs -> Orchestration Templates
Bill Wei 2016-02-09 15:26:21 UTC Summary [RFE] Orchestration templates auto collected from provider should be be hidden from Services -> Catalogs -> Orchestration Templates [RFE] Orchestration templates auto collected from provider should be hidden from Services -> Catalogs -> Orchestration Templates
Bill Wei 2016-02-22 15:17:12 UTC Component Providers Web UI
Assignee bilwei dclarizi
Bill Wei 2016-02-22 15:19:14 UTC Assignee dclarizi hkataria
Harpreet Kataria 2016-02-23 15:06:33 UTC Status ON_DEV ASSIGNED
Assignee hkataria mzazrivec
Milan Zázrivec 2016-03-07 15:08:36 UTC Status ASSIGNED ON_DEV
Milan Zázrivec 2016-04-19 08:26:59 UTC Status ON_DEV POST
Satoe Imaishi 2016-04-19 17:08:04 UTC Status POST MODIFIED
Satoe Imaishi 2016-04-22 02:28:52 UTC Status MODIFIED ON_QA
Fixed In Version 5.6.0.4
Marianne Feifer 2016-04-25 15:45:43 UTC CC mfeifer
Doc Text Feature: Orchestration templates auto collected from provider should be hidden from Services -> Catalogs -> Orchestration Templates

Reason: CFME should improve the presentation of stacks. Currently all stacks, root or nested, from all providers are shown in one flat table. A proper presentation should utilize the tree structure, starting from providers, then stacks at root level, and then nested stacks. Existing backend already supports the drill down operations.

Result: User added templates are default to orderable.
Shveta 2016-05-04 19:51:33 UTC CC sshveta
QA Contact dajohnso sshveta
Shveta 2016-05-04 19:52:30 UTC Status ON_QA VERIFIED
Dayle Parker 2016-06-28 00:55:05 UTC Doc Text Feature: Orchestration templates auto collected from provider should be hidden from Services -> Catalogs -> Orchestration Templates

Reason: CFME should improve the presentation of stacks. Currently all stacks, root or nested, from all providers are shown in one flat table. A proper presentation should utilize the tree structure, starting from providers, then stacks at root level, and then nested stacks. Existing backend already supports the drill down operations.

Result: User added templates are default to orderable.
This CloudForms release improves the presentation of stacks in the user interface by allowing user-added orchestration templates to be orderable. Additionally, orchestration templates automatically collected from a provider are no longer displayed under Orchestration Templates. This was not possible in previous versions because the code organized both root and nested stacks in one flat table instead of in a tree structure starting from provider.
Dayle Parker 2016-06-28 03:28:12 UTC Doc Text This CloudForms release improves the presentation of stacks in the user interface by allowing user-added orchestration templates to be orderable. Additionally, orchestration templates automatically collected from a provider are no longer displayed under Orchestration Templates. This was not possible in previous versions because the code organized both root and nested stacks in one flat table instead of in a tree structure starting from provider. This CloudForms release improves the presentation of stacks in the user interface by allowing user-added orchestration templates to be orderable. Additionally, orchestration templates automatically collected from a provider are no longer displayed under Orchestration Templates. This was not possible in previous versions because the code organized both root and nested stacks in one flat table instead of in a tree structure starting from the provider level.
errata-xmlrpc 2016-06-29 07:13:01 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-06-29 15:34:38 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-06-29 11:34:38 UTC

Back to bug 1302810