XenServer is fundamentally a packaging effort consisting of the Xen Project hypervisor, the XAPI toolstack, a control domain (currently CentOS 5.x based), and a variety of support services such as the open virtual switch. These components are then tuned and packaged into an installer which will turn an x86 based server or blade into a XenServer host. One of the most important aspects of that effort is research into what is possible within the current combination of components, and figuring out whether the new shiny thing can fit into the model, or whether the model needs to change. Because of this, its often a bit difficult to separate the research from that which might become a supported feature. Couple this with XenServer platfrom development being supportive of Citrix's commercial efforts, and its understandable why some might become confused. So this roadmap seeks to remove some of the confusion.
First the activities occuring on xenserver.org represent three distinct things.
- We have the research aspect occuring within trunk. This is bleeding edge stuff which may never see the light of day. Since we're open source, you can follow along as development occurs, and are welcome to participate as you see fit. When looking at the bleeding edge, you'll undoubtably see things which will need a bit of polish, or which may need some refactoring. Any one who might be interested in installing from trunk is welcome, but any discussion of trunk will need to occur on the xs-devel mailing list.
- We have the next version of XenServer. We've recently been working on Creedence, or as most know it; XenServer 6.5. As part of that effort, we provided access to pre-release installation media, and details on what it might contain. We want your feedback because together we can build a stronger XenServer, and that benefits everyone. That means we're going to give you details on what might be part of the upcoming release before it happens, including deep techincal stuff like performance and scalability information. With Creedence this process worked very well, and towards the end of feature development we even solicited feedback on what the future should look like.
- We provide access to the current shipping version of XenServer. xenserver.org isn't only about development, its about the install base and the users who manage it. We want to provide you with a centralized location from which to obtain everything you need to be sucessful with XenServer.
XenServer 6.5 (aka Creedence) status
XenServer 6.5 can be downloaded from the xenserver.org download page, and represents a supported release. All new XenServer installations should be made using XenServer 6.5. Creedence development has completed, and has entered the Lifecycle Maintenance (LCM) phase of engineering. This means that the majority of engineering focus has shifted to the next version of XenServer, and by extension back to trunk.
XenServer 6.2 status
XenServer 6.2 can be downloaded from the xenserver.org download page, and represents a supported release. While support for XenServer 6.2 will continue for some time, users of XenServer 6.2 are encouraged to upgrade to XenServer 6.5 at their earliest convenience to take advantage of the improved scalability and headroom in XenServer 6.5
XenServer trunk status
Automatic nightly snapshots from trunk are occuring, and with the transition from Creedence trunk activity will increase. Currently major work is underway to upgrade trunk from a CentOS 6.4 based dom0 to CentOS 7.