This shows you the differences between two versions of the page.
— | software:rnotes:rn-rel1.2 [2014/01/07 11:47] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~NOTOC~~ | ||
+ | < | ||
+ | |||
+ | February 9th, 2009. The OpenNebula team is happy to announce the availability of OpenNebula 1.2, the second stable release of the project. This is an important milestone for the project and marks that most of the components of OpenNebula are now in place. This is an stable release, | ||
+ | |||
+ | ===== New Features and Highlights in OpenNebula 1.2 ===== | ||
+ | |||
+ | OpenNebula 1.2 presents important improvements in the following areas: | ||
+ | * **Image Management**, | ||
+ | |||
+ | * **Networking**. With OpenNebula 1.0 it is difficult to track the MAC/IPs in use by the running VMs, and its association with physical networks. This mechanism does not scale when dealing with tens of VMs. The new Virtual Network Manager module allows you to define virtual networks and it leases IP-MAC pairs to VMs, so you do not have to keep track of the addresses in use. In this way it is pretty much like an embedded DHCP server. Additionally, | ||
+ | |||
+ | * **Robustness and scalability**, | ||
+ | |||
+ | ===== General Improvements in OpenNebula 1.2 ===== | ||
+ | |||
+ | The build system has been improved, now it can better detect the location and compilation flags for the libraries used by OpenNebula. Also support for gcc 4.3 has been added. | ||
+ | |||
+ | The logging facilities of OpenNebula core now includes support for logging arbitrary driver messages, that likely will help in debugging wrong configurations. | ||
+ | |||
+ | Finally several components underwent changes to make more coherent the naming pattern. These changes include the command line interface, that also got rid of | ||
+ | superfluous messages and the internal database schema. | ||
+ | |||
+ | We would like to thank the great labour done by Soren Hansen, reflected in submitted patches that helped to get OpenNebula closer to work with Ubuntu and Debian and cleared subtle and important issues: [[http:// | ||
+ | |||
+ | ===== Getting OpenNebula 1.2 ===== | ||
+ | |||
+ | The complete [[http:// | ||
+ | |||
+ | ===== About OpenNebula ===== | ||
+ | |||
+ | Please refer to the OpenNebula [[documentation: | ||
+ | * [[about: | ||
+ | * [[faq: | ||
+ | * [[ecosystem: | ||
+ | |||
+ | ====== Technology Dependencies ====== | ||
+ | |||
+ | **Frontend** | ||
+ | |||
+ | The OpenNebula Server machine needs to have installed the following software: | ||
+ | |||
+ | * **ruby** >= 1.8.5 | ||
+ | * **sqlite3** >= 3.5.2 | ||
+ | * **sqlite3-dev** >= 3.5.6-3 | ||
+ | * **sqlite3-ruby** | ||
+ | * **libxmlrpc-c** >= 1.06 | ||
+ | * **scons** >= 0.97 | ||
+ | |||
+ | Most of this software is already packaged in linux distributions. Here are the packages needed in a debian lenny. | ||
+ | |||
+ | * **ruby**: ruby | ||
+ | * **sqlite3**: | ||
+ | * **sqlite3-dev** : libsqlite3-dev | ||
+ | * **sqlite3-ruby**: | ||
+ | * **libxmlrpc-c**: | ||
+ | * **scons**: scons | ||
+ | |||
+ | |||
+ | **Worker Nodes** | ||
+ | |||
+ | The cluster worker-nodes need to have installed: | ||
+ | |||
+ | * **ruby** >= 1.8.5 | ||
+ | * **sudo** >= 1.6.9 | ||
+ | |||
+ | and either | ||
+ | |||
+ | * **xen** >= 3.1 | ||
+ | |||
+ | or | ||
+ | * **kvm** >= kernel 2.6.20 | ||
+ | * **libvirt** >= 0.4.0 | ||
+ | | ||
+ | |||
+ | |||
+ | ====== Supported Platforms ====== | ||
+ | |||
+ | * **Linux** : Tested with the CentOS 5/Ubuntu 8.04/Fedora 8/Debian Etch distribution. | ||
+ | |||
+ | |||
+ | ===== Solved Bugs ===== | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | [[http:// | ||
+ | |||
+ | ===== Known Issues ===== | ||
+ | |||
+ | * Under some configuration using ballooning with the Xen hypervisor, the apparent free memory of a cluster node is less than the actual one, so no new VMs are allocated to it. A solution for this [[http:// | ||
+ | * The KVM monitoring script may provide wrong information because it calculates FREECPU and USEDCPU based on the top utility. A solution for this [[http:// | ||
+ | * OpenNebula 1.2 uses '' |