• In a data center, a zone corresponds to an equipment room.
• A zone defines a visible boundary. Sub-resources within the same zone are visible mutually and can form a certain relationship. However, sub-resources within different zones are invisible mutually and cannot form mutual relationships.

• Zone isolation:

  Isolates physical sub-resources such as primary storage and hosts in different zones, ensuring stability and fault tolerance to the maximum extent.

  Reduces network delay and allows for faster access.

• Resource management:

  You can set a platform administrator for each zone. A platform administrator can manage one or more zones.

  The resources of each project can belong to only one zone.

• Global view:

  After you plan a zone, you can view all the resources in the zone on a dedicated dashboard. You can view the resource usage by KVM or vCenter.

When you plan a zone, note that:

1. Hosts in the same physical layer 2 broadcast domain must be in the same zone. These hosts can be grouped as one or more clusters.
2. A physical layer 2 broadcast domain cannot span multiple zones. Instead, it must be mapped as an L2 network in a single zone.
3. A primary storage cannot span multiple zones. Instead, it must be mapped as a primary storage in a single zone.
4. A data center can have multiple zones.
5. A zone can have one or more image storage attached.
   • Resources in a zone, such as a primary storage, can only access the image storage attached to the zone.
   • An image storage can be deleted from a zone. After the image storage is deleted, resources in the zone will not see the image storage any more.
   • If an image storage is no longer accessible to resources of a zone due to network typology changes in a data center, you can detach the image storage from this zone.
   • To better manage the relationship between image storage and zone, the UI specifies that an image storage can only be attached to one zone at a time. That is, an image storage that has been attached to a zone cannot be reattached to the other zone. When you add an image storage in the UI, the image storage will be automatically attached to the current zone. When you delete a zone, you will directly delete the image storage attached to the zone.

You can attach primary storage and L2 networks to or detach them from a cluster. The following diagram shows the relationship between cluster and primary storage, L2 network.

The following table lists the relationship between primary storage (PS) and image storage (BS).

With this method, you can specify an IP address or an IP range to add hosts. You can add up to 500 hosts at a time. To use this method, set the following parameters:

• Name: Enter a name for the host.

  The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

• Description: Optional. Enter a description for the host.
• Virtualization Technology: Select the hypervisor type of the server. You can select KVM or X-Dragon.
  • If the server applies the KVM virtualization technology, select KVM.
  • If the server applies the X-Dragon architecture, select X-Dragon.
• Tag: Optional. Attach one or more tags to the host.
• Cluster: Select the cluster where the host is located.
  Note:

  • Hosts that apply the KVM virtualization technology can be added only to KVM-based clusters.
  • You can enable network acceleration support for a KVM-based cluster. If you add a host to a cluster for which network acceleration support is enabled, note that:
    • If the L2 network associated with the cluster uses the Smart NIC network acceleration mode, the host must be attached with a smart NIC of the specified model.
  • Hosts of the X-Dragon architecture can be added only to X-Dragon-based clusters.
  • X-Dragon-based clusters do not support network acceleration support.
• Host Info: Configure the host information such as the host IP and SSH port according to your actual needs. You can configure the host information by entering an IP address or an IP range.
  • If you select the IP Address method, set the following parameters:
    • IP Address: Enter the IP address of the host.
    • SSH Port: Enter the SSH port of the host. Default: 22.
    • SSH Username: Enter the SSH user name of the host. Default: root. You can enter a user name according to your actual needs.
    • SSH Password: Enter an SSH password for the user name.
  • If you select the IP Range method, set the following parameters:
    • IP Range: Enter the planed IP range for the host.
    • SSH Port: Enter the SSH port for the host. Default: 22.
      Note: Make sure that all hosts in the specified IP range share the same SSH port.
    • SSH Username: Enter the user name of the host. Default: root. You can enter a user name according to your actual needs.
      Note: Make sure that all hosts in the specified IP range share the same user name.
    • SSH Password: Enter a password for the user name.
      Note: Make sure that all user name in the specified IP range share the same password.
• Scan Host IOMMU Setting: Optional. Choose whether to scan the IOMMU setting of the host. The IOMMU setting is used in scenarios such as peripheral device passthrough and virtualization. By default, the host IOMMU setting is not scanned.
  Note: If you choose to scan the host IOMMU setting, note the following:

  • Scanning the host IOMMU setting will traverse available GPU devices on the host and physical NICs that can be virtualized. Before you scan the setting, make sure that Intel VT-d or AMD IOMMU is enabled in the host BIOS.
  • Before you can use GPU passthrough, vGPU virtualization, and SR-IOV, scan the host IOMMU setting.
  • If you are scanning the host IOMMU setting for the first time, restart the host to make the setting take effect.
• Intel EPT Hardware Assist: Optional. Choose whether to enable Intel EPT hardware assist for Intel CPUs to improve the CPU performance. By default, Intel EPT hardware assist is enabled.
  Note:

  • If the CPU model of your Intel server is too old, you might fail to create VM instances or cannot open the console properly of the newly created VM instances. In this case, disable the Intel EPT hardware assist feature.
  • Disabling Intel EPT Hardware Assist will lower the VM performance.

With this method, download the CSV template file provided by the Cloud, fill in the host information according to the specified format, and upload the file. You can add hosts in bulk with this method. The procedures are as follows:

1. Download the configuration template.

   Click Download Template to download the configuration template file in CSV format.

   
   
   

2. Fill in the host information according to the specified format.

   The configuration template contains a header and a row of sample. You can delete or overwrite the sample as needed.

   Set the following parameters in the template:

   • Name: Enter a name for the host. If null, the Cloud allocates a name (HOST-host IP address) to the host by default.
   • Description: Optional. Enter a description for the host.
   • Cluster: Enter the UUID of the cluster where the host is located.
     Note: You can add only KVM-based clusters in the template.
   • Host IP: Enter an IP address or an IP range for the host.
     • IP Address: Enter the specified IP address of the host.
     • IP Range: Enter the specified IP range to bulk add hosts.
       Note:

       If you enter multiple IP ranges for the host, use commas (,) to separate the ranges. ^ means that the IP range is not included. For example,

       192.168.0.1-192.168.0.100,^192.168.0.3-192.168.0.5

   • Scan Host IOMMU Setting: Optional. Choose whether to scan the IOMMU setting of the host. The IOMMU setting is used in scenarios such as peripheral device passthrough and virtualization. By default, the host IOMMU setting is not scanned.
     Note: If you choose to scan the host IOMMU setting, note the following:

     • To enable this feature, enter YES, Yes, yes, Y, or y. To disable this feature, enter NO, No, no, N, or n. If null, this feature is disabled.
     • Before you can use GPU passthrough, vGPU virtualization, and SR-IOV, scan the host IOMMU setting.
     • Scanning the host IOMMU setting will traverse available GPU devices on the host and physical NICs that can be virtualized. Before you scan the setting, make sure that Intel VT-d or AMD IOMMU is enabled in the host BIOS.
     • If you are scanning the host IOMMU setting for the first time, restart the host to make the setting take effect.
   • Intel EPT Hardware Assist: Optional. Specify whether to enable Intel EPT hardware assist for Intel CPUs to improve the CPU performance.
     Note: When you set this parameter, note the following:

     • If you enter YES, Yes, yes, Y, or y, the Intel EPT hardware assist will be enabled. If you enter NO, No, no, N, or n, the Intel EPT hardware assist will be disabled. If null, this feature is disabled.
     • If the CPU model of your Intel server is too old, you might fail to create VM instances or cannot open the console properly of the newly created VM instances. In this case, disable the Intel EPT hardware assist feature.
     • Disabling Intel EPT Hardware Assist will lower the VM performance.
   • SSH Port: Enter the SSH port for the host. If null, the Cloud will use port 22 by default.
   • SSH User Name: Enter the SSH user name of the host.
   • SSH Password: Enter an SSH password for the user name.
3. Upload the configuration file.

   After you fill in the host information, verify that the grammar is correct, and then upload the file to the Cloud.

   
   
   

4. Add hosts by using the template.

   Click OK. Then, the Cloud add hosts according to the configuration file.

• NUMA: 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: 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. A pNUMA node mainly consists of pCPUs and local memory.
• vNUMA 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. A vNUMA node mainly consists of vCPUs and local memory.
• vNUMA 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.

The following describes the pNUMA topology of a host on ZStack Cloud:

• All pNUMA nodes of the host and the VM instances associated with each pNUMA node are displayed.
• Total Memory: The total amount of local memory that a pCPU can access from the pNUMA node where it resides.
• Free Memory: The amount of free local memory that a pCPU can access from the pNUMA node where it resides.
• Both the total memory and free memory are measured based on physical hardware resources.

• All hosts in a same cluster should be installed with QEMU of the same version. If you need to add a host with a QEMU version different from those of other hosts in the cluster, update the QEMU of the hosts in this cluster to the Cloud recommended version or create a new cluster to add this new host.
• To avoid function or security patch losses, we recommend that all hosts use QEMU of the recommended version.

ZStack Cloud monitors the QEMU versions of hosts in a cluster. When a part of the host use QEMU that is not of the Cloud recommended version, a prompt appears in the cluster details page to inform you to update the host QEMU version. You can view the QEMU version state of each host by clicking Check in the prompt. The QEMU state is displayed as To be Updated if it is not of the recommended version.

Updating host QEMU version mainly contains following steps:

1. Check the connection of Cloud services and hardware.
2. Set VM HA mode as None in Global Setting.
3. Query the host QEMU version.
4. Back up the database of the two management nodes.
5. Upload the latest ISO image to the two management nodes and update the local repo source.
6. Use CLI commands to updates QEMU version for hosts in the cluster.
7. Use CLI commands to query the update process and confirm that the update is successful.

• After the update, restart or migrate the VM instances, VPC vRouters, and LB instances on the hosts to make the update take effect.
• When the QEMU version of a VM instance, VPC vRouter, or LB instance is not consistent with that of the host it resides on, its QEMU state is displayed as To be Updated. You can restart or migrate the VM/VPC vRouter/LB Instance to update its QEMU version.

  
  
  

  
  
  

On the right side of the host details page, you can view a Hardware Status card, displaying the number and health state of hardware devices of the host.

• CPU: Displays the total CPU count and faulty CPU count (if any). Click the card, you can view the faulty CPU's series numbers.
• Memory: Displays the total memory count and faulty memory count (if any). Click the card, you can view the faulty memory slots.
• Disk: Displays the total disk count and faulty disk count (if any). Click the card, you can view the faulty disk slots.
• RAID Card: Displays the total RAID card count and faulty RAID card count (if any). Click the card, you can view the faulty RAID card target IDs.
• Power Supply Slot: Displays the total power supply slot count and faulty power supply slot count (if any). Click the card, you can view the faulty power supply slot names.
• Fan: Displays the total fan count and faulty fan count (if any). Click the card, you can view the faulty fan names.
• Temperature Sensor: Displays the total temperature sensor count and faulty temperature sensor count (if any). Click the card, you can view the faulty temperature sensor names.
• Physical GPU: Displays the total pGPU count and faulty pGPU count (if any). Click the card, you can view the faulty pGPU slots.
• vGPU: Displays the total vGPU count and faulty vGPU count (if any). Click the card, you can view the faulty vGPU names.

Set the following parameters:

• Zone: By default, the current zone is displayed.
• Name: Enter a name for the primary storage.

  The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

• Description: Optional. Enter a description for the primary storage.
• Type: Select LocalStorage.
  Note:

  • If you select LocalStorage, the Cloud uses the hard disks of each host as a primary storage. LocalStorage primary storage can work with ImageStore and SFTP image storage. The total capacity of a LocalStorage primary storage is the sum of each host directory capacity.
  • If you attach multiple LocalStorage primary storage, make sure that each LocalStorage primary storage is deployed on an exclusive logical volume or physical disk.
• Mount Path: Enter the directory for mounting the LocalStorage primary storage.
  Note:

  • If the directory you entered does not exist, the Cloud automatically creates one.
  • The following system directories cannot be used. Otherwise, the hosts might fail to work properly.
    • /
    • /dev
    • /proc
    • /sys
    • /usr/bin
    • /bin
• Cluster: Select a cluster to which the LocalStorage primary storage is attached.

Set the following parameters:

• Zone: By default, the current zone is displayed.
• Name: Enter a name for the primary storage.

  The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

• Description: Optional. Enter a description for the primary storage.
• Type: Select NFS.
  Note: If you select NFS, ZStack Cloud automatically mounts the same NFS shared directory on all hosts as a primary storage. NFS primary storage can work with ImageStore and SFTP image storage, and can automatically mount the directory on all hosts.
• Mount Path: Enter the shared directory of the NFS server.
  Note:

  • Format: NFS_Server_IP:/NFS_Share_folder. For example, 192.168.0.1:/nfs_root.
  • You need to set the access permissions of the corresponding directories on the NFS server in advance.
  • To ensure security control on the NFS server, we recommend that you configure corresponding security rules for access control.
  • You can check the shared directory of the NFS server by using the showmount -e command on NFS server in advance.
  • The following system directories cannot be used. Otherwise, the hosts might fail to work properly.
    • /
    • /dev
    • /proc
    • /sys
    • /usr/bin
    • /bin
• Mount Option: Optional. To add mount options, make sure that these options are supported by the NFS server.
  Note:

  • The options are separated by commas (,). For example, nfsvers=3,sec=sys,tcp,intr,timeo=5. The preceding example means that the NFS server version is 3, the standard UNIX authentication mechanism is used, TCP is used as the transmission protocol, an NFS call can be interrupted in case of an exception, and the timeout is 0.5 seconds (5/10).
  • To specify the mount options, you can refer to the content in the -o option of mount.
  • You can set the options according to the mount command on commonly used clients. If the configured options conflict with the NFS server, the server shall prevail.
• Storage Network: Enter the storage network specified for the shared storage. The storage network can be the management network of the management node.
  Note:

  • If you have a dedicated storage network, enter its CIDR.
  • We recommend that you plan an independent storage network in advance to avoid potential risks. If you do not have an independent storage network, enter the network address according to your actual needs.
  • The Cloud uses the storage network to check the health status of VM instances.
• Cluster: Select a cluster to which the NFS primary storage is attached.

The following uses MooseFS as an example to configure the primary storage:

• Download and install the client tool mfsmount of MooseFS, and create a directory as the mount node.
• Assuming that the IP address of the MooseFS Master Server is 172.20.12.19, create /mnt/mfs as the mount point, and use the mfsmount command to mount the MooseFS system.
• You can also use the mfssetgoal command to set the number of file copies to be saved as needed.

[root@localhost ~]#mkdir /mnt/mfs 
[root@localhost ~]#mfsmount /mnt/mfs -H 172.20.12.19
[root@localhost ~]#mkdir /mnt/mfs/zstack
[root@localhost ~]#mfssetgoal -r 2 /mnt/mfs/zstack/
#The preceding commands mount the files in the /mnt/mfs/zstack/ directory to 172.20.12.19, and save two copies to the MooseFS storage server.

To add a SMP primary storage, set the following parameters:

• Zone: By default, the current zone is displayed.
• Name: Enter a name for the primary storage.

  The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

• Description: Optional. Enter a description for the primary storage.
• Type: Select SharedMountPoint.
  Note:

  • For SMP primary storage, ZStack Cloud supports network shared storage provided by commonly used distributed file systems such as MooseFS, GlusterFS, OCFS2, and GFS2.
  • SMP primary storage can work with ImageStore and SFTP image storage.
• Mount Path: Enter the directory of the shared storage mounted by the host.
  Note:

  • The following system directories cannot be used. Otherwise, the hosts might fail to work properly.
    • /
    • /dev
    • /proc
    • /sys
    • /usr/bin
    • /bin
• Storage Network: Enter the storage network specified for the shared storage. The storage network can be the management network of the management node.
  Note:

  • If you have a dedicated storage network, enter its CIDR.
  • We recommend that you plan an independent storage network in advance to avoid potential risks. If you do not have an independent storage network, enter the network address according to your actual needs.
  • The Cloud uses the storage network to check the health status of VM instances.
• Cluster: Select a cluster to which the SMP primary storage is attached.

To add a Ceph primary storage, set the following parameters:

• Zone: By default, the current zone is displayed.
• Name: Enter a name for the primary storage.

  The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

• Description: Optional. Enter a description for the primary storage.
• Type: Select Ceph.
  Note: ZStack Cloud primary storage can work with the following Ceph editions:

  • Ceph open-source edition: Jewel series, Luminous series, and Nautilus series.
  • ZStack Ceph Enterprise: All released ZStack Ceph Enterprise. If you are concerned more about data security and I/O performance, ZStack Ceph Enterprise is recommended. For more information, contact our official technical support.
• Cephx: Optional. Determine whether to enable Ceph authentication.
  Note:

  • By default, Ceph authentication is enabled.
  • If the network of the storage node and the compute node is relatively safe, you can disable Cephx to avoid Ceph authentication failure.
  • Make sure that the key authentication of the Ceph storage is consistent with this option. If Cephx is not disabled for the Ceph storage, enabling Ceph authentication here may cause VM creation failure.
• Mon Node: Enter the IP address, SSH port, user name, and password of the Ceph monitor.
  • Management IP: Enter the IP address of the Ceph monitor.
  • SSH Port: Enter the SSH port of the Ceph monitor. Default: 22.
  • User Name: Enter the user name of the Ceph monitor.
  • Password: Enter the password of the Ceph monitor.

  You can click Add Mon Node to add more Ceph monitors.

• Image Cache Pool: Optional. Enter the name of an image cache storage pool.
  Note:

  • You can specify a storage pool for image caches. If you do not specify a storage pool, the Cloud creates one automatically.
  • If you specify a storage pool, make sure that a storage pool is already available in the Ceph cluster. Then you can specify the UUID of a storage pool.
• Data Volume Pool: Optional. Enter the name of a data volume storage pool.
  Note:

  • You can specify a storage pool for data volumes. If you do not specify a storage pool, the Cloud creates one automatically.
  • If you specify a storage pool, make sure that a storage pool is already available in the Ceph cluster. Then you can specify the UUID of a storage pool.
• Root Volume Pool: Optional. Enter the name of a root volume storage pool.
  Note:

  • You can specify a storage pool for root volumes. If you do not specify a storage pool, the Cloud creates one automatically.
  • If you specify a storage pool, make sure that a storage pool is already available in the Ceph cluster. Then you can specify the UUID of a storage pool.
• Storage Network: Enter the storage network specified for the shared storage. The storage network can be the management network of the management node.
  Note:

  • If you have a dedicated storage network, enter its CIDR.
  • We recommend that you plan an independent storage network in advance to avoid potential risks. If you do not have an independent storage network, enter the network address according to your actual needs.
  • The Cloud uses the storage network to check the health status of VM instances.
• Cold Migration Network: A network dedicated for VM cold migrations across Ceph primary storage. If not set, the system uses the management network for VM cold migrations across Ceph primary storage by default.
  Note: To avoid high workloads on the management network, we recommend that you set a Dedicated network for VM cold migrations and ensures the cold migration network connectivity between Ceph primary storage.
• Ceph Enterprise Access Token: Optional. If you add the access token, the ZStack Ceph Enterprise storage is managed by the token. Both elastic baremetal clusters and KVM clusters can use the token.
  Note:

  • Make sure that your ZStack Ceph Enterprise license is valid.
  • If you need to attach Ceph block storage volumes to elastic baremetal instances, add an Access Token in advance.
  • If you add an Access Token and use this Ceph primary storage to create an elastic baremetal instance (startup method: volume), the system automatically creates a block storage volume on the storage, which serves as the system volume of the instance.
• Cluster: Select a cluster to which the Ceph primary storage is attached.

Set the following parameters:

• Zone: By default, the current zone is displayed.
• Name: Enter a name for the primary storage.

  The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

• Description: Optional. Enter a description for the primary storage.
• Type: Select SharedBlock.
  Note:

  • SharedBlock primary storage uses LUN devices for storage and can work with ImageStore image storage.
  • You can add LUN devices online.
  • Currently, SharedBlock primary storage supports two shared access protocols: iSCSI, FC, and NVMe-oF.
• Default Storage Space Allocation Strategy: Select a storage space allocation strategy, including thick provisioning and thin provisioning.
  • Thick Provisioning: Allocates the required storage space in advance to provide sufficient storage capacities and to ensure storage performance.
  • Thin Provisioning: Allocates storage spaces as needed to achieve a higher storage utilization.
• Storage Network: Enter the storage network specified for the shared storage. The storage network can be the management network of the management node. You need to specify a storage network if you choose iSCSI or FC protocol.
  Note:

  • If you have a dedicated storage network, enter its CIDR.
  • We recommend that you plan an independent storage network in advance to avoid potential risks. If you do not have an independent storage network, enter the network address according to your actual needs.
  • The Cloud uses the storage network to check the health status of VM instances.
• Cluster: Select a cluster to which the SharedBlock primary storage is attached.
• LUN: Select one or more LUN devices as needed. Here you need to enter the disk unique identifier.
  Note:

  • LUNs are provided by iSCSI, FC, or NVMe storage. Make sure that the compute node is connected with the iSCSI, FC, or NVMe storage properly, and is added to the Cloud.
  • To use LUNs provided by an iSCSI storage, attach the iSCSI storage to the cluster you select for the primary storage in advance.
• Cleanse LUN: Optional. Determine whether to cleanse LUN devices. By default, LUN devices are not cleansed.
  • If you choose to cleanse LUN devices, the residual data, such as file systems, RAID, or signatures of partition tables in the LUN devices will be forced to clean up.
  • If data exists in your LUN devices, and you do not cleanse the devices, you will fail to add LUN devices or attach primary storage.
  • The LUN devices to be added cannot have partitions. Otherwise, you will fail to add the devices.

Set the following parameters:

• Zone: By default, the current zone is displayed.
• Name: Enter a name for the primary storage.

  The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

• Description: Optional. Enter a description for the primary storage.
• Type: Select Vhost.
  Note: Vhost primary storage uses vhost-user mode to connect with high-performance SSD distributed storage, and can work with ImageStore image storage.
• Vendor: Select the vendor of the Vhost storage. Currently, ZHPS and XEBS-XINFINI are supported
• Cluster: Optional. Select a cluster to which the Vhost primary storage is attached.
• Storage Device Info: Enter storage device information. The parameters that you need to set depend on the storage vendor.
  • If the vendor is ZHPS, set the following parameters:
    • IP Address: Enter the Vhost management IP address.
    • Port: Enter the port of the Vhost management IP address.
    • Username: Enter the username of the Vhost management IP address.
    • Password: Enter the password corresponding to the username.
    • Test Connection: Test the connectivity of the IP address and obtain the storage pool information.
    • Storage Pool: Specify a storage pool. Make sure that a storage pool is already available in the storage cluster.
  • If the vendor is XEBS-XINFINI, set the following parameters:
    • IP Address: Enter the Vhost management IP address and port. You can add multiple IP addresses. To ensure security, we recommend that you add 2 or more addresses.
    • Token: Enter the Vhost token.
    • Test Connection: Test the connectivity of the IP address and obtain the storage pool information.
    • Storage Pool: Specify a storage pool. Make sure that a storage pool is already available in the storage cluster.

Set the following parameters:

• Zone: By default, the current zone is displayed.
• Name: Enter a name for the primary storage.

  The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, spaces, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot begin or end with spaces.

• Description: Optional. Enter a description for the primary storage.
• Type: Select CBD.
• Cluster: Select a cluster to which the primary storage is attached.
• MDS Node:
  • MDS Node MN IP: Enter the management IP address of the MDS node.
  • SSH Port: Enter the port of the MDS management IP address. Default: 22.
  • Username: Enter the username.
  • Password: Enter the password corresponding to the username.
• Storage Pool: Click Get Pool and select pools here after creating the storage pool on the storage side in advance.

On the LUN tab, click the name of a LUN device. Then, the Resource Details page is displayed. You can view the path information of the LUN on associated hosts, including runtime name, path status, health status, and target identifier.

• You can specify a host to display the path information of the LUN on that host.

On the Create Block Storage Volume page, set the following parameters:

• Name: Enter a name for the block storage volume. The name must be 1~128 characters in length and can contain English letters, digits, and the following English characters -_. The name must start with an English letter.
• Description: Optional. Enter a description for the block storage volume.
• Quantity: Set the number of block storage volumes to be created.
• Size: Set the block storage volume size. Unit: MB/GB/TB. Valid values: 1MB~1024TB. Enter an integer.
• Primary Storage: Displays the name of the current Vhost primary storage.
• Elastic Baremetal Instance: Select an elastic baremetal instance that the block storage volume to be attached to. You can attach the block storage volume to elastic baremetal instances during or after the creation.
  Note: Attach the Vhost primary storage to the elastic baremetal cluster before you can attach its block storage volumes to this instance.
• Set QoS: Set QoS, including IOPS and bandwidth, for the block storage volume.
  • Maximum IOPS: The upper limit of the read/write times per second of the block storage volume. Valid values: 100~10000000. Default: Unlimited.
  • Maximum Bandwidth: The upper limit of the read/write speed of the block storage volume. Unit: MB/S and GB/S. Valid values: 10MB/S~100GB/S. Default: Unlimited.

The following lists the operation you can perform on a Vhost block storage volume.

The Cloud supports the following types of image storage:

1. ImageStore
   • Stores image files by means of image slices and supports incremental storage.
   • Allows you to create snapshots and images when VM instances are running or stopped.
   • Allows you to clone VM instances without data volumes when these VM instances are running, paused, or stopped.
   • Allows you to clone VM instances with data volumes when these VM instances are running, paused, or stopped, and with storage types of LocalStorage, NFS, SharedMountPoint (SMP), Ceph, or SharedBlock.
   • Supports image synchronization across ImageStore image storage on the same management node.
   • Allows you to obtain the existing image files under the URL path in the image storage.
2. Ceph
   • Stores image files by means of Ceph distributed block storage.
   • Allows you to create snapshots and images when VM instances are running or stopped.
   • Allows you to clone VM instances without data volumes when these VM instances are running, paused, or stopped.
   • Allows you to clone VM instances with data volumes when these VM instances are running, paused, or stopped, and with the storage type of Ceph.
   • Allows you to export images on the UI or image storage.
     • You can export images, copy exported image URLs, and download exported images on the UI.
     • You can also export images on an image storage.

       For example, assume that the image path you use is ceph://bak-t-c9923f9821bf45498fdf9cdfa1749943/61ece0adc7244b0cbd12dafbc5494f0c.

       Then, run the following command on the image storage:

       rbd export -p bak-t-c9923f9821bf45498fdf9cdfa1749943 --image 61ece0adc7244b0cbd12dafbc5494f0c --path /root/export-test.image
       
       # bak-t-c9923f9821bf45498fdf9cdfa1749943 is the name of the pool where the image resides.
       # 61ece0adc7244b0cbd12dafbc5494f0c is the name of the image.
       # /root/export-test.image is the name of the exported file.

3. AliyunEBS
   • Stores image by means of object storage.
   • Allows you to create snapshots and images when VM instances are running or stopped.
   • Allows you to clone VM instances without data volumes when these VM instances are running, paused, or stopped.
   • Does not allow you to clone VM instances with data volumes.
   • Allows you to export images on image storage. For more information, contact the official technical support.

The following table lists the relationship between primary storage (PS) and image storage (BS).

• When primary storage are LocalStorage, NFS, or SMP, the default type for image storage is ImageStore.
• When primary storage are NFS or SMP, you can manually mount the corresponding shared directories to the local directories of the corresponding image storage. In this regard, both primary storage and image storage can use the network shared storage.
• When primary storage is Ceph, you can use the primary storage in the same Ceph cluster as image storage. You can also use the ImageStore primary storage as image storage.
• When primary storage is SharedBlock, the default type for image storage is ImageStore.
• When primary storage is AliyunNAS, the default type for image storage is ImageStore.
• When primary storage is AliyunEBS, the default type for image storage is AliyunEBS.

Set the following parameters:

• Zone: By default, the current zone is displayed.
• Name: Enter a name for the image storage.
• Description: Optional. Enter a description for the image storage.
• Type: Select ImageStore.
• Image Storage IP: Enter an IP address for the ImageStore image storage.
• Mount Path: Enter the mount path of the storage to be mounted on the ImageStore image storage. For example, /cloud_bs
  Note:

  • We recommend that you mount a large-capacity storage for the directory, and enter the absolute path of the directory.
  • The following system directories cannot be used. Otherwise, the hosts might fail to work properly.
    • /
    • /dev/
    • /proc/
    • /sys/
    • /usr/bin
    • /bin
• Retrieve Existing Image: Optional. Choose whether to obtain existing images for the ImageStore image storage.
  Note:

  • You can obtain existing images from the mount path of the image storage.
  • Only ImageStore image storage allows you to Retrieve Existing Image.
• SSH Port: Set an SSH port for the image storage.
  Note: The port must be an integer. Default: 22.
• User Name: Use either the default user name (root) or enter a user name for the image storage.
• Password: Enter the password for the user name.
• Data Network: Optional. If you planned a dedicated network for data communication between the compute node and the image storage, enter its CIDR.
  Note:

  • If not set, the Cloud uses the management network by default.
  • If you planned a dedicated network for data communication between the compute node and the image storage, add it directly to the Cloud.
• Image Sync Network: Optional. Enter the CIDR of the image synchronization network.
  Note:

  • If not set, a management network will be used by default for image synchronization.
  • You can synchronize images between ImageStore image storage within the same management node.
  • If you deployed a dedicated network for image synchronization, add it directly to the Cloud.
  • Using a dedicated image synchronization network can avoid network congestion and improve transmission efficiencies.
  • If you set an image synchronization network for both a source ImageStore and a destination ImageStore image storage, only the image synchronization network of the destination ImageStore image storage works.

• Passes through an iSCSI or FC disk to a VM instance.
• Adds an iSCSI or FC disk as a shared block and takes the shared block as a Shared Block primary storage.

iSCSI storage:

• You can add a disk that is not attached to a VM instance as a Shared Block primary storage.
• A logical unit number (LUN) that is added as a primary storage cannot be used for other purposes.
• You can attach a disk that is not added as a primary storage to a VM instance.
• You can attach a disk to multiple VM instances or attach multiple disks to one VM instance.

FC storage:

• If a block device is not attached to a VM instance and the cluster where the block device resides is in normal state, you can add the block device as a Shared Block primary storage.
• A logical unit number (LUN) that is added as a primary storage cannot be used for other purposes.
• You can attach a block device that is not added as a primary storage to a VM instance.
• You can attach a block device to multiple VM instances or attach multiple block devices to one VM instance.

Storage device, interface, and protocol:

• Storage device: A hardware used for storing data. Hard disk drive (HDD) and solid state drive (SSD) are two common types of storage devices, featuring different form factors. Common HDD and SSD form factors are listed as follows:
  • HDD form factors: 2.5 inches and 3.5 inches.
  • SSD form factors: 2.5 inches, M.2, mSATA, and U.2.
• Interface: The connection that enables data transfer between storage devices and computer software. The interface specifications of storage devices differ from one another. Common HDD and SSD interfaces are listed as follows in decreasing order of transfer speed:
  • HDD interfaces: SAS (Serial Attached SCSI), SCSI, SATA (Serial ATA), and IDE.
  • SSD interfaces: PCIe, M.2, mSATA, and SATA III.
• Protocol: The interface specification for data transfer between a physical interface and computer software. Interfaces vary in their supported protocols. Common protocols are listed as follows:
  • AHCI (Advanced Host Controller Interface) protocol: A protocol for storage devices with SATA/M.2 interface. AHCI can be used for both HDD and SSD.
  • NVMe (Non-Volatile Memory Express) protocol: A protocol for storage devices with PCIe/M.2 interface. NVMe is specifically designed for SSD.

The NVMe storage uses NVMe SSDs to create storage arrays via NVMe-oF protocol, facilitating data transfer between storage devices and VM instances within a cluster.

• NVMe-oF (NVMe over Fabrics): An extension of the NVMe network protocol to the fabric, using Ethernet, Fiber Channel, RoCE, or InfiniBand. NVMe-oF enables all VM instances within a cluster to access NVMe storage at a high speed, improving the overall I/O performance of a cluster.
  ZStack Cloud NVMe storage supports the following two types of transports:

  • NVMe-oF using RDMA (NVMe-oF using Remote Direct Memory Access): This technology uses Remote Direct Memory Access (RDMA) to enable data exchange directly between two computers’ main memory. Since data exchange bypasses the processor, cache, and OS of either computer, this mechanism enables efficient data transfer with low-overhead costs. NVMe-oF using RDMA can be implemented in multiple ways, including RoCE (RDMA over Converged Ethernet), InfiniBand, and iWARP.
  • NVMe over FC (NVMe-oF using FC): This specification uses Fibre Channel (FC) protocol to enable data transfer between storage arrays and VM instances within a cluster.
  • NVMe of using TCP: This specification uses the standard TCP protocol to enable data transfer between storage arrays and VM instances within a cluster.

• Electronic trading: In electronic trading, the execution price is extremely time-sensitive. In other words, a few microseconds could result in a large price difference. Therefore, low end-to-end latency is required to avoid losses due to price changes in a short time and thus maintain competitiveness.
• Real-time analytics: In the field of fraud detection, marketing applications, or games that require response time in milliseconds or even microseconds, the capability of real-time analytics could define a company’s business value. Powerful real-time analytics requires the server to respond quickly with low latency. With this capability, users can resolve potential crises, grasp business opportunities, and eventually achieve business growth.

You can quickly get started with NVMe storage by following these steps:

1. Build an NVMe backend storage.
2. Log in to the Cloud and enter the NVMe Storage page where you can synchronize information of NVMe block devices.
3. On the Primary Storage page, click Add Primary Storage to add a SharedBlock primary storage using LUNs provided by NVMe SSD.
4. Create a VM instance with this SharedBlock primary storage.

Physical networks can be divided into the following categories:

• Management Network: A network used to manage physical resources on ZStack Cloud. The management nodes communicate with the hosts, primary storage, image storage, VPC vRouters, and LB instances (performance-dedicated) on the Cloud through the management network. If you deploy a management network, it can be automatically identified by ZStack Cloud.
  • The management networks you add in Resource Pool > Network Resource > Dedicated Network comply with the management network definition here.
  • The host IP addresses displayed on ZStack Cloud belong to the management network.
  • The host callback IP addresses belong to the management network.
• Storage Network: A network specified for storage services. ZStack Cloud uses a storage network to get the health status of VM instances. We recommend that you deploy a dedicated storage network to avoid possible risks.
• Business Network: A network that can be added as an L2/L3 network on and attached to VM instances on ZStack Cloud. A VM instance uses a business network to provide services.
• Backup Network: A network used to back up or recover local business data in a local backup scenario. You need to deploy a backup network if you use Backup Service.
• Migration Network: A network used for VM migrations on ZStack Cloud.

• The Physical Network page displays physical NIC ports (bonds and non-bonds) in fact. These NIC ports realize the network connections between hosts. You manage physical networks by managing these NIC ports.
• You can attach network-type tags to NIC ports according to your physical environment planning. Management network tags are attached to corresponding ports automatically by the system and other tags need to be attached by yourself.
  • If you add a management network in Resource Pool > Network Resource > Dedicated Network, the NIC port of the L2 network it belongs to is attached with a management network tag.
  • The NIC port of the network to which a host IP address belongs is attached with a management network tag.
  • The NIC port of the network to which a host callback IP address belongs is attached with a management network tag.
• You can add a custom network type to meet flexible needs.
• After you attach tags to corresponding NIC ports, you can view the flow monitoring of different network types, which help you master accurate network workloads more flexibly.

• By Cluster: the page displays physical NIC ports in a directory tree according to the clusters and hosts they belong to. You can specify a cluster or host to screen out the physical NIC ports you need.
• By Network Type: the page displays physical NIC ports by network types they belong to. The NIC ports attached with network-type tags are displayed under corresponding categories, including management network, storage network, business network, backup network, and migration network.

• Marking Method: Select a marking method. Valid values: Mark in Bulk and Mark Successively.
  If you choose Mark in Bulk, you can attach uniform network-type tags to multiple NIC ports from multiple hosts at one time. Set the following parameters:

  • Host: Select hosts that the NIC ports to be marked belong to. You can select more than one hosts here. Then, click Add Tag Configuration.
  • Physical NIC Port: Select the NIC ports to be marked. You can select more than one port.
    Note:

    • Select NIC ports that exist on each of the hosts you select. For example, to mark eth0, make sure that each of the hosts has a NIC port named eth0.
    • NIC ports that have had a network-type tag attached are not available here. To add or delete tags to/from these NIC ports, go to their action lists and click Modify Network Type.
  • VLAN ID: Optional. Select a VLAN subnet port slaving to the physical NIC port. If you select a VLAN ID here, the network-type tags are attached to the corresponding subnet port.
    Note:

    • You can select one or more VLAN ID at one time. If you select more than one physical NIC ports before, you can only select VLAN IDs that exist on each of the NIC ports. For example, to select VLAN ID 100, make sure that all physical NIC ports you select have this VLAN ID.
    • VLAN subnet ports that have had a network-type tag attached are not available here. To add or delete tags to/from them, go to their action lists and click Modify Network Type.
    • If you do not set this parameter, the network-type tags will be attached directly to the physical NIC ports you select before.
  • Physical Network Type: Select network-type tags. You can select more than one tags for a NIC port.
    Note: The management network tags are automatically attached to corresponding NIC ports by the system. You cannot add/delete a management network tag to/from a NIC port by yourself.
  If you choose Mark Successively, you can mark NIC ports one by on and attach tags to only one NIC port from one host at one time. Click Add Tag Configuration and set the following parameters:

  • Host: Select the host that the NIC port to be marked belongs to. One tag configuration supports one host.
  • Physical NIC Port: Select the NIC port to be marked. One tag configuration supports one NIC port.
    Note: NIC ports that have had a network-type tag attached are not available here. To add/delete tags to/from these NIC ports, go to their action lists and click Modify Network Type.
  • VLAN ID: Optional. Select a VLAN subnet port slaving to the NIC port. The network-type tags are attached to these subnet port only. You can select one or more VLAN ID at one time.
    Note:

    • VLAN subnet ports that have had a network-type tags attached are not available here. To add/delete tags to/from these ports, go to their action lists and click Modify Network Type.
    • If you do not set these parameter, the network-type tags will be attached to the physical NIC port you select before by default.
  • Physical Network Type: Select network-type tags. You can select more than one tags for a NIC port.
    Note: The management network tags are automatically attached to corresponding NIC ports by the system. You cannot add/delete a management network tag to/from a NIC port by yourself.

  After you finish a tag configuration, you can click Add Tag Configuration to mark next NIC port(s).

On the Physical Network Type page, click Modify Network Type. Then, the Modify Network Type is displayed. You can add/delete network-type tags to/from NIC ports on this page.

On the Physical Network page, click Manage Network Type. Then, the Manage Network Type page is displayed. You can add a custom network type, edit an existing custom network type, or delete a custom network type.

This chart displays the total host network IO data in the current zone. Two monitoring metrics are supported: Out IO and In IO.

• By default, this chart displays the out/in IO sum of all networks in the zone.
• You can specify one or more network types to make the chart display the IO data only of the networks of the specified type. To ensure the accuracy of the monitoring, we recommend that you attach network-type tags to corresponding NIC ports in advance.

This chart displays the NIC out/in data of all hosts in the cluster. Two monitoring metrics are supported: Transmit Rate and Receive Rate.

• By default, the chart displays the rate sum of all host NICs.
• You can specify one or more network types to make the chart displays the rate sum only of the NICs that belong to the networks of the specified types. To ensure the accuracy of the monitoring, we recommend that you attach network-type tags to corresponding NIC ports in advance.

Six monitoring metrics are supported: NIC Data Out Rate, NIC Data In Rate, NIC Packets Out Rate, NIC Packets In Rate, NIC Packets Out Discard Rate, NIC Packets In Discard Rate.

• You can specify one or more network types to make the chart display the monitoring data only of the NIC ports that belong to the networks of the specified types. To ensure the accuracy of the monitoring, we recommend that you attach network-type tags to corresponding NIC ports in advance.
• You can specify one or more NICs to make the chart display the monitoring data only of the specified NICs.