On Wed, Aug 27, 2008 at 10:38:23AM -0700, Orr, David-P64407 wrote:
Thanks for the response. I will look that the functions that you
have
pointed out for the other drivers here and see how they would be
implemented for ours. Based on your description I think we would use a
stateless driver, since there are external tools and configurations
available.
To answer your question, it is actually a version of VMware Workstation
with a Hypervisor added to it. This is for our TVE product here at
General Dynamics; here is a link to the product description:
In that case, I definitely agree that you should aim for a stateless
driver. VMWare has pre-existing config files / tools / APIs that can
be used for the libvirt driver.
Another question, how mature is the CIM interface of libvirt. I
have
not had much time to look at it yet, but we would be using it for remote
management.
The libvirt-CIM work is very active - there's another mailing
list you could ask on, if they don't notice your questions here
http://libvirt.org/CIM/
https://www.redhat.com/mailman/listinfo/libvirt-cim/
I know the people working on CIM have a good test suite that is
validating their work on a frequent basis against Xen and QEMU
libvirt drivers. This is described in their wiki pages
http://wiki.libvirt.org/page/Cimtest
Regards,
Daniel
--
|: Red Hat, Engineering, London -o-
http://people.redhat.com/berrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org -o-
http://ovirt.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|