Release: OpenNebula Cloud Management Platform 3.8

On October 22, OpenNebula project announced the availability of OpenNebula 3.8, Twin Jet.

The OpenNebula project provides a management console for Infrastructure-as-a-Service (IaaS) cloud computing platforms, with this release a set of new features are introduced and some old features are fixed. Furthermore OpenNebula 3.8 improved the integration with VMware and KVM, Twin Jet features an improved storage VMware interface with native support for VMFS and integration with cgroups and SPICE on KVM deployments.

This release includes the following changes in OpenNebula core:

  • Improved VM life-cycle, some VM transitions has been tuned to prevent from loosing VM states when a infrastructure related failure occurs. Now when a suspended/stopped/unknown VM fails to restart/resume it returns to its original state instead to retry the operation o manually delete the VM.
  • Enhanced VMware support through a new set of Datastore and Transfer Manager drivers.
  • Support for cgroups on KVM.
  • Support for SPICE on KVM.
  • Virtual Routers. There is a new ready to use network appliance that implements a virtual router which uses the information defined in the Virtual Network template to provide basic L3 services like NATting, DHCP, DNS
  • Poweroff. A VM in poweoff state is similar to suspended, but without a checkpoint file, so it can be restarted to immediately boot it in the same Host.
  • Pre and post migration driver actions. The new actions allow to easily integrate new storage backends.
  • Minor CLI improvements and template-less creation. The command line tools have undergone several minor changes and features a new set of options to create VMs and images in a single line.
  • Datastore location per cluster. Heterogeneous clouds with different hypervisors may simplify its deployment by setting the datastore location on the hosts per each cluster, instead of doing it globally as in previous versions.
  • More variables in CONTEXT. User related data can now be used directly, without the need to include and parse the whole user template.
  • More robust resubmit. Clean up operations are now synchronized with the VM transitions, making the resubmit operation safer and more robust.
Custom routes

The EC2 Query API has been greatly improved in Twin-Jet, including:

  • Implementation of the EBS interface
  • Implementation of the keypair interface

The OCCI API has been improved in Twin-Jet, including:

  • Implementation of new actions and hot plugging functionality

Sunstone & Self Service Portals includes:

  • Improved VNC proxy system
  • Plot of user consumption
  • Support for Internet Explorer