-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
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 iv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cool. I've been looking at the website and source trying to get a
handle on the architecture and how to fit in the VI SDK. I would like
to discuss the possibility of adding a third architecture.
The source for ivi was just committed and is viewa
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 t
-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 li
