A method, device and system for specifying NUMA nodes to implement virtual machine migration

By adding the requested_numa_nodes parameter and using the NUMA Fit algorithm in the Nova API, the cloud platform's resource scheduling uncertainty on multiple NUMA architecture hosts is solved, and flexible virtual machine migration and NUMA affinity strategy are realized, which improves the Resource utilization and migration effect.

CN117850968BActive Publication Date: 2024-11-26CHINA TELECOM CLOUD TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311722333.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-12-14
Publication Date
2024-11-26
Estimated Expiration
2043-12-14

AI Technical Summary

Technical Problem

There is uncertainty in the resource scheduling of existing cloud platforms on multi-NUMA architecture hosts, and it is difficult to implement flexible virtual machine migration and NUMA affinity strategies, resulting in low resource utilization and unsatisfactory migration results.

Method used

By adding the requested_numa_nodes parameter to the Nova API, combining Nova Conductor and Nova Scheduler, the NUMA Fit algorithm is used to match and migrate resources, ensuring that the virtual machine is migrated to the specified NUMA node and the migration of the specified NUMA node is realized.

Benefits of technology

It improves the clarity and directness of the migration plan, simplifies the implementation of secondary dynamic scheduling and affinity strategies, reduces the number of adjustments, and improves resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117850968B_ABST
    Figure CN117850968B_ABST
Patent Text Reader

Abstract

The present invention belongs to the technical field of cloud platform resource scheduling, and discloses a method, device and system for specifying NUMA nodes to realize virtual machine migration, including the following steps: S01, sending a migration request to Nova API through CLI or a dynamic resource scheduling system, and adding a requested_numa_nodes parameter to the migration interface of Nova API; S02, after Nova API receives the migration request, it verifies it, and then converts and merges the migration request parameters and the corresponding parameters required for migration and sends them to Nova Conductor. The present invention can specify the number of NUMAs and the specific NUMA node sequence number for migration according to the optimal topology calculated by the algorithm, so that the migration plan is clear and direct, and the secondary dynamic scheduling and various affinity strategies are easy to implement.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of cloud platform resource scheduling, and in particular relates to a method, device and system for implementing virtual machine migration by specifying a NUMA node. Background Art

[0002] At present, the application of public cloud is becoming more and more extensive. As the core product of public cloud, elastic cloud host has more and more categories and specifications to meet the different needs of customers in different business scenarios. For example, there are shared hosts focusing on cost-effectiveness, and there are also performance hosts focusing on high performance and isolation. At the same time, the cloud platform also needs to continuously improve its own resource utilization rate and meet various migration and scheduling requirements required for its own operation, such as room migration, hardware update iteration, fault repair, resource reuse, etc. This brings great challenges to the resource scheduling and operation strategy of the cloud platform.

[0003] Generally, when a cloud host is allocated for the first time, the scheduling system will make an optimal resource scheduling allocation based on the current status of the resource pool and the requested specification parameters; during the continuous operation process, the resource pool will produce various resource fragments and load hot and cold distributions. At this time, a secondary dynamic scheduling system is needed to adjust the resource pool and move the host through migration to achieve specific operational goals, improve resource utilization of the resource pool, eliminate load hot spots, etc. At present, mainstream cloud platform systems, such as OpenStack, provide powerful host migration capabilities, which can achieve granular migration such as specifying the destination host.

[0004] However, with the increasing popularity of multi-NUMA architecture hosts, especially ARM architecture servers that may have 4, 8, or 16 NUMA nodes, the current NUMA scheduling is based on random allocation of the allocatable node set or sorting the node set according to a certain strategy (such as the number of remaining allocatable vCPUs) and then allocating it. This scheduling mode is uncertain, and when performing resource defragmentation during secondary dynamic scheduling, or when you want to implement affinity strategies for certain PCI devices with NUMA affinity, it is often impossible to achieve or requires multiple adjustments to achieve, which has low flexibility and often unsatisfactory results, so it needs to be improved. Summary of the invention

[0005] The purpose of the present invention is to provide a method, device and system for implementing virtual machine migration by specifying a NUMA node, so as to solve the technical problems raised in the prior art.

[0006] In order to achieve the above object, the present invention adopts the following technical solution: a method for implementing virtual machine migration by specifying a NUMA node, comprising the following steps:

[0007] S01. Send a migration request to the Nova API through the CLI or the dynamic resource scheduling system, and add the requested_numa_nodes parameter to the migration interface of the Nova API.

[0008] S02. After receiving the migration request, Nova API verifies it, and then converts and merges the migration request parameters and the corresponding parameters required for migration and sends them to Nova Conductor.

[0009] S03, Nova Conductor goes to Nova Scheduler to request a suitable resource node. NovaScheduler calls the NUMA Fit algorithm to match NUMA resources and select the host.

[0010] S04. After Nova Conductor obtains the scheduling resources, it goes to the destination node to confirm whether the resources can be migrated. After confirming the migration, it obtains detailed migration information to achieve the purpose of placing the virtual machine with the specified NUMA node number.

[0011] Preferably, the steps for adding a requested_numa_nodes parameter in the migration interface of the Nova API are as follows: find the relevant code for processing migration requests in the Nova API; find the function or method used to create and send migration task requests in the relevant code; in the current function or method, add a new parameter requested_numa_nodes to receive the NUMA node number specified by the user; in the logic of processing the migration request, use the value of the requested_numa_nodes parameter to specify the NUMA node number of the target host machine as needed.

[0012] Preferably, after Nova API receives the migration request, the method for verifying it is as follows: confirm whether the request contains all required parameters; obtain the current status of the instance involved in the request; check whether its resources meet the requirements of the instance based on the information of the target host in the request; perform a health check on the instance to ensure that the instance is not in an error state or has any faults; verify whether the source and target networks are reachable, and check whether the network configuration matches the information in the request; verify whether the client has sufficient permissions to perform the migration operation.

[0013] Preferably, the Nova Conductor is an execution tracking component of a long-duration task, responsible for coordinating and managing task execution and tracking of database operations.

[0014] Preferably, the logic of NUMA resource matching is as follows:

[0015] Start NUMA allocation and fully arrange the host NUMA cells according to the number of NUMA nodes of the instance requested to migrate; arrange the obtained cells in random order;

[0016] Traverse the above random order arrangement and define an empty mismatch set to record numacells that do not meet the requested instance resource requirements;

[0017] Determine whether the random order arrangement has been traversed; if the judgment result is yes, the allocation fails and the current host does not meet the NUMA requirements; if the judgment result is no, continue to determine whether the random order arrangement is consistent with the specified numa arrangement, that is, check according to the requested_numa_nodes parameter to determine whether the sequence number value completely matches; if the judgment result is inconsistent, repeat the step of determining whether the random order arrangement has been traversed;

[0018] If the judgment result is consistent, continue to judge whether the random order contains the mismatched cell; if the judgment result is included, continue to traverse the next order and repeat the step of judging whether the random order traversal is complete; if the judgment result is not included, match all the numa cells in the order with the instance resource requirements, find out the mismatched cells and add them to the mismatch;

[0019] Determine whether all cells in the current random order are matched. If the judgment result is yes, assign the NUMA combination of the arrangement to the virtual machine; if the judgment result is no, repeat the step of determining whether the random order is traversed and completed.

[0020] Preferably, after Nova Conductor obtains the scheduling resources, the steps to confirm whether the resources can be migrated to the destination node are as follows:

[0021] After Nova Conductor obtains the scheduling resources, it sends the resource information to the destination node;

[0022] After receiving the resource information, the destination node will perform a resource availability check to confirm whether the node has sufficient resources to support instance migration;

[0023] Nova Conductor determines whether the resource can be migrated based on the confirmation information or error information of the destination node. If it can be migrated, Nova Conductor will further obtain relevant migration information again. If it cannot be migrated, the resource will be placed back to the original node and Nova Conductor will be notified;

[0024] After Nova Conductor receives the notification of resource release, it will reschedule the resources and send the new resource information to the destination node;

[0025] After the destination node receives the resource information again, it will repeat the above steps until the resources are successfully migrated to the destination node.

[0026] Preferably, the detailed information of the migration includes the following: NUMA topology information, source node information, destination node information, virtual machine status, memory data, and device status information.

[0027] A device for implementing virtual machine migration by specifying NUMA nodes, including: a migration request interface extension module, used to send a migration request to a Nova API through a CLI or a dynamic resource scheduling system, and to add a requested_numa_nodes parameter to the migration interface of the Nova API; a migration request processing module, used to verify the migration request after the Nova API receives it, and then convert and merge the migration request parameters and the corresponding parameters required for migration and send them to Nova Conductor; a resource scheduling module, used to request a suitable resource node from a Nova Scheduler resource scheduler through Nova Conductor, and to match NUMA resources and screen hosts by calling a NUMA Fit algorithm through Nova Scheduler; a migration confirmation module, used to confirm whether the resource can be migrated at the destination node after Nova Conductor obtains the scheduling resource, and to obtain detailed migration information after confirming the migration, so as to achieve the purpose of placing the virtual machine at the specified NUMA node number.

[0028] A system for implementing virtual machine migration by specifying NUMA nodes is used to implement the above-mentioned method for implementing virtual machine migration by specifying NUMA nodes, including CLI, dynamic resource scheduling system, Nova API, Nova Conductor, Nova Scheduler, Dest Node and Src Node.

[0029] Preferably, the CLI and the dynamic resource scheduling system send a migration request to the Nova API; after receiving the migration request, the Nova API converts and merges the migration request parameters and other parameters required for migration and sends them to Nova Conductor; Nova Conductor calls the NUMA Fit algorithm through the Nova Scheduler to perform NUMA resource matching and screen a suitable host; and after confirming that the resources can be migrated, migrate the virtual machine between the Dest Node and the Src Node.

[0030] In summary, due to the adoption of the above technical solution, the beneficial effects of the present invention are:

[0031] The present invention can specify the NUMA quantity and specific NUMA node sequence number migration according to the optimal topology calculated by the algorithm, so that the migration plan is clear and direct, and the implementation of secondary dynamic scheduling and various affinity strategies becomes easy; the migration plan obtained by the scheduling system does not need to be adjusted or tried multiple times, and is easy to use. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 A method flow chart of Embodiment 1 of the present invention is shown;

[0034] Figure 2 A logical flow chart of NUMA resource matching according to Embodiment 1 of the present invention is shown;

[0035] Figure 3 A module diagram of Embodiment 2 of the present invention is shown;

[0036] Figure 4 A system architecture diagram of Embodiment 3 of the present invention is shown;

[0037] Figure 5 A schematic diagram of resource distribution before migration according to Embodiment 3 of the present invention is shown;

[0038] Figure 6 A schematic diagram of resource distribution after migration in embodiment 3 of the present invention is shown. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0040] Example 1

[0041] Reference Figure 1 As shown, the method for specifying a NUMA node to implement virtual machine migration includes the following steps:

[0042] S01. Send a migration request to the Nova API through the CLI or the dynamic resource scheduling system, and add a requested_numa_nodes parameter to the migration interface of the Nova API to specify the NUMA node number that needs to be migrated to the destination host;

[0043] Among them, Nova API is a communication method in the OpenStack cloud computing platform, which includes two types: Rest API and RPC API. Rest API is the standard external interface of OpenStack, and RPC API is the remote call API of a certain functional module.

[0044] Specifically, the steps to add the requested_numa_nodes parameter in the Nova API migration interface are as follows:

[0045] Find the code in the Nova API that handles migration requests, usually in nova / api / ec2 / cloud.py, nova / api / openstack / placement / init.py, or similar files;

[0046] In the code that processes migration requests, find the function or method used to create and send migration task requests, which is usually the migrate function, which is used to perform virtual machine migration operations.

[0047] In this function or method (migrate function), add a new parameter requested_numa_nodes to receive the NUMA node number specified by the user, and set the default value to None.

[0048] For example, [0,1] indicates that the topology of the virtual machine is 2NUMA nodes, which are evenly distributed on NUMA nodes 0 and 1.

[0049] S02. After receiving the migration request, Nova API verifies it, and then converts and merges the migration request parameters and the corresponding parameters required for migration and sends them to Nova Conductor.

[0050] Specifically, after Nova API receives a migration request, it verifies it as follows:

[0051] Check required parameters: First, confirm whether the request contains all required parameters, which may include instance ID, target host information, etc. If any required parameters are missing, an error message should be returned, indicating that the request is incomplete or invalid.

[0052] Verify instance status: Get the current status of the instance involved in the request. If the instance is in a non-migratable state (for example, the instance is running or undergoing a major update), the migration request should be rejected and an error message should be returned stating that the instance is currently non-migratable;

[0053] Check the resources of the target host: Based on the information of the target host in the request, check whether its resources meet the requirements of the instance; this may include CPU, memory, storage space, etc. If the resources of the target host do not meet the requirements of the instance, an error message should be returned, indicating that the migration failed;

[0054] Perform instance health check: Perform a health check on the instance to ensure that the instance is not in an error state or has any faults. This may include checking the instance's log files, running status, etc. If there is any problem with the instance, an error message should be returned, indicating that the instance is not suitable for migration.

[0055] Perform network verification: Verify whether the source and target networks are reachable, and check whether the network configuration matches the information in the request. If they do not match or are unreachable, a corresponding error message should be returned.

[0056] Perform permission verification: Verify whether the client has sufficient permissions to perform the migration operation. This may involve the user's role, authentication information, etc. If the user does not have sufficient permissions, an error message should be returned, indicating that the user does not have permission to perform this operation;

[0057] Specifically, Nova Conductor is part of the OpenStack cloud computing platform and is a middleware service between nova-compute and the database. It is mainly responsible for processing nova-compute's CRUD operations on the database and providing API (application programming interface) services to the outside world through RPC (remote procedure call). When no worker is configured, Nova Conductor runs in multiple processes by default, and the number of processes will be consistent with the number of logical CPUs on the server.

[0058] Therefore, Nova Conductor is a long-term task execution tracking component that is responsible for coordinating and managing the task execution and tracking of database operations to improve the performance and security of the OpenStack cloud computing platform.

[0059] S03. Nova Conductor goes to Nova Scheduler to request a suitable resource node. NovaScheduler calls the NUMA Fit algorithm to match NUMA resources and select the host.

[0060] Specifically, refer to Figure 2 As shown, the logic of NUMA resource matching is as follows:

[0061] Start NUMA allocation and fully arrange the host NUMA cells according to the number of NUMA nodes of the instance requested to migrate; arrange the obtained cells in random order;

[0062] Traverse the above random order arrangement and define an empty mismatch set to record numacells that do not meet the requested instance resource requirements;

[0063] Determine whether the random order traversal is complete; if the judgment result is yes, the allocation fails and the current host does not meet the NUMA requirements;

[0064] If the result is no, continue to determine whether the random sequence is consistent with the specified numa sequence, that is, check according to the requested_numa_nodes parameter to determine whether the sequence number value completely matches; if the result is inconsistent, repeat the step of determining whether the random sequence is traversed to the end;

[0065] If the judgment result is consistent, continue to judge whether the random order contains the mismatched cell; if the judgment result is included, continue to traverse the next order and repeat the step of judging whether the random order traversal is completed; if the judgment result is not included, match all the numa cells in the order with the instance resource requirements (cpu, mem, disk, etc.), find out the mismatched cells and add them to the mismatch;

[0066] Then, it is determined whether all cells in the current random order are matched. If the determination result is yes, the NUMA combination of the arrangement is allocated to the virtual machine; if the determination result is no, the step of determining whether the random order is traversed and completed is repeated.

[0067] S04. After Nova Conductor obtains the scheduling resources, it goes to the destination node to confirm whether the resources can be migrated. After confirming the migration, it obtains the detailed migration information. During this process, the NUMA Fit algorithm is called again to perform NUMA resource matching to achieve the purpose of placing the virtual machine with the specified NUMA node number.

[0068] Specifically, after Nova Conductor obtains the scheduling resources, the steps to go to the destination node to confirm whether the resources can be migrated are as follows:

[0069] After Nova Conductor obtains the scheduling resources, it sends the resource information to the destination node (DestNode);

[0070] After receiving the resource information, the destination node will perform a resource availability check to confirm whether the node has sufficient resources to support the migration of the instance. This may involve checking whether the node's CPU, memory, storage space and other resources meet the instance requirements. If the resources are available, a confirmation message is returned; if the resources are not available, an error message is returned.

[0071] Nova Conductor determines whether the resource can be migrated based on the confirmation information or error information of the destination node. If it can be migrated, Nova Conductor will further obtain relevant migration information again, such as instance configuration information, disk mirroring, etc.; this information will be used to rebuild the instance on the destination node; if it cannot be migrated, the resource will be put back to the original node and Nova Conductor will be notified;

[0072] After Nova Conductor receives the notification of resource release, it will reschedule the resources and send the new resource information to the destination node;

[0073] After the destination node receives the resource information again, it will repeat the above steps until the resources are successfully migrated to the destination node.

[0074] Further, the migration details include the following:

[0075] NUMA topology information, source node information, destination node information, virtual machine status, memory data, device status information, etc.

[0076] After confirming that the resources can be migrated, the virtual machine is migrated between the Dest Node (destination node) and the Src Node (source node).

[0077] Example 2

[0078] Reference Figure 3 As shown, the device for specifying a NUMA node to implement virtual machine migration includes:

[0079] The migration request interface extension module is used to send migration requests to the Nova API through the CLI (command line interface) and the dynamic resource scheduling system; and the requested_numa_nodes parameter is used to specify the NUMA node number to be migrated to the destination host;

[0080] The migration request processing module is used to verify the migration request after the Nova API receives it, and then convert and merge the migration request parameters with the corresponding parameters required for migration and send them to Nova Conductor;

[0081] The resource scheduling module is used to request the appropriate resource node from the Nova Scheduler resource scheduler through Nova Conductor, and call the NUMA Fit algorithm through Nova Scheduler to perform NUMA resource matching and select the host;

[0082] The migration confirmation module is used to confirm whether the resources can be migrated at the destination node after Nova Conductor obtains the scheduling resources, and obtain detailed migration information. During this process, the NUMA Fit algorithm is called again to perform NUMA resource matching to achieve the purpose of placing the virtual machine at the specified NUMA node number.

[0083] Example 3

[0084] Reference Figure 4 As shown, a system for implementing virtual machine migration by specifying NUMA nodes includes a CLI (command line interface), a dynamic resource scheduling system, a Nova API, a Nova Conductor, a Nova Scheduler, a Dest Node, and a SrcNode;

[0085] Among them, Nova API is a communication method in the OpenStack cloud computing platform, which includes two types: Rest API and RPC API; Rest API is the standard external interface of OpenStack, and RPC API is the remote call API of a certain functional module;

[0086] Nova Conductor is a service in the OpenStack Nova component. It serves as the middleware between Nova-Compute and the database, processes Nova-Compute's CRUD operations on the database, and provides API services to the outside world through RPC.

[0087] Nova Scheduler is one of the core components of OpenStack Nova. It is responsible for finding suitable computing nodes for creating / starting virtual machine instances and checking whether the physical resources at the destination are sufficient when the virtual machine is migrated.

[0088] Dest Node is the destination node, which is the node where the virtual machine or container is currently located;

[0089] Src Node is the source node, that is, the node to which the virtual machine or container will be migrated.

[0090] During the working process, the CLI (command line interface) and the dynamic resource scheduling system are used to send migration requests to the Nova API; and the requested_numa_nodes parameter is used to specify the NUMA node number that needs to be migrated to the destination host; after receiving the migration request, the Nova API performs basic verification, and then converts and merges the migration request parameters and other parameters required for migration and sends them to Nova Conductor; Nova Conductor is an execution tracking component for long-term tasks, and it will go to the Nova Scheduler (resource scheduler) to request a suitable resource node; Nova Scheduler will call the NUMAFit algorithm to match NUMA resources and screen suitable hosts; after Nova Conductor obtains the scheduling resources, it will go to the destination node (Dest Node) to confirm whether the resources can be migrated, and obtain detailed information on the migration, including NUMA topology information; this process will also call the NUMA Fit algorithm to match NUMA resources; in the NUMA Fit algorithm logic, the requested_numa_nodes parameter will be used to verify whether the NUMA cells set matches, and only when the serial number value matches completely will the subsequent resource data matching logic continue; finally, after confirming that the resources can be migrated, the Dest Node and Src Migrate virtual machines between Nodes.

[0091] For example Figure 5 and Figure 6 As shown in the figure, there are two computing nodes Compute A and B, each with two NUMA nodes, each NUMA node has 16 vcpu (c for short), NUMA0 and NUMA1 of machine A have been allocated 12c, and NUMA0 and NUMA1 of machine B have been allocated 8c. If the virtual machine specification stipulates that the 8c host should be allocated to one NUMA node, according to the current resource allocation, two 8c cloud hosts can be allocated. Although there are 8 vcpu resources on Compute A, they cannot be allocated. At this time, the two 4c virtual machines on Compute A can be actively migrated to NUMA0 or NUMA1 of Compute B at the same time, so that three more 8c cloud hosts can be allocated.

[0092] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

[0093] The preferred embodiments of the present invention disclosed above are only used to help explain the present invention. The preferred embodiments do not describe all the details in detail, nor do they limit the invention to only specific implementation methods. Obviously, many modifications and changes can be made according to the content of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the present invention, so that those skilled in the art can understand and use the present invention well. The present invention is limited only by the claims and their full scope and equivalents.

Claims

1. A method for specifying NUMA nodes to implement virtual machine migration. It is characterized in that The steps include: S01. Send a migration request to the Nova API through the CLI or the dynamic resource scheduling system, and add the requested_numa_nodes parameter to the migration interface of the Nova API. To add the requested_numa_nodes parameter to the Nova API migration interface, follow these steps: Find the relevant code in Nova API that handles migration requests; Find the function or method used to create and send migration task requests in the relevant code; In the current function or method, add a new parameter requested_numa_nodes to receive the NUMA node number specified by the user; In the logic of processing migration requests, the value of the requested_numa_nodes parameter is used to specify the NUMA node number of the target host as needed; S02. After receiving the migration request, Nova API verifies it, converts and merges the migration request parameters and the corresponding parameters required for migration, and sends them to Nova Conductor. S03, Nova Conductor goes to Nova Scheduler to request a suitable resource node. NovaScheduler calls the NUMA Fit algorithm to match NUMA resources and select the host. S04. After Nova Conductor obtains the scheduling resources, it goes to the destination node to confirm whether the resources can be migrated. After confirming the migration, it obtains detailed migration information to achieve the purpose of placing the virtual machine with the specified NUMA node number.

2. The method for implementing virtual machine migration by specifying a NUMA node according to claim 1, It is characterized in that After Nova API receives a migration request, it verifies it as follows: Confirm that all required parameters are included in the request; Get the current status of the instance involved in the request; Based on the information of the target host in the request, check whether its resources meet the instance requirements; Perform health checks on the instances to ensure that they are not in an error state or have any failures; Verify that the source and destination networks are reachable and check that the network configuration matches the information in the request; Verify that the client has sufficient permissions to perform the migration operation.

3. The method for implementing virtual machine migration by specifying a NUMA node as claimed in claim 2, It is characterized in that The NovaConductor is an execution tracking component for long-duration tasks, responsible for coordinating and managing the task execution and tracking of database operations.

4. The method for implementing virtual machine migration by specifying a NUMA node as claimed in claim 3, It is characterized in that The logic of NUMA resource matching is as follows: Start NUMA allocation and fully arrange the host NUMA cells according to the number of NUMA nodes of the instance requested to migrate; arrange the obtained cells in random order; Traverse the above random order arrangement and define an empty mismatch set to record numacel ls that do not meet the requested instance resource requirements; Determine whether the random order arrangement has been traversed; if the judgment result is yes, the allocation fails and the current host does not meet the NUMA requirements; if the judgment result is no, continue to determine whether the random order arrangement is consistent with the specified numa arrangement, that is, check according to the requested_numa_nodes parameter to determine whether the sequence number value completely matches; if the judgment result is inconsistent, repeat the step of determining whether the random order arrangement has been traversed; If the judgment result is consistent, continue to judge whether the random order contains the mismatched cell l; if the judgment result is included, continue to traverse the next order and repeat the step of judging whether the random order traversal is completed; if the judgment result is not included, match all the numa cells in the order with the instance resource requirements, find out the mismatched cells and add them to the mismatch; It is determined whether all cells in the current random order are matched. If so, the NUMA combination of the arrangement is allocated to the virtual machine. If not, the step of determining whether the random order is traversed is repeated.

5. The method for implementing virtual machine migration by specifying a NUMA node as claimed in claim 4, It is characterized in that After NovaConductor obtains the scheduling resources, the steps to go to the destination node to confirm whether the resources can be migrated are as follows: After Nova Conductor obtains the scheduling resources, it sends the resource information to the destination node; After receiving the resource information, the destination node will perform a resource availability check to confirm whether the node has sufficient resources to support instance migration; Nova Conductor determines whether the resource can be migrated based on the confirmation information or error information of the destination node. If it can be migrated, Nova Conductor obtains the relevant migration information again. If it cannot be migrated, the resource is placed back to the original node and Nova Conductor is notified; After Nova Conductor receives the notification of resource release, it will reschedule the resources and send the new resource information to the destination node; After the destination node receives the resource information again, it will repeat the above steps until the resources are successfully migrated to the destination node.

6. The method for implementing virtual machine migration by specifying a NUMA node as claimed in claim 5, It is characterized in that The detailed migration information includes the following: NUMA topology information, source node information, destination node information, virtual machine status, memory data, and device status information.

7. Specify the NUMA node to implement the device for virtual machine migration. It is characterized in that include: Migration request interface extension module, used to send migration requests to Nova API through CLI or dynamic resource scheduling system, and add requested_numa_nodes parameter in Nova API migration interface; To add the requested_numa_nodes parameter to the Nova API migration interface, follow these steps: Find the relevant code in Nova API that handles migration requests; Find the function or method used to create and send migration task requests in the relevant code; In the current function or method, add a new parameter requested_numa_nodes to receive the NUMA node number specified by the user; In the logic of processing migration requests, the value of the requested_numa_nodes parameter is used to specify the NUMA node number of the target host as needed; The migration request processing module is used to verify the migration request after the Nova API receives it, and then convert and merge the migration request parameters with the corresponding parameters required for migration and send them to Nova Conductor; The resource scheduling module is used to request the appropriate resource node from the Nova Scheduler resource scheduler through Nova Conductor, and call the NUMA Fit algorithm through Nova Scheduler to perform NUMA resource matching and select the host; The migration confirmation module is used to confirm whether the resources can be migrated at the destination node after Nova Conductor obtains the scheduling resources, and obtain detailed migration information after confirming the migration, so as to achieve the purpose of placing the virtual machine at the specified NUMA node number.

8. A system for implementing virtual machine migration by specifying a NUMA node, for implementing the method for implementing virtual machine migration by specifying a NUMA node as described in any one of claims 1 to 6, It is characterized in that Includes CLI, dynamic resource scheduling system, Nova API, Nova Conductor, Nova Scheduler, Dest Node, and Src Node.

9. The system for implementing virtual machine migration by specifying a NUMA node as claimed in claim 8, It is characterized in that The CLI and dynamic resource scheduling system send a migration request to the Nova API. After receiving the migration request, the Nova API converts and merges the migration request parameters and other parameters required for migration and sends them to Nova Conductor. Nova Conductor calls the NUMA Fit algorithm through the Nova Scheduler to perform NUMA resource matching and screen suitable hosts. After confirming that the resources can be migrated, it migrates the virtual machine between the DestNode and the Src Node.