XenServer.next Alpha Available for Download
// Latest blog entries
XenServer.next Alpha Available
The XenServer engineering team is pleased to announce the availability an alpha of the next release of XenServer, code named "Creedence". XenServer Creedence is intended to represent the latest capabilities in XenServer with a target release date determined by feature completeness. Several key areas have been improved over XenServer 6.2, and singificantly we have also introduced a 64 bit control domain architecture and updated the Xen Project hypervisor to version 4.4. Due to these changes, we are requesting tests using this alpha be limited to core functionality such as the installation process and basic operations like VM creation, start and stop. Performance and scalability tests should be deferred until a later build is nominated to alpha or beta status.
This is pre-release code and as such isn't appropriate for production use, and is unlikely to function properly with provisioning solutions such as Citrix XenDesktop and Citrix CloudPlatform. It is expected that users of Citrix XenDesktop and Citrix CloudPlatform will be able to begin testing Creedence within the XenServer Tech Preview time-frame announced at Citrix Synergy. In preparation for the Tech Preview, all XenServer users, including those running XenDesktop, are encouraged to validate if Creedence is able to successfully install on their chosen hardware.
When does the alpha period start?
The alpha period starts on May 19th 2014
When does the alpha period end?
There is no pre-defined end to the alpha period. Instead, we're providing access to nightly builds and from those nightly builds we'll periodically promote builds to "alpha.x" status. The promotion will occur as key features are incorporated and stability targets are reached. As we progress the alpha period will naturally transition into a beta or Tech Preview stage ultimately ending with a XenServer release. Announcements will be made on xenserver.org when a new build is promoted.
Where do I get the build?
The build can be downloaded from xenserver.org at: http://xenserver.org/index.php?option=com_content&view=article&layout=edit&id=142
If I encounter a defect, how do I enter it?
Defects and incidents are expected with this alpha, and they can be entered at https://bugs.xenserver.org. Users wishing to submit or report issues are advised to review our submission guidelines to ensure they are collecting enough information for us to resolve any issues.
Where can I find more information on Creedence?
We are pleased to announce a public wiki has been created at https://wiki.xenserver.org to contain key architectural information about XenServer; including details about Creedence.
How do I report compatibility information?
The defect system offers Hardware and Vendor compatibility projects to collect information about your environment. Please report both successes and failures for our review.
What about upgrades?
The alpha will not upgrade any previous version of XenServer, including nightly builds from trunk, and there should be no expectation the alpha can be upgraded.
Do I need a new XenCenter?
Yes, XenCenter has been updated to work with the alpha and can be installed from the installation ISO.
Will I need a new SDK?
If you are integrating with XenServer, the SDK has also been updated. Please obtain the SDK for the alpha from the download page.
Where can I ask questions?
Since the Creedence alpha is being posted to and managed by the xenserver.org team, questions asked on Citrix Support Forums are likely to go unanswered. Those forums are intended for released and supported versions of XenServer. Instead we are inviting questions on the xs-devel mailing list, and via twitter to @XenServerArmy. In order to post questions, you will need to subscribe to the mailing list which can be done here: http://xenserver.org/discuss-virtualization/mailing-lists.html. Please note that the xs-devel mailing list is monitored by the engineering team, but really isn't intended as a general support mechanism. If your question is more general purpose and would apply to any XenServer version, please validate if the issue being experienced is also present with XenServer 6.2 and if so ask the question on the Citrix support forums. We've also created some guidelines for submitting incidents.
Shared via my feedly reader
Post a Comment