Discussions and observations on virtualization.
With the 1st alpha build of the new, upcoming XenServer release (codenamed " Ely") as announced by Andy Melmed's blog on the 11th October – I thought it'd be useful to provide a little retrospective on how you, the xenserver.org community, have helped getting it off to a great start by providing great feedback on previous alphas, betas and releases - and how this has been used to strengthen the codebase for Ely as a whole based on your experiences.
As I am sure you are well aware - community users of xenserver.org can make use of the incident tracking database at bugs.xenserver.org to raise issues on recent alphas, betas and XenServer releases to raise issues or problems they've found on their hardware or configuration. These incidents are raised in the form of XSO tickets which can then be commented upon by other members of the community and folks who work on the product.
Looking back on all of the XSO tickets raised on the latest 7.0 release - these total more than 200 individual incident reports. I want to take the time to thank everyone who contributed to these, often detailed, specific, constructive reports, and for working iteratively to understand more of the underlying issues. Some of these investigations are ongoing, and need further feedback, but many of them are sufficiently clear to move forward to the next step.
The incident reports were triaged and, by working with the user community, more than 80% of them have been processed. Frequently this involved questions and answers to get a better handle on what was the underlying problem. Then trying a change to the configuration or even a private fix to see and confirm if it related to the problem or resolved it. The enthusiasm and skill of the reporters has been amazing, and continually useful. At this point - we've separated the incidents into those which can be fixed as bugs, and those which are requests for features. The latter have been provided to Citrix product management for consideration.
Out of these which can be fixed as bugs, we raised or updated 45 acknowledged defects in XenServer. More than 70% of these are already fixed - with another 20% being actively worked on. The small remainder are blocked for some reason and awaiting a change elsewhere in the product, upstream or in our ability to test. The 70% of fixes have now successfully either become part of some of the hotfixes which have been released for 7.0, or are in the codebase already and are being progressively released as part of the Ely alpha programme for the community to try.
So what's next? With work continuing apace on Ely - we have now opened the "Ely alpha" as a affects-version in the incident database to raise issues with this latest build. At the same time - in the spirit of continuing to progressively improve the actively developing codebase - we have removed the 6.5 SP1 affects-version – so folks can focus on the new release.
Finally - on behalf of all xenserver.org users - my personal thanks to everyone who has helped improve both Dundee and Ely - both by reporting incidents, triaging and fixing them and by continuing to give your feedback on the latest new version. This really makes a difference to all members of the community.