[Xen-API] Future of "current" Python API and further developemen

To:	xen-api@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-API] Future of "current" Python API and further developement
From:	Olivier LAMBERT <lambert.olivier@xxxxxxxxx>
Date:	Mon, 1 Mar 2010 09:35:24 +0100
Delivery-date:	Mon, 01 Mar 2010 00:35:21 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=H7amGN3C88JuV9AKw6EwOn0tcpkJQbuEFRYu8zqQYyM=; b=YqOX7SuUafwvr7bihDlpwSBqzsBmGFJBuDkUeEc9KqE4DzHofpc1WL3lj25ayRt2i3 61yjr9a/WuHMeh1QhTBWkJJpw2czfn1ybvsXV9wYzbfOs7svF0iJNeIq0qiMOa+rR2dH JTSfrqZdWbHqyhYPe6SfuzSJirMc2eI1qzDbE=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=N0njqksC4jWzDWdtbBBeQd/TIsl+2Mj11Dnprpi5WEBgnc+H069jGEKPKjPjThPTHW jyMyitMjhaEuHw+zfMqH8c1/KUeuWrOkCCcSjOgBdIsxXja7dhZZCcY7XdwiQJP+eqhq wZmyXLEENKjwoSfQzcIzZws1EfR10odYnfh9s=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-api-bounces@xxxxxxxxxxxxxxxxxxx

Hello,

I would like to know if the python API, which is part of Xen in Debian
package, will be still incorporated in next versions. I know it can be
a question for packagers, but it's more to understand if standalone
Xen and its python API have a future (opposed to XCP, but XCP is not
always fitted for certain purpose, when standalone Xen is "enough").
If not, does OCaml one can replace it ? For example, current ocml
version of xapi can drive Xen hypervisor in Debian Lenny (v3.2 of xen)
?

Because it's hard to take decisions about interface for this API if I
don't really understand the roadmap between these products :)

Regards,


Olivier
XO Project
http://xen-orchestra.com

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

WARNING - OLD ARCHIVES

xen-api

[Xen-API] Future of "current" Python API and further developement