Bug 1025739

Summary:	[RFE] edit VMs and Templates residing on export domain
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	David Jaša <djasa>
Component:	RFEs	Assignee:	Michal Skrivanek <michal.skrivanek>
Status:	CLOSED WONTFIX	QA Contact:	Shai Revivo <srevivo>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	djasa, iheim, lpeer, rbalakri, scohen, sherold, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	sherold: Triaged+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-22 15:47:17 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:

Description David Jaša 2013-11-01 12:15:03 UTC

Description of problem:
Sometimes, e.g. when physical data center layout changes, it makes sense to edit exported templates/VMs right on export domain and then just import them multiple times, saving the import/edit/reexport cycle.

Version-Release number of selected component (if applicable):
3.3

How reproducible:


Steps to Reproduce:
1. try to edit exported VM or Template
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ayal Baron 2013-12-15 15:06:53 UTC

Could you elaborate what options you would like to edit?

Comment 2 David Jaša 2014-01-15 09:19:37 UTC

(In reply to Ayal Baron from comment #1)
> Could you elaborate what options you would like to edit?

Because some of the underlying stuff changes. Take networks: when it's name is different at import time, your VM won't work till you fix it, but you can't fix anything till the import is over which is longish operation. Being able to tailor the VM/Template to destination setup before import makes more sense.

Comment 3 Ayal Baron 2014-01-15 10:34:24 UTC

(In reply to David Jaša from comment #2)
> (In reply to Ayal Baron from comment #1)
> > Could you elaborate what options you would like to edit?
> 
> Because some of the underlying stuff changes. Take networks: when it's name
> is different at import time, your VM won't work till you fix it, but you
> can't fix anything till the import is over which is longish operation. Being
> able to tailor the VM/Template to destination setup before import makes more
> sense.

Ok, so I'd say this isn't to edit it on the export domain but rather when pushing import button you'd like to be able to edit these options before clicking 'ok', esp. considering that networks for example would depend on the target of the import so only relevant to current import operation.
would you agree?

Comment 4 David Jaša 2014-04-16 10:07:30 UTC

(In reply to Ayal Baron from comment #3)
> ...
> Ok, so I'd say this isn't to edit it on the export domain but rather when
> pushing import button you'd like to be able to edit these options before
> clicking 'ok', esp. considering that networks for example would depend on
> the target of the import so only relevant to current import operation.
> would you agree?

That would suffice, too.

Comment 5 Itamar Heim 2015-03-22 15:47:17 UTC

Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.