Upgrading from Previous Versions 4.2

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|Compatibility Guide]] and [[:software:software|Release Notes]] to know what is new in OpenNebula 4.2. {{INLINETOC}} ====== Deprecated VMware Datastore Configurations ====== OpenNebula 4.2 trims down the storage model for VMware. There are combinations of storage no longer supported (see the [[documentation:rel4.2:vmware_ds|VMFS Datastore guide]] for the supported configurations). If you want to upgrade to 4.2 and you are using ''SSH'', ''NFS'' or ''VMFS without SSH-mode'', you will need to manually migrate your images to a newly created ''VMFS with SSH-mode datastore''. To do so implies powering off all the VMs with images in any of the deprecated datastores, upgrade OpenNebula, create a ''VMFS'' datastore and then manually register the images from those deprecated datastores into the new one. [[http://opennebula.org/community:mailinglists|Let us know]] if you have doubts or problems with this process. ====== Preparation ====== 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 [[.:vm_guide_2|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. $ sunstone-server stop $ econe-server stop $ occi-server stop $ one stop ====== Backup ====== 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. ====== Installation ====== Follow the [[.:ignc|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 4.2 to your setup. If for any reason you plan to preserve your current ''oned.conf'' file, read the [[.:compatibility|Compatibility Guide]] and the complete oned.conf reference for [[..:rel4.0:oned_conf|4.0]] and [[.:oned_conf|4.2]] versions.
:!: If you are upgrading from a version prior to 4.0, read the [[..:rel3.6:upgrade#installation|3.6 upgrade guide]], [[..:rel3.8:upgrade#installation|3.8 upgrade guide]] and [[..:rel4.0:upgrade#installation|4.0 upgrade guide]] for specific notes.
====== Database Upgrade ====== 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|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 [[.:cli|onedb manpage]] for more information. Some examples: $ onedb upgrade -v --sqlite /var/lib/one/one.db $ onedb upgrade -v -S localhost -u oneadmin -p oneadmin -d opennebula If everything goes well, you should get an output similar to this one: $ onedb upgrade -v -u oneadmin -d opennebula MySQL Password: Version read: 4.0.1 : Database migrated from 3.8.0 to 4.0.1 (OpenNebula 4.0.1) 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/4.0.1_to_4.1.80.rb > Done Database migrated from 4.0.1 to 4.1.80 (OpenNebula 4.1.80) by onedb command.
:!: 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.
====== Check DB consistency ====== After the upgrade is completed, you should run the command ''**onedb fsck**''. First, move the 4.0 backup file created by the upgrade command to a save place. $ mv /var/lib/one/mysql_localhost_opennebula.sql /path/for/one-backups/ Then execute the following command: $ 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 ====== Testing ====== 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. ====== Restoring the Previous Version ====== If for any reason you need to restore your previous OpenNebula, follow these steps: * With OpenNebula 4.2 still installed, restore the DB backup using 'onedb restore -f' * Uninstall OpenNebula 4.2, and install again your previous version. * Copy back the backup of /etc/one you did to restore your configuration. ====== Known Issues ====== 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 [[http://dev.mysql.com/doc/refman/5.6/en/set-password.html | set password]] statement can be used for this: $ mysql -u oneadmin -p mysql> SET PASSWORD = PASSWORD('newpass');