Before proceeding, make sure you don't have any VMs in a transient state (prolog, migr, epil, save). Wait until these VMs get to a final state (runn, suspended, stopped, done). Check the Managing Virtual Machines guide for more information on the VM life-cycle.

Stop OpenNebula and any other related services you may have running: EC2, OCCI, and Sunstone.

<xterm> $ sunstone-server stop $ econe-server stop $ occi-server stop $ oneacctd stop $ one stop </xterm>

Backup the configuration files located in /etc/one. You don't need to do a manual backup of your database, the onedb command will perform one automatically.

Follow the Installation guide, taking into account that you will already have configured the passwordless ssh access for oneadmin.

It is highly recommended not to keep your current oned.conf, and update the oned.conf file shipped with OpenNebula 3.8 to your setup. If for any reason you plan to preserve your current oned.conf file, read the Compatibility Guide and the complete oned.conf reference for 3.6 and 3.8 versions.

If you are upgrading from a version prior to 3.6, read the 3.2 upgrade guide, 3.4 upgrade guide and 3.6 upgrade guide for specific notes.

After intalling the new OpenNebula version, please run the new install_novnc script. You can find this script in your OpenNebula share directory (/usr/share/one for most distributions)

In this particular release, the package layout has changed for all the four platforms. An important effort has been made to synchronize the packaging format used by the OpenNebula project and those used by the Linux distributions. More especifically, opennebula.org used to provide a single package per distribution, but now it follows the same package layout as the community packages, thus improving the compatibility between them.

The new package layout is explained here.

Since the package layout changes in some releases we recommend to install all the wanted packages simultaneously during an upgrade using a high-level package manager (yum, apt-get, zypper) and not a low level one (rpm, dpkg).

For example:

## For CentOS
# yum localinstall opennebula opennebula-common opennebula-java opennebula-node-kvm opennebula-ozones opennebula-ruby opennebula-server opennebula-sunstone

## For Ubuntu/Debian
# apt-get install opennebula opennebula-common opennebula-node opennebula-ozones opennebula-sunstone opennebula-tools
# apt-get -f install

Due to a bug in the OpenNebula 3.6 rpm, the package will remove the $ONE_AUTH file located in /var/lib/one/.one/one_auth. It's important to back up that file before upgrading to the new packages.

All the modified files under /etc/one will be saved to a .rpmsave file.

After upgrading the administrator will need to manually run the database upgrade, see below.

Due to a bug in the OpenNebula 3.6 rpm, the package will remove the $ONE_AUTH file located in /var/lib/one/.one/one_auth. It's important to back up that file before upgrading to the new packages.

All the modified files under /etc/one will be saved to a .rpmsave file.

After upgrading the administrator will need to manually run the database upgrade, see below.

The upgrade will work out of the box. However, the services: /etc/init.d/opennebula and /etc/init.d/sunstone won't be able to start automatically due to a database version mismatch. The administrator will need to manually run the database upgrade, see below.

The upgrade will work out of the box. However, the services: /etc/init.d/opennebula and /etc/init.d/sunstone won't be able to start automatically due to a database version mismatch. The administrator will need to manually run the database upgrade, see below.

The database schema and contents are incompatible between versions. The OpenNebula daemon checks the existing DB version, and will fail to start if the version found is not the one expected, with the message 'Database version mismatch'.

You can upgrade the existing DB with the 'onedb' command. You can specify any Sqlite or MySQL database. Check the onedb reference for more information.

After you install the latest OpenNebula, and fix any possible conflicts in oned.conf, you can issue the 'onedb upgrade -v' command. The connection parameters have to be supplied with the command line options, see the onedb manpage for more information. Some examples:

<xterm> $ onedb upgrade -v –sqlite /var/lib/one/one.db </xterm>

<xterm> $ onedb upgrade -v -S localhost -u oneadmin -p oneadmin -d opennebula </xterm>

If everything goes well, you should get an output similar to this one:

<xterm> $ onedb upgrade -v -S localhost -u oneadmin -p oneadmin -d opennebula Version read: 3.6.0 : Database migrated from 3.5.80 to 3.6.0 (OpenNebula 3.6.0) by onedb command. MySQL dump stored in /var/lib/one/mysql_localhost_opennebula.sql Use 'onedb restore' or restore the DB using the mysql command: mysql -u user -h server -P port db_name < backup_file > Running migrator /usr/lib/one/ruby/onedb/3.6.0_to_3.7.80.rb > Please enter the DATASTORE_LOCATION set in your oned.conf, Press enter to use the default /var/lib/one/datastores/ DATASTORE_LOCATION: > Done Database migrated from 3.6.0 to 3.7.80 (OpenNebula 3.7.80) by onedb command. </xterm>

Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.

This section applies only to 3.8.3. Which you should be installing instead of 3.8.0, anyway.

Virtual Machine deployment files have been moved from '/var/lib/one' to '/var/lib/one/vms'. You need to move these files manually:

<xterm> $ mv /var/lib/one/[0-9]* /var/lib/one/vms </xterm>

After the upgrade is completed, you should run the command onedb fsck.

First, move the 3.6 backup file created by the upgrade command to a save place.

<xterm> $ mv /var/lib/one/mysql_localhost_opennebula.sql /path/for/one-backups/ </xterm>

Then execute the following command:

<xterm> $ onedb fsck -S localhost -u oneadmin -p oneadmin -d opennebula MySQL dump stored in /var/lib/one/mysql_localhost_opennebula.sql Use 'onedb restore' or restore the DB using the mysql command: mysql -u user -h server -P port db_name < backup_file

Total errors found: 0 </xterm>

Transfer manager drivers changed its name from “vmware” to “vmfs”. In order to upgrade an existing Vmware based OpenNebula cloud, let's make a symlink in the remotes folder so this name change doesn't affect the existing installation (as oneadmin):

<xterm> $ rm -rf /var/lib/one/remotes/tm/vmware $ ln -s /var/lib/one/remotes/tm/vmfs /var/lib/one/remotes/tm/vmware </xterm>

You should be able now to start OpenNebula as usual, running 'one start' as oneadmin. OpenNebula will continue the monitoring and management of your previous Hosts and VMs.

As a measure of caution, look for any error messages in oned.log, and check that all drivers are loaded successfully. After that, keep an eye on oned.log while you issue the onevm, onevnet, oneimage, oneuser, onehost list commands. Try also using the show subcommand for some resources.

If for any reason you need to restore your previous OpenNebula, follow these steps:

• With OpenNebula 3.8 still installed, restore the DB backup using 'onedb restore -f'
• Uninstall OpenNebula 3.8, and install again your previous version.
• Copy back the backup of /etc/one you did to restore your configuration.

If the MySQL database password contains specials characters, such as @ or #, the onedb command will fail to connect to it.

The workaround is to temporarily change the oneadmin's password to an ASCII string. The set password statement can be used for this:

<xterm> $ mysql -u oneadmin -p

mysql> SET PASSWORD = PASSWORD('newpass'); </xterm>