• Image Repository. The Image Repository allows users to easily specify disk images from a catalog without worrying about low-level disk configuration attributes or block device mapping. Also, image access control is applied to the images registered in the repository, hence simplifying multi-user environments and image sharing. The traditional method of specifying VM disks is also fully supported. More info...

• MySQL support. OpenNebula can work now with MySQL or Sqlite DBs backends. The new MySQL support brings important performance and scalability improvements compared to the Sqlite implementation. MySQL is the recommended option for large-scale clouds. More info...

• Scalability Improvements. Several components of OpenNebula have been tuned to work with tens of thousands of VMs, including the redesign of the scheduler and adjustments to the monitoring modules.

• Cluster support. Physical hosts can now be grouped in logical clusters, so after a cluster is defined it can be then used to set the placement of a VM. More info...

• Authorization & Authentication Drivers. The authorization and authentication processes in OpenNebula have been totally redesigned. Now they can be handled natively by the OpenNebula core, offering the same functionality as OpenNebula 1.4. Alternatively, the A&A processes can be handled by an external component that can be integrated with any A&A system or user maps (e.g. LDAP, Kerberos…). As an example OpenNebula 2.0 features a quota based authorization module and user authentication based on RSA keys. More info...

• Virtual Networking Improvements. OpenNebula 2.0 lets you define generic attributes associated to a a Virtual Network (e.g. gateway, dns servers…) that can then be included in the context of a VM. This will let you easily configure VMs with multiple NICs. Additionally Virtual Networks can now be defined as public, and thus shared among multiple users.

• Improved EC2 support. The EC2 Query server can now be used with the EC2 ecosystem, supported third party applications include ElasticFox or EucaTools. More info...

• Java Bindings for the OpenNebula Cloud API (OCA) OpenNebula 2.0 includes JAVA bindings that wraps the XML-RPC interface methods exposed by the core. More info...

Here you can find the complete list of changes

OpenNebula 2.0 Beta 1 has a new DB schema which is not compatible with the schema present in OpenNebula 1.4. Host, Networks or Virtual Machines defined in OpenNebula 1.4 installs will not longer work with this release. The team will provide a DB migration script or procedure for OpenNebula 2.0 final.

OpenNebula 2.0 Beta 1 includes new API calls and methods. However there have been no changes in those API calls already supported in OpenNebula 1.4. Applications using OCA (Ruby and Java bindings) are expected to work with OpenNebula 2.0 Beta 1.

The complete source tree for OpenNebula can be freely downloaded here. The compilation has been tested on the main linux distributions, please check the platform notes for more information.

Also binary packages for Ubuntu 10.04 and CentOS 5.4 are available for download.

We will appreciate it if you let us know your feedback after trying the new version!, and report your bugs either at the development portal or at the mailing list.

Please refer to the OpenNebula 2.0 documentation guides to install and configure your system. More information about OpenNebula can be found at:

• About the project, general benefits and features
• FAQ
• Ecosystem

OpenNebula 2.0 Beta1 solves the following issues:

• Store number of VMs using an image
• Deleting an image from the pool doen't delte its file
• oneimage leaves incomplete image files in repository
• CLI should handle non existing resource IDs
• onevm show <vm_id> does not show the owner
• ftools shift to fileutils due to ruby 1.9 requirements
• http://dev.opennebula.org/issues/281 Feature Check correct number of disks
• EC2 Server: AuthFailure, account different from oneadmin
• Cancel action fails in Driver subsystem & missing method
• Rdoc dependency
• econe-server errors are not properly formatted AWS-style XML
• OCA cache doesn't get refreshed when doing a get_info
• EC2 multipart upload installation issue
• mm_sched should use the XMLRPC interface
• Host monitor should happen upon host creation
• Virtual Networks shouldn't be overwritten if a new with same name is created
• Duplicated hostnames should be allowed in host pool
• Vmware server doesn't give average net measurements
• Character & in strings breaks rexml
• Thin server should check for port availability
• oned crashes on buggy OCCI network request
• OCCI clients needs explicit SHA1/digest ruby requirement in CentOS
• Wrong mapping of CDROM devices
• wrong vnc password elemnent in the resulting XML
• Monitoring stops working with more than 10 disabled hosts
• RANK expressions using RUNNING VMS doesn't seem to work
• VCPU for XEN