Quick update for those of you following the Xen API Community project – I am close to having a Xen developer from Citrix confirmed for our next meeting to answer questions about the API specifications. Since Xen Summit is coming up, I am planning on having this 2nd project meeting the last week of June or first week of July. I will update the Blog as well as the Xen API Project page on the Wiki: http://wiki.xensource.com/xenwiki/XenApi with the meeting information.
The first meeting of the Xen API Community Project has been completed and meeting minutes are available in the Xen Wiki at http://wiki.xensource.com/xenwiki/XenApi#preview. A follow-up meeting will be scheduled for later this month or early June to discuss the existing Xen API specifications with an emphasis on comparing them to the Citrix XenServer API definitions available at http://community.citrix.com/display/cdn/XenServer%20SDK. Anyone interested in assisting in this project is encouraged to review the API specifications in preparation for the next meeting.
The kickoff meeting for the Xen-API community project is scheduled for May 15, 2008 at 4pm EST. I am still looking for people interested in working on this project and the meeting is open to all Xen.org community members. I will be posting all meeting minutes and activities on the Xen Wiki once the project is underway so attendance at the meetings is not mandatory; however, the first few meetings will be important as we discuss what work items need to be complete and people get a chance to volunteer.
The dial-in information for the meeting is:
Several community members have contacted me recently about the Xen-API utilities. I looked into this and discovered a great opportunity for community members looking for a project to contribute to. So, I am announcing a new community effort to complete the development of the Xen-API utilities. If you are interested in working on the Xen-API project please email me at firstname.lastname@example.org and I will call a meeting in mid-May with all people interested to get the project underway.
NOTE – This interface is not to be seen as a replacement for the existing XML-RPC interface and people should not infer anything by this project.
Here are some thoughts on the importance of the Xen-API if you are considering joining this community effort:
- Xen-API cleans up a lot of the cruft of the older APIs
- Authentication aspect to the Xen-API allows the API to be used off-box securely
- Xen-API’s event registration / dispatch piece is much better than the old API, making it much easier to build web GUIs or health monitors
- The Xen-API has two mechanisms, one for synchronous task invocation, and a congruent one for asynchronous tasks. This means, for example, that you can reboot a VM, and either block waiting for it to complete, or get a task handle and poll back later. This gives application developers the freedom to choose how they interact with Xend
- Xend will get a code update from this project and will give developers a chance to learn more about xm as well as Xend (Xend is written in Python)
- Xen-API already has C and Python bindings in the Xen tree; Ruby bindings are also rumored to exist
Available information on Xen-API:
- xen-api mailing list
- WIKI Page: http://wiki.xensource.com/xenwiki/XenApi
- Xen Summit Presentation on Xen-API from April 2007 event
- Xen-API documents in xen-unstable tree at /docs/xen-api (need graphviz installed to make the xen-api Latex document)