[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • 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
  • 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=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>


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 :)


XO Project

xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.