Upgrading from Previous Versions 4.0

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

This guide describes the installation procedure for systems that are already running a 2.x or 3.x OpenNebula. The upgrade will preserve all current users, hosts, resources and configurations; for both Sqlite and MySQL backends.

Read the Compatibility Guide and Relase Notes to know what is new in OpenNebula 4.0.

Driver Changes

Driver Names

OpenNebula driver names had changed the default names in the configuration file. Now the names of the vmm and im drivers are not prepended by the type of driver:

  • vmm_kvm → kvm
  • vmm_xen → xen
  • vmm_vmware → vmware
  • vmm_ec2 → ec2
  • vmm_dummy → dummy
  • im_kvm → kvm
  • im_xen → xen
  • im_vmware → vmware
  • im_ec2 → ec2
  • im_ganglia → ganglia
  • im_dummy → dummy

If you are upgrading from a previous installation where the hosts already have the drivers configured you can safely rename the drivers in the configuration file to the older name, for example, for vmm_kvm you can change: 

VM_MAD = [
    name       = "kvm",
    executable = "one_vmm_exec",
    arguments  = "-t 15 -r 0 kvm",
    default    = "vmm_exec/vmm_exec_kvm.conf",
    type       = "kvm" ]

to 

VM_MAD = [
    name       = "kvm",
    executable = "one_vmm_exec",
    arguments  = "-t 15 -r 0 kvm",
    default    = "vmm_exec/vmm_exec_kvm.conf",
    type       = "kvm" ]

Xen Drivers

Xen vmm drivers are now split in version 3 an version 4. The code of the drivers are the same but some configuration options are set for each of the drivers so they are compatible. By default both drivers are commented and have the same name (xen). To enable them just uncomment the version you want. Some parameters like the default image prefix can be changed in both /etc/one/vmm_exec/vmm_exec_xen* and /var/lib/one/remotes/vmm/xen*/xenrc.