ZStack Cloud 5.5.6 optimizes the instance-cluster binding mechanism.

Supports Enabling Instance-Cluster Binding at the Cluster Level

On the cluster details page, choose Advanced Settings and enable Instance-Cluster Binding. Then, all new instances created in this cluster inherit this configuration by default. Based on the Instance Binding Policy, they must or are prioritized to start in this cluster. Affected instance types include: VM instances, VPC vRouters, load balancer instances, advanced monitoring servers, and SDN instances.

You can also enable or disable Instance-Cluster Binding for individual instances. Once individually enabled or disabled with this switch, the instance is not affected by this cluster setting.

Binding Policy Optimization

ZStack Cloud 5.5.6 optimizes the complex instance-cluster binding logic. After optimization, two instance-cluster binding policies are supported.

• Hard: Instances must start in the current cluster. If no available hosts exist in the current cluster, startup fails. Also, manual migration to other clusters is not allowed.
• Soft : Instances are prioritized to start in the current cluster. If no available hosts exist in the current cluster, instances can start in other clusters. Also, manual migration to other clusters is allowed.

You can set Instance Binding Policy in Advanced Settings on the cluster details page. This policy applies to all instances with Instance-Cluster Binding enabled in this cluster.

Starting from ZStack Cloud 5.5.6, the VM instance VNC console supports full-screen display and small-dot cursor. This maximizes screen space utilization, eliminates visual distractions, and improves the experience for detailed console operations.

Starting from ZStack Cloud 5.5.6, you can specify individual backend server group ports for forwarding rules. This distributes requests from different domains or URLs to specific service ports of backend server groups, enabling more flexible service management.

Starting from ZStack Cloud 5.5.6, you can use Ceph block storage volumes as Elastic Baremetal system volumes. This effectively improves system volume storage performance and avoids single points of failure through multi-path mechanisms, ensuring high availability for business operations.

You need to add a Ceph Enterprise primary storage in advance, configure access paths, and add access tokens. When creating an elastic baremetal instance (startup method: volume) using this primary storage, a block storage volume is created as the system volume by default.

Starting from ZStack Cloud 5.5.6, you can create backups for elastic baremetal instances. The backup can include the data of only the system volume or both the system volume and attached data volumes (excluding shared volumes). Backup data can be restored with one click, providing further security for business running on elastic baremetal instances.

Currently, the backup is supported only when the elastic baremetal instance uses a block storage volume as the system volume.

Starting from ZStack Cloud 5.5.6, the following billing currency types are supported: Vietnamese Dong (VND), Myanmar Kyat (MMK), Cambodian Riel (KHR), Philippine Peso (PHP), Kazakhstani Tenge (KZT), and South Korean Won (KRW).

You can select the desired currency through Global Settings > Billing Currency Symbol. Once configured, bills are calculated in the selected currency.

Starting from ZStack Cloud 5.5.6, the login page title can be set to a maximum of 100 characters, flexibly accommodating more user requirement scenarios.