On Wed, Mar 7, 2018 at 12:05 PM, Richard W.M. Jones <rjones@redhat.com> wrote:

On Wed, Mar 07, 2018 at 10:42:31AM +0200, Arik Hadas wrote:
> (Moving to devel-list)
> BTW, I think that the import process should include a preliminary phase
> where ovirt-engine is informed that the import process starts.
>
> Currently, IIUC, the new process is designed to be:
> 1. virt-v2v uploads the disks
> 2. virt-v2v calls an API with the OVF configuration so ovirt-engine will
> add the VM and attach the uploaded disks to that VM

Yes, this is how it happens now, see:

https://www.redhat.com/archives/libguestfs/2018-March/msg00021.html

> IMHO, the process should be comprised of:
> 1. virt-v2v calls an API with the (probably partial since the OS and other
> things are unknown at that point) OVF configuration

Almost nothing is known at this point, I'm not sure what we could
provide. Perhaps just number and virtual size of disks. It doesn't
sound like it would be OVF, but something else.

Interesting, that contradicts my intuition - I would imagine that most of the things are actually known (the things that appear in the top-level part of the domain xml: memory size, memory size, num of CPUs, name,.. ) and only things that depend on the content of the disks or things that depend on installations during the conversion are unknown.

But anyway, it is enough IMO to send the name, memory, CPU and size of the disks to present something useful to the user and make the necessary validations at that point.

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com

virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/