From: "Itamar Heim" <iheim(a)redhat.com>
To: "Lucas Vandroux" <lucas.vandroux(a)eayun.com>, "devel"
<devel(a)ovirt.org>, "潘礼洋" <liyang.pan(a)eayun.com>, "李建盛"
<jiansheng.li(a)eayun.com>
Cc: "Michal Skrivanek" <mskrivan(a)redhat.com>, "Scott Herold"
<sherold(a)redhat.com>, "Allon Mureinik"
<amureini(a)redhat.com>, "Federico Simoncelli" <fsimonce(a)redhat.com>,
"Barak Azulay" <bazulay(a)redhat.com>, "Brian
Proffitt" <bproffit(a)redhat.com>, "Alon Bar-Lev"
<alonbl(a)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?
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.
Alon