Manage DRX

DRX periodically checks resource usage and dynamically adjusts the number of service VMs to provide

elastic and scalable resource pools for service systems.

Features

• Manage DRX services

• Configure DRX service monitoring

• Manage scheduled extension policies

• Configure a vertical extension policy

• Configure LB resource collaboration

• View DRX service summary

• View VM information in a DRX service

• View resource monitoring information in a DRX service

• View LB collaboration resources

• View DRX service operation logs

Manage DRX services

DRX adds VMs that provide the same service in the same cluster to a VM group. By periodically checking the

number of connections, average CPU usage, and average memory usage of VMs in the group, it dynamically adjusts the number of VMs in the group based on DRX policies and resource rejection mode, and resource reclaim policies and reclaim mode. With DRX, resource load balancing can be implemented for single-service systems. DRX resource management allows operators to add, edit, delete, enable, and disable DRX services.

Restrictions and guidelines

• The system automatically creates VMs when thresholds set in an extension policy and a reclaim policy are both matched, and the reclaim policy will not take effect any more.

• Deleting a DRX service does not delete VMs created by this DRX service.

• To clone all data of a VM when the resource import type is Fast Clone, you must first redeploy the VM. After the redeployment, the images of the VM will be merged.

• When the resource import type is Fast Clone, the system disables operations such as merging images, migrating storage, migrating storage volumes, and consolidating image chains on the source VM to prevent data loss.

• In a stateful failover environment, if DRX and primary/backup switchover occur at the same time, the DRX service might be interrupted unexpectedly. Even after environment recovery, tasks remain stuck. You must restart Tomcat in the host backend by using the service tomcat restart command.

Add a DRX service

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click Add DRX Service.

4. Configure the parameters as described in "Parameters."

5. Click OK.

Edit a DRX service

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click Edit in the Actions column for a DRX service.

4. Configure the parameters as described in "Parameters."

5. Click OK.

Enable a DRX service

1. Perform one of the following tasks:

   ○ On the top navigation bar, click Compute, from the left navigation pane, select DRX, and then click Enable in the Actions column for a DRX service.

   ○ On the top navigation bar, click Compute, from the left navigation pane, select DRX, click the name of a DRX service, and then click Enable DRX.

2. Select the time when DRX takes effect, Now or Custom, and then click OK.

Delete a DRX service

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click Delete in the Actions column for a DRX service.

4. In the dialog box that opens, click OK.

Redeploy a VM

Perform this task to perform a fast VM clone after the images of the VM to be cloned are merged. This makes sure the data of clone VMs added in a DRX service is consistent with the VM to be cloned. This feature is supported only when the resource import mode in the DRX service is fast clone.

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click a service name.

4. Click the icon next to the VM field in the Basic Info area.

5. In the dialog box that opens, click OK.

Parameters

Info

• Cluster: Enter the name of the cluster to run the DRX service.

• Storage: Specify a shared storage pool for automatically created VMs.

• Backup Cluster: Specify the backup cluster to run the DRX service. VMs are created in the backup cluster if the current cluster cannot satisfy the DRX requirements. For VMs to be created in the backup cluster, a cluster and its backup cluster must use the same shared storage when the resource import type is set to Fast Clone. Storage: Specify a backup shared storage pool for automatically created VMs.

• Max. VMs: Specify the maximum number of VMs supported by the DRX service. It is the maximum number of VMs allowed in a VM group.

• Effective: Select the way in which the DRX service takes effect. Options include Now, Custom, and No.

○ Now—The DRX service takes effect immediately after it is created.

○ Custom—The DRX service takes effect in the specified time range.

○ No—The DRX service does not take effect.

• Start Time: Specify the start time when the DRX service takes effect. This field is required if you select Custom from the Effective list. If you set only the start time, the DRX service is always effective from this time.

• End Time: Specify the end time when the DRX service takes effect. This field is required if you select Custom from the Effective list. If you set only the end time, the DRX service is effective from the current time to the end time.

• Bind LB Resource: Select whether to bind the VMs to an LB device. If you select Yes, you must configure LB settings.

Config

• Polling Interval:

○ Duration: Specify the time during which the average CPU usage and memory usage and the number of connections of the VMs in a VM group cross the thresholds multiple times in an extension monitoring policy, or drop below the thresholds multiple times in a reclaim monitoring policy.

○ Detection Interval: Specify the interval at which the average CPU usage, average memory usage, and connections of the VMs in a VM group are detected.

• Resource Import:

○ Select Monitoring Policy: Select a monitoring policy for resource import. When the average CPU usage, average memory usage, connections, network traffic, disk I/O, and IOPS of the VMs in a VM group cross the thresholds set in an extension policy within the specified time, a VM is automatically created in the VM group.

○ Resource Import: Select the mode in which a VM is created in the VM group. Options include Fast Deploy and Fast Clone.

▪ Fast Deploy—VMs are created in a VM group through the selected VM template.

▪ Fast Clone—VMs are created in a VM group through selecting VMs to be cloned.

○ VMs to Create: Specify the number of VMs to create for each DRX task, in the range of 1 to

100. If you configure this parameter, you cannot configure the Percentage of VMs to Add

parameter.

○ Percentage of VMs to Add: Specify the percentage of VMs to create for each DRX task, in the range of 1 to 100. The number of VMs to create is obtained by multiplying the number of running VMs by this percentage and then rounding up the product to the nearest integer. For example, if ten VMs are running and you set this parameter to 35%, the system will create four VMs in a DRX task. If you configure this parameter, you cannot configure the VMs to Create parameter.

○ Intelligent DRX: Select whether to enable intelligent DRX. This parameter is available only when intelligent DRX and DRS is enabled in "Configure system parameters "

• Resource Reclaim:

○ Select Monitoring Policy: Select a reclaim monitoring policy for resource reclamation. When the average CPU usage, average memory usage, connections, network traffic, disk I/O, and IOPS of the VMs in a VM group drop below the thresholds set in the reclaim monitoring policy within the specified time, the VM in the VM group is automatically reclaimed.

○ Reclaim Type: Select a reclamation policy. Options include Reclaim Now and Slow-Offline.

▪ Reclaim Now—A VM is reclaimed as long as the reclamation conditions are met.

▪ Slow-Offline—When the reclamation conditions are met, the system prevents the VM from receiving TCP packets and detects whether the number of packets sent by the VM is smaller than the threshold every 10 seconds. If the number is smaller than the threshold, the system reclaims the VM immediately. If the number is not smaller than the threshold, the system waits until the number is smaller than the threshold and reclaims the VM or waits until the timeout is reached and reclaims the VM.

○ Threshold—Specify the maximum number of packets sent by a VM that can trigger slow-offline VM reclamation. This parameter is required only when you select Slow-Offline as the reclaim mode.

○ Timeout—Specify the timeout that can trigger slow-offline VM reclamation. This parameter is required only when you select Slow-Offline as the reclamation mode.

○ Reclaim Mode: Select the mode in which a VM is reclaimed. Options include Shut Down VM, Delete VM, and Hibernate VM.

▪ Shut Down VM—Powers off a VM.

▪ Delete VM—Deletes a VM.

▪ Hibernate VM—Hibernates a VM.

○ Min Running VMs: Specify the minimum number of VMs that must be in running state in a resource reclamation task.

VMs

• Service VM: Click Yes to add VMs that run the same service to a VM group.

Extension

• VM Template: Select the VM template for fast deployment. This parameter is required only when you select Fast Deployment as the resource import type.

• VM to Clone: Select the VM to clone. This parameter is required only when you select Fast Clone as the resource import type. If you specified a shared file system as the storage pool in basic DRX configuration, the VM to clone must be a VM that uses an image file as its disk.and the VM must meet the following requirements:

○ No USB, PCI, SR-IOV, or TPM devices exist on the VM.

○ The VM is not bound to any NUMA node or physical CPU.

○ The storage type of the VM is intelligent and thin provisioning is used.

• VM Prefix: Enter the prefix of the VM.

• Start Number: Enter the start number of the VM. This parameter is displayed after the VM prefix. The number increases as the number of created VMs increases until the maximum number is reached.

• IPv4 configuration

○ Start IP: Specify the start IPv4 address of the VM.

○ End IP: Specify the end IPv4 address of the VM. Reserve enough IPv4 addresses for IP allocation.

○ Subnet Mask: Specify the subnet mast of the VM.

○ Default Gateway: Specify the default gateway of the VM.

• IPv6 configuration

○ Start IP: Specify the start IPv6 address of the VM.

○ End IP: Specify the end IPv6 address of the VM. Reserve enough IPv6 addresses for IP allocation.

○ Network Prefix: Specify the prefix length of the IPv6 addresses.

○ Default Gateway: Specify the default gateway of the VM.

LB Config

• Bound IP Type: Select an IP address type for the LB device.

• LB Device: Select an LB device. An LB device distributes traffic to real servers based on different policies.

• Virtual Server: Select a virtual server. A virtual server has a virtual IP. It receives user requests, and the LB device selects a real server to respond to the user requests.

• Real Server Farm: Select a real server farm. A real server farm contains real servers.

• VM Service Port: Enter a port for the VM to provide services. Different ports provide different services.

Configure DRX service monitoring

Perform this task to configure DRX service monitoring policies.

When the duration during which the average CPU usage and memory usage, connections, network traffic, disk I/O, and IOPS of the VMs in a VM group cross the thresholds set in an extension policy reaches the specified duration, VMs are automatically created in the VM group. When the duration during which the average CPU usage and memory usage, connections, network traffic, disk I/O, and IOPS of the VMs in a VM group drop below the thresholds set in a reclaim policy reaches the specified duration, the system automatically reclaims the VMs.

Procedure

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click Service Monitoring.

5. Configure the parameters as described in "Parameters."

6. Click OK.

Parameters

• Duration: Specify the time during which the average CPU usage and memory usage and the number of connections for the VMs in a VM group cross the thresholds multiple times in an

Manage scheduled extension policies

A scheduled extension policy is used to create VMs at specific time points in an application system where

service surges are periodical.

Restrictions and guidelines

• A scheduled extension task takes effect the next day if you set the frequency to Daily, and set the start time to be earlier than the current system time of the management platform.

• The default polling interval for scheduled extension is 10 minutes. DRX is not performed during the specified time period.

• During the time periods not specified in a scheduled extension policy, VMs created by using the policy are reclaimed if they meet the resource reclaim policy.

Add a scheduled extension policy

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click the Scheduled Extension Policy tab.

5. Click Add.

6. Configure the parameters as described in "Parameters."

7. Click OK.

Edit a scheduled extension policy

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click the Scheduled Extension Policy tab.

5. Click Edit in the Actions column for a scheduled extension policy.

6. Configure the parameters as described in "Parameters."

7. Click OK.

Delete a scheduled extension policy

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click the Scheduled Extension Policy tab.

5. Click Delete in the Actions column for a scheduled extension policy.

6. In the dialog box that opens, click OK.

View scheduled extension policy information

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click the Scheduled Extension Policy tab.

Parameters

• Name: Specify the name of the scheduled extension policy.

• Description: Specify the description of the scheduled extension policy.

• VMs to Create: Specify the number of VMs to create for each scheduled extension task.

Configure a vertical extension policy

Perform this task to configure a vertical extension policy for a DRX service. The system adds CPUs or

memory for a VM when the CPU usage or memory usage crosses the thresholds set in the vertical extension policy.

Procedure

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click Vertical Extension Policy.

5. Select Configure CPU or Configure Memory as needed.

   ○ If you select Configure CPU, enter the CPU usage, step, and max limit.

   ○ If you select Configure Memory, enter the memory usage, step, and max limit.

6. Click OK.

Parameters

• Configure CPU: Select this option to enable the vertical extension policy by CPU usage.

• CPU Usage: Specify the CPU usage threshold. The system adds CPUs to a VM when this threshold is reached.

• Step: Specify the number of CPUs to add for a VM.

• Max Limit: Specify the maximum number of CPUs that can be added for a VM.

• Configure Memory: Select this option to enable the vertical extension policy by memory usage.

• Memory Usage: Specify the memory usage threshold. The system adds memory to a VM when this threshold is reached.

• Step: Specify the memory size to add for a VM.

• Max Limit: Specify the maximum memory size that can be added for a VM.

Configure LB resource collaboration

Perform this task to specify an LB device for a VM group. Make sure LB devices are available and have been

configured correctly before performing this task.

Prerequisites

Make sure load balancers are available and have been configured correctly before you perform this task.

Procedure

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click LB Resource Collaboration.

5. Configure the parameters as described in "Parameters."

6. Click Finish.

Parameters

IP

• IPv4 Settings

○ Start IP: Enter the start IP address of the VM.

○ End IP: Enter the end IP address of the VM. Reserve sufficient IP addresses for allocation when you set the start IP and end IP.

○ Subnet Mask: Enter the subnet mask of the VM.

○ Default Gateway: Enter the default gateway of the VM.

• IPv6 Settings

○ Start IP: Enter the start IP address of the VM.

○ End IP: Enter the end IP address of the VM. Reserve sufficient IP addresses for allocation when you set the start IP and end IP.

○ Prefix: Enter the prefix length of the IPv6 address for the VM.

○ Default Gateway: Enter the default gateway of the VM.

• Basic Info Bound IP Type: Specify the IP address version for the LB device used by the DRX service.

• LB Device: Select an LB device. An LB device distributes traffic to real servers.

○ Device Name: Specify the name of the LB device, used for identification and management.

○ Description: Specify the description of the LB device, which can be a detailed description of the LB device's function, purpose, or role to facilitate management and identification. Clear descriptions help users quickly understand each device's role and configuration, especially in large deployments.

○ Management IP: Enter the management IP address of the LB device (IPv4 only).

○ Username: Enter the username for connecting to the NETCONF interface of the LB device, used for authentication.

○ Password: Enter the password, used for authentication.

• Virtual Server: Select a virtual server. A virtual server provides a virtual IP. It receives user requests, and the LB device selects real servers to respond to the requests.

○ Name: A unique identifier for the virtual server.

○ Type: The service type of the virtual server, including TCP, UDP, HTTP, Performance(HTTP), HTTPS, and HTTP redirection.

○ IP Address: The VIP that the virtual server exposes.

○ Mask Length: The subnet mask length of the VIP.

○ SSL Server Policy: Specifies SSL configurations (for example, certificates, cipher suites, and SSL versions) for HTTPS encryption.

○ Port: The open service port on the virtual server.

• Real Server Farm: A group of servers (VMs or physical hosts) that handle traffic from the virtual server, enabling load balancing and high availability.

○ Name: A unique identifier for the real server farm.

○ Scheduling Algorithm: Determines how the LB selects backend servers. Options include round-robin, random, least connections, source IP hash, source IP and port hash, and destination IP hash.

○ Mask Length: Subnet mask length of servers in the real server farm. This parameter is available only when the source IP hash, source IP and port hash, or destination IP hash algorithm is used.

○ Prefix Length: Prefix length of an IPv6 address. This parameter is available only when the source IP hash, source IP and port hash, or destination IP hash algorithm is used.

• Health Check Method: Select a health check method, which is a mechanism to automatically identify whether backend servers are operational, ensuring that only healthy servers provide services.

View DRX service summary

Perform this task to view the summary and resource usage for a DRX service.

Procedure

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. click the name of a DRX service to view its basic information.

Parameters

• Basic Attributes: Basic information about the DRX service.

○ Service Name: Name of the DRX service.

○ Cluster: Cluster that runs the DRX service.

○ Max. VMs: Maximum number of VMs supported by the DRX service. It is the maximum number of VMs allowed in a VM group.

○ Current VMs: Number of VMs in the VM group corresponding to the DRX service.

○ Resource Import: Mode in which a VM is created in the VM group corresponding to the DRX service.

○ VM/Template: Name of the cloned VM or name of the VM template in use. If the resource import mode is Fast Deployment, this column displays the name of the VM template used for deploying a VM. If the resource import mode is Fast Clone, this column displays the name of the cloned VM.

○ VMs to Create: Number of VMs to create for every dynamic resource extension in a DRX service.

○ Percentage of VMs to Add: Percentage of VMs to create for every dynamic resource extension in a DRX service. The number of VMs to create is obtained by multiplying the number of running VMs by this percentage and then rounding up the product to the nearest integer. For example, if ten VMs are running and you set this parameter to 35%, the system will create four VMs in a dynamic resource extension.

○ Reclaim Type: Policy for reclaiming a VM.

○ Reclaim Mode: Mode in which a VM is reclaimed.

○ State: Current state of the DRX service.

○ Extension Policy: When the parameters of VMs in a VM group match the thresholds set in an extension policy within the specified time, the VM is automatically created in the VM group.

View VM information in a DRX service

Perform this task to view information about the VMs monitored by a DRX service.

Procedure

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click the VMs tab.

5. To add a VM, click the icon, select a VM, and click OK.

6. To change the automatic reclamation setting for a VM, click the or button.

Parameters

• CPU Usage: CPU usage trend graph for a VM over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the CPU usage in percentage.

• Memory Usage: Memory usage trend graph for a VM over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the memory usage in percentage.

• Connections: Connection quantity trend graph for a VM over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the number of connections.

• Network Throughput: Network throughput trend graph for a VM over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the network throughput.

• I/O Throughput: I/O throughput trend graph for a VM over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the I/O throughput.

• IOPS: IOPS trend graph for a VM over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the number of disk requests by IOPS.

View resource monitoring information in a DRX service

View resource monitoring information in a DRX service

Perform this task to view the average resource usage of the VMs in a VM group.

Procedure

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click the Service Resource Monitoring tab.

Parameters

• CPU Usage: Average CPU usage trend graph for the VMs in a VM group over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the CPU usage in percentage.

• Memory Usage: Average memory usage trend graph for the VMs in a VM group over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the memory usage in percentage.

• Connection Statistics: Average connections trend graph for the VMs in a VM group over the last 30 minutes. The horizontal axis represents the time, and the vertical axis represents the number of connections.

View LB collaboration resources

Perform this task to view LB collaboration resources.

Procedure

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click the LB Collaboration Resources tab.

Parameters

Basic Attributes

• Device Name: Name of the LB device.

• Management IP: Management IP address of the LB device.

• Virtual Server Name: Name of the virtual server.

• Virtual Server Type: Type of the virtual server.

• Virtual Server IP: IP address that the virtual server users to provide services.

• Virtual Server Port: Port that the virtual server users to provide services.

• Real Server Farm: Name of the real server farm. A real server farm contains real servers.

• Scheduling Algorithm: Scheduling algorithm. An LB device selects a real server based on the scheduling algorithm.

• Health Check Method: Health check method. An LB device checks the health status of the real servers in the real server farm. It does not distribute user requests to a real server when it detects that the real server is unavailable. After the real server recovers, the LB device continues to distribute user requests to the real server. This process is transparent to users.

• Virtual Server Connection Statistics: Virtual server connection trend graph. The horizontal axis represents the time, and the vertical axis represents the number of connections.

• VM LB Statistics: LB statistics for VMs in the real server farm.

• VM Name: Name of the VM.

• IP: IP address of the VM.

• Active Connections: Number of active connections on the VM.

View DRX service operation logs

Perform this task to view DRX service operation logs.

Procedure

1. On the top navigation bar, click Compute.

2. From the left navigation pane, select DRX.

3. Click the name of a DRX service.

4. Click the Tasks tab.

5. To filter the tasks, configure the filter criteria, and then click Query.

6. To hide the non-default filter parameters, click Hide.

7. To display all filter parameters, click More.

Parameters

• Login Name: Login name used by the operator to log in to the management platform.

• Operator Name: Name of the operator.

• Start Time: Time when the operator started the DRX service.

• Completed At: Time when the operator ended the DRX service.

• Login Address: IP address used by the operator to log in to management platform.

• Action: Type of action executed by the operator.

• Target: DRX service to execute.

• Description: Description of the action executed by the operator.

• Result: Operation result.

○ Succeeded—The operation has succeeded.

○ Partially Succeeded—The operation has partially succeeded.

○ Failed—The operation has failed.

• Reason: Reason why an operation has failed.

• Severity Level: Severity level for the operation.

• Action Type: Type of the action that the operator performs.