[ovirt-devel] UI Plugin to Upload ISO Files

[Alon Bar-Lev]

----- Original Message -----
> From: "Nir Soffer" <nsoffer at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "Itamar Heim" <iheim at redhat.com>, "devel" <devel at ovirt.org>, "Lucas Vandroux" <lucas.vandroux at eayun.com>, "李建盛"
> <jiansheng.li at eayun.com>, "潘礼洋" <liyang.pan at eayun.com>, "Michal Skrivanek" <mskrivan at redhat.com>, "Liron Aravot"
> <laravot at 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 at redhat.com>
> > To: "Itamar Heim" <iheim at redhat.com>
> > Cc: "devel" <devel at ovirt.org>, "Lucas Vandroux" <lucas.vandroux at eayun.com>,
> > "李建盛" <jiansheng.li at eayun.com>, "潘礼洋"
> > <liyang.pan at eayun.com>, "Michal Skrivanek" <mskrivan at redhat.com>
> > Sent: Sunday, December 14, 2014 11:47:26 PM
> > Subject: Re: [ovirt-devel] UI Plugin to Upload ISO Files
> > 
> > 
> > 
> > ----- Original Message -----
> > > From: "Itamar Heim" <iheim at redhat.com>
> > > To: "Lucas Vandroux" <lucas.vandroux at eayun.com>, "devel"
> > > <devel at ovirt.org>,
> > > "潘礼洋" <liyang.pan at eayun.com>, "李建盛"
> > > <jiansheng.li at eayun.com>
> > > Cc: "Michal Skrivanek" <mskrivan at redhat.com>, "Scott Herold"
> > > <sherold at redhat.com>, "Allon Mureinik"
> > > <amureini at redhat.com>, "Federico Simoncelli" <fsimonce at redhat.com>,
> > > "Barak
> > > Azulay" <bazulay at redhat.com>, "Brian
> > > Proffitt" <bproffit at redhat.com>, "Alon Bar-Lev" <alonbl at redhat.com>
> > > Sent: Sunday, December 14, 2014 11:35:40 PM
> > > Subject: Re: [ovirt-devel] UI Plugin to Upload ISO Files
> > > 
> > > On 12/12/2014 05:15 AM, Lucas Vandroux wrote:
> > > > Dear all,
> > > >
> > > > I'm actually working to create a custom user interface plugin for oVirt
> > > > web administration application to let user upload iso files.
> > > >
> > > > I'm in the very first stage of the project. I'm planning to use
> > > > angularjs with the ng-flow module <https://github.com/flowjs/ng-flow>
> > > > on
> > > > the client-side and a java servlet using the ovirt-iso-uploader
> > > > <http://www.ovirt.org/OVirt_engine_tools#ovirt-iso-uploader> engine
> > > > tool
> > > > on the server-side.
> > > >
> > > > All my code is going to be on Github in the following repository :
> > > > iso-uploader-plugin
> > > > <https://github.com/ovirt-china/iso-uploader-plugin>. You can also
> > > > check
> > > > a more detailed version of the specifications on my wiki
> > > > <https://github.com/ovirt-china/iso-uploader-plugin/wiki/Specifications>.
> > > >
> > > > I'm writing to you guys to know if there is a way for us to collaborate
> > > > as you may also want to develop something like this to be integrated in
> > > > the oVirt Engine.
> > > >
> > > > Best regards,
> > > >
> > > > - Lucas Vandroux （冯凯）
> > > >
> > > >
> > > 
> > > looks very nice.
> > > 
> > > This is actually very interesting (and requested by multiple folks) but
> > > i'd like to see if we should focus on the more simple "upload iso's" or
> > > it doing more than just upload ISO's, but also VMs.
> > > for the latter, architecture would probably be a servlet[1] on the
> > > engine and stream to vdsm to write to storage, so both vm disks and/or
> > > iso's could be uploaded/downloaded.
> > 
> > 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.
this should be core feature, it cannot be implemented as plugin within the current monolithic implementation.

> 
> > this should be a core feature not an add-on within the current monolithic
> > implementation, as there is no access to vdsm interaction from any of the
> > interfaces.
> 
> Nir
>