Upgrade Cloud with CloudBoot Servers (from 6.2)

This guide provides a walk-through on how to upgrade OnApp Cloud 6.2 to 6.3 for a cloud where all servers are CloudBoot. Please follow the complete procedure of the upgrade process. All the packages (Control Panel and CloudBoot compute resources) must belong to the same major version to ensure the best performance of your cloud.

Upgrade Control Panel Server


To upgrade the Control Panel server, follow the procedure at Upgrade Guide for Control Panel Server

Upgrade CloudBoot Packages


Create a backup of the /tftpboot directory in case the storage packages rollback is needed.


To upgrade the CloudBoot, proceed with the steps from one to six (1-6) on Control Panel box:

  1. Upgrade the repo:

    # rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-6.3.noarch.rpm
    
  2. Update CloudBoot default packages:

    # yum update onapp-store-install onapp-ramdisk-tools onapp-ramdisk-centos7-default
  3. Depending on your compute resource type(s), update the corresponding package(s):

    # yum update onapp-ramdisk-centos6-xen
    # yum update onapp-ramdisk-centos6-kvm
    # yum update onapp-ramdisk-centos7-xen
    # yum update onapp-ramdisk-centos7-kvm

    After the packages installation, go to the Control Panel's Settings menu > Configuration and click the Save Configuration button.


    THE FOLLOWING STEPS (4-5) APPLY ONLY TO XEN-BASED COMPUTE RESOURCES:

  4. Increase the Dom0 RAM for each Xen CloudBoot compute resource at least to 5 GB from the Control Panel UI.
  5. Power off all the virtual servers that run on a Xen compute resource.

  6. Run the script:

    # /onapp/onapp-store-install/onapp-store-install.sh

    Be aware that the disk-less nodes password is the root password for the CloudBoot compute resources. By default it is blank.


    When run in the interactive mode, enter the required information.

Upgrade CloudBoot Backup Servers


Make sure to update CloudBoot packages on your Control Panel server before proceeding to the upgrade of CloudBoot backup servers.

CloudBoot backup servers are CloudBoot KVM compute resources that can be used as backup servers. The CloudBoot backup server upgrade procedure is almost the same as the CloudBoot compute resource upgrade. Follow the instructions provided in this section to upgrade CloudBoot backup servers in your cloud.

Once you have upgraded the CloudBoot dependencies, you have to reboot your CloudBoot compute resource to update the Cloud Boot RPM. You do not need to perform any backup server upgrade operations using console.

To do so:

  1. Go to your Control Panel Settings > Compute Resources menu.

  2. Click the label of the CloudBoot compute resource the backup server is based on.

  3. On the compute resource details screen, click the Actions button, then click Reboot Compute resource.

  4. A new screen will open asking for confirmation before reboot:

    • Are you sure you want to reboot this compute resource? Confirm that you want the compute resource to reboot.

  5. When you're certain you want to proceed with the reboot, click the Reboot button.

  6. Repeat these steps for all CloudBoot backup servers in your cloud.

  7. Once all are rebooted, proceed to CloudBoot compute resources upgrade.


Upgrade CloudBoot Compute Resources


Depending on the infrastructure, scale and needs of your cloud we suggest the following methods of upgrading CloudBoot compute resources:

Please note that due to the upgrade to the latest Pyton3 version, the Simple Reboot is the only available option for Xen and KVM compute resources.

Simple Reboot

This method is the simplest method technically. It also ensures all tools are updated. However, it will result in some limited downtime
(its duration depends on how many virtual servers are running on each compute resource).

In case you have applied any custom configuration to your CloudBoot servers, it is recommended to recheck that this customization does not break new cloud boot image version. For this, reboot a compute resource and run Storage Health Check and Network Health Check. Make sure that Vdisks hosted on a compute resource are redundant and healthy before rebooting a CloudBoot compute resource.

If you are using the auto healing functionality for Integrated Storage, make sure to disable it before an upgrade.


Simple Reboot

Follow the below procedure to upgrade the CloudBoot compute resources with reboot:

1. Upgrade CloudBoot Packages.

2. When the CloudBoot packages upgrade is complete, stop all virtual servers which reside on the CloudBoot compute resources.

3. Reboot all CloudBoot compute resources.

Once the compute resources are booted, the upgrade is complete. Before starting all Virtual Servers please ensure that the diagnostics page does not report any issue. In case of any issue, please clik repair button to resolve it, then continue with starting Virtual Servers.

Note that virtual servers cannot be stopped simultaneously, but must be stopped in sequence. This can result in considerable downtime if there are a large number of virtual servers.