OpenNebula 4.2 Flame is Out!

After the ground shaking release that was OpenNebula 4.0 Eagle,  it’s time to stabilise features in this next release, OpenNebula 4.2 Flame. The principal aim  is to strengthen the most demanded and useful features, reducing the complexity in order to better support the most used functionality.

OpenNebula 4.2 Flame includes a more polished Sunstone interface, after its redesign in 4.0; with important usability enhancements. It also includes a new view for cloud users, designed to offer a minimal portal for virtual resource consumption. Datastore capacity is now monitored and used to limit the amount of storage size used by images. This is a first step to also control the runtime storage used by the VMs. The VMware backend has been completely redesigned with a more comprehensive storage scheme, more functionality and less dependencies. Also we have upgraded the Xen backend to support the new interfaces introduced in Xen 4.0. And last but no least, OneFlow, the multi-tier application (a.k.a. service) manager, it is included and fully integrated in the distribution. It includes also important new features related to service management and elasticity/auto-scaling. Check the full release notes for details.

This is a stable release and so a recommended update that incorporates several bug fixes since 4.2 Beta. We’ve done our best to keep compatibility with OpenNebula 4.0 Eagle, so any application developed for previous versions should work without effort. Be sure to check the compatibility and upgrade guides.

As usual OpenNebula releases are named after a Nebula. The Flame Nebula (catalogued as NGC 2024 and Sh2-277) is an emission nebula in the constellation Orion. It is located about 900 to 1,500 light-years away from Earth.

Relevant Links

Lavish Revamped OneFlow

1 reply

Trackbacks & Pingbacks

  1. […] new version of your favourite Cloud Management Platform has been released, with version number 4.2, and codename Flame. This OpenNebula release includes a more polished […]

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *