OpenNebula 3.4 (Wild Duck)
April 11th, 2012. The OpenNebula project is proud to announce the availability of OpenNebula 3.4 (Wild Duck). The software brings countless valuable contributions by many members of our community, and specially from Research in Motion, Logica, Terradue 2.0, CloudWeavers, Clemson University, and Vilnius University.
OpenNebula 3.4 is focused on extending the storage capabilities of OpenNebula, including support for multiple Datastores. The new functionality overcomes the single Image Repository limitations in previous versions. The use of multiple Datastores provides extreme flexibility in planning the storage backend and important performance benefits, such as balancing I/O operations between storage servers, defining different SLA policies (e.g. backup) and features for different VM types or users, or easily scaling the cloud storage.
OpenNebula 3.4 also features improvements in other systems, especially in the core with the support of logic resource pools for load balancing, high availability, and high performance computing; the EC2 API with the support of elastic IPs; the Sunstone and Self-service portals with new cool features; and the EC2 hybrid cloud driver that now supports EC2 features like tags, security groups or VPCs. See below for highlights in these components.
This final release of OpenNebula 3.4 fixes several bugs since the last beta. OpenNebula 3.4 Final is considered stable and a recommended upgrade to production deployments. Special attention is needed, for those using custom Transfer Drivers, that will needed a minor update to make them work with OpenNebula 3.4.
As usual OpenNebula releases are named after a Nebula. The Wild Duck Cluster (also known as Messier 11, or NGC 6705) is an open cluster in the constellation Scutum.
In the following list you can check the highlights of 3.4 organized by component (a detailed list of changes can be found here). Also you may be interested in the detailed changes introduced in the beta release (March 30th), and in the pre-release (February, 21st).
This release includes the following minor changes in OpenNebula core:
REQUIREMENTSare automatically adapted to only use hosts from that cluster.
OpenNebula 3.4 also includes minor bug fixes and enhancements.
There are several new features in the GUI applications:
OpenNebula zones has been updated to take advantage of the new functionality offered by OpenNebula core:
There have been some improvements on the Cloud APIs:
OpenNebula 3.4 includes an improved EC2 hybrid driver, to support most of the EC2 features like tags, security groups or VPC.
OpenNebula 3.4 is API compatible with OpenNebula 3.x, so you should expect that applications and drivers developed for 3.x work with this release, with the exception of custom authentication drivers.
Also there have been changes in the Image Repository (now Datastore) and Transfer drivers. The protocol and command structure has been preserved, although some minor adaptations are needed to port existing TM or Image Repository drivers (more details here).
A detailed upgrade process can be found in the documentation.
For a complete set of changes to migrate from a 3.x installation please refer to the Compatibility Guide. You should also read this document if you are an OpenNebula 3.x user.
OpenNebula is released under the Apache 2.0 open source license. The complete source tree and binary packages for OpenNebula can be downloaded here.
The documentation of OpenNebula 3.4 can be found here. The documents are in a development state so watch out, and do not hesitate to ask in the mailing list.
The OpenNebula project would like to thank the community members and users who have contributed to this software release by being active with the discussions, answering user questions, or providing patches for bugfixes, features and documentation, and especially to: