ZStack 3.10.0>Tutorials>Private Cloud>Platform Upgrade Tutorial>Typical Upgrade Workflow

Typical Upgrade Workflow

ZStack supports two deployment methods: single management node (single MN) method and multi-management node (multi-MN method). The upgrade process varies according to different deployment methods. You need to perform upgrade according to the specific deployment method.

For details about the upgrade workflow of the single MN method, see Single MN Upgrade.
For details about the upgrade workflow of the multi-MN method, see Multi-MN Upgrade.

Single MN Upgrade

ZStack provides two versions: c76 and c74. Both versions use the same upgrade process. This topic mainly describes how to upgrade a single MN environment of the c76 version.

Obtain the installation packages.
Obtain the required software packages and save them to the /root/ directory. For more information, see Preparations.
- Incremental upgrade: The incremental upgrade must be performed when the network is connected. Please obtain the bin package in advance.
- Offline upgrade: The offline upgrade can be performed without connecting the network. However, you need to obtain the bin package, ISO package, and upgrade script in advance.
Disable the VM HA functionality in global settings.

Log in to the Cloud via the UI and choose Settings > Global Settings. On the Basic Settings tab page, set the value of VM HA to false.
Note: Triggering VM HA might affect the upgrade. Therefore, we recommend that you disable the VM HA functionality in advance.
Back up the database and the upgrade script.
Before you upgrade the Cloud, back up the database and the upgrade script for disaster recovery.
- In the management node, run the following command 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
```
- In the management node, run the following command to back up the upgrade script to the /root/ directory:
```
[root@localhost ~]# cp /usr/local/bin/zstack-upgrade /root/zstack-upgrade-bk
```
Upgrade the Cloud.
The Cloud supports two upgrade methods: incremental upgrade and offline upgrade. You can choose a method as needed:
- To perform incremental upgrade, run the following command in the management node:
```
[root@localhost ~]# bash ZStack-installer-3.10.0.bin -u -P MYSQL_ROOT_PASSWORD
```
  Note: If the root password of the database is the default password, the -P MYSQL_ROOT_PASSWORD parameter is not required.
- To perform offline upgrade, run the following commands in the management node:
```
[root@localhost ~]# bash zstack-upgrade -r ZStack-x86_64-DVD-3.10.0-c76.iso [root@localhost ~]# bash ZStack-installer-3.10.0.bin -u -P MYSQL_ROOT_PASSWORD
```
  Note: If the root password of the database is the default password, the -P MYSQL_ROOT_PASSWORD parameter is not required.
Manually clear the browser cache.

To ensure that the new features can be used properly, log in to the Cloud via the UI after the upgrade is finished, and press Ctrl+F5 or Ctrl+Shift+R to manually clear the browser cache.
Enable the VM HA functionality in global settings.

Log in to the Cloud via the UI and choose Settings > Global Settings. On the Basic Settings tab page, set the value of VM HA to true.

Multi-MN Upgrade

ZStack provides two versions: c76 and c74. Both versions use the same upgrade process. This topic mainly describes how to upgrade a multi-MN environment of the c76 version.

Obtain the installation packages.

Obtain the ISO package, bin package, upgrade script, and multi-MN HA suite, and save them to the /root/ directory in each management node. For more information, see Preparations.
Disable the VM HA functionality in global settings.

Log in to the Cloud via the UI and choose Settings > Global Settings. On the Basic Settings tab page, set the value of VM HA to false.
Note: Triggering VM HA might affect the upgrade. Therefore, we recommend that you disable the VM HA functionality in advance.
Back up the database and the upgrade script.
Before you upgrade the Cloud, back up the database and the upgrade script for disaster recovery.
- In each management node, run the following command 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
```
- In each management node, run the following command to back up the upgrade script to the /root/ directory:
```
[root@localhost ~]# cp /usr/local/bin/zstack-upgrade /root/zstack-upgrade-bk
```
Update the local repo.
In each management node, run the following command to update the local repo:
```
[root@localhost ~]# bash zstack-upgrade -r ZStack-x86_64-DVD-3.10.0-c76.iso
```
Obtain the IP address of the management node where the VIP is located.
Run the following command to obtain the IP address of the management node where the VIP is located. In the returned result, the management node whose "Owns virtual address" is yes is the management node where the VIP is located.
```
[root@localhost ~]# zsha2 status
```
Decompress the HA suite and grant execute permission.
In the management node where the VIP is located, run the following commands to decompress the HA suite, and grant execute permission to the zsha2 and zstack-hamon files:
```
[root@localhost ~]# tar zxvf Multinode-HA-Suite-3.10.0.tar.gz      #Decompress the HA suite [root@localhost ~]# chmod +x zsha2 zstack-hamon    #Grant execute permission.
```
Upgrade the HA suite.
In the management node where the VIP is located, run the following command to finish upgrading the HA suite:
```
[root@localhost ~]# ./zsha2 upgrade-ha
```
Upgrade the Cloud.
In the management node where the VIP is located, run the following command to upgrade the multi-MN environment:
```
zsha2 upgrade-mn -peerpass password ZStack-installer-3.10.0.bin
```
Note: In the preceding command, the -peerpass parameter is optional. You can use this parameter to set the SSH login password for the peer MN.
Manually clear the browser cache.

To ensure that the new features can be used properly, log in to the Cloud via the UI after the upgrade is finished, and press Ctrl+F5 or Ctrl+Shift+R to manually clear the browser cache.
Enable the VM HA functionality in global settings.

Log in to the Cloud via the UI and choose Settings > Global Settings. On the Basic Settings tab page, set the value of VM HA to true.

Next Chapter:Glossary

Typical Upgrade Workflow

Single MN Upgrade

Multi-MN Upgrade

Products

Solutions

Help & Support

Contact Us