Overview

To upgrade ZStack Cloud, you need to upgrade the management nodes, 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 Cloud in details, including:

Upgrade cloud platform
Upgrade virtualization tools (Optional)
Upgrade Kernel (Optional)

Limitations

This document applies to cloud platform upgrading of the same repository (repo), which means:

The management nodes and all hosts on the cloud platform are using the same operating system (OS) version, for example, all use the h84r OS.
The OS version used by the target ISO is consistent with OS version currently used by the management nodes and hosts. For example, if all management nodes and hosts on the cloud platform are using the h84r OS, you must use a ZStack Cloud ISO of the h84r edition to perform the upgrading.

Upgrading Mechanism

ZStack Cloud provides the following upgrading mechanisms:

Seamless upgrading: In a same-repo environment, ZStack Cloud of any old version can be upgraded to the latest version.
Lossless upgrading: The upgrade process does not affect the services running in VM instances.

Note:

This document takes upgrading the cloud platform of same-repo with the h84r ISO as an example.
If you need to change host OS or upgrade a cloud platform of multiple repos, contact the official technical support for help.

Considerations

Before upgrading ZStack Cloud, be aware of the following points:

During the upgrading, the management nodes are inaccessible and you cannot apply VM and volume resources. Therefore, we recommend that you upgrade the cloud platform during business troughs to avoid resource application and business change needs.
If you upgrade the virtualization tools (QEMU & Libvirt), it is not supported to rollback the tools to earlier versions.
If you upgrade the host QEMU, you need to reboot or migrate VM instances, VPC vRouters, and LB instances on the hosts to make the new QEMU version take effect.
If you upgrade the host Kernel, you need to restart the host to make the new Kernel version take effect.
If any errors occur during the upgrading, interrupting the upgrading process or affecting the running business, contact the official technical support immediately.
Read the feature update information to learn about the key feature changes in the target version in advance.

Version	Upgrade Information	Details
ZStack Cloud 5.1.0	Removes the UI button Set VM RDP Mode.	Starting from 5.1.0, it is not supported to set the VM RDP mode on the UI. To enable the RDP mode for a VM instance, run the CLI command `SetVmRDP uuid=${vmuuid} enable=true`
ZStack Cloud 4.7.21	Renames Entertainment Management as Tenant Management.	Starting from 4.7.21, the feature module Entertainment Management is renamed as Tenant Management. This does not affect the functions of this module.
ZStack Cloud 4.6.0	Upgrades Affinity Group to VM Scheduling Policy.	Starting from 4.6.0, the feature Affinity Group is upgraded to VM Scheduling Policy: The VM Scheduling Policy feature provides four types of policies: VM Exclusive from Each Other, VM Affinitive to Each Other, VMs Affinitive to Hosts, and VMs Exclusive from Hosts. Each policy has two execution mechanisms: Hard and Soft. Anti-Affinity Group (Hard) and Anti-Affinity Group (Soft) policies provided in earlier versions are upgraded to VM Affinitive to Each Other (Hard) and VM Affinitive to Each Other (Soft) respectively, without any modification to the underlying working principles. This upgrade has no impact on your existing application workloads and is annoyance-free.
ZStack Cloud 4.0.0	Upgrades vRouter to VPC vRouter.	Starting from 4.0.0, vRouter is upgraded to VPC vRouter and vRouter network is upgraded to VPC network. vRouter is no longer available on the UI. The seamless upgrade does not affect your business continuity.
	Replaces User Group and User by the account system in Entertainment Management.	Starting from 4.0.0, User Group and User are replaced by the system account in Entertainment Management Account System. User Group and User are no longer available on the UI. You cannot login to the Cloud by using a user or user group account. Before you implement upgrading, migrate the user and user group account data to Entertainment Management. Note: User accounts created by the admin and have the admin permissions are also can celled. Platform admins in Entertainment Management have the equivalent permissions. You can use Entertainment Management to create platform managers based on your business needs.
	Adjusts the integration of AD/LDAP and accounts.	Starting from 4.0.0, the integration of AD/LDAP and accounts is managed by Entertainment Management. Before you implement upgrading, migrate the AD/LDAP account data managed by the original account system to Entertainment Management.

Upgrade Cloud Platform

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.

ZStack Cloud supports two platform upgrade methods: standard upgrade and grayscale upgrade, for both single-management node and dual-management node deployments. Upgrade procedures vary by upgrade method and deployment method. Select the appropriate upgrade method and procedure based on the actual deployment scenario:

Standard Upgrade
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.
- For more information about single-management node upgrading, see Single-Management Node Standard Upgrading.
- For more information about dual-management node upgrading, see Dual-Management Node Standard Upgrading.
Grayscale Upgrade
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.
- For more information about single-management node grayscale upgrading, see Single-Management Node Grayscale Upgrading.
- For more information about dual-management node grayscale upgrading, see Dual-Management Node Grayscale Upgrading.
Note:
The grayscale upgrade feature is available only in ZStack Cloud 5.0.0 and later. Earlier versions do not support this upgrade mode.

Single-Management Node Standard Upgrading

About this task

This topic describes the standard upgrading process of a single-management node platform.

Procedure

Obtain software packages for upgrading.
Prepare the following packages and save them in the /root/ directory of the management node:
- ZStack Cloud ISO:
  - Software: ZStack-Cloud-x86_64-DVD-5.5.38-h84r.iso
  - Download address: Click here
- ZStack Cloud installation package:
  - Software: ZStack-Cloud-installer-5.5.38.bin
  - Download address: Click here
- ZStack Cloud Upgrade Script:
  - Software: ZStack-Cloud-upgrade
  - Download address: Click here
Note:
- ZStack-Cloud supports offline upgrading, which allows you to upgrade the cloud platform without connecting to the public network. Therefore, you need to download the software packages and upgrade script in advance.
- After you download the software packages and upgrade script, check the MD5 hash of the packages or scripts. If the MD5 hash is inconsistent with that on the official website, download again.
Disable VM HA globally.

Login 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-5.5.38-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.38-h84r.iso
[root@localhost ~]# bash ZStack-Cloud-installer-5.5.38.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.
- 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 login 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.

What to do next

Now, the management node has been upgraded. The system will automatically reconnects other nodes, such as hosts, primary storage, image storage, and VPC vRouters, to complete the cloud platform upgrading.
You can continue to upgrade virtualization tools and Kernel as needed.

Dual-Management Node Standard Upgrading

About this task

This topic describes the standard upgrading process of a dual-management node platform.

Procedure

Obtain software packages for upgrading.
Prepare the following packages and save them respectively in the /root/ directory of the two management nodes:
- ZStack Cloud ISO:
  - Software: ZStack-Cloud-x86_64-DVD-5.5.38-h84r.iso
  - Download address: Click here
- ZStack Cloud installation package:
  - Software: ZStack-Cloud-installer-5.5.38.bin
  - Download address: Click here
- ZStack Cloud Upgrade Script:
  - Software: ZStack-Cloud-upgrade
  - Download address: Click here
- Multi-MN-HA Suite:
  - Software: ZStack-Multinode-HA-Suite-5.5.38.tar.gz
  - Download address: Click here
Note:
- ZStack-Cloud supports offline upgrading, which allows you to upgrade the cloud platform without connecting to the public network. Therefore, you need to download the software packages and upgrade script in advance.
- After you download the software packages and upgrade script, check the MD5 hash of the packages or scripts. If the MD5 hash is inconsistent with that on the official website, download again.
Disable VM HA globally.

Login 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-5.5.38-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-5.5.38.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 Suite
Run the following command on the management node that corresponds to the VIP you use to upgrade Multi-MN-HA Suite:
```
[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-5.5.38.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 login 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.

What to do next

Now, the management nodes have been upgraded. The system will automatically reconnects other nodes, such as hosts, primary storage, image storage, and VPC vRouters, to complete the cloud platform upgrading.
You can continue to upgrade virtualization tools and Kernel as needed.

Single-Management Node Grayscale Upgrading

About this task

This topic describes the grayscale upgrading process of a single-management node platform.

Procedure

Obtain software packages for upgrading.
Prepare the following packages and save them in the /root/ directory of the management node:
- ZStack Cloud ISO:
  - Software: ZStack-Cloud-x86_64-DVD-5.5.38-h84r.iso
  - Download address: Click here
- ZStack Cloud installation package:
  - Software: ZStack-Cloud-installer-5.5.38.bin
  - Download address: Click here
- ZStack Cloud Upgrade Script:
  - Software: ZStack-Cloud-upgrade
  - Download address: Click here
Note:
- ZStack-Cloud supports offline upgrading, which allows you to upgrade the cloud platform without connecting to the public network. Therefore, you need to download the software packages and upgrade script in advance.
- After you download the software packages and upgrade script, check the MD5 hash of the packages or scripts. If the MD5 hash is inconsistent with that on the official website, download again.
Disable VM HA globally.

Login to the UI, choose Settings > Platform Setting > HA Policy, on the HA Policy page, click the Disable button on the upper right corner.
Select a host for grayscale upgrade validation.

During the pre-upgrade preparation phase, select a host that runs noncritical workloads as the grayscale upgrade validation node. This host will initiate manual reconnection first in the following upgrade process to verify the agent upgrade, VM instance runtime status, and service availability.
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
```
Grayscale upgrade the cloud platform.
Run the following commands on the management node to implement grayscale upgrading:
```
[root@localhost ~]# zstack-upgrade -r ZStack-Cloud-x86_64-DVD-5.5.38-h84r.iso      # Update the local repo.
[root@localhost ~]# bash zstack-installer-5.5.38.bin -u --grayscale true -P <MYSQL_ROOT_PASSWORD>      # Grayscale upgrade the cloud platform.
```
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.
- If the root password of the database is the default password, you do not need to specify -P <MYSQL_ROOT_PASSWORD>.
- -grayscale enables grayscale upgrade mode. After the upgrade completes, the platform does not automatically upgrade Hosts or related Agents.
- After the upgrade completes, resources such as hosts and VPCs remain as Not Upgraded. Proceed with the upgrade by reconnecting the resources or disabling grayscale mode.
Clean up the browser cache.

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.
Check the resource status after graysacle upgrade.

Log in to the ZStack Cloud UI and check the status of hosts, primary storage, image storage and other resources. Ensure that each resource is in the Connected state. Besides, check the Upgrade Status of resources such as hosts and VPCs. Under the grayscale upgrade mode, the Upgrade Status should be displayed as Not Upgraded at this time.
Perform grayscale upgrade validation on a noncritical host.
In the ZStack Cloud UI, manually reconnect the predesigned host that runs noncritical workloads to trigger upgrades for the host and related agents.
After the reconnection completes, verify the upgrade results to ensure that the upgrade process completes successfully and that services remain operational:
- Verify that the agent version on the host is updated and the host runs normally.
- Check that the primary storage and related components operate normally.
- Verify that VM instances run normally, network connectivity works as expected, and service access remains unaffected.
When all verification checks pass and the host upgrade status displays Upgraded, the grayscale upgrade validation completes successfully. The subsequent full-platform upgrade can then proceed.
Note:
- During a grayscale upgrade, you can reconnect hosts that have not been upgraded. Reconnection automatically triggers the agent upgrade.
- If a host disconnects unexpectedly during the grayscale upgrade and automatic reconnection fails, manually reconnect the host to restore connectivity. The manual reconnection also upgrades the agent.
Proceed with full-platform resource upgrade.
After the grayscale upgrade validation completes, use one of the following methods to upgrade the remaining resources based on operational requirements:
- Manual phased upgrade: Reconnect the remaining hosts one by one to gradually upgrade the hosts and related agents. Continuously monitor the upgrade progress and service status.
- Automatic upgrade: After the grayscale upgrade validation on noncritical hosts completes and no further phased validation is required, disable grayscale mode. The platform automatically upgrades the remaining hosts and related resources.
Regardless of the method you choose, continuously monitor VM instance status during the upgrade to ensure that services remain unaffected.

Disable Grayscale Upgrade Mode

After you confirm that the grayscale upgrade validation completes without issues, run the following command to disable the grayscale upgrade mode:

[root@localhost ~]# zstack-cli   // Enter zstack-cli.
admin >>> LogInByAccount accountName=admin password=<ADMIN_PASSWORD>     // Log in to the CLI with the admin account. <ADMIN_PASSWORD> is the password of the admin account and is used as a placeholder here.
admin >>> UpdateGlobalConfig name=grayscaleUpgrade category=upgradeControl value=false     // Disable the grayscale mode.

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.

What to do next

Now, the platform grayscale upgrade is complete in a single-management node deployment. You can continue to upgrade virtualization tools and Kernel as needed.

Dual-Management Node Grayscale Upgrading

About this task

This topic describes the grayscale upgrading process of a dual-management node platform.

Procedure

Obtain software packages for upgrading.
Prepare the following packages and save them respectively in the /root/ directory of the two management nodes:
- ZStack Cloud ISO:
  - Software: ZStack-Cloud-x86_64-DVD-5.5.38-h84r.iso
  - Download address: Click here
- ZStack Cloud installation package:
  - Software: ZStack-Cloud-installer-5.5.38.bin
  - Download address: Click here
- ZStack Cloud Upgrade Script:
  - Software: ZStack-Cloud-upgrade
  - Download address: Click here
- Multi-MN-HA Suite:
  - Software: ZStack-Multinode-HA-Suite-5.5.38.tar.gz
  - Download address: Click here
Note:
- ZStack-Cloud supports offline upgrading, which allows you to upgrade the cloud platform without connecting to the public network. Therefore, you need to download the software packages and upgrade script in advance.
- After you download the software packages and upgrade script, check the MD5 hash of the packages or scripts. If the MD5 hash is inconsistent with that on the official website, download again.
Disable VM HA globally.

Login to the UI, choose Settings > Platform Setting > HA Policy, on the HA Policy page, click the Disable button on the upper right corner.
Select a host for grayscale upgrade validation.

During the pre-upgrade preparation phase, select a host that runs noncritical workloads as the grayscale upgrade validation node. This host will initiate manual reconnection first in the following upgrade process to verify the agent upgrade, VM instance runtime status, and service availability.
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-5.5.38-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-5.5.38.tar.gz      #Decompress the Multi-MN-HA file
[root@localhost ~]# chmod +x zsha2 zstack-hamon    #Grant the decompressed files execution permission
```
Grayscale Upgrade Multi-MN-HA Suite
Run the following command on the management node that corresponds to the VIP you use to grayscale upgrade Multi-MN-HA Suite:
```
[root@localhost ~]# ./zsha2 upgrade-ha -gencfg=true
```
Grayscale upgrade the cloud platform.
Run the following command on the management node that corresponds to the VIP you use to grayscale upgrade the management nodes:
```
[root@localhost ~]# ./zsha2 upgrade-mn -grayscale -yes -db-root-pw <MYSQL_ROOT_PASSWORD> -peerpass password ZStack-Cloud-installer-5.5.38.bin
```
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.
- -grayscale enables grayscale upgrade mode. After the upgrade completes, the platform does not automatically upgrade Hosts or related Agents.
- -peerpass is optional. You can use the parameter to set the password of SSH login to the peer management nodes.
- After the upgrade completes, resources such as hosts and VPCs remain as Not Upgraded. Proceed with the upgrade by reconnecting the resources or disabling grayscale mode.
Clean up the browser cache.

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.
Check the resource status after graysacle upgrade.

Log in to the ZStack Cloud UI and check the status of hosts, primary storage, image storage and other resources. Ensure that each resource is in the Connected state. Besides, check the Upgrade Status of resources such as hosts and VPCs. Under the grayscale upgrade mode, the Upgrade Status should be displayed as Not Upgraded at this time.
Perform grayscale upgrade validation on a noncritical host.
In the ZStack Cloud UI, manually reconnect the predesigned host that runs noncritical workloads to trigger upgrades for the host and related agents.
After the reconnection completes, verify the upgrade results to ensure that the upgrade process completes successfully and that services remain operational:
- Verify that the agent version on the host is updated and the host runs normally.
- Check that the primary storage and related components operate normally.
- Verify that VM instances run normally, network connectivity works as expected, and service access remains unaffected.
When all verification checks pass and the host upgrade status displays Upgraded, the grayscale upgrade validation completes successfully. The subsequent full-platform upgrade can then proceed.
Note:
- During a grayscale upgrade, you can reconnect hosts that have not been upgraded. Reconnection automatically triggers the agent upgrade.
- If a host disconnects unexpectedly during the grayscale upgrade and automatic reconnection fails, manually reconnect the host to restore connectivity. The manual reconnection also upgrades the agent.
Proceed with full-platform resource upgrade.
After the grayscale upgrade validation completes, use one of the following methods to upgrade the remaining resources based on operational requirements:
- Manual phased upgrade: Reconnect the remaining hosts one by one to gradually upgrade the hosts and related agents. Continuously monitor the upgrade progress and service status.
- Automatic upgrade: After the grayscale upgrade validation on noncritical hosts completes and no further phased validation is required, disable grayscale mode. The platform automatically upgrades the remaining hosts and related resources.
Regardless of the method you choose, continuously monitor VM instance status during the upgrade to ensure that services remain unaffected.

Disable Grayscale Upgrade Mode

After you confirm that the grayscale upgrade validation completes without issues, run the following command to disable the grayscale upgrade mode:

[root@localhost ~]# zstack-cli   // Enter zstack-cli.
admin >>> LogInByAccount accountName=admin password=<ADMIN_PASSWORD>     // Log in to the CLI with the admin account. <ADMIN_PASSWORD> is the password of the admin account and is used as a placeholder here.
admin >>> UpdateGlobalConfig name=grayscaleUpgrade category=upgradeControl value=false     // Disable the grayscale mode.

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.

What to do next

Now, the platform grayscale upgrade is complete in a dual-management node deployment. You can continue to upgrade virtualization tools and Kernel as needed.

Upgrade Virtualization Tools

About this task

Different ZStack Cloud version may use different virtualization tools. After the cloud platform upgrading, the virtualization tools ( QEMU & Libvirt) are not updated automatically. To ensure the proper use of the latest features and security patches, you can upgrade virtualization tools manually after you upgrade the cloud platform.

Procedure

Update the local repo of the management node(s).
Make sure that you have update the local repo of the management node(s) with the new ISO. If not, run the following command on the management node(s). If you deploy dual management nodes, run the command on the two management nodes respectively:
```
[root@localhost ~]# zstack-upgrade -r ZStack-Cloud-x86_64-DVD-5.5.38-h84r.iso
```
Back up the database of the management node(s).
Make sure that you have backed up the database of the management node(s). If not, run the following command on the management node(s) to backup the database to /var/lib/zstack/mysql-backup/lib/zstack/mysql-backup/. If you deploy dual managemnt nodes, run the command on the two management nodes respectively:
```
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup
```
Check ZStack Cloud services and hardware connectivity.
Make sure that the ZStack Cloud service is normal and all hardware devices are connected well.
Disable the VM high availability globally.
Log in to the ZStack Cloud UI. On the main menu, choose Setting > Platform Setting > HA Policy. On the HA Policy page, click the Disable button on the upper right corner.
Enable the global setting zstack.experimental.repo.
Run the following commands on the management node to enable the global setting zstack.experimental.repo. If you deploy dual management nodes, run on the management node that corresponds to the VIP:
```
[root@localhost ~]# zstack-cli
# Lanuch the CLI command tool
- >>>  LogInByAccount accountName=admin password=${Password}
# Log in the admin account.
admin >>> UpdateGlobalConfig category=cluster name=zstack.experimental.repo value=true
# Enable the global setting zstack.experimental.repo.
```
Note: If you deploy dual management nodes, you can run zsha2 status on either of the management nodes. The management node whose VIP value is yes is the management node you need.

Upgrade host QEMU.

Run the following CLI commands on the management node to upgrade host QEMU:

admin >>> QueryCluster    //Query UUIDs of clusters.
admin >>> UpdateClusterOS updatePackages=qemu-kvm excludePackages=python2-crypto uuid=${ClusterUuid}    //Upgrade QEMU of hosts in the specified cluster. Record the uuid (LongJobUuid) returned.
admin >>> QueryLongJob uuid=${LongJobUuid}    //Query the upgrading progress. If the returned state value is Succeeded, the upgrading is completed.

Note: If you deploy more than one cluster, you can upgrade the QEMU of host in different clusters sequentially.

Upgrade host Libvirt.

Run the following CLI commands on the management node to upgrade host Libvirt:

admin >>> QueryCluster    //Query UUIDs of clusters.
admin >>> UpdateClusterOS updatePackages=glib2 uuid=${ClusterUuid}
admin >>> UpdateClusterOS updatePackages=libvirt excludePackages=python2-crypto uuid=${ClusterUuid}    //Upgrade Libvirt of hosts in the specified cluster. Record the uuid (LongJobUuid) returned.
admin >>> QueryLongJob uuid=${LongJobUuid}    //Query the upgrading progress. If the returned state value is Succeeded, the upgrading is completed.

Note: If you deploy more than one cluster, you can upgrade the Libvirt of host in different clusters sequentially.

Check the QEMU and Libvirt version after the upgrading.
Run the following command on the hosts to check whether the QEMU and Libvirt are upgraded to the target version:
```
[root@localhost ~]# qemu-img -V    //Check the QEMU version.
[root@localhost ~]# rpm -qa | grep libvirt    //Check the Libvirt version.
```
Disable the global setting zstack.experimental.repo.
After the upgrading, run the following CLI command on the management node to disable the global setting zstack.experimental.repo:
```
admin >>> UpdateGlobalConfig category=cluster name=zstack.experimental.repo value=false
```
Reboot/migrate VM instances, VPC vRouters, and LB instances.
Log in to the ZStack Cloud UI, reboot or migrate VM instances, VPC vRouters, and LB instances on the hosts whose QEMU is upgraded, making the QEMU version of VM instances, VPC vRouters, and LB instances consistent with the QEMU version of the hosts they are residing on.
Enable the VM high availability globally.
On the main menu of ZStack Cloud, choose Setting > Platform Setting > HA Policy. On the HA Policy page, click the Enable button on the upper right corner.

What to do next

Now, you have completed the virtualization tool (QEMU & Libvirt) upgrading.

Upgrade Kernel

About this task

Different ZStack Cloud version may use different Kernel. After the cloud platform upgrading, the host Kernel are not updated automatically. To ensure the proper use of the latest features and security patches, you can upgrade Kernel manually after you upgrade the cloud platform.

Procedure

Update the local repo of the management node(s).
Make sure that you have update the local repo of the management node(s) with the new ISO. If not, run the following command on the management node(s). If you deploy dual management nodes, run the command on the two management nodes respectively:
```
[root@localhost ~]# zstack-upgrade -r ZStack-Cloud-x86_64-DVD-5.5.38-h84r.iso
```
Back up the database of the management node(s).
Make sure that you have backed up the database of the management node(s). If not, run the following command on the management node(s) to backup the database to /var/lib/zstack/mysql-backup/lib/zstack/mysql-backup/. If you deploy dual management nodes, run the command on the two management nodes respectively:
```
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup
```
Check ZStack Cloud services and hardware connectivity.
Make sure that the ZStack Cloud service is normal and all hardware devices are connected well.
Disable the VM high availability globally.
Log in to the ZStack Cloud UI. On the main menu, choose Setting > Platform Setting > HA Policy. On the HA Policy page, click the Disable button on the upper right corner.
Enable the global setting zstack.experimental.repo.
Run the following commands on the management node to enable the global setting zstack.experimental.repo. If you deploy dual management nodes, run on the management node that corresponds to the VIP:
```
[root@localhost ~]# zstack-cli
# Lanuch the CLI command tool
- >>>  LogInByAccount accountName=admin password=${Password}
# Log in the admin account.
admin >>> UpdateGlobalConfig category=cluster name=zstack.experimental.repo value=true
# Enable the global setting zstack.experimental.repo.
```
Note: If you deploy dual management nodes, you can run zsha2 status on either of the management nodes. The management node whose VIP value is yes is the management node you need.

Upgrade host Kernel.

Run the following CLI commands on the management node to upgrade host Kernel:

admin >>> QueryCluster    //Query UUIDs of clusters.
admin >>> UpdateClusterOS updatePackages=kernel excludePackages=python2-crypto uuid=${ClusterUuid}    //Upgrade Kernel of hosts in the specified cluster. Record the uuid (LongJobUuid) returned.
admin >>> QueryLongJob uuid=${LongJobUuid}    //Query the upgrading progress. If the returned state value is Succeeded, the upgrading is completed.

Note: If you deploy more than one cluster, you can upgrade the Kernel of host in different clusters sequentially.

Check the Kernel version after the upgrading.
Run the following command on the hosts to check whether the Kernel are upgraded to the target version:
```
[root@localhost ~]# rpm -qa | grep -i kernel
```
Reboot hosts.
Reboot hosts to make the new Kernel version take effect.
Note: Rebooting a host temperately interrupts VM business running on it. We recommend that you perform this action during off-peak periods.
Disable the global setting zstack.experimental.repo.
After the upgrading, run the following CLI command on the management node to disable the global setting zstack.experimental.repo:
```
admin >>> UpdateGlobalConfig category=cluster name=zstack.experimental.repo value=false
```
Enable the VM high availability globally.
On the main menu of ZStack Cloud, choose Setting > Platform Setting > HA Policy. On the HA Policy page, click the Enable button on the upper right corner.

What to do next

Now, you have completed the Kernel upgrading and the whole typical upgrading process of ZStack Cloud. If you have any other question or need upgrading help, contact the official technical support.

Glossary

Instance

An instance is a virtual machine or server that runs the images of operating systems in Cloud, such as VM instance and elastic baremetal instance.

VM Instance

A VM instance is a virtual machine instance running on a host. A VM instance has its own IP address and can access public networks and run application services.

Volume

A volume provides storage space for a VM instance. Volumes are categorized into root volumes and data volumes.

Root Volume

A root volume provides support for the system operations of a VM instance.

Data Volume

A data volume provides extended storage space for a VM instance.

Image

An image is a template file used to create a VM instance or volume. Images are categorized into system images and volume images.

Instance Offering

An instance offering defines the number of vCPU cores, memory size, network bandwidth, and other configuration settings of VM instances.

Disk Offering

A disk offering defines the capacity and other configuration settings of volumes.

GPU Specification

A GPU specification defines the frame per second (FPS), video memory, resolution, and other configuration settings of a physical or virtual GPU. GPU specifications are categorized into physical GPU specifications and virtual GPU specifications.

vNUMA Configuration

vNUMA uses CPU pinning to passthrough the topology of associated host physical NUMA (pNUMA) nodes to a VM instance, generating a topology of virtual NUMA (vNUMA) nodes for the VM instance. This topology enables a vCPU on a vNUMA node to primarily access the local memory and thus improves VM performance.

NUMA (Non-Uniform Memory Access)

Non-uniform memory access (NUMA) is a computer memory design where the memory access time depends on the memory location relative to the CPU. Under NUMA, a processor can access its own local memory faster than non-local memory and thus improves VM performance.

pNUMA Node (physical NUMA Node)

A pNUMA node (physical NUMA node) is a host NUMA node predefined based on the host NUMA architecture. It is used to manage the CPUs and memory of the host.

pNUMA Topology (physical NUMA Topology)

A pNUMA topology (physical NUMA topology) is the topology of the host NUMA nodes predefined by the CPU vendor based on the host NUMA architecture.

vNUMA Node (virtual NUMA Node)

A vNUMA node (virtual NUMA node) is generated by passing-through associated pNUMA nodes via CPU pinning. It is used to manage the CPUs and memory of a VM instance.

vNUMA Topology (virtual NUMA Topology)

A vNUMA topology (virtual NUMA topology) is the topology of VM NUMA nodes generated by passing-through associated pNUMA nodes via CPU pinning.

Local Memory

Local memory is the memory that a CPU (pCPU or vCPU) accesses through the Uncore iMC (Integrated Memory Controller) of the same NUMA (pNUMA or vNUMA) node. Compared with accessing non-local memory, accessing local memory has lower latencies.

CPU Pinning

CPU pinning assigns the virtual CPUs (vCPUs) of a VM instance to specific physical CPUs (pCPUs) of the host, which improves VM performance.

EmulatorPin Configuration

EmulatorPin assigns all other threads than virtual CPU (vCPU) threads and IO threads of a VM instance to physical CPUs (pCPUs) of the host so that these threads run on assigned pCPUs.

Auto-Scaling Group

An auto-scaling group is a group of VM instances that are used for the same scenarios. An auto-scaling group can automatically scale out or in based on application workloads or health status of VM instances in the group.

Snapshot

A snapshot is a point-in-time capture of data status in a volume.

Affinity Group

A VM scheduling policy is a resource orchestration policy based on which VM instances are assigned hosts to achieve the high performance and high availability of businesses.

Zone

A zone is a logical group of resources such as clusters, L2 networks, and primary storage. Zone is the largest resource scope defined in the Cloud.

Cluster

A cluster is a logical group of hosts (compute nodes).

Host

A host provides compute, network, and storage resources for VM instances.

Primary Storage

A primary storage is one or more servers that store volume files of VM instances. These files include root volume snapshots, data volume snapshots, image caches, root volumes, and data volumes.

Image Storage

An image storage is a storage server that stores VM image templates, including ISO image files.

iSCSI Storage

iSCSI storage is an SAN storage that uses the iSCSI protocol for data transmission. You can add an iSCSI SAN block as a Shared Block primary storage or pass through the block to a VM instance.

FC Storage

FC storage is an SAN storage that uses the FC technology for data transmission. You can add an FC SAN block as a Shared Block primary storage or pass through the block to a VM instance.

NVMe Storage

A type of storage implemented via the NVMe-oF (NVMe over fabrics) protocol. You can add a block device configured from an NVMe storage as SharedBlock primary storage.

L2 Network

An L2 network is a layer 2 broadcast domain used for layer 2 isolation. Generally, L2 networks are identified by names of devices on the physical network.

VXLAN Pool

A VXLAN pool is a collection of VXLAN networks established based on VXLAN Tunnel Endpoints (VTEPs). The VNI of each VXLAN network in a VXLAN pool must be unique.

L3 Network

An L3 network includes IP ranges, gateway, DNS, and other network configurations that are used by VM instances.

Public Network

Generally, a public network is a logical network that is connected to the Internet. However, in an environment that has no access to the Internet, you can also create a public network.

Flat Network

A flat network is connected to the network where the host is located and has direct access to the Internet. VM instances in a flat network can access public networks by using elastic IP addresses.

VPC Network

A VPC network is a private network where VM instances can be created. A VM instance in a VPC network can access the Internet through a VPC vRouter.

Management Network

A management network is used to manage physical resources in the Cloud. For example, you can create a management network to manage access to hosts, primary storage, image storage, and VPC vRouters.

Flow Network

A flow network is a dedicated network for port mirror transmission. You can use a flow network to transmit the mirrors of data packets of NIC ports to the target ports.

VPC vRouter

A VPC vRouter is a dedicated VM instance that provides multiple network services.

VPC vRouter HA Group

A VPC vRouter HA group consists of two VPC vRouters. Either VPC vRouter can be a primary or secondary VPC vRouter for the group. If the primary VPC vRouter does not work as expected, the VPC vRouter becomes the secondary VPC vRouter in the group to ensure high availability of business.

vRouter Image

A vRouter image encapsulates network services and can be used to create VPC vRouters.

Dedicated-Performance LB Image

A dedicated-performance load balancer (LB) image encapsulates dedicated-performance load-balancing services and can be used to create load balancer instances. However, a dedicated-performance load balancer image cannot be used to create VM instances.

vRouter Offering

A vRouter offering defines the number of vCPU cores, memory size, image, management network, and public network configuration settings of VPC vRouters. You can use a vRouter offering to create VPC vRouters that can provide network services for public networks and VPC networks.

LB Instance Offering

A load balancer (LB) instance offering defines the CPU, memory, image, and management network configuration settings used to create LB instances. LB instances provide load balancing services for the public network, flat network, and VPC network.

SDN Controller

The SDN controller is the core of the SDN architecture, responsible for centralized management and control of network devices.

SDN Cluster

A cluster of dedicated VM instances designed to provide highly available SDN capabilities.

SDN Instance

A dedicated VM instance designed to provide SDN network capabilities.

SDN Image

An SDN image encapsulates an SDN software and can be used to create SDN instances.

SDN Instance Offering

An SDN instance offering defines the CPU, memory, SDN image, and management network configuration used for creating SDN instances.

Security Group

A security group provides security control services for VM NICs. It filters the ingress or egress TCP, UDP, and ICMP packets of VM NICs based on the specified security rules.

VIP

In bridged network environments, a virtual IP address (VIP) provides network services such as serving as an elastic IP address (EIP), port forwarding, load balancing, IPsec tunneling. When a VIP provides the preceding network services, packets are sent to the VIP and then routed to the destination network where VM instances are located.

EIP

An elastic IP address (EIP) functions based on the NAT technology. IP addresses in a private network are translated into an EIP that is in another network. This way, private networks can be accessed from other networks by using EIPs.

Port Forwarding

Port forwarding functions based on the layer-3 forwarding service of VPC vRouters. This service forwards traffic flows of the specified IP addresses and ports in a public network to specified ports of VM instances by using the specified protocol. If your public IP addresses are insufficient, you can configure port forwarding for multiple VM instances by using one public IP address and port.

Load Balancer

A load balancer distributes traffic flows of a virtual IP address to backend servers. It automatically inspects the availability of backend servers and isolates unavailable servers during traffic distribution. This way, the load balancer improves the availability and service capability of your business.

Listener

A listener monitors the frontend requests of a load balancer and distributes the requests to a backend server based on the specified policy. In addition, the listener performs health checks on backend servers.

Forwarding Rule

A forwarding rule forwards the requests from different domain names or URLs to different backend server groups.

Backend Server Group

A backend server group is a group of backend servers that handles requests distributed by load balancers. It is the basic unit for traffic distribution by load balancer instances.

Backend Server

A backend server handles requests distributed by a load balancer. You can add a VM instance on the Cloud or a server on a third-party cloud as a backend server.

Frontend Network

A frontend network is a type of network that is associated with a load balancer. Requests from the network are distributed by the load balancer to backend servers based on a specified policy.

Backend Network

A backend network is a type of network that is associated with a load balancer. Requests from frontend networks are distributed by the load balancer to servers in the backend network.

Load Balancer Instance

A load balancer instance is a custom VM instance used to provide load balancing services.

Certificate

If you select HTTPS for a listener, associate it with a certificate to make the listener take effect. You can upload either a certificate or certificate chain.

Firewall

A firewall is an access control policy that monitors ingress and egress traffic of VPC vRouters and decides whether to allow or block specific traffic based on the associated rule sets and rules.

Firewall Rule Set

A firewall rule set is a set of rules that a firewall uses to defend against network attacks. You need to associate a rule set with the egress or ingress flow direction of VPC vRouter NICs to make the rule set take effect.

Firewall Rule

A firewall rule is an access control entry associated with the egress or ingress flow direction of VPC vRouter NICs to defend against network attacks. A firewall rule includes rule priority, match condition, and behavior.

Rule Template

A rule template is a template that you can select when you add rules to a rule set or a firewall.

IP/Port Set

An IP or port set is a set of IP addresses or ports that you can select when you add rules to a rule set or a firewall.

IPsec Tunnel

An IPSec tunnel encrypts and verifies IP packets that transmit over a virtual private network (VPN) from one site to another.

OSPF Area

An Open Shortest Path First (OSPF) area is divided from an autonomous system based on the OSPF protocol. This simplifies the hierarchical management of vRouters.

NetFlow

A NetFlow monitors the ingress and egress traffic of the NICs of VPC vRouters. The supported versions of data flows are V5 and V9.

Port Mirroring

Port mirroring mirrors the traffic data of VM NICs and sends the traffic data to the target ports. This allows for the analysis of data packets of ports and simplifies the monitoring and management of data traffic and makes it easier to locate network errors and exceptions.

Route Table

A route table contains information about various routes that you configure. Route entries in a route table must include the destination network, next hop, and route priority.

CloudFormation

CloudFormation is a service that simplifies the management of cloud resources and automates deployment and O&S. You can create a stack template to configure cloud resources and their dependencies. This way, resources can be automatically configured and deployed in batches. CloudFormation provides easy management of the lifecycle of cloud resources and integrates automatic O&S into API and SDK.

Resource Stack

A resource stack is a stack of resources that are configured by using a stack template. The resources in the stack have dependencies with each other. You can manage resources in the stack by managing the resource stack.

Stack Template

A stack template is a UTF8-encoded file based on which you can create resource stacks. The stack template defines the resources that you want, the dependencies between the resources, and the configuration settings of the resources. When you use a stack template to create a resource stack, CloudFormation parses the template and the resources are automatically created and configured.

Sample Template

A sample template is a commonly used resource stack. You can use a sample template provide by the Cloud to create resource stacks.

Designer

A designer is a CloudFormation tool that allows you to orchestrate cloud resources. You can drag and drop resources on a canvas and use lines to establish dependencies between the resources.

Baremetal Cluster

A baremetal cluster consists of baremetal chassis. You can manage baremetal chassis by managing a baremetal cluster where the chassis reside.

Deployment Server

A deployment server is a server that provides PXE service and console proxy service for baremetal chassis.

Baremetal Chassis

A baremetal chassis is used to create a baremetal instance and is identified based on the BMC interface and IPMI configuration setting.

Preconfigured Template

A preconfigured template is used to create a preconfigured file that allows for unattended batch installation of an operating system for baremetal instances.

Baremetal Instance

A baremetal instance is an instantiated baremetal chassis.

Elastic Baremetal Management

Elastic Baremetal Management provides dedicated physical servers for your applications to ensure high performance and stability. In addition, this feature allows elastic scaling. You can apply for and scale resources based on your needs.

Provision Network

A provision network is a dedicated network for PXE boot and image downloads while creating elastic baremetal instances in a gateway proxy cluster.

Elastic Baremetal Cluster

Provides a separated cluster to manage baremetal nodes.

Gateway Node

A gateway node is a node where the ingress and egress traffic of the Cloud and elastic baremetal instances in gateway proxy clusters is forwarded.

Baremetal Node

A baremetal node is used to create a baremetal instance and is identified based on the BMC interface and IPMI configuration setting.

Elastic Baremetal Instance

An elastic baremetal instance has the same performance as physical servers and allows elastic scaling. You can apply for and scale resources based on your needs.

Elastic Baremetal Offering

An elastic baremetal offering defines the number of vCPU cores, memory size, CPU architecture, CPU model, and other configuration settings of elastic baremetal instances.

vCenter

The Cloud allows you to take over vCenter and manage resources on the vCenter.

VM Instance

A VM instance is an ESXi virtual machine instance running on a host. A VM instance has its own IP address to access public networks and can run application services.

Network

A vCenter network defines the network settings of VM instances on vCenter, such as IP range, gateway, DNS, and network services.

Volume

A volume provides storage space for a VM instance on vCenter. A volume attached to a VM instance can be used as a root volume or data volume. A root volume provides support for the system operations of a VM instance. A data volume provides extended storage space for a VM instance.

Image

An image is a template file used to create a VM instance or volume on vCenter. Images are categorized into system images and volume images.

Event Message

Event Message displays event alarm messages of vCenter that is took over by the Cloud. This feature allows you to locate errors and exceptions efficiently.

Network Topology

A network topology visualizes the network architecture of the Cloud. It allows for efficient planning, management, and improvement of network architecture. Network topologies can be categorized into global topologies and custom topologies.

Performance Analysis

Performance Analysis displays the performance metrics of key resources monitored externally or internally in the Cloud. You can view the performance analysis or export the analysis report as needed to improve the O&M efficiency.

Capacity Management

Capacity Management visualizes the capacities and usages of key resources in the Cloud. You can use this feature to improve O&S efficiency.

MN Monitoring

Management Node (MN) monitoring allows you to view the health status of each management node when you use multiple management nodes to achieve high availability.

Alarm

An alarm is used to monitor the status of time-series data and events and respond to the status change. Alarms can be categorized into resource alarm, event alarm, and extended alarm.

One-Click Alarm

A one-click alarm integrates multiple metrics of a resource. You can create one-click alarms for multiple resources to monitor these resources.

Alarm Template

An alarm template is a template of alarm rules. If you associate an alarm template with a resource group, an alarm is created to monitor the resources in the group.

Resource Group

A resource group consists of resources grouped based on your business needs. If you associate an alarm template with a resource group, the alarm rules specified by the template take effect on all the resources in the group.

Message Template

A message template specifies the text template of a resource alarm message or event alarm message sent to an SNS system.

Message Source

A message source is used to take over extended alarm messages. If you configure alarms for message sources, extended alarm messages can be sent to various endpoints.

Endpoint

An endpoint is a method that users obtain subscribed messages. Endpoints are categorized into system endpoints, email, DingTalk, HTTP application, short message service, and Microsoft Teams.

Alarm Message

An alarm message is a message sent the time when an alarm is triggered.

Current Task

A current task is an ongoing operation performed in the Cloud. You can perform centralized management over ongoing operations.

Operation Log

An operation log is a chronological record of operations on the specified objects and their operation results.

Audit

Audit monitors and records all activities on the Cloud. You can use this feature to implement operation tracking, cybersecurity classified protection compliance, security analysis, troubleshooting, and automatic O&M.

Log Collection

Allows you to collect with one click the log data from the Cloud and various nodes on the Cloud generated in the specified time period and download the log data.

One-Click Inspection

Comprehensively inspects the health status of key resources and services of the Cloud and scores their healthiness based on the inspection results. In addition, the one-click inspection service provides O&M suggestions and inspection reports.

Backup Management

Backup management integrates multiple disaster recovery technologies such as incremental backup and full backup that are suitable for multiple business scenarios. You can implement local backup and remote backup based on your business needs.

Backup Job

You can create a backup job to back up local VM instances, volumes, or databases to a specified storage server on a regular basis.

Local Backup Data

Local backup data of VM instances, volumes, and databases is stored in the local backup server.

Local Backup Server

A local backup server is located at the local data center and is used to store local backup data.

Remote Backup Server

A remote backup server is located at a remote data center or a public cloud and is used to store remote backup data.

Continuous Data Protection (CDP)

Continuous Data Protection (CDP) provides second-level and fine-grained continuous backups for important business systems in VM instances, allowing users to restore VM data to a specific time state, and retrieve files without restoring the system.

CDP Task

You can create a CDP task to continuously back up your VM data to a specified backup server to achieve continuous data protection and recovery.

CDP Data

The backup data generated from continuous data protection on VM instances is stored in local backup servers.

Recovery Point

A recovery point is a data point generated during continuous data protection. A recovery point corresponds to a data record within the recovery point interval specified by the user.

Locked Recovery Point

You can lock or unlock a recovery point as needed. After a recovery point is locked, data of the recovery point will not be automatically cleared or deleted.

Recovery Task

A recovery task helps you quickly restore data by specifying a CDP task and recovery point, and allows you to view the recovery progress and logs in a more friendly way.

Cryptography Security Compliance

The Cryptography Security Compliance service provides applications with cloud security capabilities based on commercial cryptography, meeting the requirements of commercial cryptography application security assessments.

HSM Pool

An HSM pool is a logical group of hardware security modules (HSMs) and is used to provide unified cryptography services such as signature validation and encryption.

HSM

A hardware security module (HSM) is a dedicated device that encrypts, decrypts, and authenticates information by using the cryptographic technology.

Platform Cryptography Security Compliance

Enables the Cloud to meet the requirements of Cryptography Security Compliance through the cryptography capabilities provided by HSM pools.

Certificate Login

Authenticates the identity of a user by using a UKey device.

Data Protection

Protects important data on the Cloud to ensure the data confidentiality and integrity.

Scheduled Job

A scheduled job defines that a specific action be implemented at a specified time based on a scheduler.

Scheduler

A scheduler is used to schedule jobs. It is suitable for business scenarios that last for a long time.

Tag

A tag is used to mark resources. You can use a tag to search for and aggregate resources.

Migration Service

The Cloud provides V2V migration service that allows you to migrate VM instances and data from other virtualized platform to the current cloud platform.

ZMigrate Migration Service

A migration service installed from Application Market that migrates VM instances and their data from VMware environments to the current cloud platform.

V2V Migration

V2V Migration allows you to migrate VM instances from the VMware or KVM platform to the current cloud platform.

V2V Conversion Host

A V2V conversion host is a host in the destination cluster that you need to specify during V2V migration to cache VM instances and data when you implement V2V migration. After the VM instances and data are cached in the V2Vconversion host, they are migrated to the destination primary storage.

User

A user is a natural person that constructs the most basic unit in Tenant Management.

User Group

A user group is a collection of natural persons or a collection of project members. You can use a user group to grant permissions.

Role

A role is a collection of permissions that can be granted to users. A user that assumes a role can call API operations based on the permissions specified by the role. Roles are categorized into platform roles and project roles.

Single Sign-On

The Single Sign-On service provided by the Cloud. It supports seamless access to SSO systems. Through the service, related users can directly log in to the Cloud and manage cloud resources.

Project

A project is a task that needs to be accomplished by specific personnel at a specified time. In Tenant Management, you can plan resources at the project granularity and allocate an independent resource pool to a project. The word Tenant in Tenant Management mainly refers to projects. A project is a tenant.

Project Member

A project member is a member in a project who is granted permissions on specific project resources and can use the resources to accomplish tasks. Project members include the project admin, project managers, and normal project members.

Process Management

Process management is part of ticket management that manages the processes related to the resources of projects. Processes can be categorized into default processes and custom processes.

My Approvals

In the Cloud, only the administrator and project administrators are granted approval permissions. the administrator and project administrators can approve or reject a ticket. If a ticket is approved, resources are automatically deployed and allocated to the specified project.

Bills

A bill is the expense of resources totaled at a specified time period. Billing is accurate to the second. Bills can be categorized into project bills, department bills, and account bills.

Pricing List

A pricing list is a list of unit prices of different resources. The unit price of a resource is set based on the specification and usage time of the resource.

Console Proxy

Console proxy allows you to log in to a VM instance by using the IP address of a proxy.

AccessKey Management

An AccessKey pair is a security credential that one party authorizes another party to call API operations and access its resources in the Cloud. AccessKey pairs shall be kept confidential.

IP Allowlist/Blocklist

An IP allowlist or blocklist identifies and filters IP addresses that access the Cloud. You can create an IP allowlist or blocklist to improve access control of the Cloud.

Application Center

Application Market allows you to add applications to the Cloud and then access the applications with one click. It extends the functionality of the Cloud. You can add default applications through the built-in installation package or add more applications through URLs.

Sub-Account Management

A sub-account can be created by the admin or synced from an SSO authentication system and is managed by the admin. Resources created under a sub-account are managed by the sub-account.

Theme and Appearance

You can customize the theme and appearance of the Cloud.

Email Server

If you select Email as the endpoint of an alarm, you need to set an email server. Then alarm messages are sent to the email server.

Log Server

A log server is used to collect management node logs or the platform operation logs. You can add a log server to the cloud and use the collected logs for operation trace or troubleshooting. This makes your O&M more efficient.

Global Setting

Global Setting allows you to configure settings that take effect on the whole platform.

Scenario Template

Scenario Template provides multiple templates that encapsulate scenario-based global settings. You can apply a template globally with one click based on your business needs. This improves your O&M efficiency.

HA Policy

HA Policy is a mechanism that ensures sustained and stable running of the business if VM instances are unexpectedly stopped or are errored because of errors occurring to compute, network, or storage resources associated with the VM instances. By enabling this feature, you can customize VM HA policies to ensure your business continuity and stability.

Time Management

Manages the Cloud system time and allows you to configure time servers for the Cloud. After you configure NTP time servers for the Cloud, the clock of the time servers is synced with all nodes of the Cloud.

GPU Device

A GPU device is a powerful microprocessor with high computational capabilities. You can use a GPU device to handle intricate graphics rendering and parallel computing jobs, thus improving the efficiency of businesses such as graphic production, video processing, and machine learning.

Script Library

The script library stores and manages script files centrally. By executing scripts on VM instances, you can complete complex O&M operations and automated jobs.

XML Hook

An XML Hook is a script that can flexibly insert or modify parameters in XML files of VM instances. By attaching an XML Hook to a VM instance, you can customize VM configurations and enable specialized functionalities.

Container Service

A simple and user-friendly container management service, providing features like GPU management & scheduling, multi-tenancy, multi-cluster, quota configuration, CI/CD. and microservice. The service reduces the container using complexity and aligns well with traditional user's habits, helping you easily manage and deploy your container cluster, and enjoy the benefits of cloud-native technologies in a quick and convenient way.

Advanced Monitoring Server

An advanced monitoring server is a dedicated VM instance used to receive advanced monitoring data of load balancers and other resources.

Advanced Monitoring Server Image

An advanced monitoring server image encapsulates the advanced monitoring service and can be used to create advanced monitoring server.

Advanced Monitoring Server Offering

An advanced monitoring server offering defines the CPU cores, memory size, image, management network, and public network configurations of advanced monitoring server. You can use an advanced monitoring server offering to create advanced monitoring servers.

Plugin Management

You can package extended resources or tools into standardized plugins for quick installation and integration, expanding the Cloud capabilities.

Region Management

A region is a self-contained cloud environment with independent management node(s), networks, hardware, and cloud resources. ZStack IAM enabled user synchronization and SSO across multiple regions.

PreviousZStack Cloud NextZStack Cloud