ZStack Cloud 4.8.10>ZStack Cloud Tutorials>Private Cloud>Platform Upgrade Tutorial>Typical Upgrading Processes

Typical Upgrading Processes

ZStack Cloud provides single-management node and multi-management node deployment methods. The two deployment methods have different upgrading processes.

For more information about single-management node upgrading, see Single-Management Node Upgrading.
For more information about multi-management node upgrading, see Multi-Management Node Upgrading.

Single-Management Node Upgrading

This topic takes h84r ISO as an example to describe the upgrading process of a single-management node platform.

Obtain software packages for upgrading.
See Preparations to obtain the packages you need and save the packages in the /root/ directory.
- Offline upgrading does not require connection to the public network but requires the bin package, ISO package, and upgrade script.
Disable VM HA globally.

Log in to the UI, choose Settings > Platform Setting > HA Policy, on the HA Policy page, click the Disable button on the upper right corner.
Back up the database and upgrading script.
Before you upgrade the cloud platform, back up the database and upgrading script, in case of any unexpected situations.
- Run the following command on the management node to back up the database in the /var/lib/zstack/mysql-backup/ directory:
```
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup
```
- Run the following command on the management node to back up the upgrading script in the /root/ directory:
```
[root@localhost ~]# cp /usr/local/bin/zstack-upgrade /root/zstack-upgrade-bk
```
Upgrade the cloud platform.
Run the following commands on the management node to implement offline upgrading:
```
# Two offline upgrading methods are supported. The first one is recommended: # First method: Upgrade the local repo and management service simultaneously: [root@zstack-1 opt]# zstack-upgrade ZStack-Cloud-x86_64-DVD-4.8.10-h84r.iso # Second method: Upgrade the local repo first and then the management service: [root@localhost ~]# zstack-upgrade -r ZStack-Cloud-x86_64-DVD-4.8.10-h84r.iso [root@localhost ~]# bash ZStack-Cloud-installer-4.8.10.bin -u -P MYSQL_ROOT_PASSWORD
```
Note:
- If the root password of the database is the default password, you do not need to specify -P MYSQL_ROOT_PASSWORD.
- Before you run the zstack-upgrade command, make sure that you use ISO of the h84r version instead of other versions.
- While upgrading the local repo, the upgrade script is auto-updated. When the update is completed, rerun the preceding command.
Clean up the browser cache.

To make sure that the upgraded platform works as expected, after the upgrading is completed, you need to log in to the UI platform and press Ctrl+F5 or Ctrl+Shift+R to clean up the browser cache.
Enable VM HA globally.

Login to the UI, choose Settings > Platform Setting > HA Policy, on the HA Policy page, click the Enable button on the upper right corner.

Multi-Management Node Upgrading

This topic takes h84r ISO as an example to describe the upgrading process of a multi-management-node platform.

Obtain software packages for upgrading.

See Preparations to obtain the ISO package, bin package, upgrading script, multi-MN-HA you need and save the packages or scripts in the /root/ directory of the management nodes.
Disable VM HA globally.

Log in to the UI, choose Settings > Platform Setting > HA Policy, on the HA Policy page, click the Disable button on the upper right corner.
Back up the database and upgrading script.
Before you upgrade the cloud platform, back up the database and upgrading script, in case of any unexpected situations.
- Run the following command on the management nodes respectively to back up the database in the /var/lib/zstack/mysql-backup/ directory:
```
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup
```
- Run the following command on the management nodes respectively to back up the upgrading script in the /root/ directory:
```
[root@localhost ~]# cp /usr/local/bin/zstack-upgrade /root/zstack-upgrade-bk
```
Update the local repo.
Run the following command on the management nodes respectively to update the local repo:
```
[root@localhost ~]# bash zstack-upgrade -r ZStack-Cloud-x86_64-DVD-4.8.10-h84r.iso
```
Note: While upgrading the local repo, the upgrade script is auto-updated. When the update is completed, rerun the preceding command.
Obtain the IP address of the management node that corresponds to the VIP you use.
Run the following command to obtain the IP address of the management node that corresponds to the VIP you use. The management node that corresponds to the yes result is the management node you need:
```
[root@localhost ~]# zsha2 status
```
Decompress the Multi-MN-HA file and grant the decompressed files execution permission.
Run the following commands on the management node that corresponds to the VIP you use to decompress the Multi-MN-HA file and grant the decompressed files zsha2 and zstack-hamon execution permission:
```
[root@localhost ~]# tar zxvf ZStack-Multinode-HA-Suite-4.8.10.tar.gz      #Decompress the Multi-MN-HA file [root@localhost ~]# chmod +x zsha2 zstack-hamon    #Grant the decompressed files execution permission
```
Upgrade Multi-MN-HA
Run the following command on the management node that corresponds to the VIP you use to upgrade Multi-MN-HA:
```
[root@localhost ~]# ./zsha2 upgrade-ha
```
Upgrade the cloud platform.
Run the following command on the management node that corresponds to the VIP you use to upgrade the management nodes:
```
zsha2 upgrade-mn -peerpass password ZStack-Cloud-installer-4.8.10.bin
```
Note: -peerpass is optional. You can use the parameter to set the password of SSH login to the peer management nodes.
Clean up the browser cache.

To make sure that the upgraded platform works as expected, after the upgrading is completed, you need to log in to the UI platform and press Ctrl+F5 or Ctrl+Shift+R to clean up the browser cache.
Enable VM HA globally.

Login to the UI, choose Settings > Platform Setting > HA Policy, on the HA Policy page, click the Enable button on the upper right corner.

Next Chapter: Glossary

Typical Upgrading Processes

Single-Management Node Upgrading

Multi-Management Node Upgrading

Products

Solutions

Help & Support

Contact Us