Overview

To upgrade a cloud platform, you need to upgrade the management node, compute nodes, storage nodes, and network nodes to the latest version and update basic software packages, software library dependencies, and core virtualization tools. This document describes how to upgrade ZStack Cube Ultimate.

Limitations

This document applies to cloud platform upgrading of the same repo, which means that the operating system (OS) version of the hosts is consistent with the management nodes. For example, both the hosts and management nodes use h84r OS.

Note: If you need to upgrade host OS or upgrade the cloud platform of multiple repos, contact the official technical support for help.

Upgrading Mechanism

ZStack Cube Ultimate provides the following upgrading mechanisms:

Seamless upgrading: seamlessly upgrades ZStack Cube Ultimate of any old version to the latest.
Lossless upgrading: does not affect the services that VM instances are running during ZStack Cube Ultimate upgrading.

Considerations

When you upgrade ZStack Cube Ultimate, note that:

During the upgrade, the management node is inaccessible, and you cannot request VM instances, volumes, or other resources. Therefore, we recommend that you perform the upgrade during off-peak hours to avoid resource requests or service changes during the upgrade.
After ZStack Cube Ultimate is upgraded, all hosts, primary storages, backup storages, and routers are reconnected, and related resources are automatically upgraded. During reconnection, VM instances, volumes, and related resources cannot be operated.
If an exception interrupts the ZStack Cube Ultimate upgrade, resolve the exception and then perform the upgrade again.

The following summarizes considerations for upgrading to different versions. If you have any questions or need upgrade assistance, contact the official technical support.

Starting from ZStack Cube Ultimate 1.3.2, the default QEMU version is automatically upgraded from 2.12 to 4.2.
- If you use the 1.3.2 or later ISO to perform a fresh deployment of ZStack Cube Ultimate, QEMU 4.2 is installed by default. If you upgrade to 1.3.2 or later, the existing QEMU 2.12 version is retained by default.
- ZStack Cube Ultimate requires all hosts in the same cluster to use the same QEMU version. Therefore, after you upgrade to 1.3.2 or later, you cannot use the 1.3.2 or later ISO to install hosts in an existing cluster for capacity expansion. To expand capacity, use a new cluster.

Preparations

When you upgrade the cloud platform, you may need the following software packages. Before the upgrading, prepare the packages based on your needs:

ZStack Cube Ultimate ISO:
- h84r: ZStack-Cube-x86_64-DVD-2.4.8.38-h84r.iso
- Download address: Contact the official technical support.
ZStack Cube Ultimate installation package:
- Software: ZStack-Cube-installer-2.4.8.38.bin
- Download address: Contact the official technical support.
Multi-MN-HA:
- Software: ZStack-Multinode-HA-Suite-2.4.8.38.tar.gz
- Download address: Contact the official technical support.

Note: After you download the software packages or scripts, check the MD5 hash of the packages or scripts.

Typical Upgrade Procedure

About this task

This topic takes the c76 edition of ZStack Cube Ultimate as an example to describe the detailed management node upgrade procedure.

Procedure

Obtain upgrade packages.

See Preparations to obtain the ISO package and the Multi-MN-HA Suite, and store one copy in the /root/ directory of a management node.
Note: You can select any management node to execute the steps in this topic to complete the upgrade. You do not need to repeat the operations on other management nodes.
Disable VM HA globally.

Log in to the ZStack Cube Ultimate UI, choose Settings > Platform Setting > HA Policy. On the HA Policy page, click the Disable button in the upper right corner.
Back up the database.
Before you upgrade the management node, back up the database for recovery if any errors occur.
- Run the following command on two management nodes respectively to back up the database to the /var/lib/zstack/mysql-backup/lib/zstack/mysql-backup/ directory:
```
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup
```
Decompress the Multi-MN-HA Suite.
Run the following command on the management node to decompress the Multi-MN-HA Suite:
```
# Decompress the Multi-MN-HA Suite.
[root@localhost ~]# tar zxvf Multinode-HA-Suite-zsha2_ZStack_2.4.8.38.tar.gz
```
Upgrade the Multi-MN-HA Suite.
Run the following command on the management node to upgrade the Multi-MN-HA Suite:
```
[root@localhost ~]# ./zsha2 upgrade-ha
```
Confirm the management node status.
After the Multi-MN-HA Suite is upgraded, run the following command to check the management node status:
```
[root@localhost ~]# zsha2 status
```
Confirm the server.
Run the following command to check the server. The result can serve as a reference after ZStack Cube Ultimate is upgraded:
```
[root@localhost ~]# zstack-ctl status
```
Upgrade the management node.
Run the following command on the management node to upgrade the management node:
```
zsha2 upgrade-mn -peerpass password ./ZStack-Cube-x86_64-DVD-2.4.8.38-h84r.iso
```
Note: -peerpass is optional. You can set the SSH login password for the peer management node.
Check the server.
After the upgrade is complete, run the following command to check the server status:
```
[root@localhost ~]# zstack-ctl status
```
Check the management node status.
Run the following command to check the management node status:
```
[root@localhost ~]# zsha2 status
```
Confirm resource connection status.

Log in to the ZStack Cube Ultimate UI, choose Resource Center > Hardware. On the Hardware page, check the connection status of hosts, primary storage, and image storage respectively.
Enable VM HA globally.
Log in to the ZStack Cube Ultimate UI, choose Settings > Platform Setting > HA Policy. On the HA Policy page, click the Enable button in the upper right corner.

PreviousInstallation and Deployment Tutorial