This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] RE: [Xen-devel] release of 'xapi' toolstack

To: 'Mark Johnson' <johnson.nh@xxxxxxxxx>
Subject: [Xen-API] RE: [Xen-devel] release of 'xapi' toolstack
From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Date: Tue, 3 Nov 2009 18:35:16 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 03 Nov 2009 10:35:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <521a4d120911030956n399938cdh59fd5330d34084b1@xxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <81A73678E76EA642801C8F2E4823AD2143B74F148F@xxxxxxxxxxxxxxxxxxxxxxxxx> <521a4d120911030807v33b0e495j26364f55f5680609@xxxxxxxxxxxxxx> <81A73678E76EA642801C8F2E4823AD2143B74F1493@xxxxxxxxxxxxxxxxxxxxxxxxx> <521a4d120911030956n399938cdh59fd5330d34084b1@xxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acpcru+9H4iuQtrGR+a9YYa7MJDLKwAArjag
Thread-topic: [Xen-devel] release of 'xapi' toolstack
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 
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 


xen-api mailing list