OnApp IS Upgrade Paths (5.0 to 6.0)

IS Version Upgrading to 5.0.0-21 5.1.0-5 5.2.0-5 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 6.0
Upgrade by "Simple Reboot" Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Upgrade by "Migrate and Reboot" Yes Yes Yes Yes Yes* Yes Yes Yes Yes Yes Yes Yes
Upgrade by "Live Upgrade" N/A N/A Yes N/A Yes* Yes No No No No No No

* Applicable only to CentOS 6 KVM/XEN

Yes - recommended by OnApp
N/A - not recommended by OnApp, will not update properly the CloudBoot OS or Integrated Storage
No - not available in the corresponding release

  • For versions < 5.0 please use only the "Simple Reboot" method. Use "Migrate and Reboot" only if you are running 4.2.1-8.
  • For information about the upgrade of versions previous to 5.0.0-21, refer to the OnApp IS Upgrade Paths (4.0.0-3 - 4.2.1-11 versions) section.

General information and recommendations about CloudBoot OS and Integrated Storage upgrades

Starting with OnApp 5.0 LTS, we have made some changes to updates for CloudBoot OS and Integrated Storage.
CloudBoot OS upgrades that include security patches, kernel upgrades and updated drivers will be released on a regular basis. If a security patch was released by CentOS it will be included in the next released RPM.
These releases may not include updates for Integrated Storage, a component of the CloudBoot OS, as this platform is very stable and does not require changes with every release.

For the best experience, stability and security OnApp recommends that the CloudBoot compute resources should be upgraded by reboot at a convenient time if a new CloudBoot RPM is released. This is required to completely apply the security patches, kernel upgrades and updated drivers.

Integrated Storage as a platform does not strictly require the CloudBoot compute resource to be rebooted after upgrade. However, in case of critical updates and fixes it can be required to reboot the CloudBoot compute resource for them to take full effect. Currently, only version 4.1 requires to be rebooted after Integrated Storage update. OnApp will notify in future release notes if the Simple Reboot method is the recommended way to upgrade.

Each upgrade procedure explanation:

Simple Reboot

This upgrade method requires to reboot the CloudBoot compute resources with all VSs (Virtual Servers) powered off to apply security patches, kernel upgrades and updated drivers to the CloudBoot OS. Simple reboot is the fastest and the safest way to upgrade, but does result in some downtime for the Virtual Servers. Integrated Storage virtual disks do not become degraded. This upgrade method also upgrades the Integrated Storage platform as a component of the CloudBoot OS.


Migrate and Reboot

This upgrade method requires to reboot the CloudBoot compute resources to apply security patches, kernel upgrades and updated drivers to the CloudBoot OS and Integrated Storage platform. Your VSs will remain online, you only need to migrate them from the CloudBoot compute resources that will be rebooted. Keep in mind that it is required to repair any degraded virtual disks before proceeding with reboot.


Live Upgrade

This upgrade method upgrades the Integrated Storage platform only. Your VSs will remain online. There is almost no risk of data loss and zero downtime. However this method does not update the CloudBoot OS, you will not get the security patches, kernel upgrades and updated drivers if they are included in the release.

  • Live Upgrade is not available for an upgrade from OnApp 5.0 to 6.0.
  • Starting from OnApp 5.3, each CloudBoot OS image is divided into a separate package for better experience and support. For example, if the CentOS 6 Xen CloudBoot OS image receives a security patch, it will be updated and released by OnApp. Only this image will be downloaded during the upgrade procedure, saving internet traffic and time.

Please contact our Support team if you are unsure regarding the right upgrade path for you to ensure you choose the right path for you and your clients.