Bug 1346847 (V2V_REST_API)

Summary:	virt-v2v basic REST API
Product:	[oVirt] ovirt-engine	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	BLL.Virt	Assignee:	Martin Betak <mbetak>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.0.0	CC:	bugs, melewis, mgoldboi, nsimsolo, s.kieske, tjelinek
Target Milestone:	ovirt-4.0.5	Flags:	rule-engine: ovirt-4.0.z+ mgoldboi: planning_ack+ michal.skrivanek: devel_ack+ mavital: testing_ack+
Target Release:	4.0.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	With this update, the ability to import virtual machines from VMware, VMware OVA, XEN, and KVM via the Red Hat Virtualization REST API has been added. Previously, this was only possible using the web UI.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-18 07:38:00 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:
Embargoed:
Bug Depends On:	1236075
Bug Blocks:	1324137

Description Michal Skrivanek 2016-06-15 13:00:49 UTC

Since the original feature bug 1236075 implemented only the UI integration, we want to also have a REST API support to trigger conversion of VMs

Comment 1 Red Hat Bugzilla Rules Engine 2016-06-15 13:01:03 UTC

Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Tomas Jelinek 2016-06-24 10:12:59 UTC

*** Bug 1316854 has been marked as a duplicate of this bug. ***

Comment 3 Michal Skrivanek 2016-07-25 06:56:02 UTC

API supporting VM import from external hypervisors, covering virt-v2v use case (specifying vCenter URI and VM to convert) - this is to be delivered prior to 4.1.
Additionally it should support VMware OVA, xen+ssh URI and KVM guests.

Comment 4 Michal Skrivanek 2016-07-28 11:49:11 UTC

due to lack of TM values setting 4.0.4, but it will likely be later than that

Comment 5 Sven Kieske 2016-10-20 13:10:16 UTC

Hi,

the doctext misspells "VMware" as "WMware".

HTH

Sven

Comment 6 Martin Betak 2016-10-20 13:22:56 UTC

Thanks, Sven :-)

Comment 7 Nisim Simsolo 2016-11-07 09:52:06 UTC

Verified:
ovirt-engine-4.0.5.5-0.1.el7ev
qemu-kvm-rhev-2.6.0-27.el7.x86_64
vdsm-4.18.15.2-1.el7ev.x86_64
libvirt-client-2.0.0-10.el7.x86_64
virt-v2v-1.32.7-3.el7.x86_64

Verification scenarios:
Using v2v REST API, import Windows and RHEL VMs from VMware, Xen and KVM (qemu+tcp and qemu+ssh) using block devices and NFS disks (source and target disks).
After the import is completed, Verify VM is running. CPU, memory and disks are equal to the source values. Target network MAC addresses are within the system MAC addresses pool and VirtIO win drivers are installed correctly.