 Home |
Products |
Support |
Community |
News |
xen-api
Re: [Xen-API] Changes to the API
| To: | "Richard Hartmann" <richih.mailinglist@xxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-API] Changes to the API |
| From: | Tom Wilkie <tom.wilkie@xxxxxxxxx> |
| Date: | Mon, 2 Jul 2007 14:49:55 +0100 |
| Cc: | xen-api@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Mon, 02 Jul 2007 06:47:29 -0700 |
| Dkim-signature: | a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=lq5CHfLNhMUo9Vsypga9dsAoBzXJqxwWc+IYINsEy8vSpZxFe+oigUfe7zV9TabboTGE6s7+VNcAW2nb2w2JKHYLHmPP1yr5XyAba1ikX3ZPtZT2noSWbmYfOfFOF0bcKQG9YuxpJsvm09BWiENO/BtUU4KI8XD3Er1gPXZEumQ= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=C6g7zEPzHPpu/b2j6/5mCisvX1XxMSwwsilkAVJpOpWDgSNE9odF/UJYfUEfwQv4x9cyr1aMQgcjpLXW/nT+dgbIg0KUZQz2h7jn+ylg4hwOazb68kb93YWD4VCd67UD//kCrbAf2WEiDbussAQgc6+m2mGcBnC7dH+8Ta2vcfc= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <2d460de70707020342g5c9f6967ib8ef7be7c763df9a@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/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe> |
| References: | <2d460de70707020342g5c9f6967ib8ef7be7c763df9a@xxxxxxxxxxxxxx> |
| Sender: | xen-api-bounces@xxxxxxxxxxxxxxxxxxx |
Rich the wiki states that the API should not be considered final, yet. I wanted to ask what areas are still undergoing development and what parts could be considered stable. Ah I think they may be a bit out of date. Xen 3.1 implements version 1.0 of the API, and (within the constraints of an open source project) we intend to keep this API stable. I also wanted to ask if anyone has an idea about a rough ETA and/or roadmap for the final release of the API specs. The final API specs (version 1.0) can be found on the wiki, and are included in xen-unstable.hg in the docs directory. Finally, I wanted to ask what API version XEN 3.1 implements. Any future development of the API will have to be done in a backwards compatible way. Right now I'm quite busy, but when I do get a chance to come back to it we have a whole new set of security classes to add (from IBM) and some general fixes etc. Cheers Tom _______________________________________________ xen-api mailing list xen-api@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-API] Changes to the API, Richard Hartmann |
|---|---|
| Next by Date: | Re: [Xen-API] Changes to the API, John Levon |
| Previous by Thread: | [Xen-API] Changes to the API, Richard Hartmann |
| Next by Thread: | Re: [Xen-API] Changes to the API, John Levon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
