Starting form ZStack Cloud 4.6.21, the Cloud supports displaying the QEMU state of resources and alerts in VM instance/cluster to help users to avoid missing security patches or incomplete functions caused by QEMU version inconsistency.

On Cluster Level

ZStack Cloud 4.6.21 supports monitoring the QEMU state of hosts in a cluster. You can timely get the information about the QEMU version of hosts through the cluster details page or an event alarm, and update the corresponding host QEMU.

Adds Alert of QEMU Version on Cluster Details Page

ZStack Cloud 4.6.21 adds an alert of QEMU version on the cluster details page. When the QEMU version of hosts in a cluster is inconsistent with the recommended version, an alert message will appear on the top of the cluster details page, advising users to check and update the host QEMU version to timely avoid security or functional use problems.

Adds Event Alarm: QEMU Version of Hosts in Cluster Needs to be Updated

In addition to the alert on details page, ZStack Cloud 4.6.21 adds a default event alarm: QEMU Version of Hosts in Cluster Needs to be Updated, which monitors and alarms the QEMU state of hosts in a cluster. You can quickly locate the corresponding cluster based on alarm messages and efficiently fix problems related to the host QEMU version.

On VM Instance Level

When the host QEMU version is updated, you need to update the VM instances on the host to make the QEMU configuration take effect. ZStack Cloud 4.6.21 supports displaying the QEMU state of VM instances/VPC vRouters/LB instances, helping users to quickly locate VM instance whose QEMU version need to be updated.

Supports Displaying and Filtering QEMU State on VM/VPC vRouter Lists

Starting from ZStack Cloud 4.6.21, a new QEMU state column is added to the VM instance/VPC vRouter list to display the QEMU version information. When the QEMU version of a VM instance/VPC vRouter is inconsistent with that of the host it resides on, the QEMU state is displayed as To be Updated. You can reboot or migrate the VM instance/VPC vRouter to update the QEMU version.

You can also filter VM instances/VPC vRouters by QEMU state. When you filter all resources whose QEMU state is To be updated, you can migrate or reboot these resources with one click to batch update the QEMU version.

Supports Displaying QEMU State on LB Instance Details Page

In addition to VM instances/VPC vRouters, ZStack Cloud 4.6.21 supports displaying the QEMU state of an LB instance. On the details page of a load balancer, click the LB instance tab and you can view the QEMU state. When the LB instance QEMU version is inconsistent with that of the host it resides on, the QEMU state is displayed as To be updated. You can reboot or migrate the instance to update its QEMU version.

ZStack Cloud 4.6.21 makes optimizations on the VM instance hot migration.

Supports Displaying Migration Rate and Data Migrated When Hot Migrate VM Instance

Starting from ZStack Cloud 4.6.21, when you hot migrate a VM instance (change host, change primary storage, or change host and primary storage), ZStack Cloud dynamically displays the real-time migration rate and the data migrated.

You can hover over the progress bar of Data Migrated to view the Total Data Volume, Data Migrated, and Remaining Data Volume, so as to visualize the migration progress and make business adjustment as needed.

Supports Canceling VM Hot Migration Task

When hot migrating a VM instance (change host), you can cancel the task at any time as needed and the cancellation process is business-unaware.

In earlier versions, when you create an L3 network, you need to configure network ranges, netmask, gateway, and other parameters to allocate an IP address for VM instances using this L3 network. The VM instance IP address must be in the network range of the network to which it belongs.

Starting from ZStack Cloud 4.6.21, a new IP Address Management (IPAM) switch is added when creating a flat network. After disabling IPAM, you do not need to configure network ranges, netmask, gateway or DHCP service. When creating VM instance using the network, you can self-allocate and self-manage the IP address without being restricted by the L3 network range.

Self-allocated IP address can be specified on the Cloud or configured in the VM instance. If you specify a self-allocated IP address on the Cloud, you need to deploy the IP configuration through GuestTools to make it take effect.

Currently, the flat network with IPAM disabled still supports security group services to provide network security control for VM instances, and more network services will be adapted in the future.

In earlier versions, an L3 network supports three IP allocation policies: Random, Allocate in Order, and Allocate in Cycle. You can specify an IP allocation policy after the DHCP service is enabled.

ZStack Cloud 4.6.21 disassociates specifying IP allocation policy from enabling DHCP service. You can customize an IP allocation policy for an L3 network with DHCP service enabled or disabled.

In earlier versions, when adding a SharedBlock primary storage based on an iSCSI storage LUN, you need to attach the SharedBlock primary storage and the associated iSCSI storage to the same cluster to ensure that the primary storage LUN works properly.

ZStack Cloud 4.6.21 optimizes the attachment steps. When you attach a SharedBlock storage to the target cluster, ZStack Cloud automatically detects and attaches the associated iSCSI storage and prompts an alert message about the association between SharedBlock and iSCSI storage, so as to avoid usage problems caused by inconsistent attachment.

ZStack Cloud 4.6.21 begins to support NVMe storage. You can add a block device configured from a NVMe storage as a SharedBlock primary storage.

Supports One-Click Scanning and Displaying NVMe Storage and LUNs

After you build a NVMe backend storage and ensure that the Cloud compute node is connected to NVMe block devices, you can log in to the Cloud and click Sync Device Info. ZStack Cloud scans all NVMe block devices and display the key information of the block devices in detail in a list.

Supports Adding NVMe LUNs as SharedBlock Storage

After a NVMe Lun is synced to the Cloud, you can add it as a SharedBlock storage. When you created VM instances and volumes using a NVMe storage, you can leverage the powerful storage performance of NVMe to improve the read/write rate and IOPS of VM instances and reduce read/write latency.

ZStack Cloud 4.6.21 makes enhancements on backup service.

Optimizations of Backup Resource Name in Backup Job Details Page

In earlier versions, backup job details only display the UUID of resources. Starting from ZStack Cloud 4.6.21, backup job details page supports displaying resource name, which is easy for O&M personnel to view.

Adding Local Backup Server Requires Setting Backup Network

Starting from ZStack Cloud 4.6.21, when you add a local backup server on the Cloud, you need to specify a backup network. In local backup scenarios, data backups are implemented by using the backup network to avoid network congestion and improve transmission efficiency.