11:09 a.m.
----- Original Message -----
From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "Nir Soffer" <nsoffer(a)redhat.com>
Cc: "devel" <devel(a)ovirt.org>, "李建盛"
<jiansheng.li(a)eayun.com>, "Lucas Vandroux"
<lucas.vandroux(a)eayun.com>, "Liron
Aravot" <laravot(a)redhat.com>, "潘礼洋" <liyang.pan(a)eayun.com>,
"Michal Skrivanek" <mskrivan(a)redhat.com>
Sent: Monday, December 15, 2014 5:52:36 PM
Subject: Re: [ovirt-devel] UI Plugin to Upload ISO Files
----- Original Message -----
> From: "Nir Soffer" <nsoffer(a)redhat.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: "Itamar Heim" <iheim(a)redhat.com>, "devel"
<devel(a)ovirt.org>, "Lucas
> Vandroux" <lucas.vandroux(a)eayun.com>, "李建盛"
> <jiansheng.li(a)eayun.com>, "潘礼洋" <liyang.pan(a)eayun.com>,
"Michal Skrivanek"
> <mskrivan(a)redhat.com>, "Liron Aravot"
> <laravot(a)redhat.com>
> Sent: Monday, December 15, 2014 6:47:44 PM
> Subject: Re: [ovirt-devel] UI Plugin to Upload ISO Files
>
> ----- Original Message -----
> > From: "Alon Bar-Lev" <alonbl(a)redhat.com>
> > To: "Itamar Heim" <iheim(a)redhat.com>
> > Cc: "devel" <devel(a)ovirt.org>, "Lucas Vandroux"
> > <lucas.vandroux(a)eayun.com>,
> > "李建盛" <jiansheng.li(a)eayun.com>, "潘礼洋"
> > <liyang.pan(a)eayun.com>, "Michal Skrivanek"
<mskrivan(a)redhat.com>
> > Sent: Sunday, December 14, 2014 11:47:26 PM
> > Subject: Re: [ovirt-devel] UI Plugin to Upload ISO Files
> >
> >
> > using ssh and/or nfs to send artifacts to hosts is something we should
> > avoid
> > so using iso/image uploader tools are not a solution.
> > vdsm should support uploading images using its own protocol based on the
> > authentication between engine and vdsm, is it already?
>
> Vdsm does support upload over http/https directly to storage.
>
> This feature is used to store ovf backups on storage domains, and probably
> not very efficient, but may be good enough for now.
>
> See vdsm/rpc/BindingXMLRPC.py (do_PUT)
thanks.
I hear this function is not supported by the new jsonrpc, nor will it be
supported when messaging will be used... so not sure if it is a good idea to
add functionality on top of this one.
The format (xmlrpc/jsonrpc) here is not much interesting, the interesting
part is the transport. In fact current download/uploadImage uses REST
GET/PUT for downloading/uploading the images (only the errors/messages are
reported with xmlrpc or eventually they could be reported with jsonrpc).
By design they were not mixed with the other control APIs (because it's
not control, it's data). And indeed it cannot be transported with
messaging.
Uploading/dowloading data to/from the host involves a data transport
(and http REST is the most commonly used). Which is exactly what you
need here, and it was in fact designed for this use case.
this should be core feature, it cannot be implemented as plugin
within the
current monolithic implementation.
+1
--
Federico