I have created a new page on the Xen Wiki where anyone wishing to post change requests to the Xen Documentation can do so: http://wiki.xensource.com/xenwiki/Xen3.xDocumentUpdateProject. If anyone makes any of these changes, please update the Wiki so people know what has been completed and what remains to be updated.
Aron Giffis from HP has been helping me with the Xen Wiki and has created a great update to the Wiki to improve the css stylesheet. You can see his proposed update at http://userstyles.org/styles/8431. I am in the process of updating the stylesheets to implement this change permanently, but you can at least see the update in the mean time.
Thanks to Aron for his help on improving the Xen Wiki.
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)
I am starting a new community initiative to collect and write Xen hypervisor case studies to demonstrate the variety of ways that the Xen hypervisor is leveraged in the IT world. The initial case study is from a Swedish company, ATG: ATG Case Study Feb 29, 2008
I have created a new section in the Wiki to store all the case studies that the community or I create. You can get to the Wiki case study section here.Â Please feel free to create your own case study and upload into the Wiki site or contact me at email@example.com if you would like my assistance. Having an updated collection of case studies is a great way for the community to show the power and capabilities of the Xen hypervisor.