Hi team

>>>

For best performance, you should run your application on an oVirt host, using unix

socket to communicate with imageio. See:

http://ovirt.github.io/ovirt-imageio/unix-socket

(will be available in 4.2.5)

Just to reconfirm here… the unix socket option to communicate with imageio is only available if the client application runs on the ovirt host. For remote client, the only way is the REST API, right ?

Thanks

-Suchitra

From: Ranjit DSouza <Ranjit.DSouza@veritas.com>
Date: Thursday, July 12, 2018 at 3:47 PM
To: "devel@ovirt.org" <devel@ovirt.org>
Cc: devel <devel@ovirt.org>, DL-VTAS-ENG-NBU-EverestFalcons <DL-VTAS-ENG-NBU-EverestFalcons@veritas.com>, Navin Tah <Navin.Tah@veritas.com>, Sudhakar Paulzagade <Sudhakar.Paulzagade@veritas.com>, Pavan Chavva <pchavva@redhat.com>, "Yaniv Lavi (Dary)" <ylavi@redhat.com>, "Nisan, Tal" <tnisan@redhat.com>, Daniel Erez <derez@redhat.com>, Nir Soffer <nsoffer@redhat.com>
Subject: Re: Image Transfer mechanism queries/API support

For best performance, you should run your application on a oVirt host, using unix

socket to communicate with imageio. See:

http://ovirt.github.io/ovirt-imageio/unix-socket

(will be available in 4.2.5)