{{ secondMenu.name }}
Precautions:
Steps:
Step 1: Log in to SCP, go to Reliability > DRS, in the left-up corner select a resource pool, and click Scheduling Policy.
Step 2: Select an Automation Level. The Automation Level supports three levels.
• Automated: VMs will be automatically migrated to another node based on the resource rating results. For the details refer to the current Table VM Performance score method and Table Node Performance score method.
• Manual: Migration recommendations will be given but need to be applied manually. For the detail, please refer to step 6.
• Disabled: No migration recommendations will be given.
The above three-automation level applies to all VMs by default. You can configure excluded VMs as needed. clicking excluded VMs > New click the 
button select VMs then in the Automation Level filed select the level you want apply.
Step 3: Select a Scheduling Mode. Based on which optimal destination nodes and recommendations are given to optimize the cluster. The Better Performance mode balances the load on each node, and the Less Cost mode saves node resources by centralizing VMs to run on one or more nodes as much as possible.
• Better Performance: Migrates VMs on nodes with high loads to nodes with low loads to improve the performance of the nodes and VMs. The reliability level of the destination nodes cannot be lower than that of the source nodes.
• Less Cost: Migrates VMs in order of node memory load from the lowest to the highest to nodes with high loads. The VM performance score decrease after migration cannot exceed the threshold and the reliability level of the destination nodes cannot be lower than that of the source nodes.
Step 4: Select a Sensitivity level.
• Conservative (less frequent): DRS will be triggered when loads of nodes in the cluster are seriously unbalanced. Trigger: The load of a node exceeds 70%, and the load difference between this node and other clustered nodes exceeds 30%.
• Moderate (default): DRS will be triggered when loads of nodes in the cluster are unbalanced. Trigger: The load of a node exceeds 60%, and the load difference between this node and other clustered nodes exceeds 20%.
• Aggressive (frequent) for Sensitivity: DRS will be triggered when loads of nodes in the cluster are slightly unbalanced. Trigger: The load of a node exceeds 50%, and the load difference between this node and other clustered nodes exceeds 5%.
Step 5: Select Disable, Low, Medium, High, or Highest for AI Prediction Capability based on the number of VMs. If this feature is enabled, AI algorithms will be used to predict the loads of the nodes and VMs for the next two days and schedule resources based on the load trends of the past seven days.
• Disable: AI-powered prediction will be disabled.
• Low: About 1 CPU core and 500 MB of memory will be consumed to predict the load of 500 VMs.
• Medium: About 2 CPU cores and 1 GB of memory will be consumed to predict the load of 1,000 VMs.
• High: About 4 CPU cores and 2 GB of memory will be consumed to predict the load of 2,000 VMs.
• Highest: CPU and memory resources will be consumed to predict the load of all VMs. The actual resource consumption is related to the number of VMs. 1 CPU core and 500 MB of memory may be consumed for every 500 VMs.
Step 6: You can specify the schedule for enabling dynamic resource scheduling according to business service priorities. If the end time is equal to or smaller than the start time, the end time is on the following day. You can select Every day, Every week or Every month.
Suggest configuring the Schedule to prevent DRS from being performed during the off-peak hours.
After the DRS configuration is finished, if the environment meets your DRS conditions you can get the DRS recommendations, the VM scheduling history and resource rating information by clicking Recommendations, Scheduling History, Resource Rating.
Recommendations: If the Automation Level you selected Manual when the node load does not meet the DRS settings it will generate recommendations to migrate the VMs. After the recommendations generated you can click the left-up corner button Start Scheduling to migrate all the VM, or you can locate the VM you want to migrate and click Start Scheduling in the Operation column.
Scheduling History: Here you can view the scheduling history of a virtual machine by specifying a period. This includes the scheduling result (whether completed or failed), the virtual machine that was scheduled, the physical machine it was scheduled from and to, the reason for the scheduling, and the time of the scheduling.
Resource Rating: Here you can view the Node and VM resource rating, both include reliability score and performance score.
Reliability Score: The full score is 100, indicating the best status. Measures of node reliability. Deductions are made based on the actual impact of node failures.
Performance Score: The full score is 100, indicating the best status. A score is given based on the actual CPU demand, memory demand, network performance, and storage performance of a node.
For the node if the Reliability Score is not 100. You can click View Deductions to check the points deducted. VM Reliability Score = Reliability score of the run location node.
Node Performance score method:
| Metric |
Data |
| CPU Demand |
Actual CPU usage, estimated CPU usage, and number of logical CPU cores |
| Memory Demand |
Actual memory usage and size of the swap space used |
| Network Performance |
Packet loss rate and packet error rate |
| Storage Performance |
Checks whether the VM has a replica on the node where it runs |
Table: Node Performance score method
VM Performance score method:
| Metric |
Data |
| CPU Demand |
Actual CPU usage, estimated CPU usage, number of logical CPU cores of the node, and sum of the number of logical cores of all VMs running on the node |
| Memory Demand |
Actual memory usage, size of the swap space used, size of memory allocated to all VMs running on the node, and total memory size of the node |
| Network Performance |
Packet loss rate and packet error rate |
| Storage Performance |
Checks whether the VM has a replica on the node where it runs. |
Table: VM Performance score method
{{ $t('index.defaultHeader.chromeBrowserTip') }}