Bug 1386297

Summary:	[RFE] Manage deployment plans that are loaded into UI
Product:	Red Hat OpenStack	Reporter:	Anandeep Pannu <apannu>
Component:	openstack-tripleo-ui	Assignee:	Honza Pokorny <hpokorny>
Status:	CLOSED ERRATA	QA Contact:	Ola Pavlenko <opavlenk>
Severity:	high	Docs Contact:
Priority:	high
Version:	12.0 (Pike)	CC:	achernet, hpokorny, jjoyce, jrist, jschluet, slinaber, tvignaud
Target Milestone:	Upstream M1	Keywords:	FutureFeature, Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-ui-7.1.1-0.20170624213423.cb896fd.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1463708 (view as bug list)		Environment:
Last Closed:	2017-12-13 20:49:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1420915, 1442136, 1463708, 1469865

Description Anandeep Pannu 2016-10-18 15:18:51 UTC

Description of problem: User Story Epic

As a cloud administrator I would like to be able to be able to edit deployment plans so that any changes made to the deployment plan are saved in the appropriate template form and any validations and configuration changes necessary to execute the deployment plan are saved so that I can execute the deployment plan in my environment with a successful validated deployment

Tests: 
1. Add a composable role to the deployment plan - the role should be saved in a template, be able to be assigned to a node and registered. Any validations neccessary for the registered node for that role should be carried out. The role should be deployed as indicated by the user.
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anandeep Pannu 2017-03-09 19:06:29 UTC

Import and export of plans is part of this user story

Comment 3 Ola Pavlenko 2017-05-22 14:22:15 UTC

HI!
Is update of existing plan considered as part of the RFE?

Comment 4 Honza Pokorny 2017-05-25 12:44:58 UTC

Ola, yes, we are changing the way that the environment of a plan is stored so updating a plan will be affected by the work done in fulfillment of this RFE.  It might be indirect but plan updating should be tested before this RFE can be verified.

Comment 5 Honza Pokorny 2017-06-28 12:43:17 UTC

The plans management interface has been reshaped into a more visually pleasing card interface.  This allows us to include more information each plan and its state than in the case of the table view.

The rest of the features will be moved to Queens, and will be tracked in the linked ticket.

Comment 10 errata-xmlrpc 2017-12-13 20:49:23 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-2017:3462