Start Here

This guide describes the upgrade procedure for systems that are already running OpenNebula 6.0.x or newer. The upgrade will preserve all current users, hosts, resources, and configurations, for both SQLite and MySQL/MariaDB back-ends.

Read the Compatibility Guide and Release Notes to learn what’s new in OpenNebula 7.2.

Previous Steps

OpenNebula 7.0 or newer is distributed with onecfg as part of the main server package. This tool simplifies the upgrade process of configuration files, and is always included in the latest version of OpenNebula.

Upgrade OpenNebula

Update your OpenNebula packages by following only the guide that applies to your current OpenNebula configuration:

Upgrading Contextualization Packages

When upgrading your OpenNebula infrastructure, you do not need to execute a massive update of the contextualization packages of all your running Virtual Machines. For details on the highly flexible compatibility support between contextualization and infrastructure versions, see the Contextualization page

To ensure stability and minimize disruption, follow these best practice recommendations:

  1. Keep Running VMs as They Are: Do not update the context packages of currently running VMs during an infrastructure upgrade. The new OpenNebula version will continue to manage them without issue.
  2. Update Context on Golden Images: Update the contextualization packages on your customized “golden” images and templates. This ensures that all new VMs provisioned after the upgrade will utilize the latest contextualization features.
  3. Targeted Updates for Running VMs: Only update the context package on an actively running VM if you specifically need a new feature introduced in the newer context version, or if you need to resolve a known bug that impacts that specific VM.

You can find the installation and upgrade instructions in the one-apps wiki for Linux and Windows guest VMs.