Deploying an open source enterprise cloud just got a little bit easier yesterday with the release of the newest version of the OpenStack platform: Icehouse. To quote an email from OpenStack release manager Thierry Carrez announcing the release, "During this cycle we added a new integrated component (Trove), completed more than 350 feature blueprints, and fixed almost 3000 reported bugs in integrated projects alone!"
We looked at a sneak peek of OpenStack Nova (compute) a few weeks ago, thanks to Red Hat project manager Steve Gordon, but to quickly summarize: one of the most exciting new features is the ability to do rolling live upgrades. There are also numerous new features supported for various hypervisors, API upgrades, and other new features.
Support for containers has improved significantly, which is surely welcome news to anyone looking to use Docker in an enterprise environment.
Storage has also improved, with the inclusion of an object replication feature within Swift, the ability of clients to communicate with multiple Swift clusters, system level metadata support, and more. Block storage through Cinder has improved as well, with users now able to import/export backups directly to Cinder, update volume type encryption, change the types of existing volumes, delete quota, and other important improvements.
This, of course, is only a sampling of the hundreds of new features available in the Icehouse release. For a more comprehensive list, check out the official release notes, or check out the individual lists of bugfixes and new features at the links below. And, if your favorite feature request didn't make this release cycle, now is a perfect time to get involved and start contributing.
- Compute (Nova)
- Object Storage (Swift)
- Image Service (Glance)
- Networking (Neutron)
- Block Storage (Cinder)
- Identity (Keystone)
- Dashboard (Horizon)
- Telemetry (Ceilometer)
- Orchestration (Heat)
- Database Service (Trove)
Just like when any other piece of software comes out, most folks aren’t compiling and installing it from source, but rather, waiting on a vendor to do the hard work and heavy lifting for them, as well as, helping to ensure that the software will run smoothly on their distribution. Each distributor follows their own release cycle. Some made test versions available before Icehouse was even officially released, but for production systems, you'll probably want to wait until your vendor has tested and hardened your release and made sure that they can provide the support you count on.
Now, onward to building the Juno release!