For those of you writing documents that are intended to be from the Xen.org community, I have created a new About Xen.org treatment for you to leverage. The following text is currently proposed:
About Xen.org. Xen.org is the home of the open source Xen® hypervisor, a fast, secure industry standard code base for operating system virtualization. Founded and led by Ian Pratt the community benefits from the hundreds of contributors from leading hardware, software, and security vendors. Xen.org is guided by the Xen Advisory Board, which is drawn from key contributors to the project. For more information, visit www.xen.org.
If you have any comments or would like changes, please discuss in the Comments section below. I will be using this text treatment in all new Xen.org documents (e.g. xen_32-datasheet.pdf )
The Xen.org community will have a booth (#210) at the joint LinuxWorld / Next Generation Data Center event held in San Francisco, August 5- 7 at the Moscone Center. The booth will be staffed by myself as well as community members with spare time during the event. If you are planning on attending this event and would like to help please let me know. I will be creating a schedule for community members later this year as we get closer to August.
Being somewhat new to the Xen community, just my third month in the community, I want to make every effort I can to meet with people who are directly or indirectly supporting the Xen initiative. I will be posting my travel schedule on this blog to allow members the opportunity to contact me for a meeting (informal of course) to talk about Xen and possibly have a nice “Xen” refreshment (on Xen’s tab). I am based in Ft Lauderdale, Florida in the US but will be in San Francisco, CA later this month at the 2008 InfoSys Open Source Business Conference at the Palace Hotel from March 24 – 26.
The event starts Tuesday morning and I arrive early afternoon on the 24th so I have time to meet and enjoy those “Xen” refreshments with any community member. I am leaving on a red eye on the 26th so I have some time to meet during the event as well. If you are interested in offering feedback on Xen.org please contact me at email@example.com. I look forward to meeting with the community throughout the coming year.
As part of the Xen Summit at USENIX Technical Conference in Boston this June, we have the opportunity to run a full day Xen training session (xen-summit-training-overview.txt). I am looking for one or two volunteers who would like to organize and run this full day training sessions. If you are interested, please contact me at firstname.lastname@example.org.
Yesterday I just finished the migration of all physical servers to the virtualized ones. Now We (as company) have 7 servers (2 win2k3 and 5 linux) into just one. And yes, we are the first Chilean enterprise using virtualization with Xen in our data center. That makes me really happy, because the idea of use Xen to virtualize the data center, use a new technology, and all those things makes the decision a little bit… complex.
Right now, servers are in a testing period before they can go to the production environment so any test must be done now! If you have any idea for testing, just let me know!
OK, maybe the title of this post is a slight exaggeration but it’s good to have goals for the future!
It’s a goal which many would argue will be unreachable without the genesis of Strong AI. It’s also a goal where we can achieve very useful results just by trying to get there. I’m going to write a series of articles about my current work on static checking the Xen codebase. The goal here is to find errors before they occur, spot bugs that aren’t caught by human reviewers and improve the overall quality of codebase. Unfortunately, global harmony and toast which doesn’t fall butter-side-down are probably still outside the scope of this work – sorry.
This first article gives an overview of the historical background of static code checking. Future articles in this series will describe what I’m doing to apply static checking to the Xen codebase and the possibilities for Xen in the future.