Compatibility Guide 3.8

:!: Development version of OpenNebula 3.8. The material on this page needs to be reviewed for completeness and accuracy.

This guide is aimed at OpenNebula 3.6 users and administrators who want to upgrade to the latest version. The following sections summarize the new features and usage changes that should be taken into account, or prone to cause confusion. You can check the upgrade process in the following guide

Visit the Features list and the Release Notes for a comprehensive list of what's new in OpenNebula 3.8.

inlinetoc

OpenNebula Administrators and Users

  • The new Virtual Router Appliance allows users to deploy VMs without being contextualized before, as it offers routing, port forwarding, DHCP, NTP and DNS services (ticket)
  • To ease the access to some user attributes, more variables are now available in context, namely: UNAME, GID and GNAME. Note that this information was already available in the USER template (USER[$TEMPLATE]).
  • Virtual Machines have a new state: PowerOff. A VM in poweroff is like a suspended one, but without a checkpoint file, so it can be restarted to immediately boot it in the same Host. There is also a new poweroff action (ticket)
  • The commands oneuser and onegroup have a new subcommand: batchquota. It allows to set the same quotas to several users or groups. See the Managing Quotas guide (ticket)
  • Fixed VM state transitions from SUSPENDED, UNKNOWN, STOPPED. A failed boot operation in previous version would move the VM to FAILED, making the VM state impossible to recover. In OpenNebula 3.8, the VM will return to the previous state, making possible to retry the resume operation.
  • There is a new onedb fsck command that checks the DB consistency, and fixes any problems found, like wrong 'running_vms' counters or quotas usage.

Command Line Interface

New CLI commands:

  • onegroup batchquota
  • oneuser batchquota
  • onevm poweroff
  • onedb fsck

Changed CLI commands:

  • The oneimage, onetemplate and onevm has been extended to include template options to create new VMs, VM Templates and images, respectively. For example now you can use

<xterm> #Example for oneimage $ oneimage create -d 1 –name ubuntu –path /tmp/ubuntu.qcow2 –prefix sd –type OS –driver qcow2 \

  1. -description “A OS plain installation”

#Example for onevm or onetemplate $onevm create –name “test vm” –memory 128 –cpu 1 –disk arch,data –network public </xterm>

  • You can get the list of one* list table columns using the parameter –describe. This will descibe the meaning of each column. It will also be useful to know the parameters we can pass to –list to restrict the columns shown:

<xterm> $ onevm list –describe ID : ONE identifier for Virtual Machine NAME : Name of the Virtual Machine USER : Username of the Virtual Machine owner GROUP : Group of the Virtual Machine STAT : Actual status UCPU : CPU percentage used by the VM UMEM : Memory used by the VM HOST : Host where the VM is running TIME : Time since the VM was submitted $ onevm list –list ID,NAME 

  ID NAME           
   0 web-server
   1 db-server

</xterm>

  • A new acct method is available in the ruby bindings to filter the accounting information

Sunstone

  • KVM users can now specify SPICE as graphic type to access the VM display, keyboard and mouse. Sunstone has been also updated to reflect this.
  • Sunstone now allows you to add volatile disks in the VM template creation widzard, this was a missing option completely functional through the CLI or the advanced modes in Sunstone

Storage

EC2 Cloud Server

Log files

  • Improved log file format for xml-rpc requests. Now each request message has a Request ID, and includes the User ID doing the request and all the parameters. For example:
Mon Oct 15 18:32:00 2012 [ReM][D]: Req:5560 UID:0 HostPoolInfo invoked
Mon Oct 15 18:32:00 2012 [ReM][D]: Req:5560 UID:0 HostPoolInfo result SUCCESS, "<HOST_POOL><HOST><ID..."
Mon Oct 15 18:33:23 2012 [ReM][D]: Req:5520 UID:- UserPoolInfo invoked
Mon Oct 15 18:33:23 2012 [ReM][E]: Req:5520 UID:- UserPoolInfo result FAILURE [UserPoolInfo] User couldn't be authenticated, aborting call.

Developers and Integrators

VM Life Cycle

  • New states and transitions. These transitions are only relevant to developers, users will perceive the same functionality.
    • POWEROFF
    • SHUTDOWN_POWEROFF
    • BOOT_UNKNOWN
    • BOOT_POWEROFF
    • BOOT_SUSPENDED
    • BOOT_STOPPED

Storage

  • The default path for datastores in the hosts (DATASTORE_LOCATION) can now be defined for each cluster. It is the same for all the hosts in the cluster and it defaults to the OpenNebula 3.6 value: /var/lib/one/datastores. More details in can be found in the cluster guide

VMware drivers

KVM drivers

  • Using the new cgroups support, OpenNebula can enforce the amount of CPU assigned to a VM, as defined in its template. So a VM with CPU=0.5 will get half of the physical CPU cycles than a VM with CPU=1.0 (ticket)

EC2 Cloud Server

OCCI Cloud Server

Sunstone Server

Generic Document Resources

Configuration File Changes

Changes in /ect/one/oned.conf

Changes in /etc/one/sunstone-server.conf

  • vnc_proxy_base_port has been renamed to vnc_proxy_port
  • New attribute routes: Array of files containing ruby code to extend the default sunstone-server routes

Changes in /etc/one/occi-server.conf

  • vnc_proxy_base_port has been renamed to vnc_proxy_port

Changes in EC2 Server configuration files:

  • /ect/one/econe.conf ssl_server attribute needs the port
  • /ect/one/econe.conf new attribute ebs_fstype: FSTYPE that will be used when creating new volumes (DATABLOCKs)
  • /etc/one/ec2query_templates/m1.small.erb EC2 keys