This document introduces how to install and deploy ZStack Cube Ultimate.
Planning and Prerequisites
Configure Network Environment
This section describes the network planning and switch connection requirements for
deploying ZStack Cube Ultimate.
Network Planning
Prepare the following networks in advance:
Management network: Used for managing and controlling the platform's
hardware resources. It is recommended to configure at least dual 1GbE
networks.
Storage network: Used for providing storage services and carrying
storage traffic. It is recommended to configure dual 10GbE networks.
Business network: Used by VM instances to provide application
services externally. It is recommended to configure at least dual 1GbE
networks.
Migration network: Dedicated network for VM migrations. It is
recommended to configure a separate migration network. If no dedicated
migration network is configured, the system will use the management network
for VM migrations by default.
Note: To achieve high availability and avoid single-point failures, we
recommend ensuring the redundancy in switches, NICs, and other network
equipment.
Switch Connections
Note: The switch connection procedure may vary slightly across different ZStack Cube Ultimate models due to hardware configuration differences.
Proceed according to the specific hardware you use.
Configure switch ports based on your VLAN requirements:
Configure switch ports in Trunk mode for networks requiring VLAN
specification.
Configure switch ports in Access mode for networks not requiring VLAN
specification.
The following are recommended switch port modes for each network:
Management network: Access mode.
Business network: Trunk mode.
Storage Network: Access mode.
Figure 1. Network Topology
(Optional) Prepare Installation Package
The hyper-converged appliance comes with a pre-installed ISO, allowing you to skip the
installation package preparation. For software-only deployment or if you need to replace
the pre-installed ISO, follow the instructions in this section.
Obtain Installation Package
Obtain ZStack Cube Ultimate ISO.
ZStack Cube Ultimate ISO. ZStack Cube Ultimate provides multiple ISO versions, allowing you
to select and download the appropriate one based on your situation:
Bootstrap_Agent: Checks the
hyperconverged-bootstrap.service status.
Storage_path: Checks storage-related files.
License_path: Checks license-related files.
Serial_Number: Checks the machine serial number.
Data_Disk_Size: Checks the disk specification.
Figure 4. Self-Check
Note: If the self-check fails, a red error massage appears, indicating that
installation errors are detected. You can contact official technical support
for help.
Check the operating system version.
Log in to the server operating system and run bootstrap
version to check the system version.
Deploy ZStack Cube Ultimate
ZStack Cube Ultimate supports visualized deployment. Before the
deployment, you need configure a bootstrap IP and start the bootstrap_ui service.
Start bootstrap_ui service.
Log in to the management node system as root. The default password for
the root account is cube_password
Run bootstrap init_ui to configure a bootstrap IP and
start the bootstrap_ui service.
After you run the command, the system
automatically scans all NICs. Select one NIC on the
management/storage/other networks to start the bootstrap_ui service.
We recommend using a management network NIC to start the bootstrap
service.
# Step1: Choose Network Interface //Choose a NIC to configure bootstrap IP.
------------------------------------------------------------------------------------------------------
Please select an interface (enter the number)
# Step2: Network Configuration for Selected Interface
------------------------------------------------------------------------------------------------------
1) Enter IP Address (default: xxx.xx.xx.xxx) // We recommend using a management network IP.
2) Enter Subnet Mask (default: xxx.xxx.x.x)
3) Enter Gateway (leave blank if none)
4) Enter VLAN ID [1-4096] (leave blank if none)
# Step3: Confirm
------------------------------------------------------------------------------------------------------
Choose an option
1) Confirm configuration
2) Modify configuration
3) Exit without applying changes
Figure 5. Start bootstrap_ui Service
Enter bootstrap UI.
After starting the bootstrap_ui successfully, connect your
laptop to the business network switch. We recommend configuring your laptop
with an IP in the same subnet as the bootstrap_ui IP. For example, if the
bootstrap_ui IP is 172.26.30.242, you can set your laptop IP to
172.26.30.245.
Open a browser and navigate to the bootstrap
UI via http://bootstrap_ui_ip. On the displayed page, select one
deployment scenario:
New HCI Deployment: 0-1 implementation. You can choose this
option to deploy a new HCI environment.
Expansion & DR: Add new compute or backup nodes to an
existing HCI environment. You can choose this option to configure
operating systems and networks for the new nodes.
Figure 6. Select Deployment Scenario
New HCI Deployment
Build a new HCI environment, configuring compute and storage resources.
Discover Host
In this step, the system automatically scans hosts and displays
host information on the UI. Select three or more hosts for deployment.Figure 7. Discover Hosts
Note:
Select hosts with the same version for deployment or upgrade
hosts to a uniform version before the deployment.
Make sure that each selected host has at least one 10GbE NIC.
These NICs must be with identical names and in the UP
status.
Make sure that all selected hosts share identical disk
configurations. For example, either all hosts use exclusively
SSD disks or all hosts uniformly use mixed SSD and HDD
disks.
To detect any newly added hosts, click
Rescan in the upper-right
corner.
Network Configuration
In this step, configure the
management network, storage network, business network, and BMC network
according to your network planning.
Configure management network.Figure 8. Network Configuration | Management Network Set the following parameters:
NIC: Select one or two NICs with the same
speed to configure a bond.
Bond Mode: Select a bond mode.
Note:
The bond mode must match your switch
configuration:
If you configure a dynamic/static link
aggregation for the switch, select LACP
(mode4).
If you do not configure link aggregation,
select Active-Backup (mode1).
If you select only one NIC, only Active-Bakup
(mode1) is available.
IP Range: Set an IP range for the
management network.
Netmask: Set a netmask for the management
network.
Gateway: Specify the gateway
address.
VLAN ID: Optional.
Note: The corresponding switch port mode
decides whether you need to enter a VLAN ID.
Access mode: the network must be configured as a
NoVLAN network. In this scenario, leave
VLAN ID blank.
Trunk mode: the network must be configured as a VLAN
network. In this scenario, enter a VLAN ID
here.
Configuration Mode: Supports three
configuration modes.
Combined Public & Cluster
Network: Configure a network used as
both the public network and the cluster network.
NIC: Select one or two
10GbE NICs to configure a bond.
Bond Mode: By default,
supports LACP (mode4) and Active-Backup (mode1).
Recommended: Active-Backup (mode1).
Note: If you
select only one NIC, only Active-Backup mode is
available.
IP Range: Set an IP
range for the public & cluster network.
Netmask: Set a netmask
for the public & cluster network.
VLAN ID: Optional.
Note: The corresponding switch port mode
decides whether you need to enter a VLAN ID.
Access mode: the network must be configured as a
NoVLAN network. In this scenario, leave
VLAN ID blank.
Trunk mode: the network must be configured as a VLAN
network. In this scenario, enter a VLAN ID
here.
Separate Public & Cluster
Network: Deploy separate public and
cluster networks, each with independent NIC, bond
mode, IP range, netmask, and VLAN ID.
Reuse Management Network:
Reuse the management network as the public network
and cluster network. Any modifications on the
management network also apply to the storage
networks.
Note: Storage networks require 10GbE
NICs. You cannot reuse a management network
configured with 1GbE NICs as storage
networks.
(Optional) Configure business network.
Figure 10. Network Configuration | Business Network
Set the following parameters:
Configure Business Network: Choose
whether to configure the business network. The switch is
turned on by default.
NIC: Select one or two NICs with the
same speed to configure a bond.
Bond Mode: Select a bond mode.
Note:
The bond mode must match your switch
configuration:
If you configure a dynamic/static link
aggregation for the switch, select LACP
(mode4).
If you do not configure link aggregation,
select Active-Backup (mode1).
If you select only one NIC, only Active-Bakup
(mode1) is available.
IP Range: Set an IP range for the
business network.
Netmask: Set a netmask for the
business network.
VLAN ID: Optional.
Note: The corresponding switch port mode
decides whether you need to enter a VLAN ID.
Access mode: the network must be configured as a
NoVLAN network. In this scenario, leave
VLAN ID blank.
Trunk mode: the network must be configured as a VLAN
network. In this scenario, enter a VLAN ID
here.
(Optional) Configure BMC network.
Figure 11. Network Configuration | BMC Network
Set the following parameters:
Configure BMC Network: Choose whether
to configure BMC network for host IPMI remote connection and
management. If you choose to configure the BMC network, make
sure that hosts are mounted with BMC NICs.
IP Range: Set an IP range for the BMC
network.
Netmask: Set a netmask for the BMC
network.
Gateway: Enter the gateway
address.
Host System
In this step, bulk-configure host systems, including the hostname
and root password. You can also adjust the configurations for specific hosts
individually.Figure 12. Host System
Set the following parameters:
Hostname: Set a hostname and sequence number.
The system will automatically generate sequential hostnames for all
hosts.
Root Password: Set a root password. All hosts
will use the same password.
Confirm Root Password: Re-enter the root
password to confirm it.
Host Information: The section displays hosts'
SN, hostname, management IP, and storage IP. You can sort the hosts
by SN and adjust hostnames and IP addresses for specific hosts as needed.
Note:
If a host's management or storage IP is the bootstrap
IP, this IP cannot be modified.
If you reuse the management network as the storage
network, you can manually adjust the managment IP and
the storage IP is updated synchronously.
If you reuse the public network as the cluster network,
you can manually adjust the public IP and the cluster IP
is updated synchronously.
Management Configuration
In this step, configure management nodes, VIP, DNS
server, NTP server, and distributed storage for the HCI platform.
Figure 13. Management Configuration
Set the following parameters:
HCI Platform Configuration
Management Node: Select two hosts
with the same version as platform management nodes.
Management Node VIP: Set the
management node VIP.
DNS Server: Optional. Enter the DNS
server address to provide the domain name resoulution
service.
NTP Server: Enter the NTP server
address. You can use either an internal or external NTP
server. By default, an internal NTP server is used, which
means using a platform node as the time source. You can also
configure an external NTP server and enter its address
here.
Distributed Storage Configuration
Management Role: Select three hosts
to serve as the management & monitoring nodes for the
distributed storage system.
Replicas: Displays the replicas
count.
Deployment Mode: Determined by the
type of disks mounted to the hosts.
If all hosts use SSD disks, the deployment mode is
All-Flash Pool
If all hosts use mixed SSD and HDD disks, the
deployment mode is Hybrid Pool.
Cache Ratio: Set the cache disk to
data disk ratio.
If you use SATA SSD as cache disks, the recommended
ratio is 1:5.
If you use NVMe SSD as cache disks, the recommended
ratio is 1:8.
Storage System:
Select the distributed storage system you use.
Preview
This page displays all completed configurations. You can view them by
device or in bulk. After confirming the configurations, click
Next to begin deployment.Figure 14. Preview
Deployment
This page displays real-time deployment progress for each host and
allows you to view logs or export configurations as a CSV file.
Note: If
errors occur, click Retry Now to reinstall affected
hosts.
After the deployment succeeds, you are navigated to the Enter HCI
Platform page, where you can access ZStack Cube Ultimate
UI by clicking Enter HCI Platform.
Additional Information
ZStack Cube Ultimate provides a comprehensive command line
interface (CLI) to support advanced deployment operations, such as database
inspection and firewall configuration. You can run bootstrap -h
for all supported commands and their usage.
If you deploy a distributed storage of the ZStone type and modify the database
password of ZStack Cube Ultimate, log in to the ZStone management
nodes to run the following command to ensure the distributed storage work
properly. For ZStone with dual management nodes, execute the command on both
management nodes
respectively:
[root@localhost~]# /opt/zstone/bin/zstnctl db config update -p $PASSWORD // $PASSWORD indicates the new database password
Expansion & DR
Add new compute or backup nodes to an existing HCI environment for expansion or disaster
recovery.
Discover Host
In this step, the system automatically scans hosts and displays
host information on the UI. Select one or more hosts for deployment.Figure 15. Discover Host
Note:
Make sure that each selected host has a 10GbE NIC. These NICs
must be with identical names and in the UP status.
Make sure all selected hosts share identical disk
configurations. For example, all hosts use exclusively SSD disks
or use uniformly mixed SSD and HDD disks.
To detect any newly added hosts, click
Rescan in the upper-right
corner.
Network Configuration
In this step, configure the
management network, storage network, business network, and BMC network
according to your network planning.
Configure management network.Figure 16. Network Configuration | Management Network Set the following parameters:
NIC: Select one or two NICs with the same
speed to configure a bond.
Bond Mode: Select a bond mode.
Note:
The bond mode must match your switch
configuration:
If you configure a dynamic/static link
aggregation for the switch, select LACP
(mode4).
If you do not configure link aggregation,
select Active-Backup (mode1).
If you select only one NIC, only Active-Bakup
(mode1) is available.
IP Range: Set an IP range for the
management network.
Netmask: Set a netmask for the management
network.
Gateway: Specify the gateway
address.
VLAN ID: Optional.
Note: The corresponding switch port mode
decides whether you need to enter a VLAN ID.
Access mode: the network must be configured as a
NoVLAN network. In this scenario, leave
VLAN ID blank.
Trunk mode: the network must be configured as a VLAN
network. In this scenario, enter a VLAN ID
here.
Configuration Mode: Supports three
configuration modes.
Combined Public & Cluster
Network: Configure a network used as
both the public network and the cluster network.
NIC: Select one or two
10GbE NICs to configure a bond.
Bond Mode: By default,
supports LACP (mode4) and Active-Backup (mode1).
Recommended: Active-Backup (mode1).
Note: If you
select only one NIC, only Active-Backup mode is
available.
IP Range: Set an IP
range for the public & cluster network.
Netmask: Set a netmask
for the public & cluster network.
VLAN ID: Optional.
Note: The corresponding switch port mode
decides whether you need to enter a VLAN ID.
Access mode: the network must be configured as a
NoVLAN network. In this scenario, leave
VLAN ID blank.
Trunk mode: the network must be configured as a VLAN
network. In this scenario, enter a VLAN ID
here.
Separate Public & Cluster
Network: Deploy separate public and
cluster networks, each with independent NIC, bond
mode, IP range, netmask, and VLAN ID.
Reuse Management Network:
Reuse the management network as the public network
and cluster network. Any modifications on the
management network also apply to the storage
networks.
Note: Storage networks require 10GbE
NICs. You cannot reuse a management network
configured with 1GbE NICs as storage
networks.
(Optional) Configure business network.
Figure 18. Network Configuration | Business Network
Set the following parameters:
Configure Business Network: Choose
whether to configure the business network. The switch is turned
on by default.
NIC: Select one or two NICs with the same
speed to configure a bond.
Bond Mode: Select a bond mode.
Note:
The bond mode must match your switch
configuration:
If you configure dynamic/static link
aggregation for the switch, select LACP
(mode4).
If you do not configure link aggregation,
select Active-Backup (mode1).
If you select only one NIC, only Active-Bakup
(mode1) is available.
(Optional) Configure BMC network.
Figure 19. Network Configuration |BMC Network
Configure BMC Network: Choose whether
to configure BMC network for host IPMI remote connection and
management. If you choose to configure the BMC network, make
sure that hosts are mounted with BMC NICs.
IP Range: Set an IP range for the BMC
network.
Netmask: Set a netmask for the BMC
network.
Gateway: Enter the gateway
address.
Host System
In this step, bulk-configure host systems, including the hostname
and root password. You can also adjust the configurations for specific hosts
individually.Figure 20. Host System
Set the following parameters:
Hostname: Set a hostname and sequence number.
The system will automatically generate sequential hostnames for all
hosts.
Root Password: Set a root password. All hosts
will use the same password.
Confirm Root Password: Re-enter the root
password to confirm it.
Host Information: The section displays hosts'
SN, hostname, management IP, and storage IP. You can sort the hosts
by SN and adjust hostnames and IP addresses for specific hosts as needed.
Note:
If a host's management or storage IP is the bootstrap
IP, this IP cannot be modified.
If you reuse the management network as the storage
network, you can manually adjust the managment IP and
the storage IP is updated synchronously.
If you reuse the public network as the cluster network,
you can manually adjust the public IP and the cluster IP
is updated synchronously.
Preview
This page displays all completed configurations. You can view them by
device or in bulk. After confirming the configurations, click
Next to begin deployment.Figure 21. Preview
Deployment
This page displays real-time deployment progress for each host and
allows you to view logs or export configurations as a CSV file.
Note: If
errors occur, click Retry Now to reinstall affected
hosts.
Additional Information
ZStack Cube Ultimate provides a comprehensive command line interface (CLI) to
support advanced deployment operations, such as database inspection and firewall
configuration. You can run bootstrap -h for all supported commands and
their usage.
Automated Initialization
During the automated initialization, ZStack Cube Ultimate automatically
creates the following basic resources:
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.
Backup Storage: An image storage is a storage server that stores VM image
templates, including ISO image files.
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.
Instance Offering: An instance offering defines the number of vCPU cores,
memory size, network bandwidth, and other configuration settings of VM
instances.
Image: An image is a template file used to create a VM instance
or volume. Images are categorized into system images and volume
images.
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.
L3 Network: An L3 network includes IP ranges, gateway, DNS, and other network
configurations that are used by VM instances.
Note: If you do not configure a business network when deploying ZStack Cube Ultimate, the system does not automatically create L2 and L3
networks during the automated initialization and you need to manually create them.
For more information, see Create Network
When creating the above resources:
The system creates hosts, backup storage, and primary storage according to the
hardware information it scans.
The system creates multiple instance offerings:
Balanced Type: The CPU-to-memory ratio is 1:4, such as 1C4G, 2C8G,
4C16G, and 8C32G.
Compute-Enhanced Type: The CPU-to-memory ratio is 1:2, such as1C2G,
2C4G, 4C8G, and 8C16G.
Memory-Enhanced Type: The CPU-to-memory ratio is 1:8，such as 2C16G,
4C32G, 8C64G, 16C128G.
The system creates multiple disk offerings, including 20GB, 40GB, 100GB, 200GB,
and 500GB.
Note: If any resources fail to be created or added, click Retry
to reattempt the failed step and continue initialization.
Create Network
If you do not configure a business network when deploying ZStack Cube Ultimate, the system does not automatically create L2 and L3
networks during the automated initialization and you need to manually create them.
Create L2 Network
Set the following parameters:
Name: Enter a name for the L2 network.
Description: Optional. Enter a description for the L2
network.
Switch Type: Supported switch types include Linux
Bridge and OVS-DPDK.
Network Type: Choose a network type for the L2
network. Valid values: L2NoVlanNetwork, L2VlanNetwork.
L2NoVlanNetwork
If you do not need to use VLAN, select L2NoVlanNetwork.
If you select L2NoVlanNetwork, the switch port connected by
the specified NIC must be in the Access mode.
L2VlanNetwork
If you need to use VLAN on ZStack Cube Ultimate, select L2VlanNetwork.
If you select L2VlanNetwork, the switch port connected by
the specified NIC must be in the Trunk mode.
VLAN ID: Enter a VLAN ID that matches
the actual network configurations. Valid values: 1 to
4094.
Cluster: Display the the cluster to which the L2
network will be attached.
NIC Name: Select or enter an NIC
name for the L2 network. For example, em01.
Note: You can only select or
enter an NIC name shared across all hosts in the cluster.
Figure 22. Create L2 Network
Create L3 Network
Set the following parameters:
Name: Enter a name for the L3 network.
Description: Optional. Enter a description for the L3
network.
Network Type: The wizard supports only flat
network.
Network Range Method: Select a method to add a
network range for the L3 network. You can select IP Range or CIDR.
If you
select IP Range, you need to set the following parameters:
Start IP: Set a start IP address for the
network range, for example, 172.20.108.100.
End IP: Set an end IP address for the
network range, for example, 172.20.108.200.
Netmask: Set a netmask for the network
range, for example, 255.255.0.0.
Gateway: Set a gateway for the network
range, for example, 172.20.0.1.
DNS: Add a DNS server
to provide domain name resolution services for the L3 network.
You can specify 223.5.5.5, 8.8.8.8, or
114.114.114.114.
If you select CIDR, you need to set the following
parameters:
CIDR: Set a CIDR block for the L3
network, for example, 192.168.108.1/24.
Gateway: Set a gateway for the L3
network, for example, 192.168.108.1.
Note:
You can use the first or last IP address in the
specified CIDR block as the gateway.
If left blank, the first IP address in the specified
CIDR block is used as the gateway.
DNS: Add a DNS server to provide domain
name resolution services for the L3 network. You can specify
223.5.5.5, 8.8.8.8, or
114.114.114.114.
Figure 23. Create L3 Network
Now, the automated initialization is completed.
Platform Setting
ZStack Cube Ultimate presets the following global settings to recommended
values. After the initialization, if you need to modify theses settings, enter the
Global Setting page by clicking Settings > Platform Setting > Global Setting on the main menu of ZStack Cube Ultimate.
Setting
Preset Value
Description
Host Reserved Memory
16G (for OS） + OSD Count * 5G
Specify the reserved memory for hosts. Unit:
G/M/K/B. Recommended: 8G or more.
CPU Overcommit
4
Specify host CPU overcommit. This decides the count of vCPU
that can be allocated to VM instances.
Host CPU threads * CPU overcomnmit = Allocatable vCPUs.
An excessively low CPU overcommit may result in negative
available resources or a percentage greater than 100% in
resource statistics. Set an appropriate value.
Memory Overcommit
1.0
Specify host memory overcommit. This decides the virtual
memory size that can be allocated to VM instance.
An excessively low memory overcommit may result in negative
available resources or a percentage greater than 100% in
resource statistics. Set an appropriate value.
We recommend that you do not overcommit memory in a
production environment to prevent VM auto-shutdown and
unexpected host reboot caused by OOM.
Host Login Password Encrypted Storage
LocalEncryption
Specify an encryption policy for host passwords
stored in the database.
None: Do not encrypt host passwords.
LocalEncryption: Encrypt host passwords by using the
platform's native encryption feature.
Primary Storage Reserved Space
200G
Set reserved space on primary storage. Unit:
G/M/K/B.
Primary Storage Usage Threshold
0.8
Specify primary storage usage threshold to
prevent storage overutilization (especially in scenarios where
memory overcommit is enabled and excessive volume allocation may
cause storage overflow and VM crashes).
Primary Storage Overcommit
1.0
Specify primary storage overcommit. This decides virtual
storage space that can be allocated to VM instances.
Available virtual storage = Total storage - Total volume
size/overcommit - total snapshot size - total Imagecache
size - reserved space.
We recommend that you do not overcommit primary storage in a
production environment
Volume Space Preallocation Policy of Shared Block
Primary Storage
metadata
Valid values: none and metadata.
Change Host Online on Local Storage
true
Specify whether to allow online VM (using local
storage) migrations across hosts.
Reserved Storage Space of Backup Storage
200G
Specify the reserved space on backup
storage.
Temporary Image Auto Deletion
true
Specify whether to automatically delete temporary
images produced when cloning VM instance or recovering VMs/volumes
from backup data.
VM HA
true
Specifies whether to enable high availability for
VM instances. Default: true. If set to false, the high availability
feature is disabled globally for VM instances. Please proceed with
caution.
VM Cross-Cluster HA
true
Specifies whether to enable VM migration across
clusters to achieve high availability. Default: false. If set to
true, hosts across clusters can be detected to achieve VM high
availability. Before you enable this feature, make sure that
clusters are well connected.
CPU Mode
host-passthrough
Specifies whether to select the same CPU model as
the host for a VM instance.
none: the CPU model of VM instance is simulated via QEMU. In
this mode, the VM instance inherits necessary host CPU
features to a small degree. We recommend you select this
mode if you need to migrate your VM instance.
host-model: the CPU model of the VM instance is similar to
or same as that of the host, such as Intel Haswell CPU. In
this mode, the VM instance inherits many host CPU features.
You can select this mode if you need to migrate your VM
instance.
host-passthrough: the CPU model as well as CPU features of
the VM instance are the same as the CPU model and CPU
features of the host. For example, both the VM instance and
host support the extended page table extension, huge page,
and virtualization features. Compared with the none,
host-model, and Custom modes, VM instance in this mode has
the most CPU features. You can select this mode if your
business requires many features.
Custom (a specific CPU model): the CPU model of the VM
instance is set to the specified model.
Hyper-V Virtualization
true
Specify whether to enable VM Hyper-V
virtualization.
High Availability Policy
Force
Permissive: if a VM instance is in unknown state, the
management node does not migrate the VM instance and the
self fencer process that runs on the host does not stop the
VM instance.
Force: the management node migrates the VM instance to
another host once the HA conditions are met.
Support for Kernel AIO
true
Specify whether to enable kernel asynchronous I/O
in the QEMU storage driver.
Volume Snapshot Default Quota
5
Specify the volume snapshot quota for projects
and sub-accounts.
Extended Alarm Notification
true
Specifies whether to enable the extended alarm
notification feature. Default: false. If set to true, extended alarm
notifications can be displayed on the UI.
Monitoring Data Retention Period
3 Months
The retention period of locally retained
monitoring data. Unit: month. Valid values: 1 to 12.
Note: To achieve high availability and avoid single-point failures, we
recommend ensuring the redundancy in switches, NICs, and other network
equipment.
