ZStack Cloud Platform
Single Server, Free Trial for One Year
Manually upgrade the management nodes of ZStack Cloud to the latest version. Then, automatically or manually upgrades resources such as hosts, primary storage, image storage, and VPC vRouters, depending on the selected upgrade method.
Standard upgrade method upgrades the management node first. Then, the platform automatically reconnects and upgrades resources such as hosts, primary storage, image storage, and VPC vRouters in a single operation. This method does not support batch-based or phased upgrade control.
Grayscale upgrade method upgrades the management node first but does not immediately upgrade all hosts and other nodes. The platform advanc
es the upgrade in batches by using grayscale control. You can prioritize hosts that run noncritical workloads for validation. After verification completes without issues, gradually proceed to a full upgrade to reduce upgrade risk.
Note: The grayscale upgrade feature is available only in ZStack Cloud 5.0.0 and later. Earlier versions do not support this upgrade mode.
Note: Login to the UI, choose , on the HA Policy page, click the Disable button on the upper right corner.
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup[root@localhost ~]# cp /usr/local/bin/zstack-upgrade /root/zstack-upgrade-bk# 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-5.5.0-h84r.iso # Second method: Upgrade the local repo first and then the management service: [root@localhost ~]# zstack-upgrade -r ZStack-Cloud-x86_64-DVD-5.5.0-h84r.iso [root@localhost ~]# bash ZStack-Cloud-installer-5.5.0.bin -u -P <MYSQL_ROOT_PASSWORD>
Note: <MYSQL_ROOT_PASSWORD> is the password of the MySQL root user. The placeholder is for example purposes only and must be replaced with the actual password.-P <MYSQL_ROOT_PASSWORD>.To make sure that the upgraded platform works as expected, after the upgrading is completed, you need to login to the UI platform and press Ctrl+F5 or Ctrl+Shift+R to clean up the browser cache.
Login to the UI, choose , on the HA Policy page, click the Enable button on the upper right corner.
Note: Login to the UI, choose , on the HA Policy page, click the Disable button on the upper right corner.
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup[root@localhost ~]# cp /usr/local/bin/zstack-upgrade /root/zstack-upgrade-bk[root@localhost ~]# bash zstack-upgrade -r ZStack-Cloud-x86_64-DVD-5.5.0-h84r.iso
Note: While upgrading the local repo, the upgrade script is auto-updated. When the update is completed, rerun the preceding command.[root@localhost ~]# zsha2 status[root@localhost ~]# tar zxvf ZStack-Multinode-HA-Suite-5.5.0.tar.gz #Decompress the Multi-MN-HA file [root@localhost ~]# chmod +x zsha2 zstack-hamon #Grant the decompressed files execution permission[root@localhost ~]# ./zsha2 upgrade-hazsha2 upgrade-mn -peerpass password ZStack-Cloud-installer-5.5.0.bin
Note: -peerpass is optional. You can use the parameter to set the password of SSH login to the peer management nodes.To make sure that the upgraded platform works as expected, after the upgrading is completed, you need to login to the UI platform and press Ctrl+F5 or Ctrl+Shift+R to clean up the browser cache.
Login to the UI, choose , on the HA Policy page, click the Enable button on the upper right corner.