[ovirt-devel] UI Plugin to Upload ISO Files

[Federico Simoncelli]

----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Federico Simoncelli" <fsimonce at redhat.com>
> Cc: "Alon Bar-Lev" <alonbl at redhat.com>, "devel" <devel at ovirt.org>, "李建盛" <jiansheng.li at eayun.com>, "Lucas Vandroux"
> <lucas.vandroux at eayun.com>, "Liron Aravot" <laravot at redhat.com>, "潘礼洋" <liyang.pan at eayun.com>, "Michal Skrivanek"
> <mskrivan at redhat.com>
> Sent: Monday, December 15, 2014 11:32:47 PM
> Subject: Re: [ovirt-devel] UI Plugin to Upload ISO Files
> 
> On 12/16/2014 12:27 AM, Federico Simoncelli wrote:
> >>
> >>
> >> iirc, the current verbs allow vdsm to download or upload, not the
> >> engine. not sure if this will work with "streaming" the images via the
> >> engine, vs. having to 'store and forward' them.
> >
> > Using "download" would require 'store and forward'. On the other hand
> > upload should support streaming because engine (or its separate component)
> > would be just a (streaming) proxy between the client and vdsm.
> >
> 
> I thought 'upload' is vdsm pushing to say, glance. not accepting from
> engine?

Yeah it's confusing. Those are different upload/download verbs that
are not involving data to/from engine at all.

Basically those are regular tasks: upload or download an image to/from
an http server. They go through control path because data path is
between vdsm and the remote http server.

The REST api that we're discussing here instead is the (let's say)
glance-like interface that was designed exactly for this download
and upload image use-case from the calling endpoint (it is used for
the ovf files and I think hosted-engine is using it to inject the
engine appliance).

In mind we had streaming, not sure how much of that ended up in
real code (schedule was extremely tight at that time).

-- 
Federico