UI Configuration Method
The following sections delve into the HTTPS configuration on the Cloud. In the following sections, you will learn how to:
- Add a third-party certificate
- Add a system self-signed certificate
- Update certificate
- Switch back to HTTP to log in to the UI
Add a Third-Party Certificate
In this section, you will learn how to import a third-party certificate via the UI interface.
You will need the following resources or permissions to proceed with this section:
A latest ZStack Cloud environment.
A admin or platform administrator permission to configure certificates.
A valid certificate issued by the commercial CA.
Certificates and certificate chains are only supported in CRT or PEM format, and private keys are only supported in KEY or PEM format.
If your certificate does not meet the format requirements, please convert the format on your own.
Log in to ZStack Cloud.
Choose Settings > System and Security > Certificate Management.
On the Certificate Management page, click Add Certificate.
On the Import Certificate page, set the following parameters:
Import Mode: Choose Third-party Certificate.
Certificate Document: Upload or import a certificate.
- Only CRT and PEM formats are supported.
- The certificate content starts with
----BEGIN CERTIFICATE----and ends with----END CERTIFICATE----.
Private Key: Upload or import a private key.
- Only KEY and PEM formats are supported.
- The private key content starts with
----BEGIN (RSAIEC) PRIVATE KEY----and ends with----END (RSAIEC) PRIVATE KEY----.
Certificate Chain: Upload or import a certificate chain.
- Only CRT and PEM formats are supported.
- The certificate content starts with
----BEGIN CERTIFICATE----and ends with----END CERTIFICATE----.
HTTP Redirection: Optional. If enabled, requests are redirected by default from port 5000 of the HTTP address to port 5443 of the HTTPS address.
Review the configuration and click OK.
After the above operations, the Cloud platform will automatically refresh and you can access the UI via the HTTPS protocol.
After configuring the certificate, the system will establish a new session, and you will need to log in to the UI interface again.
Add a System Self-Signed Certificate
In this section, you will learn how to import a system self-signed certificate via the UI interface.
You will need the following resources or permissions to proceed with this section:
- A latest ZStack Cloud environment.
- A admin or platform administrator permission to configure certificates.
Log in to ZStack Cloud.
Choose Settings > System and Security > Certificate Management.
On the Certificate Management page, click Add Certificate.
On the Import Certificate page, set the following parameters:
Import Mode: Choose System Self-signed Certificate.
Duration: Specify a validation duration for the system self-signed certificate. Valid values: 3 months, 1 year, 3 years, 5 years, and 10 years. By default, 10 years is selected.
HTTP Redirection: Optional. If enabled, requests are redirected by default from port 5000 of the HTTP address to port 5443 of the HTTPS address.
Custom Certificate Information: Optional. If enabled, you can customize your self-signed certificate information.
Common Name: Optional. Set a common name. By default, the common name is localhost.
The input must be 1 to 64 characters in length and can contain letters, digits, and special characters. Supported special characters include ~`@#$%^&*()-_+={}[]|:;’<>.?/
Organization Name: Optional. Set a name for your organization. By default, the organization name is localhost.
The input must be 1 to 64 characters in length and can contain letters, digits, and special characters. Supported special characters include ~`@#$%^&*()-_+={}[]|:;’<>.?/
Organization Unit Name: Optional. Set a name for your organization unit.
The input must be 1 to 64 characters in length and can contain letters, digits, and special characters. Supported special characters include ~`@#$%^&*()-_+={}[]|:;’<>.?/
Country/Region Name: The country/region name can only be set as CN.
State/Province Name: Optional. Set the state or province name.
The input must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, and special characters. Supported special characters include ~`@#$%^&*()-_+={}[]|:;’<>.?/
Locality Name: Optional. Set a city name.
The input must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, and special characters. Supported special characters include ~`@#$%^&*()-_+={}[]|:;’<>.?/
Email Address: Optional. Set an email address.
Review the configuration and click OK.
After the above operations, the Cloud platform will automatically refresh and the UI can be accessed via the HTTPS protocol.
After configuring the certificate, the system will establish a new session, and you will need to log in to the UI interface again.
Update Certificate
In this section, you will learn how to how to update a certificate via the UI interface.
You will need the following resources or permissions to proceed with this section:
- A latest ZStack Cloud environment.
- A admin or platform administrator permission to configure certificates.
- The added certificate has changed and requires updates.
Log in to ZStack Cloud.
Choose Settings > System and Security > Certificate Management.
On the Certificate Management page, click Update Certificate
Review the configuration and click OK to update the certificate.
The system will detect the current certificate path and write the certificate information to that path when updating the certificate.
Switch back to HTTP to Log in to the UI
In this section, you will learn how to switch back to HTTP to log in to the UI .
You will need the following resources or permissions to proceed with this section:
- A latest ZStack Cloud environment.
- A admin or platform administrator permission to configure certificates.
- The user has configured the SSL certificate.
Log in to ZStack Cloud.
Choose Settings > System and Security > Certificate Management.
On the Certificate Management page, Click Switch back to HTTP.
In the confirmation pop-up, Click OK to switch back to HTTP to login in to the UI.
The session is reestablished after you switch back to HTTP. You need to log in to the UI again. You can then log in to the UI via HTTP protocol after switching back to HTTP.
Command-line Configuration Method
The following sections will introduce the command line configuration method of HTTPS login to UI in two scenarios of single management node and multi-management node.
- HTTPS mode is disabled by default.
- After enabling HTTPS, the system supports port 5443 by default and you can specify other ports for login.
- When HTTPS is enabled, if you log in to the Cloud on port 5000 using HTTP, the login page will be automatically redirected to HTTPS. Currently, only HTTP port 5000 is supported for automatic redirection to HTTPS.
- The system supports PKCS12 format certificates by default. Currently, only PKCS12/JKS format certificate is supported. If you use certificates in other formats, please convert the format yourself.
Single Management Node Scenario
This section primarily focuses on scenarios involving a single management node and you will learn:
- How to log in to the UI using the default HTTPS method
- How to log in to the UI with a custom HTTPS configuration
- How to switch back to HTTP for UI login
Log in to UI Using Default HTTPS Method
By default, the Cloud supports HTTPS login to the UI with a system default certificate.
Stop the management node service and UI service by running the following commands on the management node.
zstack-ctl stopMake sure that the VNC console supports the HTTPS feature.
Run the following command to view the certificate path and the private key password (which are both initially set to system default values).
zstack-ctl show_ui_configExample:
[root@localhost ~]# zstack-ctl show_ui_config db_url = jdbc:mysql://10.0.233.184:3306 db_username = zstack_ui db_password = zstack.ui.password mn_host = 127.0.0.1 mn_port = 8080 webhook_host = 127.0.0.1 webhook_port = 5000 server_port = 5000 log = /usr/local/zstack/apache-tomcat/logs enable_ssl = false ssl_keyalias = zstackui ssl_keystore = /usr/local/zstack/zstack-ui/ui.keystore.p12 //certificate path ssl_keystore_type = PKCS12 ssl_keystore_password = password //private key passwordBy default, the UI supports PKCS12 formatted certificates, whereas the VNC console proxy supports x509 formatted certificates. If you want to use the UI certificate for the VNC console proxy as well, you need to convert the PKCS12 formatted certificate into x509 format.
openssl pkcs12 -in /path/to/mykeystore.p12 -out ui.keystore.pem -nodesIn this command,
/path/to/mykeystore.p12is the PKCS12 formatted certificate andui.keystore.pemis the converted x509 formatted certificate.Example:
[root@localhost ~]# openssl pkcs12 -in /usr/local/zstack/zstack-ui/ui.keystore.p12 -out ui.keystore.pem -nodes Enter Import Password: MAC verified OKEdit the zstack.properties configuration file in
/usr/local/zstack/apache-tomcat/webapps/zstack/WEB-INF/classes/zstack.properties, and set the certificate path to an absolute path (pointing to the certificate private key password file).consoleProxyCertFile = /usr/local/zstack/zstack-ui/ui.keystore.pem
Run the following command to automatically generate a certificate based on the default configuration and log in to the UI using HTTPS with the default certificate. The default port is 5443.
zstack-ctl config_ui --enable-ssl TrueRun the following command on the management node to enable the management node service and UI service.
zstack-ctl startTo access the ZStack Cloud management interface (https://your_domain_name:5443), use a Chrome or Firefox browser. Enter the default username and password (admin/password) to log in to the UI via HTTPS.
Set the console proxy address.
Log in to the UI interface, on the main menu of ZStack Cloud, choose Operational Management > Access Control > Console Proxy and set the console proxy as your_domain_name to make sure the console opens properly.
Log in to UI with Custom HTTPS Configuration
By default, the Cloud supports logging in to the UI using HTTPS with the custom certificate.
A custom certificate is required. You can generate a system self-signed certificate using related tools or purchase a certificate issued by a commercial CA.
You can use Keytool (a Java data certificate management tool) to generate a self-signed certificate.
mkdir certs keytool -genkey -alias tomcat -storetype PKCS12 -keyalg RSA -keysize 2048 -keystore ./certs/keystore.p12 -validity 365Example:
[root@localhost ~]# mkdir certs [root@localhost ~]# keytool -genkey -alias tomcat -storetype PKCS12 -keyalg RSA -keysize 2048 \ -keystore ./certs/keystore.p12 -validity 365 Enter keystore password: Re-enter new password: What is your first and last name? [Unknown]: Jack Chen What is the name of your organizational unit? [Unknown]: ZStack What is the name of your organization? [Unknown]: DOC What is the name of your City or Locality? [Unknown]: SH What is the name of your State or Province? [Unknown]: SH What is the two-letter country code for this organizational unit? [Unknown]: CN Is CN=Jack Chen, OU=Cloud, O=DOC, L=SH, ST=SH, C=CN correct? [No]: Yes [root@localhost certs]# ls keystore.p12On the management node, run following command to stop the management node service and the UI service.
zstack-ctl stopEnsure that the VNC console proxy supports HTTPS.
The VNC console proxy supports x509 formatted certificates by default. You can convert the certificate format if needed.
For example, you can convert a PKCS12 formatted certificate into x509 format.
openssl pkcs12 -in /path/to/mykeystore.p12 -out ui.keystore.pem -nodesIn this command,
/path/to/mykeystore.p12is the PKCS12 formatted certificate andui.keystore.pemis the converted x509 formatted certificate.Example:
[root@localhost ~]# openssl pkcs12 -in /root/certs/keystore.p12 -out ui.keystore.pem -nodes Enter Import Password: MAC verified OKModify the zstack.properties configuration file. Set the certificate path to an absolute path (the absolute path points to the certificate private key password file).
consoleProxyCertFile = /usr/local/zstack/zstack-ui/ui.keystore.pem
Run following command to customize certificate alias, certificate path, certificate type, private key password, HTTPS login port, and other information. Then log in to the UI via HTTPS using the custom certificate.
zstack-ctl config_ui --enable-ssl True \ --ssl-keyalias=*** --ssl-keystore=*** --ssl-keystore-type=*** \ --ssl-keystore-password=*** --server-port=*** --webhook-port=*** //Record the custom parameter information in the zstack.ui.properties configuration file. //Including settings for: enabling HTTPS, certificate alias, certificate path, certificate type, private key password, HTTPS login port. zstack-ctl show_ui_config //View the custom parameter information zstack-ctl stop_ui zstack-ctl start_ui //Log in to the UI via HTTPS each timeExample:
[root@localhost ~]# zstack-ctl config_ui --enable-ssl True \ --ssl-keyalias=tomcat --ssl-keystore=/root/certs/keystore.p12 --ssl-keystore-type=PKCS12 \ --ssl-keystore-password=password --server-port=8888 [root@localhost ~]# zstack-ctl show_ui_config db_url = jdbc:mysql://10.0.233.184:3306 db_username = zstack_ui db_password = zstack.ui.password mn_host = 127.0.0.1 mn_port = 8080 webhook_host = 127.0.0.1 webhook_port = 5000 server_port = 8888 log = /usr/local/zstack/apache-tomcat/logs enable_ssl = true ssl_keyalias = tomcat ssl_keystore = /usr/local/zstack/zstack-ui/ui.keystore.p12.cp ssl_keystore_type = PKCS12 ssl_keystore_password = password [root@localhost ~]# zstack-ctl stop_ui successfully stopped the UI server [root@localhost ~]# zstack-ctl start_ui successfully started UI server on the local host, PID[32166], https://10.0.233.184:8888On the management node, run following command to start the management node service and the UI service.
zstack-ctl startEnter the ZStack Cloud management interface (https://your_domain_name:your_server_port) using a Chrome or Firefox browser. Enter the default username and password (admin/password) to log in via custom HTTPS.
If you encounter issues with accessing VNC console using Firefox browser, follow these steps:
- Access https://your_domain_name:4900 using Firefox browser.
- Follow the prompts from the Firefox browser and add https://your_domain_name:4900 to the security exceptions.
- Open the VNC console using the Firefox browser.
For more information, see Firefox.
Set the console proxy address.
Log in to the UI interface, on the main menu of ZStack Cloud, choose Operational Management > Access Control > Console Proxy and set the console proxy to your_domain_name to make sure the console opens properly.
Switch Back to HTTP for UI Login
Run the following command to restore the HTTPS related parameters in the zstack.ui.properties to the system default values.
zstack-ctl config_ui --restoreRun
zstack-ctl stop_uiandzstack-ctl start_ui.Example:
[root@localhost ~]# zstack-ctl config_ui --restore [root@localhost ~]# zstack-ctl show_ui_config db_url = jdbc:mysql://10.0.233.184:3306 db_username = zstack_ui db_password = zstack.ui.password mn_host = 127.0.0.1 mn_port = 8080 webhook_host = 127.0.0.1 webhook_port = 5000 server_port = 5000 log = /usr/local/zstack/apache-tomcat/logs enable_ssl = false ssl_keyalias = zstackui ssl_keystore = /usr/local/zstack/zstack-ui/ui.keystore.p12 ssl_keystore_type = PKCS12 ssl_keystore_password = password [root@localhost ~]# zstack-ctl stop_ui successfully stopped the UI server [root@localhost ~]# zstack-ctl start_ui successfully started UI server on the local host, PID[43261], http://10.0.233.184:5000Enter the ZStack Cloud management interface (https://your_domain_name:your_server_port) using a Chrome or Firefox browser. Enter the default username and password (admin/password). Then, you can switch back to HTTP for UI login.
Set the console proxy address.
Log in to the UI interface, on the main menu of ZStack Cloud, choose Operational Management > Access Control > Console Proxy and set the console proxy to your_domain_name to make sure the console opens properly.
Now, you have learned how to log in to the UI interface via HTTPS.
Multiple Management Nodes Scenario
This section primarily focuses on scenarios involving multiple management nodes and you will learn:
- How to log in to the UI with custom HTTPS configuration
- How to switch back to HTTP for UI login
Log in to UI with Custom HTTPS Configuration
Under a dual management node scenario, you can log in to the UI using HTTPS with the custom certificate.
Prepare a multi-domain HTTPS certificate.
- Prepare a multi-domain HTTPS certificate in advance, for example, **.test.com*.
- Bind each of the two management nodes and the VIP to a domain, for example, mna.test.com (management nodeA), mnb.test.com (management nodeB), and mn.test.com (VIP).
Run the following command on both management nodes to stop the management service, UI service, and the zsha2service.
[root@localhost ~]# zsha2 stop-nodeEnsure the VNC console supports HTTPS.
Both management nodes must ensure the VNC console supports HTTPS. For more information, see Step 3.
Configure the parameters.
Customize the certificate alias, certificate path, certificate type, private key password, HTTPS login port, and other information on both management nodes. Then, log in to the UI via HTTPS using the custom certificate. For more information, see Step 4.
Run the following command on both management nodes to start the management node service, UI service, and the zsha2 service.
[root@localhost ~]# zsha2 start-nodeUse a custom certificate to log in to the UI via HTTPS.
Enter the ZStack Cloud management interface (https://your_domain_name:your_server_port) using a Chrome or Firefox browser. Enter the default username and password (admin/password) to log in via custom HTTPS.
If you encounter issues with accessing VNC console using Firefox browser, follow these steps:
- Access https://your_domain_name:4900 using Firefox browser.
- Follow the prompts from the Firefox browser and add https://your_domain_name:4900 to the security exceptions.
- Open the VNC console using the Firefox browser.
For more information, see Firefox.
Set the console proxy address.
Log in to the UI interface, on the main menu of ZStack Cloud, choose Operational Management > Access Control > Console Proxy. Set the console proxy to your_domain_name, for example, mna.test.com (management nodeA) and mnb.test.com (management nodeB) to make sure the console opens properly.
Switch Back to HTTP for UI Login
Under a dual management node scenario, you can restore the default HTTP method to log in to the UI.
Run the following command on both management nodes to stop the management service, UI service, and the zsha2service.
[root@localhost ~]# zsha2 stop-nodeDisable the HTTPS feature.
Run the following command on each of the two management nodes to restore the HTTPS related parameters in the zstack.ui.properties to their system default values.
[root@localhost ~]# zstack-ctl config_ui --restoreReconfigure webhook-host.
Run the following command on each of the two management nodes to configure the webhook-host address to the VIP address of the dual management nodes.
[root@localhost ~]# zstack-ctl config_ui --webhook-host VIPRun the following command on both management nodes to start the management node service, UI service, and the zsha2 service.
[root@localhost ~]# zsha2 start-nodeLog in to the UI interface via HTTP
Enter the ZStack Cloud management interface (http://your_machine_ip:5000) using a Chrome or Firefox browser. Enter the default username and password (admin/password). Then, you can switch back to HTTP for UI login.
Set the console proxy address.
Log in to the UI interface, on the main menu of ZStack Cloud, choose Operational Management > Access Control > Console Proxy and set the console proxy to your_machine_ip to make sure the console opens properly.
Now, you have learned how to log in to the UI interface via HTTPS under a dual management nodes scenario.
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.
