The windows drivers are freely distributable, but not open
source. It’s not clear that various MSFT libraries used permit them to be
Regarding XenCenter: a cloud platform probably doesn’t
need a windows GUI. Hopefully 3rd party clients will be able to
manage xapi via its API (or, at some point, libvirt: http://www.xen.org/products/cloud_roadmap.html).
shows how to talk to xapi via XMLRPC (with a JSON server-side shim for unmarshalling
convenience). It’s capable of viewing consoles, powercycling VMs etc as
well as automatically picking up metadata changes from the server via the event
mechanism. We use it quite a lot internally when debugging stuff.
Hope this helps,
From: Dirk Utterback
Sent: 04 November 2009 02:59
To: Dave Scott
Cc: Mark Johnson; xen-devel@xxxxxxxxxxxxxxxxxxx;
Subject: Re: [Xen-devel] release of 'xapi' toolstack
Thanks a lot.
One quick question, is it likely the Windows things(XenCenter,
pvdrivers, and others) open source someday as well?
I just don't want to be surprised again. :)
On Wed, Nov 4, 2009 at 2:35 AM, Dave Scott <Dave.Scott@xxxxxxxxxxxxx> wrote:
Mark Johnson wrote:
> Other than the GUI, what will remained closed source in the
> XenServer product? i.e. are there any extensions to the cli,
> xapi? Any additional libs not present in xen-api-libs.hg?
> Any extensions to blktap?
At present a few server-side pieces are not open-source.
These are (from memory):
1. the heartbeat/liveset management daemon which is needed for HA (xapi talks
to this via a simple interface)
2. some 3rd party FC tools
3. a few storage backends (NetApp, EQL and StorageLink)
Some pieces of the XenServer product (eg 'Workload Balancing') are actually
off-box windows services which talk to xapi via the API. These are closed.
> I assume things like the p2v and v2v tools will remain
> closed source...
Actually there is some basic linux P2V stuff in there: the
install CD doubles as a P2V client, which uploads to a special 'P2V' VM