-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wow. I wasn't even thinking of the latter : ) I've had some experience
with the SDK, so I'll take that stab at it. Like I said though, the
hierarchy of the VI SDK does not mesh well with the domain-oriented
architecture of libvirt, so that is a barrier.
- --
- -a
On Jan 22, 2008, at 10:38 AM, Daniel P. Berrange wrote:
On Tue, Jan 22, 2008 at 10:23:06AM -0600, Schley Andrew Kutz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Does anyone know if there is work being done on a VMware driver? If
> not, I could write one. I'm about to release an application via
> SearchServerVirtualization called ivi (Java Virtual Interface) that
> uses the VI SDK and the XenApi (cannot get libvirt to work on my dev
> platform - OS X) to enable management of both VMware VI3 boxes as
> well
> as Xen boxes. I would love to move away from the XenApi to libvirt,
> and even more so to extend libvirt to support the VI SDK.
There's probably 2 different ways to write a VMWare driver,
depending on
who your target audience is.
For people using the VirtualIntrastructure stuff, there is a enourmous
management API which you talk to using RPC (there are WSDL definition
for it IIRC).
For people using VMWare Desktop / Player / GSX there is a not really
any
good API. We'd have to manually read/write config files for guests
in the
directory that VMWare stores them, and invoke CLI tools to stop/start.
Ultimately I think we'll need impls for both approaches becaue they
are
both valid non-overlapping use cases (home users vs enterprise).
AFAIK,
there's no one working on either approach, so feel free to take a
stab at
it !
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392
2496 -=|
|=- Perl modules:
http://search.cpan.org/
~danberr/ -=|
|=- Projects:
http://freshmeat.net/
~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B
9505 -=|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFHlh0LTg8lceyAqqQRAmb6AKCAyTfCTTK5QaYz2bZAq9ClxvAvVQCg0+Bt
HindM8N0Y1cUpvI2/esXcH0=
=Ed0X
-----END PGP SIGNATURE-----