Re: [PATCH 1/5] Public API to allow defining new domain using OVA file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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).
 
>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.
 
1. https://www.redhat.com/archives/libvir-list/2012-December/msg01377.html
2. https://www.redhat.com/archives/libvir-list/2013-January/msg00007.html

Thanks!
Ata
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]