This shows you the differences between two versions of the page.
— | software:rnotes:rntp1 [2014/01/07 11:47] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Technology Preview Overview ====== | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | ====== Feature Summary ====== | ||
+ | |||
+ | The OpenNebula Virtual Infrastructure Engine differentiates from existing VM managers in its **highly modular and open architecture designed to meet the requirements of cluster administrators**. | ||
+ | * **Efficient Resource Management**. The scheduling module provides a generic framework to build any scheduling policy. The default scheduling policy determines the best host to start a VM according to requirement and rank expressions consisting on infrastructure parameters. | ||
+ | * **Centralized Management**. A single access point to manage a pool of VMs and physical resources. | ||
+ | * **3rd Party Software Integration**. The OpenNebula Engine provides a command line interface for monitoring and controlling VMs and physical resources quite similar to that provided by well-known cluster management services. Such interface allows its integration with third-party tools, such as LRMs (Local Resource Managers), service adapters, VM image managers…; | ||
+ | * **Open and Flexible Architecture**. The access to the hypervisors is performed through customizable programs. So the administrator can taylor the behavior of OpenNebula by adding new infrastructure metrics and parameters or even supporting new Hypervisors. | ||
+ | * **Ease of Installation and Administration**. OpenNebula is installed on a cluster front-end without requiring the installation of new services in the remote resources, apart from the Xen Hypervisor. | ||
+ | * **Open Source Software**. OpenNebula is open source software released under Apache license v2.0 and support is provided through a mailing lists. | ||
+ | * **OpenNebula is an Active Project**. We are working to extend its functionality. Please check the [[software|Roadmap Section]]. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ====== Technology Dependencies ====== | ||
+ | |||
+ | **Frontend** | ||
+ | |||
+ | The ONE 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 | ||
+ | |||
+ | |||
+ | **Hosts** | ||
+ | |||
+ | |||
+ | Provisioning hosts (here Host 1 and Host 2) need to have installed: | ||
+ | |||
+ | * **ruby** >= 1.8.5 | ||
+ | * **sudo** >= 1.6.9 | ||
+ | * **xen** >= 3.1 | ||
+ | | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ====== Supported Platforms ====== | ||
+ | |||
+ | * **Linux** : Tested with the Debian distribution. | ||
+ | * **Mac OS X 10** | ||
+ | |||
+ | ====== Known Problems ====== | ||
+ | |||
+ | * The ONE database file (that lives in $ONE_LOCATION/ | ||
+ | * Whenever the possibility to install ONE in the NFS server is unfeasible, there is a solution involving a soft link that points from ONE's **var** directory to a local empty file called one.db that will be used as the ONE database. A sample of a bash command that will perform this operation is: | ||
+ | < | ||
+ | $> mkdir / | ||
+ | $> touch / | ||
+ | $> ln -s / | ||
+ | </ | ||
+ | After this make sure this file is readable and writable by < | ||