CN106033373B - A virtual machine resource scheduling method and scheduling system in a cloud computing platform - Google Patents

Abstract

The invention discloses resources of virtual machine dispatching methods in a kind of cloud computing platform, comprising the following steps: S10 obtains resource situation information of the distribution in physical machine, generates physical machine the Resources list；S20 is ranked up physical machine according to the virtual machine quantity created in each physical machine, generates physical machine sorted lists；S30 is compared resources of virtual machine to be created with physical resource remaining in each physical machine, generates physical machine list to be allocated；S40 chooses physical machine from physical machine list to be allocated, and creates virtual machine in the physical machine.Meanwhile the invention also discloses resources of virtual machine in a kind of cloud computing platform to dispatch system, including physical machine the Resources list generation module, physical machine sorted lists generation module, physical machine List Generating Module to be allocated and creation module.The dispatching method and scheduling system overcome the unicity of existing resources of virtual machine scheduling, improve the high availability of virtual machine.

Description

A virtual machine resource scheduling method and scheduling system in a cloud computing platform

technical field

The invention relates to the field of cloud computing, in particular to a virtual machine resource scheduling method and a scheduling system in a cloud computing platform.

Background technique

The operating system of a cloud computing center usually includes the following modules: large-scale basic software and hardware management, virtual computing management, distributed file system, business/resource scheduling management, security management and control, etc. Resource management is the core issue of cloud computing system. In the field of cloud computing infrastructure as a service, the engineering of cloud computing is still full of difficulties, and relevant technical personnel have not found an operable system architecture and implementation plan. At present, the cloud computing infrastructure solutions proposed by technical personnel have not focused on the optimization technology of resource scheduling in the cloud computing infrastructure. The effectiveness and acceptability of a cloud computing resource management system depends heavily on the implemented resource scheduling system. The resources in the cloud computing system are highly dynamic. According to the actual resource usage requirements, choosing an appropriate scheduling method in real time is the guarantee to ensure that the resources are fully and effectively utilized. However, the existing cloud computing operating system resource scheduling method does not consider the project type and business type of the virtual machine, and has a single nature, so resource scheduling cannot be performed flexibly.

Contents of the invention

Technical problem: The technical problem to be solved by the present invention is to provide a virtual machine resource scheduling method and a scheduling system in a cloud computing platform, which overcomes the singleness of the existing virtual machine resource scheduling and improves the high availability of the virtual machine.

Technical solution: In order to solve the above-mentioned technical problems, on the one hand, the present invention provides a virtual machine resource scheduling method in a cloud computing platform, comprising the following steps: S10 obtains resource status information allocated on a physical machine, and generates a physical machine resource list; S20 according to The number of created virtual machines on each physical machine sorts the physical machines to generate a sorted list of physical machines; S30 compares the virtual machine resources to be created with the remaining physical resources on each physical machine to generate a list of physical machines to be allocated; Select a physical machine from the machine list, and create a virtual machine on the physical machine.

As an embodiment, in the above S10, the physical machine resource list contains the universal unique identification code of the physical machine, the number of virtual machines created on the physical machine, and the remaining physical resources on the physical machine, the remaining physical resources include CPU, disk and memory.

As an embodiment, in S20, the process of generating the sorted list of physical machines is as follows: first, according to the business type of the virtual machine to be created, according to the virtual machine with the same business type as the virtual machine to be created that has been created on the physical machine According to the number of physical machines, sort the physical machines from small to large; secondly, if the number of virtual machines with the same service type created on the physical machines is equal, the number of virtual machines with the same item type as the virtual machine to be created on the physical machine , sort the physical machines from small to large; finally, if the number of created virtual machines with the same item type on the physical machines is equal, then sort the physical machines randomly.

As an embodiment, in the above S30, the process of generating the list of physical machines to be allocated is as follows: first, query the physical machine resource list according to the universal unique identification code of the physical machine, and combine the remaining physical resources on each physical machine with the virtual machine to be created Compare the physical resources that need to be consumed. If the former is less than the latter, filter out the physical machine from the physical machine sorting list. If the former is greater than or equal to the latter, keep the physical machine in the physical machine sorting list; The physical machines reserved in the sorted list of physical machines generate a list of physical machines to be allocated; this list contains physical machines that can be allocated.

As an embodiment, in S40, the first physical machine is selected from the list of physical machines to be allocated, and a virtual machine is created on it.

On the other hand, the present invention also provides a virtual machine resource scheduling system in a cloud computing platform, the scheduling system includes: a physical machine resource list generating module, configured to obtain resource status information allocated on a physical machine, and generate a physical machine resource list; The physical machine sorting list generation module is used to sort the physical machines according to the number of virtual machines created on the physical machines to generate a physical machine sorting list; the physical machine list generation module to be allocated is used to link the virtual machine resources to be created with each physical machine Comparing the remaining physical resources to generate a list of physical machines to be allocated; creating a module for selecting a physical machine from the list of physical machines to be allocated and creating a virtual machine on the physical machine.

As an embodiment, the physical machine sorting list generating module includes: a first physical machine sorting list generating submodule, configured to, according to the business type of the virtual machine to be created, sort the virtual machines that have been created on the physical machine and the virtual machines to be created The number of virtual machines with the same business type, sort the physical machines from small to large; the second physical machine sorting list generates a submodule, which is used when the number of virtual machines with the same business type created on the physical machine is equal, then sort the physical machines according to the number of virtual machines on the physical machine The number of virtual machines with the same item type as the virtual machine to be created has been created, and the physical machines are sorted from small to large; the third physical machine sort list generates a submodule, which is used when the virtual machine with the same item type has been created on the physical machine If the number of machines is equal, the physical machines are randomly arranged.

As an embodiment, the module for generating the list of physical machines to be allocated includes: a query sub-module: used to query the physical machine resource list according to the universal unique identification code of the physical machine, and find out the remaining physical resources on each physical machine; the comparison sub-module Module: used to compare the remaining physical resources on the physical machine with the physical resources required to be consumed by the virtual machine to be created; sub-module selection: when the remaining physical resources on the physical machine are less than the physical resources required to be consumed by the virtual machine to be created, then Filter the physical machine from the sorted list of physical machines; if the remaining physical resources on the physical machine are greater than or equal to the physical resources to be consumed by the virtual machine to be created, then reserve the physical machine in the sorted list of physical machines; generate submodules: use Based on the physical machines reserved in the physical machine sorting list, a list of physical machines to be allocated is generated.

Beneficial effects: compared with the prior art, the present invention has the following beneficial effects: the present invention sorts the physical machines according to the number of created virtual machines on each physical machine, generates a sorted list of physical machines, and then selects from the list to create a virtual machine. The physical machine of the machine. By setting the physical machine sorting list, the physical machines are sorted according to the number of virtual machines of the same business type or project type, from small to large, so that the physical machines with different business types or project types from the virtual machine to be created are prioritized in the front. In this way, the singleness of resource scheduling of the existing virtual machine is overcome, and the high availability of the virtual machine is improved.

Description of drawings

Fig. 1 is a frame diagram of an application structure of the present invention.

Fig. 2 is a flowchart of Embodiment 1 of the present invention.

Fig. 3 is a system structure block diagram of Embodiment 2 of the present invention.

Fig. 4 is a structural block diagram of a physical machine ranking list generation module in Embodiment 2 of the present invention.

Fig. 5 is a structural block diagram of a module for generating a list of physical machines to be allocated in Embodiment 2 of the present invention.

Detailed ways

The technical solutions of the present invention will be discussed in detail below in conjunction with the accompanying drawings and embodiments.

Example 1

As shown in FIG. 1 , it is a frame diagram of an application structure of the present invention. In Figure 1, the server communicates with each physical machine, and a virtual machine (VM) runs on the physical machine. The server is responsible for collecting information about virtual machines on each physical machine, such as the number of virtual machines, remaining CPU, remaining memory, and remaining disk space. The server selects on which physical machine to create the virtual machine according to the scheduling method of the present invention.

As shown in Figure 2, a virtual machine resource scheduling method in a cloud computing platform includes the following steps:

S10 acquires resource status information allocated on the physical machine, and generates a physical machine resource list;

S20 sorts the physical machines according to the number of created virtual machines on each physical machine, and generates a sorted list of physical machines;

S30 compares the virtual machine resources to be created with the remaining physical resources on each physical machine, and generates a list of physical machines to be allocated;

S40 selects a physical machine from the list of physical machines to be allocated, and creates a virtual machine on the physical machine.

In S10, the physical machine resource list contains the physical machine's universally unique identifier (corresponding to the English abbreviation: UUID), the number of virtual machines created on the physical machine, and the remaining physical resources on the physical machine. By creating a physical machine resource list, the status of each running physical machine can be obtained. The remaining physical resources include the remaining CPU, remaining disk, and remaining memory of the physical machine. The virtual machine to be created also needs to consume CPU, disk, and memory, so the remaining physical resources on the physical machine must meet the physical resources consumed by the virtual machine to be created. Only when this condition is met can a virtual machine be created on the physical machine. Before comparing the physical resources, in step S10 of the present invention, a physical machine resource list is generated, and the remaining physical resource information on each running physical machine is stored in the table.

As a preferred solution, in S20, the process of generating the sorted list of physical machines is as follows: first, according to the business type of the virtual machine to be created, according to the number of virtual machines with the same business type as the virtual machine to be created on the physical machine , sort the physical machines from small to large; secondly, if the number of virtual machines with the same service type created on the physical machines is equal, then according to the number of virtual machines that have Sort the physical machines to the largest; finally, if the number of created virtual machines with the same item type on the physical machine is equal, the physical machines are sorted randomly.

In the above preferred solution, firstly, the sorting of physical machines is determined according to the type of business, and then the sorting of physical machines is determined according to the type of project, and finally, when the business type and project type are the same, and the number of virtual machines running on each physical machine is also the same , in random order. For example, as shown in Table 1, there are three physical machines running, and the resource status of each physical machine is shown in Table 1.

The resource status of the virtual machine to be created is shown in Table 2.

When the virtual machine to be created is the virtual machine 1 to be created in Table 2, the generation process of the physical machine sorting list is as follows: first, according to the service type of the virtual machine 1 to be created, the physical machine 1 is the same as the virtual machine 1 to be created The number of virtual machines of the service type is 3, the number of virtual machines of the same service type on physical machine 2 as virtual machine 1 to be created is 0, and the number of virtual machines of the same service type on physical machine 3 as virtual machine 1 to be created is 4 , the sorted list of physical machines is physical machine 2, physical machine 1, and physical machine 3.

When the virtual machine to be created is the virtual machine 2 to be created in Table 2, the generation process of the physical machine sorting list is as follows: first, according to the business type of the virtual machine 2 to be created, the physical machine 1 is the same as the virtual machine 2 to be created The number of virtual machines of the service type is 3, the number of virtual machines of the same service type on physical machine 2 as virtual machine 2 to be created is 3, and the number of virtual machines of the same service type on physical machine 3 as virtual machine 2 to be created is 0 . Because the number of virtual machines of the same service type as the virtual machine 2 to be created on the physical machine 1 and the physical machine 2 is equal, the physical machine 1 and the physical machine 2 are sorted according to the item type of the virtual machine 2 to be created. The number of virtual machines of the same project type as the virtual machine 2 to be created on physical machine 1 is 1, and the number of virtual machines of the same project type as the virtual machine 2 to be created on physical machine 2 is 3. Therefore, for the virtual machine 2 to be created, the sorted list of physical machines is physical machine 3, physical machine 1, and physical machine 2.

In S20, the physical machines are sorted from small to large according to the business type and project type of the virtual machine to be created, and according to the number of virtual machines of the same business type or project type. In this way, according to the sorted list of physical machines obtained according to the condition, the virtual machine to be created will be allocated as much as possible on the physical machine having a different service type or project type from the virtual machine to be created. As shown in Table 2, when the virtual machine 1 to be created is created on the physical machine 2, the original virtual machine on the physical machine 2 has no Web service type. When the virtual machine 2 to be created is created on the physical machine 3, the original virtual machine on the physical machine 3 does not have the MQ service type. In this way, virtual machines of the same type (business type or project type) will not be built on the same physical machine as far as possible, thus ensuring high availability. When a physical machine goes down, the virtual machines on other normal physical machines have the same business type or project type as the downtime virtual machine, which can ensure the normal operation of the business and ensure the high availability of the entire system .

Project types such as workflow engine, push platform, cloud disk system, etc. Business types such as webpage (Web), application program (App), database (DB), cache (Cache), message queuing (MQ), etc.

In S30, the process of generating the list of physical machines to be allocated is as follows: first query the list of physical machine resources according to the universal unique identification code of the physical machine, and compare the remaining physical resources on each physical machine with the physical resources required to be consumed by the virtual machine to be created , if the former is smaller than the latter, filter out the physical machine from the physical machine sorting list, if the former is greater than or equal to the latter, then keep the physical machine in the physical machine sorting list; finally, the physical machine kept in the physical machine sorting list The machine generates a list of physical machines to be allocated; the list contains physical machines that can be allocated. Physical resources refer to CPU, disk, and memory.

In the foregoing Table 2, the CPU of the virtual machine 1 to be created is 2 cores, the occupied disk is 1T, and the occupied memory is 2G. The remaining CPU, disk, and memory on physical machine 2, physical machine 1, and physical machine 3 are larger than the CPU, disk, and memory required by virtual machine 1 to be created. Therefore, the virtual machine 1 to be created can be created on the physical machine 2 , the physical machine 1 , and the physical machine 3 . The generated list of physical machines to be allocated is physical machine 2, physical machine 1, and physical machine 3.

The CPU of virtual machine 2 to be created has 2 cores, the occupied disk is 1T, and the occupied memory is 3.5G. The remaining CPU, disk, and memory on physical machine 1 and physical machine 3 are larger than the CPU, disk, and memory required by virtual machine 2 to be created. The remaining memory of the physical machine 2 is smaller than the memory required by the virtual machine 2 to be created. Therefore, the virtual machine 2 to be created cannot be created on the physical machine 2. The generated list of physical machines to be allocated is physical machine 3 and physical machine 1.

The virtual machine to be created needs to occupy physical resources, so there must be enough physical resources for the virtual machine to be created on the finally selected physical machine. In step S10, the physical machine resource list contains remaining physical resources on the physical machine. Step S20 sorts all physical machines connected to the server. In this sorting, the physical machines that have different service types or project types from the virtual machines to be created are placed in the front as the preferred physical machines. However, not all physical machines in the sorted list of physical machines have sufficient physical resources for the virtual machines to be created. The purpose of step S30 is to filter the physical machines whose remaining physical resources cannot satisfy the virtual machine to be created from the sorted list of physical machines. In this embodiment, firstly, the physical machine resource list is queried according to the universal unique identification code of the physical machine, and the remaining physical resources on each physical machine are compared with the physical resources consumed by the virtual machine to be created. The physical machines that can meet the needs of creating virtual machines are kept in the sorted list of physical machines, and the physical machines that cannot meet the needs of creating virtual machines are filtered from the sorted list of physical machines to generate a list of physical machines to be allocated. The list contains available physical machines. That is to say, all physical machines in the list of physical machines to be allocated can be used to create virtual machines. However, as a preferred method, the first physical machine is selected from the list of physical machines to be allocated to create a virtual machine. After sorting in step S20 and filtering and retaining in step S30, the first physical machine in the list of physical machines to be allocated has the greatest possibility of having a business type or project type different from that of the virtual machine to be created. Distributing virtual machines of the same business type or project type on different physical machines is conducive to high system availability.

When resource scheduling is performed in the prior art, business types and project types are not considered, resulting in that virtual machines of the same business type or project type are likely to be built on the same physical machine. In this embodiment, the physical machine is selected by comparing the remaining physical resources of the physical machine with the physical resources consumed by the virtual machine, not only comparing the physical resources, but also including the judgment of the service type and project type, so as to ensure high availability.

Example 2

As shown in Figure 3, a virtual machine resource scheduling system in a cloud computing platform includes:

The physical machine resource list generation module is used to obtain resource status information allocated on the physical machine and generate a physical machine resource list;

The physical machine sorting list generation module is used to sort the physical machines according to the number of virtual machines created on the physical machine, and generate the physical machine sorting list;

The module for generating a list of physical machines to be allocated is used to compare the virtual machine resources to be created with the remaining physical resources on each physical machine to generate a list of physical machines to be allocated;

The creation module is used to select a physical machine from the list of physical machines to be allocated, and create a virtual machine on the physical machine.

The physical machine resource list generation module includes the universal unique identification code of the physical machine, the number of created virtual machines on the physical machine, and the remaining physical resources on the physical machine, including CPU, disk and memory. Physical resources refer to CPU, disk, and memory.

As shown in Figure 4, the physical machine sorting list generating module includes: a first physical machine sorting list generating submodule, which is used to select each physical machine with the same business type as the virtual machine to be created according to the business type of the virtual machine to be created. Machines are sorted from small to large according to the number of virtual machines created on the physical machine.

The second physical machine sorting list generation submodule is used for when the number of created virtual machines on the physical machine with the same service type is equal, according to the item type of the virtual machine to be created, the virtual machine has the same item type as the virtual machine to be created The physical machines in , are sorted according to the number of virtual machines created on the physical machines, from small to large.

The third physical machine sorting list generation submodule is used for randomly sorting the physical machines when the number of created virtual machines on the physical machines with the same item type is equal.

By setting three physical machine sorting list generation sub-modules, all physical machines are sorted, and the generated physical machine sorting list is generated. The physical machine sorting list generation module sequentially sorts the physical machines from small to large according to the business type and project type of the virtual machine to be created, and according to the number of virtual machines of the same business type or project type. In this way, according to the sorted list of physical machines obtained according to the condition, the virtual machine to be created will be allocated as much as possible on the physical machine having a different service type or project type from the virtual machine to be created. In this way, virtual machines of the same type (business type or project type) should not be built on the same physical machine as far as possible, thus ensuring high availability. When a physical machine goes down, the virtual machines on other normal physical machines have the same business type or project type as the downtime virtual machine, which can ensure the normal operation of the business and ensure the high availability of the entire system .

The existing scheduling system only determines whether to create a virtual machine according to whether the physical resources are sufficient. However, in the scheduling system of the present invention, whether to create a virtual machine is determined not only according to physical resources, but also according to business type and project type, and the granularity is higher. The present invention schedules physical resources in a more fine-grained manner, and utilizes physical resources reasonably.

As shown in Figure 5, the generation module of the list of physical machines to be allocated includes:

Query sub-module: used to query the physical machine resource list according to the universal unique identification code of the physical machine, and find out the remaining physical resources on each physical machine.

Comparison sub-module: used to compare the remaining physical resources on the physical machine with the physical resources to be consumed by the virtual machine to be created.

Select sub-module: When the remaining physical resources on the physical machine are less than the physical resources required to be consumed by the virtual machine to be created, filter out the physical machine from the physical machine sorting list, if the remaining physical resources on the physical machine are greater than or equal to the virtual machine to be created If the physical resources required by the machine are not available, the physical machine will be reserved in the sorted list of physical machines.

Generate sub-module: used to sort the physical machines reserved in the list of physical machines, and generate a list of physical machines to be allocated.

Every physical machine has a universally unique identifier. The query sub-module queries the remaining physical resources on the physical machine from the list of physical machine resources through the universal unique identification code. This lays the groundwork for comparing the work of the submodules. The comparison submodule is used to compare the remaining physical resources on the physical machine found by the query submodule with the physical resources required to be consumed by the virtual machine to be created. When the remaining physical resources on the physical machine are less than the physical resources required to be consumed by the virtual machine to be created, the selection module filters out the physical machine from the sorted list of physical machines. When the remaining physical resources on the physical machine are greater than or equal to the physical resources required to be consumed by the virtual machine to be created, the selection module reserves the physical machine in the sorted list of physical machines. After the filtering and retaining operations, the physical machines in the sorted list of physical machines are not exactly the same as the physical machines in the sorted list of physical machines generated in step S20. After the filtering and reservation operations, the sorted list of physical machines is generated, and the list of physical machines to be allocated is generated by the generating submodule. The creation module selects the first physical machine from the list of physical machines to be allocated generated by the generation sub-module, and creates a virtual machine on the physical machine.

After sorting all physical machines by the physical machine sorting list generation module and filtering and retaining the physical machines by the physical machine list generation module to be allocated, the physical machine ranks first in the physical machine list to be allocated, and has the same virtual machine to be created Different business types or project types are most likely. The creation module selects the first physical machine from the list of physical machines to be allocated generated by the generation sub-module to create a virtual machine. In this way, the virtual machines of the same business type or project type are distributed on different physical machines, which is beneficial to the high availability of the system.

In the dispatching system of the present invention, the physical machine sorting list generation module sequentially sorts the physical machines from small to large according to the business type and project type of the virtual machine to be created, and according to the number of virtual machines of the same business type or project type. In this way, the physical machine that has a different service type or project type from the virtual machine to be created is prioritized in the front row.

The module for generating the list of physical machines to be allocated compares the remaining physical resources on each physical machine with the physical resources consumed by the virtual machine to be created. If the former is smaller than the latter, the physical machine is filtered out from the physical machine sorting list. If If the former is greater than or equal to the latter, the physical machine is reserved in the physical machine sorting list; finally, the physical machines reserved in the physical machine sorting list are generated into a list of physical machines to be allocated. The sorting order of the physical machines in the list of physical machines to be allocated is the same as the order in which they are arranged in the sorting list of physical machines. The creating module selects the first physical machine from the list of physical machines to be allocated, and creates a virtual machine on the physical machine. In this way, virtual machines of the same type (business type or project type) will not be built on the same physical machine as far as possible, thus ensuring high availability. When a physical machine goes down, the virtual machines on other normal physical machines have the same business type or project type as the downtime virtual machine, which can ensure the normal operation of the business and ensure the high availability of the entire system .

Those skilled in the art should know that the methods or systems for implementing the above embodiments may be implemented by computer program instructions. The computer program instructions are loaded into a programmable data processing device, such as a computer, so that the corresponding instructions are executed on the programmable data processing device, so as to realize the functions realized by the methods or systems of the above embodiments.

Those skilled in the art may make non-inventive technical improvements to the present application based on the above embodiments without departing from the spirit of the present invention. These improvements should still be considered within the protection scope of the claims of the present application.

Claims (8)

1. a virtual machine resource scheduling method in a cloud computing platform, characterized in that, the scheduling method comprises the following steps: S10 acquires resource status information allocated on the physical machine, and generates a physical machine resource list; S20 sorts the physical machines according to the number of virtual machines that have been created on each physical machine, and generates a physical machine sorting list; in the S20, the process of generating the physical machine sorting list is: first, according to the business type of the virtual machine to be created, Sort the physical machines from small to large according to the number of created virtual machines with the same service type as the virtual machine to be created on the physical machine; secondly, if the number of created virtual machines with the same service type on the physical machine is equal, sort them according to the physical The number of virtual machines with the same item type as the virtual machine to be created has been created on the machine, and the physical machines are sorted from small to large; finally, if the number of virtual machines with the same item type created on the physical machine is equal, the physical machines are sorted random order; S30 compares the virtual machine resources to be created with the remaining physical resources on each physical machine, and generates a list of physical machines to be allocated; S40 selects a physical machine from the list of physical machines to be allocated, and creates a virtual machine on the physical machine. 2. According to the method for scheduling virtual machine resources in the cloud computing platform according to claim 1, it is characterized in that, in said S10, the physical machine resource list contains the universal unique identification code of the physical machine, the created virtual machine on the physical machine quantity, and the remaining physical resources on the physical machine, including CPU, disk, and memory. 3. The virtual machine resource scheduling method in the cloud computing platform according to claim 1, wherein in said S30, the process of generating a list of physical machines to be allocated is: first querying the physical machine according to the universal unique identification code of the physical machine machine resource list, compare the remaining physical resources on each physical machine with the physical resources consumed by the virtual machine to be created, if the former is less than the latter, filter the physical machine from the sorted list of physical machines, if the former is greater than or equal to the latter Otherwise, the physical machine is reserved in the physical machine sorting list; finally, the physical machine reserved in the physical machine sorting list is generated into a list of physical machines to be allocated. 4. According to the virtual machine resource scheduling method in the cloud computing platform described in any one of claims 1 to 3, it is characterized in that, in said S40, select the first physical machine from the list of physical machines to be allocated. machine and create a virtual machine on it. 5. A virtual machine resource scheduling system in a cloud computing platform, characterized in that the scheduling system includes: The physical machine resource list generation module is used to obtain resource status information allocated on the physical machine and generate a physical machine resource list; The physical machine sorting list generation module is used to sort the physical machines according to the number of virtual machines created on the physical machine, and generate the physical machine sorting list; The module for generating a list of physical machines to be allocated is used to compare the virtual machine resources to be created with the remaining physical resources on each physical machine to generate a list of physical machines to be allocated; Create a module for selecting a physical machine from the list of physical machines to be allocated, and create a virtual machine on the physical machine; The physical machine sorting list generating module includes: a first physical machine sorting list generating submodule, configured to, according to the service type of the virtual machine to be created, according to the virtual machine that has been created on the physical machine and has the same business type as the virtual machine to be created The number of machines, sort the physical machines from small to large; The second physical machine sorting list generates a submodule, which is used for when the number of virtual machines with the same service type created on the physical machine is equal, according to the number of virtual machines with the same item type as the virtual machine to be created on the physical machine, from small Sort the physical machines to the largest; The third physical machine sorting list generation submodule is used for randomly sorting the physical machines when the number of virtual machines with the same item type created on the physical machines is equal. 6. The virtual machine resource scheduling system in the cloud computing platform according to claim 5, wherein the physical machine resource list contains the universal unique identification code of the physical machine, the number of virtual machines created on the physical machine, and the number of virtual machines on the physical machine. The remaining physical resources include CPU, disk, and memory. 7. according to the virtual machine resource dispatching system in the cloud computing platform of claim 5, it is characterized in that, described to-be-allocated physical machine list generation module comprises: Query sub-module: used to query the physical machine resource list according to the universal unique identification code of the physical machine, and find out the remaining physical resources on each physical machine; Comparison sub-module: used to compare the remaining physical resources on the physical machine with the physical resources to be consumed by the virtual machine to be created; Select sub-module: When the remaining physical resources on the physical machine are less than the physical resources consumed by the virtual machine to be created, filter the physical machine from the sorted list of physical machines; if the remaining physical resources on the physical machine are greater than or equal to the virtual machine to be created When the physical resources needed to be consumed are required, the physical machine is reserved in the physical machine sorting list; Generate sub-module: used to sort the physical machines reserved in the list of physical machines to generate a list of physical machines to be allocated. 8. According to the virtual machine resource scheduling system in the cloud computing platform described in any one of claims 5 to 7, it is characterized in that the creation module is used to select the first place in the list of physical machines to be allocated physical machine and create a virtual machine on that physical machine.