On Tue, Jun 26, 2018 at 02:46:39AM +0300, Nir Soffer wrote:
On Thu, Jun 21, 2018 at 3:35 PM Richard W.M. Jones <rjones@redhat.com> wrote:
These two patches add support for using a Unix domain socket to directly access imageio in the case where imageio is running on the conversion host (usually that means virt-v2v is running on the RHV node and something else -- eg. CFME scripts -- arranges that the RHV node is the same one running imageio).
Actually CFME does not know anything about this optimization. It is virt-v2v starting the transfer on the same host it is running on.
Conversions in the normal case are not affected - they happen over TCP as usual.
This was extremely hard to test,
Why? is this something that we can improve in ovirt?
I don't think there's anything needed in oVirt. It's just that to test it I had to build virt-v2v on the RHV node (running RHEL 7) which was quite complicated.
but I did eventually manage to test it both ways.
Do you mean both using https and unix socket?
Yes. 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/