On Fri, Feb 08, 2013 at 05:26:24PM -0800, Ata Bohra wrote: > > > > > NACK, as I said with previous postings, this does not belong in > > libvirt APIs, it should be built as a layer above. > [AB]: Thanks for reviewing this Daniel. I completly understand the concern of > not making it part of libvirt API, but as discussed in other thread (https://www.redhat.com/archives/libvir-list/2012-December/msg00385.html) I was unable to find API supported way to > upload OVA disk to the ESX server (which is an integral part of OVA install). See the virStorageVolUpload API. > >Further this API design fundamentally flawed as it is assuming the hypervisor > > driver can access files that are on the libvirt application > > machine which is not the case in general. > [AB]: If possible please suggest if there can be any other way to overcome this design flaw. > Further, there are two unrealted reviews that I posted fixing issues with > exisitng ESX driver, it would be useful if someone can review them. Again see the design of the virStorageVolUpload API Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list