search for: imageio

Dear R helpers I have a problem with R COMPILE. While the Makefile consisting of the lines SOURCES = imageio.c procbase.c readargs.c regSegs.c goodiesPH.c \ generalAnalysis.c edgeAggregation.c utilities.alga.c \ cs.parametrizing.c tst.so: $(SOURCES) R SHLIB -o $@ $(SOURCES) works fine, the Makefile with the target replaced by imageio.o: imageio.c R COMPILE imageio.c results in cd /u/holzer...

Dear R helpers I have a problem with R COMPILE. While the Makefile consisting of the lines SOURCES = imageio.c procbase.c readargs.c regSegs.c goodiesPH.c \ generalAnalysis.c edgeAggregation.c utilities.alga.c \ cs.parametrizing.c tst.so: $(SOURCES) R SHLIB -o $@ $(SOURCES) works fine, the Makefile with the target replaced by imageio.o: imageio.c R COMPILE imageio.c results in cd /u/holzer...

This is mainly for testing the new parallel python threading model, but it also an example how to manage multiple connection from a plugin. I tested this with local imageio server, serving qcow2 image on local SSD. Start imageio server from imageio source: ./ovirt-imageio -c test Create test disk: qemu-img create -f qcow2 /var/tmp/disk.qcow2 6g Add ticket to accessing the image, using nbd example ticket: curl --unix-socket ../daemon/test/daemon.sock...

On Fri, Aug 7, 2020 at 1:54 AM Nir Soffer <nirsof@gmail.com> wrote: > > This is mainly for testing the new parallel python threading model, but > it also an example how to manage multiple connection from a plugin. > > I tested this with local imageio server, serving qcow2 image on local > SSD. > > Start imageio server from imageio source: > > ./ovirt-imageio -c test > > Create test disk: > > qemu-img create -f qcow2 /var/tmp/disk.qcow2 6g > > Add ticket to accessing the image, using nbd example ticket: &...

...-W flag to the qemu-img command I tested this on Fedora 32, with ovirt-engine-sdk built from source, since the package is not available on Fedora 31 or 32, and the Fedora 30 package cannot be installed on Fedora 32. Signed-off-by: Nir Soffer <nsoffer@redhat.com> --- plugins/python/examples/imageio.py | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/plugins/python/examples/imageio.py b/plugins/python/examples/imageio.py index f8ade7a2..38ad5ac4 100644 --- a/plugins/python/examples/imageio.py +++ b/plugins/python/examples/imageio.py @@ -4,10 +4,18 @@ # #...

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). Conversions in the normal case are not affected - they happen over TCP as usual...

On 8/6/20 5:54 PM, Nir Soffer wrote: > This is mainly for testing the new parallel python threading model, but > it also an example how to manage multiple connection from a plugin. > > I tested this with local imageio server, serving qcow2 image on local > SSD. > > diff --git a/plugins/python/examples/imageio.py b/plugins/python/examples/imageio.py > new file mode 100644 > index 00000000..e77fd2f4 > --- /dev/null > +++ b/plugins/python/examples/imageio.py > @@ -0,0 +1,167 @@ > +# Exa...

On Thu, Jul 9, 2020 at 10:53 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Jul 09, 2020 at 01:51:44AM +0300, Nir Soffer wrote: > > We can use now ImageioClient to communicate with ovirt-imageio server > > on oVirt host. > > > > Using the client greatly simplifies the plugin, and enables new features > > like transparent proxy support. The client will use transfer_url if > > possible, or fall back to proxy_url. > >...

On Thu, Jul 9, 2020 at 4:12 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Jul 09, 2020 at 03:30:22PM +0300, Nir Soffer wrote: > > Testing with a real server is easy. I have incomplete patch using > > imageio server with some manual setup. > [...] > > For a certain definition of "easy" :-) > > Our QE team tests -o rhv-upload from time to time, and will do an > end-to-end test of the system when RHV 4.4 arrives with the new > feature. > > For “make check” we need some...

Old imageio proxy was using Authorization header for GET and PUT requests. Remove unneeded authorization when sending OPTIONS request. Remove unneeded duplicated comments about authorization for old imageio, and replace them with a comment when we set needs_auth. --- v2v/rhv-upload-plugin.py | 12 +++++------...

Hi Richard, We've added zero and flush functionality to imageio-daemon. You can download and test the latest build (for el7/fc) from: - http://jenkins.ovirt.org/job/ovirt-imageio_master_build-artifacts-el7-x86_64/200/artifact/exported-artifacts/ - http://jenkins.ovirt.org/job/ovirt-imageio_master_build-artifacts-fc27-x86_64/53/artifact/exported-artifacts/ - ht...

We can use now ImageioClient to communicate with ovirt-imageio server on oVirt host. Using the client greatly simplifies the plugin, and enables new features like transparent proxy support. The client will use transfer_url if possible, or fall back to proxy_url. Since the client implements the buffer protocol, move to...

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 optimizatio...

...;nsoffer@redhat.com> wrote: > > On Thu, Jul 9, 2020 at 4:12 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > On Thu, Jul 09, 2020 at 03:30:22PM +0300, Nir Soffer wrote: > > > Testing with a real server is easy. I have incomplete patch using > > > imageio server with some manual setup. > > [...] > > > > For a certain definition of "easy" :-) > > > > Our QE team tests -o rhv-upload from time to time, and will do an > > end-to-end test of the system when RHV 4.4 arrives with the new > > feature. >...

v1 was here: https://www.redhat.com/archives/libguestfs/2018-June/msg00099.html v2: - Just fixes the two problems noted in the review of the previous version. Rich.

...The output when the optimization is used looks like this: disk.id = '45d1a30c-82c0-4b00-8bfb-c4d628dbf72d' hw_id = '81F716C4-4D19-CB35-82F7-94C691189FEB' host.id = '87daa64d-b27e-4336-a156-973544be708b' transfer.id = '5ffea7fa-966c-42a4-a77a-3efd6dc45c34' imageio features: flush=True trim=False zero=True unix_socket='\x00/org/ovirt/imageio' optimizing connection using unix socket '\x00/org/ovirt/imageio' Rich.

...check TESTS=test-v2v-python-syntax.sh However I have now fixed them. > Do we have an easy way to test the plugin without running the entire > virt-v2v pipeline? Not really. In fact we don't have any unit tests for -o rhv-upload functionality because there's no way to simulate the imageio server. However you can run virt-v2v locally against an oVirt instance without needing VMware. The command is rather lengthy, but here it is: $ virt-builder fedora-27 $ ./run virt-v2v -i disk /var/tmp/fedora-27.img \ -o rhv-upload \ -oc https://ovirt-engine.example.com/ovirt-engine/api \...

...ver I have now fixed them. > Thanks! > > > Do we have an easy way to test the plugin without running the entire > > virt-v2v pipeline? > > Not really. In fact we don't have any unit tests for -o rhv-upload > functionality because there's no way to simulate the imageio server. > Actually it is easy to use real imageio server for testing. 1. install ovirt-imageio-daemon 2. configure it for testing # /etc/ovirt-imageio-daemon/daemon.conf [daemon] # directory with this structure # certs/ # vdsmcert.pem # keys # vdsmkey.pem pki_dir = t...

On Thu, Jul 09, 2020 at 01:51:44AM +0300, Nir Soffer wrote: > We can use now ImageioClient to communicate with ovirt-imageio server > on oVirt host. > > Using the client greatly simplifies the plugin, and enables new features > like transparent proxy support. The client will use transfer_url if > possible, or fall back to proxy_url. > > Since the client imple...

In the case where virt-v2v runs on the same server as the imageio daemon that we are talking to, it may be possible to optimize access using a Unix domain socket. This is only an optimization. If it fails or if we're not running on the same server it will fall back to the usual HTTPS over TCP connection. Thanks: Nir Soffer, Daniel Erez. --- v2v/rhv-upload...