----- Original Message ----- > From: "Alon Bar-Lev" <[email protected]> > To: "Nir Soffer" <[email protected]> > Cc: "devel" <[email protected]>, "李建盛" <[email protected]>, "Lucas > Vandroux" <[email protected]>, "Liron > Aravot" <[email protected]>, "潘礼洋" <[email protected]>, "Michal > Skrivanek" <[email protected]> > Sent: Monday, December 15, 2014 5:52:36 PM > Subject: Re: [ovirt-devel] UI Plugin to Upload ISO Files > > ----- Original Message ----- > > From: "Nir Soffer" <[email protected]> > > To: "Alon Bar-Lev" <[email protected]> > > Cc: "Itamar Heim" <[email protected]>, "devel" <[email protected]>, "Lucas > > Vandroux" <[email protected]>, "李建盛" > > <[email protected]>, "潘礼洋" <[email protected]>, "Michal Skrivanek" > > <[email protected]>, "Liron Aravot" > > <[email protected]> > > 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" <[email protected]> > > > To: "Itamar Heim" <[email protected]> > > > Cc: "devel" <[email protected]>, "Lucas Vandroux" > > > <[email protected]>, > > > "李建盛" <[email protected]>, "潘礼洋" > > > <[email protected]>, "Michal Skrivanek" <[email protected]> > > > 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 _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
