On Wed, Feb 6, 2019, 5:26 AM Fedor Gavrilov <fgavr...@redhat.com> wrote:

> Thanks, Roy! I will try setting it up according to what you suggested.
> Last attempt failed indeed: according to logs, both daemon and proxy tried
> establishing a connection with each other with some 200 OK in logs, no
> error messages but nevertheless upload did not happen after all.
>
> Speaking about it, does anyone know more straightforward way to have ISO
> disk on data domain? I am not as much interested in debugging ISO upload
> but rather attaching it to VM.
>

+1, rsync to the iso domain directory has always been useful for me. How do
we do similar with data domains?


> Thanks,
> Fedor
>
> ----- Исходное сообщение -----
> От: "Roy Golan" <rgo...@redhat.com>
> Кому: "Nir Soffer" <nsof...@redhat.com>
> Копия: "devel" <devel@ovirt.org>, "Fedor Gavrilov" <fgavr...@redhat.com>
> Отправленные: Среда, 6 Февраль 2019 г 9:47:27
> Тема: [ovirt-devel] Re: imageio proxy and engine dev setup
>
>
>
> On Tue, 5 Feb 2019 at 20:58, Nir Soffer < nsof...@redhat.com > wrote:
>
>
>
> On Tue, Feb 5, 2019 at 6:46 PM Fedor Gavrilov < fgavr...@redhat.com >
> wrote:
>
>
> Right!
>
> Oh, it just occured to me that imageio prject is two parts and they expect
> me to be in proxy/ directory in the installation docs.
> There is indeed a make-install goal there :)
>
> Tried running it and it seems now setup script recognizes it now.
>
> Right, the instructions should be improved to show all the steps.
>
> This should work:
>
> git clone ...
> cd ovirt-imageio
> make
> cd proxy
> make install-dev ENGINE_PREFIX=/home/nsoffer/ovirt-engine
>
> /home/nsoffer/ovirt-engine/bin/engine-setup
> (configure it...)
>
> There are 2 bugs here - 1. the engine will fail to talk with the proxy
> because the default proxy
> address is localhost:54323 which will fail ssl verification. This needs to
> be address in the
> engine setup plugin
> 2. The engine will not fail an attempt to upload when it can't actually
> communicate with the proxy. ImageTransfer needs validation there.
>
> To fix it you need to:
> $ENGINE_PREFIX/bin/engine-config -s
> ImageProxyAddress=OVIRT-ENGINE-FQDN:54323
>
>
>
>
> export PYTHONPATH=/home/nsoffer/src/ovirt-imageio/common
> ./ovirt-imageio-proxy
>
> Nir
>
>
>
>
> Thanks!
> Fedor Gavrilov
>
> ----- Исходное сообщение -----
> От: "Fedor Gavrilov" < fgavr...@redhat.com >
> Кому: "Nir Soffer" < nsof...@redhat.com >
> Копия: "devel" < devel@ovirt.org >
> Отправленные: Вторник, 5 Февраль 2019 г 17:33:15
> Тема: [ovirt-devel] Re: imageio proxy and engine dev setup
>
> Hi,
>
> I tried that already unfortunately. Executing make install-dev from
> imageio sources directory complains about no such target.
> Autocomplete for make suggests the following:
>
> [fgavrilo@localhost ovirt-imageio]$ make
> all check clean common daemon dist proxy rpm srpm
>
> Wasn't successful with these targets either.
>
> Fedor Gavrilov
>
> ----- Исходное сообщение -----
> От: "Nir Soffer" < nsof...@redhat.com >
> Кому: "Fedor Gavrilov" < fgavr...@redhat.com >
> Копия: "devel" < devel@ovirt.org >, "Daniel Erez" < de...@redhat.com >,
> "Roy Golan" < rgo...@redhat.com >
> Отправленные: Вторник, 5 Февраль 2019 г 17:18:42
> Тема: Re: [ovirt-devel] imageio proxy and engine dev setup
>
> On Tue, Feb 5, 2019 at 5:05 PM Fedor Gavrilov < fgavr...@redhat.com >
> wrote:
>
> > Hi,
> >
> > It seems to be rather difficult to have development setup for the engine
> > with imageio proxy.
> > engine-setup script never asks about it, running it again with
> > --reconfigure-optional-components changes nothing and answers file
> contains
> > no mention of imageio (thus,
> > https://bugzilla.redhat.com/show_bug.cgi?id=1446094 does not look to be
> > fixed for dev setups). There is no package to install separately either.
> >
> > Quite confused now. Do you happen to know what am I missing?
> >
>
> Installing with development engine (not installed with rpms) is documented
> here:
>
>
>
> http://ovirt.github.io/ovirt-imageio/installation.html#installation-with-ovirt-engine-developer-environment
>
>
> >
> > Fedor Gavrilov
> > _______________________________________________
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> >
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JTLEMRZMGMNNLKNCJ45L2VJO5EANY56W/
> >
> _______________________________________________
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HVEXCKBLSRDRTSLHM2SYCHFQVVQQEBUF/
>
> _______________________________________________
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IPWTKN6Y2GGF3JBTZXH2RG75E2EDC4DX/
> _______________________________________________
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/RC22OL7HB5ZL6CO32NZ5AND66QRIWATG/
>
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/55J34KI224CD5PODTTVICFYABFNRPLVV/

Reply via email to