Re: [libvirt] Question about supporting other hypervisor

On Fri, Oct 17, 2008 at 10:42:25AM +0100, Daniel P. Berrange wrote: > > As a CIM Provider, libvirt-cim is going on. > > But for CIM Client, Is not going on. > > > > Is there any reason for not supporting CIM on libvirt driver layer? > > I am thinking about cim-xml driver (like remote driver) in libvirt. > > It is certainly a possibility, but personally I'd prefer native drivers > for each hypervisor - there is only VMWare & Hyper-V left that are the > main players with no driver support. Having an abstraction layer like > libvirt run over an abstraction layer like CIM, in turn over the native > layer will make quite a complex system to debug & be inherantly less > efficient than taking to the native APIs. So although it'd probably > be more work to write a separate VMWare & Hyper-V driver, I think that > it'd result in better drivers for each in the long term. I agree that an abstraction layer doesn't sounds a good thing, *but* since there hasn't been that many volunteers to implement VMWare or Hyper-V, the fact that Hyper-V native would certainly have to be working locally on the Windows machine and be compiled with MSC [1], the fact that for VMWare we would have to do remote access with SOAP anyway for deployment issues, that all considered maybe a client CIM remote driver may not be that bad in comparison. Also having looked at the VMWare vix and SOAP APIs I'm not sure that CIM can really be that much worse (but I'm certainly biased).