• opennebula-common: Provides the user and common files
• libopennebula-ruby: All ruby libraries
• opennebula-node: Prepares a node as an opennebula-node
• opennebula-sunstone: OpenNebula Sunstone Web Interface
• opennebula-tools: Command Line interface
• opennebula-gate: Gate server that enables communication between VMs and OpenNebula
• opennebula-flow: Manages services and elasticity
• opennebula: OpenNebula Daemon

Add the OpenNebula repository:

<xterm> # wget -q -O- http://downloads.opennebula.org/repo/Ubuntu/repo.key | apt-key add - # echo "deb http://downloads.opennebula.org/repo/Ubuntu/12.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list </xterm>

<xterm> # apt-get update # apt-get install opennebula opennebula-sunstone nfs-kernel-server </xterm>

There are two main processes that must be started, the main OpenNebula daemon: oned, and the graphical user interface: sunstone.

Sunstone listens only in the loopback interface by default for security reasons. To change it edit /etc/one/sunstone-server.conf and change :host: 127.0.0.1 to :host: 0.0.0.0.

Now we must restart the Sunstone:

<xterm> # /etc/init.d/opennebula-sunstone restart </xterm>

Skip this section if you are using a single server for both the frontend and worker node roles.

Export /var/lib/one/ from the frontend to the worker nodes. To do so add the following to the /etc/exports file in the frontend:

/var/lib/one/ *(rw,sync,no_subtree_check,root_squash)

Refresh the NFS exports by doing:

<xterm> # service nfs-kernel-server restart </xterm>

OpenNebula will need to SSH passwordlessly from any node (including the frontend) to any other node.

To do so run the following commands: <xterm> # su - oneadmin $ cp ~/.ssh/id_rsa.pub ~/.ssh/authorized_keys </xterm>

Add the following snippet to ~/.ssh/config so it doesn't prompt to add the keys to the known_hosts file:

<xterm> $ cat << EOT > ~/.ssh/config Host * StrictHostKeyChecking no UserKnownHostsFile /dev/null EOT $ chmod 600 ~/.ssh/config </xterm>

Add the OpenNebula repository:

<xterm> # wget -q -O- http://downloads.opennebula.org/repo/Ubuntu/repo.key | apt-key add - # echo "deb http://downloads.opennebula.org/repo/Ubuntu/12.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list </xterm>

<xterm> # apt-get update # apt-get install opennebula-node nfs-common bridge-utils </xterm>

Backup all the files that are modified in this section before making changes to them.

You will need to have your main interface, typically eth0, connected to a bridge. The name of the bridge should be the same in all nodes.

If you were using DHCP for your eth0 interface, replace /etc/network/interfaces with:

auto lo
iface lo inet loopback

auto br0
iface br0 inet dhcp
        bridge_ports eth0
        bridge_fd 9
        bridge_hello 2
        bridge_maxage 12
        bridge_stp off

If you were using a static IP addresses instead, use this other template:

auto lo
iface lo inet loopback

auto br0
iface br0 inet static
        address 192.168.0.10
        network 192.168.0.0
        netmask 255.255.255.0
        broadcast 192.168.0.255
        gateway 192.168.0.1
        bridge_ports eth0
        bridge_fd 9
        bridge_hello 2
        bridge_maxage 12
        bridge_stp off

After these changes, restart the network:

<xterm> # /etc/init.d/networking restart </xterm>

Skip this section if you are using a single server for both the frontend and worker node roles.

Mount the datastores export. Add the following to your /etc/fstab:

192.168.1.1:/var/lib/one/  /var/lib/one/  nfs   soft,intr,rsize=8192,wsize=8192,noauto

Replace 192.168.1.1 with the IP of the frontend.

Mount the NFS share:

<xterm> # mount /var/lib/one/ </xterm>

The oneadmin user must be able to manage libvirt as root:

<xterm> # cat << EOT > /etc/libvirt/qemu.conf user = "oneadmin" group = "oneadmin" dynamic_ownership = 0 EOT </xterm>

All the operations in this section can be done using Sunstone instead of the command line. Point your browser to: http://frontend:9869.

The default password for the oneadmin user can be found in ~/.one/one_auth which is randomly generated on every installation.

To interact with OpenNebula, you have to do it from the oneadmin account in the frontend. We will assume all the following commands are performed from that account. To login as oneadmin execute su - oneadmin.

To start running VMs, you should first register a worker node for OpenNebula.

Issue this command for each one of your nodes. Replace localhost with your node's hostname.

<xterm> $ onehost create localhost -i kvm -v kvm -n dummy </xterm>

Run onehost list until it's set to on. If it fails you probably have something wrong in your ssh configuration. Take a look at /var/log/one/oned.log.

Once it's working you need to create a network, an image and a virtual machine template.

To create networks, we need to create first a network template file mynetwork.one that contains:

NAME = "private"
TYPE = FIXED

BRIDGE = br0

LEASES = [ IP=192.168.0.100 ]
LEASES = [ IP=192.168.0.101 ]
LEASES = [ IP=192.168.0.102 ]

Replace the leases with free IPs in your host's network. You can add any number of leases.

Now we can move ahead and create the resources in OpenNebula:

<xterm> $ onevnet create mynetwork.one $ oneimage create --name "CentOS-6.4_x86_64" \ --path "http://us.cloud.centos.org/i/one/c6-x86_64-20130910-1.qcow2.bz2" \ --driver qcow2 \ --datastore default $ onetemplate create --name "CentOS-6.4" --cpu 1 --vcpu 1 --memory 512 \ --arch x86_64 --disk "CentOS-6.4_x86_64" --nic "private" --vnc \ --ssh </xterm>

(The image will be downloaded from http://wiki.centos.org/Cloud/OpenNebula)

You will need to wait until the image is ready to be used. Monitor its state by running oneimage list.

In order to dynamically add ssh keys to Virtual Machines we must add our ssh key to the user template, by editing the user template: <xterm> $ EDITOR=vi oneuser update oneadmin </xterm>

Add a new line like the following to the template:

SSH_PUBLIC_KEY="ssh-dss AAAAB3NzaC1kc3MAAACBANBWTQmm4Gt..."

Substitute the value above with the output of cat ~/.ssh/id_dsa.pub.

To run a Virtual Machine, you will need to instantiate a template:

<xterm> $ onetemplate instantiate "CentOS-6.4" --name "My Scratch VM" </xterm>

Execute onevm list and watch the virtual machine going from PENDING to PROLOG to RUNNING. If the vm fails, check the reason in the log: /var/log/one/<VM_ID>/vm.log.

• Planning the Installation
• Installing the Software
• Basic Configuration
• FAQs. Good for troubleshooting
• Main Documentation