Bug 1324137

Summary:	[RFE] Implement v2v support in REST API
Product:	[oVirt] ovirt-engine	Reporter:	Shira Maximov <mshira>
Component:	RFEs	Assignee:	Michal Skrivanek <michal.skrivanek>
Status:	CLOSED DUPLICATE	QA Contact:	Shira Maximov <mshira>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.6.3.3	CC:	bugs, michal.skrivanek
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	michal.skrivanek: ovirt-future? mshira: planning_ack? mshira: devel_ack? mshira: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-16 13:59:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1346847
Bug Blocks:

Description Shira Maximov 2016-04-05 15:27:08 UTC

Description of problem:
Please implement v2v support in REST API.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Michal Skrivanek 2016-04-06 06:03:20 UTC

I understand the need for QA automation, but I'm not sure about practical usefulness. it's a very long running operation, rarely used. And it is just supposed to wrap virt-v2v invocation. It would be easier to call tools directly instead of proxying through ovirt.

Comment 2 Michal Skrivanek 2016-04-15 08:19:59 UTC

setting this to low then

Comment 3 Michal Skrivanek 2016-04-15 08:22:59 UTC

damn you, bot

Comment 4 Yaniv Kaul 2016-07-06 13:06:26 UTC

We need to have probably two APIs:
1. When there is a VMware external provider in RHEV configured, to v2v the VMs.
2. Via CloudForms, be able to perform a V2V without specifying (creating) a VMware external provider in RHEV.

Comment 5 Michal Skrivanek 2016-07-25 06:51:28 UTC

basic REST support is covered by bug 1346847, this one is for providers, perhaps even remote listing of VMs (item 1 from comment #4)

Comment 6 Yaniv Kaul 2017-11-16 13:56:10 UTC

I thought this is all implemented?

Comment 7 Michal Skrivanek 2017-11-16 13:59:06 UTC

I do not quite recall, but I think this one asked for more (like listing) than the "basic" support in bug 134687
I do not really see the need so let's close it

*** This bug has been marked as a duplicate of bug 134687 ***