In the following list you can check the highlights of 3.2 by component, a detailed list of changes can be found here:

Most of the changes in the new release have been done in the OpenNebula core (oned) and libraries to support the following new features:

• Improved Network Management, The network operations are now coupled with the VM life-cycle. This simplifies the management of networking (no hooks are needed), and solves previous issues with VLANs when migrating and restoring VMs. The network drivers define three actions (pre-boot, post-boot and clean) that can be easily customized if needed. Default installation comes with 8021.Q, OpenvSwtich and ebtables VLAN drivers. Also the firewalling functionlity has been embedded in the new networking driver.

• Flexible Network definition. Networks can be now defined with an arbitrary range including an starting and ending IP, network and network mask or CIDR notation. It is possible also to define a network and a starting IP to lease addresses.

• New Lease Operations. Network leases can now be put on hold to reserve them. This comes in handy when there are some IPs within the VLAN already assigned (e.g. .1 to the gateway). When a lease is put on hold OpenNebula will not use it for a VM, til it is released.

We've further improved the usability of SunStone, and extend it to catch up with OpenNebula core's new features. Also some of the dialogs has been simplified and polished. In this new release the dependencies with third party libraries has been updated to the latest versions.

This release includes some improvements in the web ui of the Zones component, as well as minor bug fixes.

The OCCI API has been extended to include:

• VM types, can now be defined in the server configuration file and tagged with arbitrary information, like size, QoS parameters or price. These types can be programatically queried through the API.
• Network templates, to support the new VLAN features in OpenNebula the OCCI networks can now be defined through a template, as for Virtual Machines.

OpenNebula 3.2 is API compatible with OpenNebula 3.0, so you should expect that applications, and drivers developed for 3.0 to work with this release, with the exception of custom authentication drivers. A detailed upgrade process upgrade can be found in the documentation.

For a complete set of changes to migrate from a 3.0 installation please refer to the Compatibility Guide. You should also read this document if you are an OpenNebula 3.0 user.

• This release includes a set of VMware drivers that are not fully integrated yet.

• CPU Quotas are bypassed if CPU attribute is not define in the VM template.

• There are a couple of known issues and limitations in 3.0, you can check the development portal to find out what you should expect from OpenNebula 3.2

OpenNebula is released under the Apache 2.0 open source license. The complete source tree and binary packages for OpenNebula can be downloaded here.

Please report any bug or send feedback at the development portal or at the mailing list.

The documentation of OpenNebula 3.2 can be found here. The documents are in a development state so watch out, and do not hesitate to ask in the mailing list.

More information about the project can be found at the project web page. You may be also interested in checking the OpenNebula Ecosystem that includes many interesting projects contributed by the community to enhance or add new features to OpenNebula.