[ovirt-devel] Extended import of Virtual Machines

[Shahar Havivi]

On 11.10.15 02:27, Christopher Pereira wrote:
> Hi Arik, Shahar, Richard,
> 
> We would like to test and contribute to the "Extended import of Virtual
> Machines" project [1].
> Our particular interest is in importing VMs (from libvirt domains or other
> existing oVirt storage domains) into oVirt ideally avoiding image
> conversions.
> This would be achieved by moving existing raw/qcow2 images into a given
> oVirt storage domain (using 'mv' instead of 'qemu-img') and dealing with the
> OVF_STORE files.
> A problem we faced is that importing VMs using virt-v2v is currently broken
> in 3.6-rc1 as Richard W.M. Jones reported some weeks ago [2].
Hi,
Take a look at file vdsm/vdsm/v2v.py which have two convert methods:
1. convert_external_vm (convert from libvirt)
2. convert_ova (convert from a ova tar file)
You can add an entry there (which is called from API.py that you will need to
patch as well).

Both methods are calling to external command virt-v2v in order to convert the
disk images which you don't need - but you do need something else that will
copy/move your images.

Please note for the status, description and progress fields which are
reporting back to oVirt engine.

You will need to address the abort() method as well.

Shahar.


> 
> [1] : http://www.ovirt.org/Features/virt-v2v_Integration
> [2] : https://bugzilla.redhat.com/show_bug.cgi?id=1266930
> 
> -- 
> 
> *J. Christopher Pereira*
> IMATRONIX S.A.
> www.imatronix.com
> 
>