Uploading iso / ovirt-imageio
Hi, After a long break I am trying setup my engine so that I could upload images (ISO) there and use them when spinning new VMs. First I tried recent master (FC31) and then latest 4.4 beta from RPMs (Centos8). I have ovirt-imageio daemon running on the same host engine is running. (with the simplest possible configuration - TLS disabled) Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep seeing error message complaining about ovirt-imageio-proxy setup. I know that recently there has been quite a lot of changes related to the next version of imageio. Is there something else besides ovirt-imageio daemon that I should have installed/configured? Perhaps there is some documentation I could use? thanks! -- Artur Socha Senior Software Engineer, RHV Red Hat
Upload solved with: https://github.com/oVirt/ovirt-engine-/blob/master/sdk/examples/upload_disk.... Artur On Mon, 2020-04-27 at 11:23 +0200, Artur Socha wrote:
Hi, After a long break I am trying setup my engine so that I could upload images (ISO) there and use them when spinning new VMs. First I tried recent master (FC31) and then latest 4.4 beta from RPMs (Centos8).
I have ovirt-imageio daemon running on the same host engine is running. (with the simplest possible configuration - TLS disabled)
Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep seeing error message complaining about ovirt-imageio-proxy setup. I know that recently there has been quite a lot of changes related to the next version of imageio.
Is there something else besides ovirt-imageio daemon that I should have installed/configured? Perhaps there is some documentation I could use?
thanks!
On Mon, 2020-04-27 at 13:20 +0200, Artur Socha wrote:
Upload solved with: https://github.com/oVirt/ovirt-engine-/blob/master/sdk/examples/upload_disk....
The url above is incomplete. Here is the corrected one. https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_di... Artur
Artur
On Mon, 2020-04-27 at 11:23 +0200, Artur Socha wrote:
Hi, After a long break I am trying setup my engine so that I could upload images (ISO) there and use them when spinning new VMs. First I tried recent master (FC31) and then latest 4.4 beta from RPMs (Centos8).
I have ovirt-imageio daemon running on the same host engine is running. (with the simplest possible configuration - TLS disabled)
Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep seeing error message complaining about ovirt-imageio-proxy setup. I know that recently there has been quite a lot of changes related to the next version of imageio.
Is there something else besides ovirt-imageio daemon that I should have installed/configured? Perhaps there is some documentation I could use?
thanks!
On Mon, Apr 27, 2020 at 12:24 PM Artur Socha <asocha@redhat.com> wrote:
Hi, After a long break I am trying setup my engine so that I could upload images (ISO) there and use them when spinning new VMs. First I tried recent master (FC31) and then latest 4.4 beta from RPMs (Centos8).
I have ovirt-imageio daemon running on the same host engine is running. (with the simplest possible configuration - TLS disabled)
We require TLS for imageio, it is not secure enough to use without TLS and we don't support it.
Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep seeing error message complaining about ovirt-imageio-proxy setup. I know that recently there has been quite a lot of changes related to the next version of imageio.
Probably because engine was not ready for imgeio in the latest beta build.
Is there something else besides ovirt-imageio daemon that I should have installed/configured? Perhaps there is some documentation I could use?
On master everything (but development setup) works: commit ce3a94aedcfc85ede5bd7090cab27a9b592b4187 Author: Daniel Erez <derez@redhat.com> Date: Sun Apr 19 23:40:59 2020 +0300 core: increase ticket timeout value Increased ImageTransferClientTicketValidityInSeconds to 300 Change-Id: Iae3fb6ad0c6b5af1e2dc747bfbc67375a5cd7b2c Signed-off-by: Daniel Erez <derez@redhat.com> But this commit fixed development setup but broke installation from rpms: commit 81a5e757fd8768ace825140ca7dc701cc2e011ce Author: Vojtech Juranek <vjuranek@redhat.com> Date: Thu Apr 23 11:44:41 2020 +0200 spec: allow imageio config in dev env Add $PREFIX into imageio config directory to allow imageio configuration in development environment when config files are installed into a specified directory. Currently it fails with: [Errno 13] Permission denied: '/etc/ovirt-imageio' Change-Id: I9e13bba0e97f681b0b07d5a135be76113e391ddc Signed-off-by: Vojtech Juranek <vjuranek@redhat.com> Fix is here: https://gerrit.ovirt.org/c/108672 For development setup there is this patch in review: https://gerrit.ovirt.org/c/108620 Until the patch is ready, this is the recommended way to set up development environment: 1. Install ovirt-imageio service dnf install ovit-imageio-daemon 2. Run engine setup This creates a working configuration file at $PREFIX/etc/ovirt-imagei/daemon.conf However it does not create a logger.conf file, so you need to create one. The default configuration will not work for you since you want to run ovirt-imageio as yourself, and you cannot write logs to /var/log/ovirt-imageio. 3. Create logger.conf for development $ curl https://raw.githubusercontent.com/oVirt/ovirt-imageio/master/daemon/test/con...
$PREFIX/etc/ovirt-imageio/logger.conf
Now run imageio using: $ ./ovirt-imageio --conf-dir $PREFIX/etc/ovirt-imageio
thanks!
-- Artur Socha Senior Software Engineer, RHV Red Hat
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JDDVTQC6K7U56D...
On Mon, Apr 27, 2020 at 11:05 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Apr 27, 2020 at 12:24 PM Artur Socha <asocha@redhat.com> wrote:
Hi, After a long break I am trying setup my engine so that I could upload images (ISO) there and use them when spinning new VMs. First I tried recent master (FC31) and then latest 4.4 beta from RPMs (Centos8).
I have ovirt-imageio daemon running on the same host engine is running. (with the simplest possible configuration - TLS disabled)
We require TLS for imageio, it is not secure enough to use without TLS and we don't support it.
Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep seeing error message complaining about ovirt-imageio-proxy setup. I know that recently there has been quite a lot of changes related to the next version of imageio.
Probably because engine was not ready for imgeio in the latest beta build.
Is there something else besides ovirt-imageio daemon that I should have installed/configured? Perhaps there is some documentation I could use?
On master everything (but development setup) works:
commit ce3a94aedcfc85ede5bd7090cab27a9b592b4187 Author: Daniel Erez <derez@redhat.com> Date: Sun Apr 19 23:40:59 2020 +0300
core: increase ticket timeout value
Increased ImageTransferClientTicketValidityInSeconds to 300
Change-Id: Iae3fb6ad0c6b5af1e2dc747bfbc67375a5cd7b2c Signed-off-by: Daniel Erez <derez@redhat.com>
But this commit fixed development setup but broke installation from rpms:
commit 81a5e757fd8768ace825140ca7dc701cc2e011ce Author: Vojtech Juranek <vjuranek@redhat.com> Date: Thu Apr 23 11:44:41 2020 +0200
spec: allow imageio config in dev env
Add $PREFIX into imageio config directory to allow imageio configuration in development environment when config files are installed into a specified directory. Currently it fails with:
[Errno 13] Permission denied: '/etc/ovirt-imageio'
Change-Id: I9e13bba0e97f681b0b07d5a135be76113e391ddc Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
Fix is here: https://gerrit.ovirt.org/c/108672
Merged, so installing from master should work now.
For development setup there is this patch in review: https://gerrit.ovirt.org/c/108620
Until the patch is ready, this is the recommended way to set up development environment:
1. Install ovirt-imageio service
dnf install ovit-imageio-daemon
2. Run engine setup
This creates a working configuration file at $PREFIX/etc/ovirt-imagei/daemon.conf
However it does not create a logger.conf file, so you need to create one. The default configuration will not work for you since you want to run ovirt-imageio as yourself, and you cannot write logs to /var/log/ovirt-imageio.
3. Create logger.conf for development
$ curl https://raw.githubusercontent.com/oVirt/ovirt-imageio/master/daemon/test/con...
$PREFIX/etc/ovirt-imageio/logger.conf
Now run imageio using:
$ ./ovirt-imageio --conf-dir $PREFIX/etc/ovirt-imageio
thanks!
-- Artur Socha Senior Software Engineer, RHV Red Hat
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JDDVTQC6K7U56D...
participants (2)
-
Artur Socha -
Nir Soffer