Rolling upgrades, federated identity and tighter platform integration reflect software maturity; continuous integration process drives software reliability The ninth release of OpenStack, code-named Icehouse, has been released with new features reflecting a community-wide effort to bring the voice of the user into the rapidly maturing open source cloud software platform.
The software, used by hundreds of companies for building public, private, and hybrid clouds, adds features such as rolling upgrades in OpenStack Compute (Nova). Rolling upgrades simplify the process of upgrading to new versions of the OpenStack software by not requiring virtual machine (VM) instances to be shut down in order for upgrades to install.
Each OpenStack release has attracted larger and larger groups of contributors. The Icehouse release had 1,202 contributors, a 32 percent increase from the Havana release six months ago. Approximately 350 new features and 2,902 bug fixes were added in the Icehouse release cycle, with a focus on testing, maturity and stability. A new focus on third-party continuous integration (CI) systems has resulted in 53 external systems testing OpenStack compatibility across broad sets of hardware and software configurations. OpenStack Dashboard (Horizon) now supports 16 languages, and the internationalization team translated nearly 700,000 words during the Icehouse cycle.
Top companies contributing code to the Icehouse release were Red Hat, IBM, HP, Rackspace, Mirantis, SUSE, OpenStack Foundation, eNovance, VMware and Intel. Top users contributing code also included Samsung, Yahoo! and Comcast.
Among the approximately 350 new features added are a new program, OpenStack Database Service (Trove), which was incubated during the Havana release cycle and is now available in the Icehouse release. Programs in incubation include OpenStack Bare Metal (Ironic), OpenStack Messaging (Marconi) and OpenStack Data Processing (Sahara).
Features new to Icehouse include:
- OpenStack Compute (Nova): New support for rolling upgrades minimizes the impact to running workloads during the upgrade process. Testing requirements for third-party drivers have become more stringent, and scheduler performance is improved. Other enhancements include improved boot process reliability across platform services, new features exposed to end users via API updates (e.g., target machines by affinity) and more efficient access to the data layer to improve performance, especially at...