OpenNebula - Flexible Enterprise Cloud Made Simple documentation:archives:rel2.0

documentation:archives:rel2.0:accounting

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

:!: To use this functionality you need to install the Accounting Toolset Addon The accounting toolset visualizes and reports resource usage data, and allows their integration with chargeback and billing platforms. The toolset generates accounting reports using the information from the internal OpenNebula Database, and a set of policies and practices to integrate OpenNebula accounting tools within the data-centers accounting procedures.

documentation:archives:rel2.0:api

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

This documentation provides a description of the xmlrpc methods exposed by OpenNebula. The methods consist of the name of the method that will be invoked, input values needed to the execution and results of execution as outputs. The information strings returned by the

documentation:archives:rel2.0:architecture

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The OpenNebula internal architecture can be divided into three layers: * Tools, management tools developed using the interfaces provided by the OpenNebula Core. * Core, the main virtual machine, storage, virtual network and host management components.

documentation:archives:rel2.0:auth

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

Authentication and authorization module (auth module) is designed so it can be easily modified or completely replaced. In this guide we will learn how to modify the auth module so you can add new authorization methods or tune it for your needs. Adding Authentication System

documentation:archives:rel2.0:cg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

OpenNebula Components OpenNebula comprises the execution of three type of processes: * The OpenNebula daemon (oned), to orchestrate the operation of all the modules and control the VM's life-cycle * The drivers to access specific cluster systems (e.g. storage or hypervisors)

documentation:archives:rel2.0:cli

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

OpenNebula provides six commands to interact with the system: * onevm: to submit, control and monitor virtual machines * onehost: to add, delete and monitor hosts * onevnet: to add, delete and monitor virtual networks * oneuser: to add, delete and monitor users

documentation:archives:rel2.0:cluster_guide

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

In order to use your existing physical nodes, you have to add them to the system as OpenNebula hosts. You need the following information: * Hostname of the cluster node or IP * Information Driver to be used to monitor the host, e.g. im_kvm.

documentation:archives:rel2.0:cong

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

There are two contextualization mechanisms available in OpenNebula: the automatic IP assignment, and a more generic way to give any file and configuration parameters. You can use any of them individually, or both. Using Virtual Network Leases within a Virtual Machine

documentation:archives:rel2.0:dbschema

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

This page presents a simplified view of the database schema used by OpenNebula. It includes only the tables relevant for third party accounting software developers. These tables apply to both the Sqlite and MySQL backends. History table It contains information of VM execution on a given host. During its life-cycle a VM can be executed on multiple hosts (e.g. because of a migration or a stop/resume operation).

documentation:archives:rel2.0:ec2g

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

You should take into account the following technical considerations when using the EC2 cloud with OpenNebula: * There is no direct access to the dom0, so it cannot be monitored (we don't know where the VM is running on the EC2 cloud). * The usual OpenNebula functionality for snapshotting, restoring, or migration is not available with EC2.

documentation:archives:rel2.0:ec2qcg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

Overview The OpenNebula EC2 Query is a web service that enables you to launch and manage virtual machines in your OpenNebula installation through the Amazon EC2 Query Interface. In this way, you can use any EC2 Query tool or utility to access your Private Cloud. The EC2 Query web service is implemented upon the new

documentation:archives:rel2.0:ec2qcs

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

COMMON_OPTIONS VALUE --help, -h Show help --access-key , -K The name of the user --secret-key , -S The password of the user --url , -U

documentation:archives:rel2.0:ec2qec

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

In order to interact with the EC2 Service that OpenNebula implements you can use the client included in the OpenNebula distribution, but also you can choose one of the well known tools that are supposed to interact with cloud servers through the EC2 Query

documentation:archives:rel2.0:ec2qug

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The EC2 Query API offers the functionality exposed by Amazon EC2: upload images, register them, run, monitor and terminate instances, etc. In short, Query requests are HTTP or HTTPS requests that use the HTTP verb GET or POST and a Query parameter. OpenNebula implements a subset of the EC2 Query interface, enabling the creation of public clouds managed by OpenNebula. In this first release of the

documentation:archives:rel2.0:ehg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

[ ] ElasticHosts offers KVM based virtualized hosts in a cloud like fashion, i.e., à la Amazon EC2. This set of drivers speaks with the neat RESTful ElasticHosts API enabling cloudbursting if needed. As seen in the figure, OpenNebula can be used to manage a virtual infrastructure on top of physical local infrastructure. In particular, we are using dedicated physical servers to provide the fabric for the flexible virtual infrastructure, which can be dynamically increased or decreased driven by …

documentation:archives:rel2.0:evmwareg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

:!: To use this functionality you need to install the VMware Driver Addon The VMware Drivers Addon enables the management of an OpenNebula cloud based on VMware ESX, vCenter and/or VMware Server hypervisors. It uses libvirt to invoke the Virtual Infrastructure SOAP

documentation:archives:rel2.0:features

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

This section describes the key features and benefits of the last version of OpenNebula (v2.0). For more details you can download [OpenNebula 2.0 Features for Cloud Management, Integration and Production]. Key Features and Benefits for Cloud Management Private Cloud Computing Capabilities for the management of the private data center or cluster (

documentation:archives:rel2.0:hooks

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The Hook Manager present in OpenNebula enables the triggering of custom scripts tied to a change in state in a particular resource, being that a Host or a Virtual Machine. This opens a wide area of automation for system administrators to tailor their cloud infrastructures.

documentation:archives:rel2.0:ignc

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

:!: Do not forget to check the Platform Notes for a list of specific software requirements to build OpenNebula. Follow these simple steps to install the OpenNebula software: * Download and untar the OpenNebula tarball. * Change to the created folder and run scons to compile OpenNebula

documentation:archives:rel2.0:img

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The Information Manager (IM) is in charge of monitoring the cluster nodes. It comes with various sensors, each one responsible of a different aspects of the computer to be monitored (CPU, memory, hostname...). Also, there are sensors prepared to gather information from different hypervisors (currently KVM and XEN).

documentation:archives:rel2.0:img_guide

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The Image Repository system allows OpenNebula administrators and users to set up images, which can be operative systems or data, to be used in Virtual Machines easily. These images can be used by several Virtual Machines simultaneously, and also shared with other users.

documentation:archives:rel2.0:img_template

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

This page describes how to define a new image template. An image template follows the same syntax as the VM template. If you want to learn more about the image repository, you can do so here. :!: The template described here is the one expected by the oneimage command. If you are a developer and want to submit an image template using our OCA or XML-RPC interface, please take a look at the

documentation:archives:rel2.0:intro

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

What is a Private Cloud? The aim of a Private Cloud is not to expose to the world a cloud interface to sell capacity over the Internet, but to provide local users with a flexible and agile private infrastructure to run virtualized service workloads within the administrative domain

documentation:archives:rel2.0:introc

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

What is a Public Cloud? A Public Cloud is an extension of a Private Cloud to expose RESTful Cloud interfaces. Cloud interfaces can be added to your Private or Hybrid Cloud if you want to provide partners or external users with access to your infrastructure, or to sell your overcapacity. Obviously, a local cloud solution is the natural back-end for any public cloud.

documentation:archives:rel2.0:introh

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

What is a Hybrid Cloud? A Hybrid Cloud is an extension of a Private Cloud to combine local resources with resources from remote Cloud providers. The remote provider could be a commercial Cloud service, such as Amazon EC2 or ElasticHosts, or a partner infrastructure running a different OpenNebula instance. Such support for cloudbursting enables highly scalable hosting environments.

documentation:archives:rel2.0:java

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

This page contains the OpenNebula Cloud API Specification for Java. It has been designed as a wrapper for the XML-RPC methods, with some basic helpers. This means that you should be familiar with the XML-RPC API and the XML formats returned by the OpenNebula core. As stated in the

documentation:archives:rel2.0:kvmg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

KVM (Kernel-based Virtual Machine) is a complete virtualization technique for Linux. It offers full virtualization, where each Virtual Machine interacts with its own virtualized hardware. This guide describes the use of the KVM virtualizer with OpenNebula, please refer to KVM specific documentation for further information on the setup of the KVM hypervisor itself.

documentation:archives:rel2.0:ldap

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

:!: To use this functionality you need to install the LDAP Authentication Addon The LDAP Authentication addon permits users to have the same credentials as in LDAP, so effectively centralizing authentication. Enabling it will let any correctly authenticated LDAP user to use OpenNebula.

documentation:archives:rel2.0:libvirtapi

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The OpenNebula libvirt implementation lets you use any libvirt application at a distributed level. In a nutshell, you'll be able to use your libvirt XML description files and any libvirt tool, like virsh or virt-manager to connect to OpenNebula. In this way, you can manage and monitor your VMs in a distributed environment using the current libvirt tools. This is, a whole cluster can be managed as any other libvirt node.

documentation:archives:rel2.0:mysql

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The MySQL backend has been introduced in OpenNebula 2.0 as an alternative to the Sqlite backend available in previous releases. Either of them can be used seamlessly to the upper layers and ecosystem tools. These high level components do not need to be modified or configured.

documentation:archives:rel2.0:nm

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

Overview The physical hosts that will conform the fabric of our virtual infrastructures will need to have some constraints in order to be able to deliver virtual networks effectively to our virtual machines. Therefore, we can define our physical cluster under the point of view of networking as a set of hosts with one or more network interfaces, each of them connected to a different physical network.

documentation:archives:rel2.0:notes

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

Ubuntu/Kubuntu If you want to build OpenNebula install the following packages: * libsqlite3-dev * libxmlrpc-c3-dev * scons * g++ * ruby * libopenssl-ruby * libssl-dev Optional software: * ruby-dev * make * rake

documentation:archives:rel2.0:occicg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

Overview The OpenNebula OCCI is a web service that enables you to launch and manage virtual machines in your OpenNebula installation using the latest draft of the OGF OCCI API specification. The OpenNebula OCCI service is implemented upon the new OpenNebula Cloud API (OCA) layer that exposes the full capabilities of an OpenNebula private cloud; and

documentation:archives:rel2.0:occidd

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

Resources The OpenNebula OCCI API is a RESTful service to create, control and monitor cloud resources based on the latest draft of the OGF OCCI API specification. There are two types of resources that resemble the basic entities managed by the OpenNebula system, namely: * Pool Resources (PR)

documentation:archives:rel2.0:occiug

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The OpenNebula OCCI API is a RESTful service to create, control and monitor cloud resources based on the latest draft of the OGF OCCI API specification. Interactions with the resources are done through HTTP verbs (GET, POST, PUT and DELETE). OCCI Resources There are three kind of resources, listed below with their implemented methods:

documentation:archives:rel2.0:oned_conf

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The OpenNebula daemon oned manages the cluster nodes, virtual networks, virtual machines, users and image repository. The configuration file for the daemon is called oned.conf and it is placed inside the $ONE_LOCATION/etc directory. In this reference document we describe all the format and options that can be specified in

documentation:archives:rel2.0:plan

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

Overview OpenNebula assumes that your physical infrastructure adopts a classical cluster-like architecture with a front-end, and a set of cluster nodes where Virtual Machines will be executed. There is at least one physical network joining all the cluster nodes with the front-end.

documentation:archives:rel2.0:ruby

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

This page contains the OpenNebula Cloud API Specification for Ruby. It has been designed as a wrapper for the XML-RPC methods, with some basic helpers. This means that you should be familiar with the XML-RPC API and the XML formats returned by the OpenNebula core. As stated in the

documentation:archives:rel2.0:schg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

Overview The Scheduler module is in charge of the assignment between pending Virtual Machines and known Hosts. OpenNebula's architecture defines this module as a separate process that can be started independently of oned. The OpenNebula scheduling framework is designed in a generic way, so it is highly modifiable and can be easily replaced by third-party developments.

documentation:archives:rel2.0:sm

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

One key aspect of virtualization management is the process of dealing with Virtual Machines images. Allegedly, there are a number of possibly different configurations depending on the user needs. For example, the user may want all her images placed on a separate repository with only http access. Or images can be shared through NFS between all the hosts. OpenNebula aims to be flexible enough to support as many different image storage configurations as possible.

documentation:archives:rel2.0:template

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

A template file consists of a set of attributes that defines a Virtual Machine. The syntax of the template file is as follows: * Anything behind the pound sign (#) is a comment. * Strings are delimited with double quotes (“), if the a double quote is part of the string it needs to be escaped (\

documentation:archives:rel2.0:ug

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

OpenNebula is a VM manager that is executed and configured by a cluster administrator. This cluster administrator would be also the ONE administrator, and therefore he should be the holder of the account. This guide assumes that the cluster administrator is the only user for

documentation:archives:rel2.0:users

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

OpenNebula comes with an internal user/password authentication and authorization system and the ability to use an external driver that takes care of these duties. Current Authentication/Authorization module (from now on auth module) has support for user/password and rsa private/public key authentication and also user quota support. By default OpenNebula comes configured to use internal user/password authentication, here you will learn how to enable the external auth module, configure it to acce…

documentation:archives:rel2.0:vgg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

A cluster node is connected to one or more networks that are available to the virtual machines through the corresponding bridges. To set up a virtual networks you just need to know the name of the bridge to bind the virtual machines to. In this guide you'll learn how to define and use virtual networks. For the sake of completeness the following examples assumes that the cluster nodes are attached to two

documentation:archives:rel2.0:vmg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The purpose of this section is to demonstrate how to quickly deploy a VM with OpenNebula in a few easy steps. We will assume that you have properly configured OpenNebula and that you have at least one worker node running KVM (this guide does not work with Xen for the moment).

documentation:archives:rel2.0:vmwareg

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The VMware Infrastructure API (VI API) provides a complete set of language-neutral interfaces to the VMware virtual infrastructure management framework. By targeting the VI API, the OpenNebula VMware drivers are able to manage various flavors of VMware hypervisors: ESXi (free), ESX and VMware Server.

documentation:archives:rel2.0:vm_guide

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

OpenNebula is able to assign, deploy, monitor and control VMs. This guide explains how to describe the wanted-to-be-ran Virtual Machine, and how users typically interact with the system. Virtual Machine Model A Virtual Machine within the OpenNebula system consists of:

documentation:archives:rel2.0:xeng

Anonymous (anonymous@undisclosed.example.com) — 2014-01-07T11:47:53+00:00

The XEN hypervisor offers a powerful, efficient and secure feature set for virtualization of x86, IA64, PowerPC and other CPU architectures. It delivers both paravirtualization and full virtualization. This guide describes the use of Xen with OpenNebula, please refer to the Xen specific documentation for further information on the setup of the Xen hypervisor itself.