Configure system parameters

Perform this task to configure the global parameters of CVM.

System parameters include the following:

• Basic System Parameters—Configure basic parameters of CVM.

• Customization Parameters—Configure CVM interface customization parameters.

• Customized Menu Parameters—Configure the customized menu parameters used to access other systems.

• VNC Proxy Server Parameters—Configure VNC proxy server parameters.

Virtual Network Computing (VNC) enables you to remotely control another computer. It transmits the remote computer screen to the local over the network. VNC consists of VNC clients and VNC servers. The VM consoles in CVM are VNC clients and VMs on the hosts are VNC servers. Operators might access the VMs within the data center from an external network. As a best practice to ensure data security, specify a VNC proxy server for the VMs. The VNC proxy server is the only node that the data center exposes to external networks. The external network can communicate with VMs within the data center only through the VNC proxy server.

• HA Parameters—Configure the host heartbeat interval and the storage heartbeat interval. The host heartbeat and storage heartbeat enables CVM to manage hosts, monitor HA resources, detect failed hosts and VMs in the cluster, and migrate VMs to available hosts.

• Image Clean Up—Set the resource usage thresholds for cached images saved in /vms/nova, for example, cached images for interoperation with CloudOS and native OpenStack. The system will clean up cached images that exceed the usage thresholds automatically.

• CPU and Memory Parameters—Set the maximum VM CPU and memory allocation ratios for each host. The system no longer creates VMs on a host if one of the ratio is reached.

Procedure

1. On the top navigation bar, click System.

2. From the left navigation pane, select Parameters.

3. Click the System Parameters tab.

4. Configure basic system parameters, customization parameters, customized menu parameters, VNC proxy server parameters, and HA parameters as described in "Parameters."

5. Click Save.

Parameters

Basic System Parameters

• Idle Timeout: Specify the idle timeout for the operators. An operator automatically logs off of the system when the idle timeout expires.

• Lockout Period: Specify the time period during which the IP address that an operator uses to access the system is forbidden from logging in to the system. The timer starts for an operator's IP address after the operator fails to log in to the system consecutively for the specified times.

• Max Login Attempts: Specify the maximum number of allowable consecutive login failures. If an operator fails to log in to the system for the specified times, the operator's IP address cannot log in to the system within the specified time period.

• Max Online Operators: Specify the maximum number of online operators. 0 indicates that the number of online operators is not limited.

• Log Level: Select a log level. Options include Error, Warning, and Tip.

• Monitor Refresh Interval: Select the refresh interval for the monitoring information about hosts and VMs. Options include 30 sec, 1 min, 5 min, and 10 min.

• Alarm Lifetime: Specify the lifetime period of alarms.

• Recycled VM Lifetime: Specify the lifetime period of VMs in the recycle bin. The system automatically deletes a VM in the recycle bin after the lifetime period of the VM expires. The value of 0 indicates that VMs in the recycle bin will not be automatically deleted.

• Monitor Data Lifetime: Specify the lifetime period of the performance monitoring data.

• Migration Timeout: Specify the migration timeout period. If the system fails to migrate a running VM when the migration timeout period expires, the system will suspend the VM to speed up the migration. After the VM is successfully migrated, the system will resume the VM.

• Monitoring Data Polling Interval: Select the interval at which the system collects the CPU, memory, disk, and network performance data of hosts and VMs. After you select an interval, the performance monitoring pages display performance monitoring data collected at this interval.

• Animation Effects: Select whether to enable animation effects for the navigation tree.

• Secure Mode: Select whether to enable the secure mode or not. You can enable secure mode only after you enable Mandatory HTTPS. After you enable the secure mode, the following restrictions take effect:

• A storage volume can be used by only one VM.

• The login names of operators cannot be modified.

• An operator account can be used by only one user at a time.

• Users can access CAS only through HTTPS.

If the security zone is configured, you cannot disable the secure mode. The security zone, secrecy policy, and security service workflows are available only when secure mode is enabled. If secure mode is disabled, those features are unavailable.

For a VM to access the VNC console, you must specify a VNC proxy server when the secure mode or mandatory HTTPS mode is enabled.

 

• Mandatory HTTPS: When secure mode is enabled, you can select whether to enable mandatory HTTPS mode. When this mode is enabled, you can access CVM only through HTTPS. To avoid task failure, do not edit this parameter when other tasks are running in the system.

• Shared Storage Fault Action: Select the action to take when the shared storage of a host fails. Options include Restart Host and Do Not Restart Host. To avoid shared storage volume unmounting error, you must enable cluster HA if you select Do Not Restart Host.

• VM IPv6 Address Management: Select whether to enable IPv6 configuration for VMs. If you select Yes, you can configure IPv6 addresses for VMs when you add, Edit, or clone VMs, or deploy VMs through templates. When you view information about a VM, its IPv6 address is displayed.

• Temporary File Directory: Enter a temporary directory for uploaded and downloaded files.

• Root SSH Login Permission: Set whether to enable root SSH login permission on CVK hosts.

• If you enable this feature, operators can only add CVK hosts by using username root.

• If you disable this feature, operators can only add or log in to CVK hosts through SSH by using username sysadmin. The default password of user sysadmin is Sys@1234.

Changing the state of root SSH login permission switches the account used for login on all hosts managed by the system. When the system prompts for a password, enter the password of the correct account. If you have forgotten the password, you can enter a new password directly.

 

• Operation Log Lifetime: Specify the time period within which operation logs cannot be deleted.

• Migration Pause Period: Set the VM pause period for migrating the remaining dirty pages before online migration is completed. As a best practice, do not set this parameter.

• Change VNC Console Password: Select whether to edit the VNC console password.

• VNC Console Password: Specify the password used to connect to the VNC consoles of VMs. This password takes effect only on VMs that are created after the password configuration. To change the VNC console password of a specific VM, access the VM editing page.

• VNC Password: Select whether to use VNC random password for the VMs. After you enable this feature, the configured VNC passwords become invalid.

• Max Client Connection: Specify the maximum number of connections that an IP address can establish to CVM.

• Intel RDT Noisy Neighbor Quieting: Select whether to enable Intel RDT noisy neighbor quieting. After you enable this feature on the system parameter configuration page, you can enable this feature for a VM on the VM editing page. To enable Intel RDT noisy neighbor quieting for a VM, make sure the physical CPUs on the host where the VM resides support this feature.

• Encoding Mode: Select the encoding mode that the hosts use to report alarms to the alarm server. Options include BASE64, GBK, and UTF-8.

• Max External Snapshots: Specify the maximum number of external snapshots that can be stored for a VM.

• Shared Storage Overcommitment Limit: Select whether to enable shared storage overcommitment limit. With this feature disabled, shared storage overcommitment is not limited. As a best practice, enable this feature for critical services. With this feature enabled, you can set the shared storage overcommitment ratio. If you do not enable this feature, monitor the shared storage pool usage. When the shared storage pool usage is high, scale up the pool or delete unnecessary files to avoid read/write service interruption.

• Shared Storage Overcommitment Ratio: Set the shared storage overcommitment ratio. If you set the value of this parameter to 0, shared storage resources cannot be overcommitted, and the maximum capacity that can be allocated is equivalent to the actual shared storage capacity. If you set the value of this parameter to n, the maximum capacity that can be allocated is n+1 times the actual shared storage capacity. This parameter is configurable only when shared storage overcommitment limit is enabled. As a best practice, do not set an excessively high shared storage overcommitment ratio and monitor the shared storage pool usage. When the shared storage pool usage is high, scale up the pool or delete unnecessary files to avoid read/write service interruption.

• Storage Pool Level-2 Directory: Enable the system to create level-2 directories for VMs in storage pools.

• With this feature enabled, the system automatically creates a level-2 directory named VM name_dir in the root directory of a storage pool to store a VM image file when you perform an operation that creates the VM image file, such as deploying a VM.

• With this feature disabled, the system does not create level-2 directories in storage pools, and existing level-2 directories are still available for use.

• DRS VM Startup: Set the state of DRS VM startup. With this function enabled, the system checks whether a host meets the VM startup requirements before starting up a VM on the host. If the requirements are not met, the system migrates the VM to the optimal host to start up. This function takes effect only when automatic migration is enabled for VMs.

• CPU Model: Specify the default CPU operating mode. Options include Compatible, Host Model, and Host Passthrough. The default CPU model for x86 hosts is compatible, and the default CPU model for ARM hosts is host passthrough. You can change the CPU operating mode for a VM when you create or edit the VM.

Customization Parameters

• System Name: Enter a name for the CAS system.

• Copyright Info: Enter the copyright information on the login page.

• Login Page Background: Enter the path where the login page background is saved.

• Homepage Logo: Enter the path where the homepage logo is saved. The logo is displayed on the top left of the homepage.

• Login Page Logo: Enter the path where the login page logo is saved.

• Homepage Tiny Logo: Enter the path where the small size homepage logo is saved. The logo is displayed on the top left of the homepage when the navigation tree is collapsed.

• Favicon: Enter the path where the favicon is saved.

• Copyright Logo: Enter the path where the copyright logo is saved.

• Display Columns Lines: Configure whether to display the lines between columns.

Customized Menu Parameters

• Menu Name: Enter the name of the system to be accessed from CVM.

• Menu URL: Enter the URL for accessing the system.

VNC Proxy Server Parameters

• Server IP: Enter the IP address of the VNC proxy server.

• Username: Enter the username used to access the VNC proxy server.

• Password: Enter the password for the user to access the VNC proxy server.

DNS Server Parameters

DNS server settings take effect only on a CVM server. If stateful failover is configured, the settings take effect on both the primary and back CVM servers.

 

• DNS Server: Enter a maximum of three semicolon-separated DNS server IP addresses for CVM.

HA Parameters

·          Use the default settings for the HA system as long as possible. The stability of CAS might degrade if a too large or too small value is set. ·          Do not change the default HA settings for initial deployment. To change the HA settings for temporary use, evaluate your configuration first and make sure you understand the impact of the change on services. To change HA settings for long time use, contact technical support to evaluate the impact on services.

 

• Host Heartbeat: Specify the interval at which CVK hosts send heartbeat packets to CVM. If a CVK host fails, the heartbeat is interrupted, and VMs on the host are migrated to other hosts in the same cluster after three host heartbeat intervals and three storage heartbeat intervals.

• Storage Heartbeat: Specify the interval at which CVK writes timestamps to the storage pool. If a storage network fails, the heartbeat is interrupted, and affected VMs are migrated to other hosts in the same cluster after three storage heartbeat intervals.

Image Cleanup

• Max Usage (%): Specify the threshold for triggering image cleanup.

When the space usage of /vms/nova exceeds the maximum usage threshold, the system cleans up the cached images in this path until the space is larger than the reserved space or smaller than the specified space usage after cleanup.

• Reserved Space: Specify the space that must be reserved after image cleanup.

• Usage After Cleanup: Specify the maximum space usage after image cleanup.

CPU and memory

• Reserve Host Memory: Configure whether to reserve host memory. If you select Yes, the system reserves 20% of the host memory or 10 GB host memory (whichever is smaller). The reserved memory of a host cannot be used for VMs started on or migrated to the VM.

• Memory Allocation Ratio for All VMs: Configure the maximum ratio of the memory allocated to all VMs to the total memory size of a host. The system identifies whether this ratio is reached when one of the following events occurs:

• A VM is created, deployed, or cloned.

• A VM is migrated manually or automatically by the HA or DRS feature.

• A VM is restored from the recycle bin.

• A VM is added by DRX.

• A VM is migrated to a host through cloud rainbow.

• CPU or memory allocation is edited for a VM.

• An OVF template is imported.

• A VM is restored from a snapshot or backup.

• Memory Allocation Ratio for Running VMs: Configure the maximum ratio of the memory allocated to running VMs to the total memory size of a host. The system identifies whether this ratio is reached when one of the following events occurs:

• A VM starts.

• CPU or memory allocation is edited for a running VM.

• A VM is restored from a memory snapshot.

• A running VM is migrated manually.

• A VM is migrated automatically by DRS.

• A VM is added by DRX.

• A VM is migrated to a host through cloud rainbow.

• CPU Overcommit: Select whether to enable CPU overcommitment. Options include Yes and No. If you select Yes, the number of vCPUs bound to the physical CPUs of a NUMA node can exceed the number of the physical CPUs. If you select No, the number of vCPUs bound to the physical CPUs of a NUMA node cannot exceed the number of the physical CPUs.

• CPU Allocation Ratio for All VMs: Configure the maximum ratio of the CPUs allocated to all VMs to the total number of CPUs on a host. The system identifies whether this ratio is reached when one of the following events occurs:

• A VM is created, deployed, or cloned.

• A VM is migrated manually or automatically by the HA or DRS feature.

• A VM is restored from the recycle bin.

• A VM is added by DRX.

• A VM is migrated to a host through cloud rainbow.

• CPU or memory allocation is edited for a VM.

• An OVF template is imported.

• A VM is restored from a snapshot or backup.

• CPU Allocation Ratio for Running VMs: Configure the maximum ratio of the CPUs allocated to running VMs to the total number of CPUs on a host. The system identifies whether this ratio is reached when one of the following events occurs:

• A VM starts.

• CPU or memory allocation is edited for a running VM.

• A VM is restored from a memory snapshot.

• A running VM is migrated manually.

• A VM is migrated automatically by DRS.

• A VM is added by DRX.

• A VM is migrated to a host through cloud rainbow.