CN115700481A - Resource management method and related equipment of public cloud data center - Google Patents

Abstract

The present application provides a resource management method and related equipment of a public cloud data center. The method includes the following steps: the cloud management platform records resource pool information, wherein the resource pool information is used to record each hardware resource pool in the public cloud data center. The resource occupied by the virtual instance that each physical server needs to run and the instance type of the virtual instance that each physical server needs to run. The instance type includes on-demand instance type and reserved instance type. The virtual instance of the reserved instance type is dispatched to at least one physical server, so that the physical server associated with the virtual instance of the reserved instance type can be used by the virtual instance of the on-demand instance type before scheduling. The method can reduce the resource fragmentation of the public cloud and improve the resource utilization rate of the public cloud without affecting the use of users.

Description

Resource management method and related equipment of public cloud data center

technical field

This application relates to the field of cloud computing, in particular to a resource management method and related equipment of a public cloud data center.

Background technique

With the rapid development of cloud computing technology and various network infrastructures, the traditional Internet technology (Internet Technology, IT) business architecture is gradually being dispatched to the public cloud, and more and more business applications are also redesigned and used based on the public cloud architecture . Through the public cloud, users can send resource acquisition requests to the cloud management platform of the public cloud. The cloud management platform screens and analyzes the resources in the hardware resource pool according to the resource requests, finds out suitable physical servers and performs resource deduction on them , to create a corresponding resource carrier, and the user can connect to the resource carrier at any time, place, and use different terminal devices to perform business processing.

However, a physical server includes a variety of resources, the number of each resource and the ratio between resources are fixed, and the specifications of the resources requested by users are not fixed. For example, the CPU and memory ratio of a physical server is 1:1. Specifically, it can be 2 cores and 2 GB memory. The CPU and memory ratio of the resource requested by the user is 1:2. Specifically, it can be 1 core and 2 GB memory. remaining. These remaining resources cannot be used to create other resource carriers, and will be reserved in physical servers in the form of resource fragments. For public clouds with a large number of physical servers, the resource fragments on each physical server will lead to resource fragmentation in the public cloud. Waste, low resource utilization, and increased operating costs of the public cloud.

Contents of the invention

The present application provides a resource management method of a public cloud data center and related equipment, which are used to solve the problem of waste of public cloud resources due to resource fragmentation and reduce the operating cost of the public cloud.

In the first aspect, a method for resource management of a public cloud data center is provided, the method is applied to a cloud management platform of a public cloud data center, and the method may include the following steps: the cloud management platform records resource pool information, wherein the resource pool The information is used to record the resources occupied by the virtual instances that each physical server needs to run in the hardware resource pool of the public cloud data center and the instance type of the virtual instances that each physical server needs to run. The instance types include on-demand instance types and Reserved instance type, the cloud management platform centrally schedules the virtual instance of the reserved instance type to at least one physical server in the resource pool information, so that the physical server associated with the virtual instance of the reserved instance type Virtual instances of the required instance type are used.

In the specific implementation, the virtual instance of the above-mentioned on-demand instance type refers to the virtual instance that can be used after the user pays. The virtual instance to use. For example, if a user pays for a virtual machine with specification X on June 1 and chooses to reserve it for 3 months, then the user can use the virtual machine with specification X after September 1. It should be understood that there is a certain deviation between the prices of reserved instances and on-demand instances on the public cloud platform. For example, the price of reserved instances is lower than that of on-demand instances. cost.

In specific implementation, the above-mentioned virtual instance can be a virtual resource, such as a virtual machine or a container, or a physical resource, such as a physical server, or a service resource provided by other public cloud data centers, such as a process, which is not covered by this application. limited.

In a specific implementation, the resource pool information may include resource usage and instance types of multiple physical servers, and the resource usage of each physical server includes the usage of different types of resources. For example, the resource usage of physical server 1 may include CPU resource usage status, memory resource usage, cache resource usage, memory bandwidth usage, network bandwidth resource usage, disk capacity resource usage, GPU resource usage, etc. Among them, the usage of each category of resources can also be described by multiple parameter information. For example, the usage of CPU resources can include the number of CPU cores, CPU model, etc., and the usage of memory resources can further include memory size, remaining capacity of memory, etc. , not one by one examples are given here.

Implementing the method described in the first aspect, the cloud management platform can record the resources occupied by the virtual instances to be run by each physical server in the hardware resource pool of the public cloud data center and the instance type of the virtual instances to be run by each physical server, The system can centrally schedule the reserved instances recorded in the resource pool information, so that the physical servers associated with the virtual instances of the reserved instance type can be used by the virtual instances of the on-demand instance type before scheduling, so that users can In the case of use, reduce the resource fragmentation of the public cloud and improve the resource utilization of the public cloud.

In a possible implementation of the first aspect, the cloud management platform may receive a first virtual instance creation request, the first virtual instance creation request includes the instance type of the first virtual instance, and the instance type of the first virtual instance is on-demand Instance type: the cloud management platform updates the resource pool information, and the updated resource pool information includes the record of the first virtual instance created by the first physical server and the instance type of the first virtual instance, and the cloud management platform sends the created A request for the first virtual instance.

Optionally, the cloud management platform receives a second virtual instance creation request, the second virtual instance creation request includes the instance type of the second virtual instance, and the instance type of the second virtual instance is a reserved instance type; The updated resource pool information includes the record of the second virtual instance created by the second physical server and the instance type of the second virtual instance.

In the above implementation, if the instance type of the virtual instance is a reserved instance, the cloud management platform does not need to send a request to create the virtual instance to the physical server used to create the virtual instance; if the instance type of the virtual instance is an on-demand instance, The cloud management platform needs to send a request for creating the virtual instance to the physical server used to create the virtual instance. It should be understood that since reserved instances will not be used by users during the reserved time, the reserved instances may not be created on the physical server during the reserved time, which can avoid resource waste and improve public cloud resource utilization Rate.

In a possible implementation of the first aspect, when the cloud management platform schedules the reserved instances in the resource pool information, it may schedule one reserved instance, or schedule some reserved instances, or All reserved instances are scheduled, which is not specifically limited in this application. The reserved instances participating in centralized scheduling can be determined according to the number of reserved instances and the number of resource fragments, so that the number of resource fragments recorded in the resource pool information after centralized scheduling can be reduced. Resources used to create virtual instances.

In the above implementation, the cloud management platform can filter out resource fragments and physical servers with reserved instances from the resource pool information, and then schedule the reserved instances to other physical servers that can create the reserved instances, thereby reducing public cloud The number of resource fragments can reduce the operating cost of the public cloud.

In a possible implementation of the first aspect, before the cloud management platform centrally schedules virtual instances of the reserved instance type to at least one physical server in the resource pool information, it may determine the first number of remaining resources recorded in the resource pool information. quantity, the cloud management platform acquires the second quantity of remaining resources of multiple physical servers in the hardware resource pool from the hardware resource pool, and when the ratio between the first quantity and the second quantity is less than or equal to the first threshold, the resource In the pool information, virtual instances of the reserved instance type are centrally scheduled to at least one physical server.

The number of remaining resources may refer to the number of standard virtual instances that can be created. The specifications of standard virtual instances are determined according to the historical virtual machine creation records of the public cloud. The specifications of standard virtual instances may include one or more types of virtual instances Specifications. For example, according to the historical virtual machine creation records of the public cloud, it is determined that the distribution frequency of VM1 and VM2 is relatively high, then the total number of VM1 and VM2 that can be distributed by the remaining resources can be determined according to the remaining resources recorded in the resource pool information, so as to obtain the above-mentioned first Quantity, and then obtain the remaining resources of multiple physical servers in the hardware resource pool from the hardware resource pool, determine the total quantity of VM1 and VM2 that can be distributed by the remaining resources, so as to obtain the above-mentioned second quantity, if the first quantity and the second quantity If the ratio is less than or equal to the first threshold, the cloud management platform can perform centralized scheduling on the reserved instances in the resource pool information.

Optionally, the cloud management platform periodically determines the first quantity of remaining resources recorded in the resource pool information, and then performs centralized scheduling on the reserved instances, where the periodicity may be scheduled at fixed time intervals, or may be It is to schedule the reserved instance after receiving M virtual instance creation requests every time, which is not specifically limited in this application.

Optionally, when the creation of the virtual instance fails, the cloud management platform determines the first quantity of remaining resources recorded in the resource pool information, and then performs centralized scheduling on the reserved instance. Reduce the number of resource fragments in the resource pool information, and retry to process the virtual instance creation request that failed to create before, so as to improve the user experience and the resource utilization of the public cloud.

In the above implementation, the first number is determined based on the resource pool information, and the second number is determined based on the remaining resources of multiple physical servers in the hardware resource pool. The resource pool information additionally records the creation record of the reserved instance. Therefore, the first A number is less than the second number, and the smaller the ratio of the two, it means that the number of resource fragments in the current resource pool information is more, so when the ratio of the first number to the second number is less than or equal to the second threshold, the cloud management The platform schedules the reserved instances, and centrally dispatches the virtual instances of the reserved instance type in the resource pool information to at least one physical server, so that the physical servers associated with the reserved instance type virtual instances before scheduling can be used by the on-demand instance type The use of virtual instances avoids waste of resources and improves the resource utilization of public clouds.

In a possible implementation manner of the first aspect, the reserved instance recorded in the resource pool information not only includes the instance specification, but also includes the reserved time of the reserved instance. When the reserved time of the reserved instance is about to expire, the cloud management platform can send a virtual instance creation request to the physical server where the reserved instance is recorded in the resource pool information, and update the resource pool information.

The above implementation can prevent the user from being unable to use the reserved instance after the reserved time expires, and improve the user experience.

In the second aspect, a cloud management platform is provided, which is applied to the cloud management platform of the public cloud data center. The cloud management platform includes: a recording unit, the recording unit is used to record resource pool information, and the resource pool information is used to record the public cloud data center The resource occupied by the virtual instance that each physical server needs to run in the hardware resource pool and the instance type of the virtual instance that each physical server needs to run. The instance type includes on-demand instance type and reserved instance type; scheduling unit, scheduling The unit is used to centrally schedule the virtual instance of the reserved instance type to at least one physical server in the resource pool information, so that the physical server associated with the virtual instance of the reserved instance type can be available for the virtual instance of the on-demand instance type before scheduling use.

Implement the cloud management platform described in the second aspect, the cloud management platform records the resources that each physical server needs to run on the virtual instance in the hardware resource pool of the public cloud data center and the instances that each physical server needs to run on the virtual instance Type, the resource pool information recorded by the system includes the creation information of the reserved instance, but the physical server of the hardware resource pool will not create the reserved instance, so as to avoid the resources generated by the reserved instance not being used by the user within the reserved time At the same time, the system can also centrally schedule the reserved instances recorded in the resource pool information, so that the physical server associated with the virtual instance of the reserved instance type can be used by the virtual instance of the on-demand instance type before scheduling. It can reduce the resource fragmentation of the public cloud and improve the resource utilization of the public cloud without affecting the use of users.

The second aspect or any implementation of the second aspect is the implementation of the cloud management platform corresponding to the first aspect or any implementation of the first aspect, and the descriptions in the first aspect or any implementation of the first aspect are applicable to the first aspect The second aspect or any implementation manner of the second aspect will not be repeated here.

In a third aspect, a computer program product is provided, which, when running on a computer, causes the computer to execute the methods in the above aspects.

In a fourth aspect, a computer-readable storage medium is provided. Instructions are stored in the computer-readable storage medium. When the computer-readable storage medium is run on a computer, it causes the computer to execute the methods in the above aspects.

According to a fifth aspect, a computing device is provided, and the computing device includes a processor, and the processor is configured to execute the methods described in the foregoing aspects.

According to a sixth aspect, a computer-readable storage medium is characterized in that instructions are stored in the computer-readable storage medium, and when the instructions are run on a processor, they are used to implement the methods described in the above aspects.

On the basis of the implementation manners provided in the foregoing aspects, the present application may further be combined to provide more implementation manners.

Description of drawings

Fig. 1 is a schematic structural diagram of a public cloud system provided by the present application;

Fig. 2 is a schematic diagram of the architecture of a cloud management platform provided by the present application;

FIG. 3 is an exemplary representation of resource pool information provided by the present application;

FIG. 4 is a flow chart of centralized scheduling of reserved instances by resource pool information provided by the present application;

FIG. 5 is a schematic flow chart of a method for resource management of a public cloud data center provided by the present application;

FIG. 6 is a schematic structural diagram of a computing device provided by the present application.

Detailed ways

In order to facilitate the understanding of the technical solution of the present invention, firstly, the application scenario of the "public cloud" involved in the present invention is explained.

Public cloud refers to the computing services provided by third-party providers to users through public networks. Under the public cloud architecture, users can rent resources from the public cloud after paying a certain fee according to their own business application needs, such as renting a virtual machine. After successful payment, users can use different terminal devices at any time and place. Connect with the public cloud for data access, computing and other purposes.

Exemplarily, FIG. 1 is a schematic structural diagram of a public cloud system provided by the present application. The system may include a terminal device 110 and a data center 130 of the public cloud, and the terminal device 110 and the data center 130 of the public cloud pass through a network 120 connect. Wherein, the network 120 may be a public network, such as the Internet (internet).

The terminal device 110 can be a personal computer, a tablet computer, a mobile notebook, a smart phone, a handheld processing device, a virtual reality device, a wearable device, an integrated handheld device, etc. A personal computer is taken as an example for description, but this application does not specifically limit it.

The data center 130 of the public cloud can provide users with shared resource services, and the shared resource services can include OBS services, SFS services, cloud phone (cloud phone) services, content delivery network services (content delivery network, CDN), cloud backup services (cloud backup and recovery, CBR), data management service (data admin service, DAS), etc., this application does not limit the types of shared resource services that the data center 130 of the public cloud can provide.

Exemplarily, the data center 130 of the public cloud may include a cloud management platform 131 and a hardware resource pool 132. It should be understood that the division method shown in FIG. , this application does not limit the division method of the data center 130 of the public cloud.

Wherein, the cloud management platform 131 may be implemented by a common physical server, for example, an ARM server or an X86 server, or may be a virtual machine (virtual machine, VM) implemented in combination with network functions virtualization (network functions virtualization, NFV) technology, The cloud management platform 131 may also be a virtual machine or a physical server in the hardware resource pool 132, which is not specifically limited in this application.

The hardware resource pool 132 may include at least one physical server (Fig. 2 is an example illustrating that the resource pool includes physical server 1, physical server 2, physical server 3 and physical server 4), wherein the physical server may be a general physical server , such as an ARM server or an X86 server, which is not specifically limited in this application. The physical servers in the hardware resource pool 132 can communicate with other physical servers or the cloud management platform 131 through the internal network. Wherein, each physical server includes at least hardware resources (for example, physical server 1 includes hardware resource 1, and physical server 2 includes hardware resource 2) and an operating system (such as operating system 1 and operating system 2), and some physical servers can also include multiple Virtual instance, the virtual instance can be a container (for example, physical server 1 includes container 11 and container 12), or a virtual machine (such as virtual machine 21 and virtual machine 22), multiple virtual instances in the physical server can share the physical Operating system and hardware resources in the server.

Wherein, the hardware resources (such as hardware resource 1 and hardware resource 2) may include various available hardware resources of the physical server, such as processor 1, memory 1, PCI device 1, etc., and may also include other hardware resources that may be required by the user, This application does not make specific limitations. The operating system (such as operating system 1 and operating system 2) can be an operating system suitable for a container, a virtual machine, or a physical server, such as an Android (Android) operating system, a windows operating system, a linux operating system, etc., which are not specifically limited in this application. It should be noted that the operating system may be an official and complete operating system, or an operating system modified by individual driver modules of the official and complete operating system in order to adapt to the operating mode of the server, which is not specifically limited in this application. Moreover, the number of physical servers, number of virtual machines, number of containers, type and number of hardware resources shown in FIG. 2 are only for illustration, and are not specifically limited in this application.

The user can send a virtual instance creation request to the cloud management platform 131 through the terminal device 110, and the virtual instance creation request carries the specification information of the virtual instance requested by the user. Specification information, determine the physical server used to create the virtual instance, and then send the above specification information to the physical server to request the creation of the corresponding virtual instance.

Wherein, the above-mentioned virtual instance may be a virtual resource, such as a virtual machine or a container, or a physical resource, such as a physical server, or a service resource provided by other public cloud data centers, such as a process, which is not limited in this application.

The specification information of the above-mentioned virtual instance may include specification information under multiple resource categories. For example, the specification information of the first virtual instance may include CPU resource specification information, memory resource specification information, cache resource specification information, memory bandwidth resource specification information, network bandwidth resource specification information, and network bandwidth resource specification information. Resource specification information, disk capacity resource specification information, GPU resource specification information, etc. Among them, the specification information under each resource category can also include multiple parameter information. For example, the CPU resource specification can include CPU core number, CPU model, etc., and the memory resource specification can further include memory size, memory remaining capacity, etc., which are not mentioned here. One by one examples. Moreover, the specification information may also include constraints, such as the first virtual instance requested by the user, whose CPU resources and memory resources are on the same physical server, and where the CPU resources and GPU resources are in the same nonuniform memory access (nonuniform memory access, NUMA) architecture, this application does not make specific limitations.

It should be noted that the cloud management platform 131 determines the physical server used to create the virtual instance according to the virtual instance creation request sent by the user, and sends the above specification information to the physical server. The physical server can create an instance of the corresponding specification according to the specification information. Specifically, a virtual instance can be a container, a virtual machine, a physical server, or a process, and then the connection method of the virtual instance, such as a connection password, is sent to the user's terminal device 110, and the user can use the terminal device at any time, place, and location according to the connection password 110 is connected to the virtual instance, and the workload is run on the virtual instance to achieve data access, computing, and other purposes. It should be understood that the above examples are for illustration, and the present application does not specifically limit them.

However, since the number of resources on each physical server is relatively fixed, and the specification information of the virtual instance requested by the user is not fixed, when resource deduction is performed, some resources on some physical servers are deducted. , the remaining part of resources cannot be used to create other resource carriers, and will be reserved in the physical server in the form of resource fragments.

For example, if the CPU and memory ratio of physical server 1 is 1:1, and the memory ratio of the virtual instance created by the user request is 1:2, then when resource deduction is performed on physical server 1, the After all the memory resources are distributed, there are still CPU resources remaining; similarly, if the memory ratio of the virtual instance created by the user request is 2:1, then when the physical server 1 is deducted, the CPU resources of the physical server 1 are all After being allocated, there are still remaining memory resources, which cannot be continuously allocated because they exist independently. The above examples are for illustration, and the present application does not make specific limitations.

To sum up, the physical servers in the public cloud usually have resource fragments. For a public cloud with a large number of physical servers, these resource fragments will lead to waste of public cloud resources and increase the operating cost of the public cloud.

In order to solve the problem of resource fragmentation in physical servers in the public cloud, which leads to waste of public cloud resources and high operating costs, this application provides a resource management system. The cloud management platform in the system records the hardware resource pool of the public cloud data center The resource occupied by the virtual instance that each physical server needs to run and the instance type of the virtual instance that each physical server needs to run, the instance type includes on-demand instance type and reserved instance type, where the on-demand instance type is the user Instances that are used immediately after purchase. The reserved instance type is an instance that the user will not use within the reserved time and will be used after the reserved time expires. The resource pool information recorded by the system includes the creation information of reserved instances, but the physical servers in the hardware resource pool do not create reserved instances, so as to prevent users from creating reserved instances within the reserved time after the reserved instances are created on the physical servers. There will be no waste of resources caused by using this resource, and the system can centrally schedule the virtual instances of the reserved instance type to at least one physical server in the resource pool information, so that the virtual instances of the reserved instance type The associated physical servers can be used by virtual instances of the on-demand instance type, so that the resource management system can reduce the resource fragmentation of the public cloud, avoid the waste of public cloud resources, and improve the resources of the public cloud without affecting the use of users. Utilization, reduce the operating cost of the public cloud.

FIG. 2 is a schematic diagram of the architecture of a cloud management platform provided by the present application. As shown in FIG. For the description and connection manner with the hardware resource pool 132, reference may be made to the embodiment in FIG. 1 , and details are not repeated here.

Among them, the cloud management platform 131 can be further divided into multiple unit modules, such as the scheduling unit 1311, the receiving unit 1312, the recording unit 1313 and the sending unit 1314 shown in FIG. 2. It should be understood that FIG. 2 is an exemplary division method , and each module may be a software module, may also be a hardware module, or may be a part of software and part of a hardware module, which is not specifically limited in this application.

The receiving unit 1312 is configured to receive a virtual instance creation request sent by a user. The virtual instance creation request includes specification information and an instance type of the virtual instance, and the instance type includes an on-demand instance type and a reserved instance type. Among them, the on-demand instance type refers to the virtual instance that can be used after the user pays, and the reserved instance type refers to the virtual instance that will be used after the reserved time expires. X virtual machine, and select the reservation time as 3 months, then the user can use the virtual machine with X specification after September 1. It should be understood that there is a certain deviation between the prices of reserved instances and on-demand instances on the public cloud platform. For example, the price of reserved instances is lower than that of on-demand instances. cost. For the detailed description of the specification information of the virtual instance, reference may be made to the embodiment in FIG. 1 , and details are not repeated here.

The recording unit 1313 is used to record resource pool information, and the resource pool information includes the resources occupied by the virtual instances to be run by each physical server in the hardware resource pool 132 of the public cloud data center and the resources required by the virtual instances to be run by each physical server. instance type.

In a specific implementation, the resource pool information may include resource usage and instance types of multiple physical servers, and the resource usage of each physical server includes the usage of different types of resources. For example, the resource usage of physical server 1 may include CPU resource usage status, memory resource usage, cache resource usage, memory bandwidth usage, network bandwidth resource usage, disk capacity resource usage, GPU resource usage, etc. Among them, the usage of each category of resources can also be described by multiple parameter information. For example, the usage of CPU resources can include the number of CPU cores, CPU model, etc., and the usage of memory resources can further include memory size, remaining capacity of memory, etc. , not one by one examples are given here.

For example, FIG. 3 is an exemplary representation of resource pool information provided by this application. Assume that the recording unit 1313 has recorded the CPU resource usage and memory resource usage of four physical servers. According to the resource pool shown in FIG. 3 The pool information shows that part of the CPU resources and memory resources of physical servers 1 to 4 are used to create reserved instances, and part of the CPU resources and memory resources of physical servers 2 and 3 are not only used to create reserved instances, but also used to create reserved instances. Part of the CPU resources and memory resources are also used to create on-demand instances.

It should be understood that FIG. 3 is only used as an example to reflect content contained in the resource pool information, and in practical applications, the resource pool information may also be stored in other forms. In other representations of resource pool information, the usage of each resource type can also be marked with specific values, such as 50% CPU resource usage, 80% memory resource usage, etc.; the resource usage of each physical server It can also be marked with other information, and other information can specifically be the deduction time, the user to which it belongs, and the corresponding specification information, etc.; each physical server in the resource pool information can also include more resource categories, such as the cache resources in the foregoing content , network bandwidth resources, disk capacity resources, GPU resources, etc.; resource pool information can also be marked with instance categories in other ways (Figure 3 marks different instance categories with different shades); the presentation of resource pool information is not limited to that shown in Figure 3 The graphical interface shown can also record resource pool information through tables, characters, files, etc., which is not specifically limited in this application.

In this embodiment of the application, the recording unit 1313 can determine the physical server used to create the virtual instance according to the specification information in the above-mentioned virtual instance creation request, and update the above-mentioned resource pool information. The updated resource pool information includes the physical server A record of the creation of the virtual instance, and the instance type of the virtual instance.

Specifically, the recording unit 1313 may first determine at least one physical server that can deduct the virtual instance according to the above-mentioned specification information, and may select one physical server from the above-mentioned at least one physical server as the physical server for creating the virtual instance, The physical server with the largest number of remaining resources may also be used as the physical server for creating the virtual instance, or the physical server for creating the virtual instance may be selected from among them in other ways, which is not specifically limited in this application.

The sending unit 1314 is configured to send the above virtual instance to the physical server after the recording unit 1313 determines the physical server used to create the virtual instance and updates the resource pool information when the instance type of the virtual instance is an on-demand instance type. Instance specification information to request the creation of a virtual instance.

In a specific implementation, the receiving unit 1312 may receive a first virtual instance creation request, the first virtual instance creation request includes the instance specification and instance type of the first virtual instance, if the instance type of the first virtual instance is an on-demand instance type, The recording unit 1313 can update the resource pool information according to the instance specification of the first virtual instance, and the updated resource pool information includes the record of the first physical server creating the first virtual instance and the instance type of the first virtual instance (on-demand instance ), the sending unit 1314 may send a request for creating the first virtual instance to the first physical server, and the first physical server may respond to the request to locally create the first virtual instance.

In this embodiment of the application, the receiving unit 1312 may receive a second virtual instance creation request, the second virtual instance creation request includes the instance specification and instance type of the second virtual instance, if the instance type of the second virtual instance is reserved Instance type, the recording unit 1313 can update the resource pool information according to the instance specifications of the second virtual instance, and the updated resource pool information includes the record of the second physical server creating the second virtual instance and the instance type of the second virtual instance (pre- leave examples). In short, if the instance type of the virtual instance is a reserved instance, the sending unit 1314 does not need to send a request to create the virtual instance to the physical server used to create the virtual instance; if the instance type of the virtual instance is an on-demand instance, send Unit 1314 needs to send a request to create the virtual instance to the physical server used to create the virtual instance. It should be understood that since the reserved instance will not be used by the user within the reserved time, the reserved instance may not be created on the physical server during the reserved time, so as to avoid waste of resources and increase the utilization of the hardware resource pool 132. resource utilization.

The scheduling unit 1311 can centrally schedule the virtual instance of the reserved instance type to at least one physical server in the resource pool information, so that the physical server associated with the reserved instance type before scheduling can be used by the virtual instance of the on-demand instance type.

Specifically, one reserved instance may be scheduled, some reserved instances may be scheduled, and all reserved instances may be scheduled, which is not specifically limited in this application. The reserved instances participating in centralized scheduling can be determined according to the number of reserved instances and the number of resource fragments, so that the number of resource fragments recorded in the resource pool information after centralized scheduling can be reduced. For the resources used to create a virtual instance, for a specific description, refer to the embodiment in FIG. 1 , which will not be repeated here.

Specifically, the scheduling unit 1311 can screen out the physical servers with resource fragments and reserved instances from the resource pool information, and then schedule the reserved instances to other physical servers that can create the reserved instances, thereby reducing public cloud resources The number of fragments reduces the operating cost of the public cloud.

For example, Figure 4 is a flow chart of resource pool information provided by this application for centralized scheduling of reserved instances. As shown in Figure 4, assuming that physical server X1 has on-demand instances and reserved instances, the remaining resources are For resource fragments that cannot be used to create virtual instances, the scheduling unit 1311 can determine the physical server Y1 that can create the reserved instance according to the resource pool information, and then schedule the reserved instance to the physical server Y1. After resource scheduling, the physical server X1' The remaining resources can be used to create virtual instances, and the physical server X1' no longer has resource fragments, thereby increasing the number of resource fragments in the public cloud and reducing the operating cost of the public cloud. At the same time, because the scheduling unit 1311 does not schedule the on-demand instance that the user is using, it can avoid the impact on the user during the resource scheduling process and improve the user experience, and the resource scheduling is to update the resource pool information instead of the physical instance. The virtual instance migration of the server can reduce the overhead of network and memory bandwidth, and further reduce the operating cost of the public cloud.

In one embodiment, before the scheduling unit 1311 performs resource scheduling on the reserved instance, it may first determine the first quantity of remaining resources recorded in the resource pool information, and then obtain the information of multiple physical servers in the hardware resource pool from the hardware resource pool 132 The second number of remaining resources. When the ratio between the first number and the second number is less than or equal to the first threshold, the scheduling unit 1311 performs the above steps of resource scheduling, and performs resource allocation for the reserved instances in the resource pool information. Scheduling, the number of resource fragments recorded in the resource pool information after centralized scheduling is reduced.

The number of remaining resources may refer to the number of standard virtual instances that can be created. The specifications of standard virtual instances are determined according to the historical virtual machine creation records of the public cloud. The specifications of standard virtual instances may include one or more types of virtual instances Specifications. For example, according to the historical virtual machine creation records of the public cloud, it is determined that the distribution frequency of VM1 and VM2 is relatively high, then the total number of VM1 and VM2 that can be distributed by the remaining resources can be determined according to the remaining resources recorded in the resource pool information, so as to obtain the above-mentioned first Quantity, and then obtain the remaining resources of multiple physical servers in the hardware resource pool 132 from the hardware resource pool 132, determine the total quantity of VM1 and VM2 that can be distributed by the remaining resources, so as to obtain the above-mentioned second quantity, if the first quantity and the second If the ratio of the numbers is less than or equal to the first threshold, the scheduling unit 1311 may perform centralized scheduling on the reserved instances in the resource pool information.

It should be understood that the above-mentioned first quantity is determined according to the resource pool information, and the second quantity is determined according to the remaining resources of multiple physical servers in the hardware resource pool 132, and the resource pool information additionally records creation records of reserved instances, so the second A number is less than the second number, and the smaller the ratio of the two, it means that the number of resource fragments in the current resource pool information is more, so when the ratio of the first number to the second number is less than or equal to the second threshold, the scheduling unit 1311 Scheduling the reserved instance, centrally dispatching the virtual instance of the reserved instance type in the resource pool information to at least one physical server, so that the physical server associated with the virtual instance of the reserved instance type before scheduling is available for the on-demand instance type The use of virtual instances avoids waste of resources and improves the resource utilization of public clouds.

Optionally, the scheduling unit 1311 may also schedule the reserved instances periodically, where the periodicity may be scheduling the reserved instances at fixed time intervals, or every time after receiving M virtual instance creation requests, Scheduling of reserved instances is not specifically limited in this application.

Optionally, the scheduling unit 1311 may also periodically determine the first number and the second number, and schedule the reserved instances in the resource pool information when the ratio of the first number to the second number is less than or equal to the second threshold . For the periodic description, reference may be made to the aforementioned content, which will not be repeated here.

Optionally, the scheduling unit 1311 may also determine the first number and the second number through the above steps in the case of failure to create a virtual instance, and then schedule the reserved instance, reduce the number of resource fragments in the resource pool information, and re- Try to process the virtual instance creation request that failed to create before, improve the user experience, and improve the resource utilization of the public cloud.

In an embodiment, the reserved instance recorded in the resource pool information not only includes the instance specification, but also includes the reserved time of the reserved instance. When the reserved time of the reserved instance is about to expire, the sending unit 1314 can send a virtual instance creation request to the physical server where the reserved instance is recorded in the resource pool information, and update the resource pool information to create the virtual instance The instance type is changed from reserved instance to on-demand instance, which prevents users from being unable to use reserved instances after the reserved time expires and improves user experience.

To sum up, the cloud management platform provided by this application records the resources occupied by the virtual instances that each physical server needs to run in the hardware resource pool of the public cloud data center and the instance type of the virtual instances that each physical server needs to run. The resource pool information recorded by the system includes the creation information of the reserved instance, but the physical server of the hardware resource pool will not create the reserved instance, so as to avoid the resource waste caused by the reserved instance not being used by the user within the reserved time; at the same time , the system can also centrally schedule the reserved instances recorded in the resource pool information, so that the physical servers associated with the virtual instances of the reserved instance type can be used by the virtual instances of the on-demand instance type before scheduling. In the case of affecting user use, reduce the resource fragmentation of the public cloud and improve the resource utilization of the public cloud.

Fig. 5 is a schematic flow chart of the steps of a resource management method provided by the present application. The method can be applied to the resource management system shown in Fig. 2. As shown in Fig. 5, the method may include the following steps:

S510: The cloud management platform records resource pool information. Wherein, the resource pool information is used to record the resource occupied by the virtual instance that each physical server needs to run in the hardware resource pool of the public cloud data center and the instance type of the virtual instance that each physical server needs to run, and the instance type includes On-Demand and Reserved Instance types.

In a specific implementation, the resource pool information may include resource usage and instance types of multiple physical servers, and the resource usage of each physical server includes the usage of different types of resources. For example, the resource usage of physical server 1 may include CPU resource usage status, memory resource usage, cache resource usage, memory bandwidth usage, network bandwidth resource usage, disk capacity resource usage, GPU resource usage, etc. Among them, the usage of each category of resources can also be described by multiple parameter information. For example, the usage of CPU resources can include the number of CPU cores, CPU model, etc., and the usage of memory resources can further include memory size, remaining capacity of memory, etc. , not one by one examples are given here. For the description of the resource pool information, reference may be made to the foregoing embodiments in FIG. 2 to FIG. 3 , and details are not repeated here.

In the embodiment of this application, the cloud management platform can receive the virtual instance creation request sent by the user, the virtual instance creation request includes the specification information of the virtual instance and the instance type of the virtual instance, and the instance type includes on-demand instance type and reserved instance type. The cloud management platform can determine the physical server used to create the virtual instance according to the specification information and resource pool information in the virtual instance creation request, and then update the above resource pool information. The updated resource pool information includes the physical server to create the virtual instance and the instance type of the virtual instance.

Among them, the specification information may include specification information of different resource categories, such as the number of CPU cores, CPU model, memory size, cache size, etc. For details, please refer to the description of the specification information in the embodiments shown in Figures 1 to 4, which will not be repeated here. . On-demand instances refer to instances that can be used after payment by the user. Reserved instances refer to instances that will not be used within the reserved time after payment by the user, but will be used after the reserved time expires. If you pay for a virtual machine with specification X and choose to reserve it for 3 months, then the user can use the virtual machine with specification X after September 1. A virtual instance can be a virtual machine, a physical machine, a container, a thread, etc. It should be understood that the description of a virtual instance, an on-demand instance, and a reserved instance can refer to the embodiments in FIG. 2 to FIG. 4 , and details are not repeated here.

Optionally, if a first virtual instance creation request is received, wherein the instance type in the first virtual instance creation request is an on-demand instance type, after updating the resource pool information according to the first virtual instance creation request, update After the resource pool information includes the record of the first virtual instance created by the first physical server and the instance type (on-demand instance) of the first virtual instance, the cloud management platform sends the creation For the request of the first virtual instance, the first physical machine may create a virtual instance in response to the request.

Optionally, if a second virtual instance creation request is received, wherein the instance type in the second virtual instance creation request is a reserved instance type, after updating the resource pool information according to the second virtual instance creation request, update The subsequent resource pool information includes the record of the second virtual instance created by the second physical server and the instance type (reserved instance) of the second virtual instance. But the second physical server will not create the second virtual instance. It should be understood that since the reserved instance will not be used by the user within the reserved time, the reserved instance may not be created on the physical server during the reserved time, thereby avoiding resource waste and increasing the resources of the hardware resource pool 132 utilization rate.

Further, the reserved instance recorded in the resource pool information includes not only the instance specification, but also the reserved time of the reserved instance. When the reserved time of the reserved instance is about to expire, the cloud management platform can send a virtual instance creation request to the physical server where the reserved instance is recorded in the resource pool information, and update the resource pool information to create the virtual instance The instance type is changed from reserved instance to on-demand instance, which prevents users from being unable to use reserved instances after the reserved time expires and improves user experience.

S520: The cloud management platform centrally schedules the virtual instance of the reserved instance type to at least one physical server in the resource pool information, so that the physical server associated with the virtual instance of the reserved instance type before scheduling is available for the on-demand instance type Virtual instance usage.

In specific implementation, when the cloud management platform centrally schedules virtual instances of the reserved instance type, it can schedule one reserved instance, some reserved instances, or all reserved instances. Applications are not specifically limited. Specifically, the reserved instances participating in the centralized scheduling can be determined according to the number of reserved instances and the number of resource fragments. It should be understood that after centralized scheduling, the amount of resource fragments recorded in the resource pool information is reduced. Here, resource fragments refer to resources that cannot be used to create a virtual instance. The description of resource fragments can refer to the embodiments in FIG. 1 to FIG. 4 , and details will not be repeated here.

In the specific implementation, the cloud management platform can filter out the physical servers with resource fragments and reserved instances from the resource pool information, and then schedule the reserved instances to other physical servers that can create the reserved instances, thereby reducing public cloud traffic The number of resource fragments reduces the operating cost of the public cloud. For details, reference may be made to the example described in the embodiment in FIG. 4 , and details are not repeated here.

In an embodiment, before the cloud management platform performs resource scheduling on the reserved instance, it may first determine the first amount of remaining resources recorded in the resource pool information, and then obtain the remaining resources of multiple physical servers in the hardware resource pool from the hardware resource pool. The second quantity of resources. When the ratio between the first quantity and the second quantity is less than or equal to the first threshold, resource scheduling is performed on the reserved instance, and the amount of resource fragments in the resource pool information after resource scheduling is obtained. reduce.

The number of remaining resources may refer to the number of standard virtual instances that can be created. The specifications of standard virtual instances are determined according to the historical virtual machine creation records of the public cloud. The specifications of standard virtual instances may include one or more types of virtual instances Specifications. For example, according to the historical virtual machine creation records of the public cloud, it is determined that the distribution frequency of VM1 and VM2 is relatively high, then the total number of VM1 and VM2 that can be distributed by the remaining resources can be determined according to the remaining resources recorded in the resource pool information, so as to obtain the above-mentioned first Quantity, and then obtain the remaining resources of multiple physical servers in the hardware resource pool from the hardware resource pool, determine the total quantity of VM1 and VM2 that can be distributed by the remaining resources, so as to obtain the above-mentioned second quantity, if the first quantity and the second quantity If the ratio is less than or equal to the first threshold, the cloud management platform can perform centralized scheduling on the reserved instances in the resource pool information.

It should be understood that the above-mentioned first quantity is determined according to the resource pool information, and the second quantity is determined according to the remaining resources of multiple physical servers in the hardware resource pool. The resource pool information additionally records creation records of reserved instances, so the first The number is less than the second number, and the smaller the ratio between the two, the more resource fragments in the current resource pool information. Therefore, when the ratio of the first number to the second number is less than or equal to the second threshold, the cloud management platform Scheduling the reserved instances, and centrally dispatching the virtual instances of the reserved instance type in the resource pool information to at least one physical server, so that the physical servers associated with the reserved instance type virtual instances before scheduling can be used by the virtual instances of the on-demand instance type instance usage, thereby avoiding resource waste and improving the resource utilization of the public cloud.

Optionally, the cloud management platform may also schedule the reserved instances periodically, where the periodicity may be scheduling the reserved instances at fixed time intervals, or after receiving M virtual instance creation requests, Scheduling of reserved instances is not specifically limited in this application.

Optionally, the cloud management platform may also periodically determine the first number and the second number, and when the ratio of the first number to the second number is less than or equal to the second threshold, schedule the reserved instances in the resource pool information . For the periodic description, reference may be made to the aforementioned content, which will not be repeated here.

Optionally, the cloud management platform can also determine the first number and the second number through the above steps in the case of a virtual instance creation failure, and then schedule reserved instances, reduce the number of resource fragments in the resource pool information, and re- Try to process the virtual instance creation request that failed to create before, improve the user experience, and improve the resource utilization of the public cloud.

In summary, using the resource management method provided by this application, the cloud management platform records the resources occupied by the virtual instances that each physical server needs to run in the hardware resource pool of the public cloud data center and the virtual instances that each physical server needs to run The resource pool information recorded by the system includes the creation information of the reserved instance, but the physical server of the hardware resource pool will not create the reserved instance, so as to avoid the situation that the reserved instance is not used by the user within the reserved time waste of resources; at the same time, the system can also centrally schedule the reserved instances recorded in the resource pool information, so that the physical server associated with the virtual instance of the reserved instance type before scheduling can be used by the virtual instance of the on-demand instance type , which can reduce the resource fragmentation of the public cloud and improve the resource utilization of the public cloud without affecting the use of users.

FIG. 6 is a schematic structural diagram of a computing device 600 provided in the present application. Wherein, the computing device 600 may be the cloud management platform 131 in FIGS. 1-5 . As shown in FIG. 6 , the computing device 600 includes: a processor 610 , a communication interface 620 and a memory 630 . Wherein, the processor 610, the communication interface 620, and the memory 630 may be connected to each other through the internal bus 640, and may also communicate through other means such as wireless transmission. In this embodiment of the present application, connection through a bus is taken as an example, and the bus may be a PCI bus. The bus 640 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 6 , but it does not mean that there is only one bus or one type of bus.

The processor 610 may be composed of at least one general-purpose processor, such as a CPU, or a combination of a CPU and a hardware chip. The aforementioned hardware chip may be an ASIC, a PLD or a combination thereof. The aforementioned PLD may be CPLD, FPGA, GAL or any combination thereof. Processor 230 executes various types of digitally stored instructions, such as software or firmware programs stored in memory 630, which enable computing device 600 to provide various services.

The memory 630 is used to store program codes, which are executed under the control of the processor 610 to execute the processing steps of the cloud management platform 131 in the above embodiments. The program code may include one or more software modules, and the one or more software modules may be software modules provided by the cloud management platform 131 in the embodiment of FIG. Pool information, the resource pool information is used to record the resources occupied by the virtual instances that each physical server needs to run in the hardware resource pool of the public cloud data center and the instance type of the virtual instances that each physical server needs to run. The scheduling unit uses In the resource pool information, the virtual instance of the reserved instance type is centrally scheduled to at least one physical server, so that the physical server associated with the virtual instance of the reserved instance type before scheduling can be used by the virtual instance of the on-demand instance type. Specifically, it can be used to execute S510-step S520 and its optional steps in the embodiment of FIG. 5 , and can also be used to execute other steps performed by the cloud management platform 131 described in the embodiments of FIG. 1-FIG. 5 , which will not be repeated here.

The memory 630 may include a volatile memory, such as RAM, DRAM, SRAM, SDRAM, DDR, Cache, etc., and the memory 630 may also include a combination of the above types.

The communication interface 620 can be a wired interface (such as an Ethernet interface), an internal interface (such as a PCI bus interface), a wired interface (such as an Ethernet interface) or a wireless interface (such as a cellular network interface or a wireless local area network interface), for Communicate with other devices or modules.

It should be noted that this embodiment can be implemented by a general physical server, for example, an ARM server or an X66 server, or it can be realized based on a general physical server combined with a virtual machine implemented by NFV technology. A virtual machine refers to a virtual machine simulated by software A complete computer system with complete hardware system functions and running in a completely isolated environment, for example, can be implemented on a cloud computing infrastructure in this embodiment, and the specific process implemented on the cloud computing infrastructure can refer to the embodiment in Figure 3, This will not be repeated.

It should be noted that FIG. 6 is only a possible implementation of the embodiment of the present application. In practical applications, the computing device 600 may include more or fewer components, which is not limited here. Regarding the contents not shown or described in the embodiments of the present application, reference may be made to the related explanations in the foregoing embodiments of FIGS. 1-5 , and details are not repeated here.

It should be understood that the computing device shown in FIG. 6 may also be a computer cluster composed of at least one physical server. For details, reference may be made to the embodiments in FIG. 1 to FIG. 4 , and details are not repeated here to avoid repetition.

The embodiment of the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are run on a processor, the method flow shown in FIG. 5 and its optional steps are implemented.

An embodiment of the present application further provides a computer program product. When the computer program product runs on a processor, the method flow shown in FIG. 5 and its optional steps are implemented.

The above-mentioned embodiments may be implemented in whole or in part by software, hardware, firmware or other arbitrary combinations. When implemented using software, the above-described embodiments may be implemented in whole or in part in the form of computer program products. A computer program product comprises at least one computer instruction. When the computer program instructions are loaded or executed on the computer, the processes or functions according to the embodiments of the present invention will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g. Coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center. A computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage node such as a server or a data center that includes at least one set of available media. Available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, high-density digital video disc (DVD), or semiconductor media. The semiconductor media may be SSDs.

The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or modifications within the technical scope disclosed in the present invention. Replacement, these modifications or replacements shall all fall within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (14)

1. A resource management method of a public cloud data center, characterized in that, being applied to a cloud management platform of a public cloud data center, the method comprises: The cloud management platform records resource pool information, and the resource pool information is used to record the resources that each physical server needs to run in the hardware resource pool of the public cloud data center and the resources that each physical server needs to run. The instance type of the virtual instance, the instance type includes on-demand instance type and reserved instance type; The cloud management platform centrally schedules the virtual instance of the reserved instance type to at least one physical server in the resource pool information, so that the physical server associated with the virtual instance of the reserved instance type before scheduling can be available as an on-demand instance The virtual instance of the type used. 2. The method according to claim 1, characterized in that the method further comprises: The cloud management platform receives a first virtual instance creation request, the first virtual instance creation request includes an instance type of the first virtual instance, and the instance type of the first virtual instance is an on-demand instance type; The cloud management platform updates the resource pool information, and the updated resource pool information includes a record of creating the first virtual instance by the first physical server and an instance type of the first virtual instance; The cloud management platform sends a request for creating the first virtual instance to the first physical server. 3. The method according to claim 1 or 2, characterized in that the method further comprises: The cloud management platform receives a second virtual instance creation request, the second virtual instance creation request includes an instance type of the second virtual instance, and the instance type of the second virtual instance is a reserved instance type; The cloud management platform updates the resource pool information, and the updated resource pool information includes a record of creating the second virtual instance by the second physical server and an instance type of the second virtual instance. 4. The method according to claim 3, wherein before the cloud management platform centrally schedules the virtual instance of the reserved instance type to at least one physical server in the resource pool information, the method further comprises: The cloud management platform determines the first quantity of remaining resources recorded in the resource pool information; The cloud management platform acquires a second quantity of remaining resources of multiple physical servers in the hardware resource pool from the hardware resource pool; Centrally dispatching virtual instances of the reserved instance type to at least one physical server by the cloud management platform in the resource pool information includes: When the ratio between the first number and the second number is less than or equal to a first threshold, the cloud management platform centrally schedules virtual instances of the reserved instance type in the resource pool information to at least one physical server. 5. The method according to claim 3 or 4, wherein the cloud management platform determines the first amount of remaining resources recorded in the resource pool information includes: The cloud management platform periodically determines the first quantity of remaining resources recorded in the resource pool information; or, The cloud management platform determines the first quantity of remaining resources recorded in the resource pool information when the creation of the virtual instance fails. 6. The method according to any one of claims 1 to 5, wherein the virtual instance includes a virtual machine, a container, and/or a bare metal server. 7. A cloud management platform, characterized in that, it is applied to the cloud management platform of the public cloud data center, and the cloud management platform includes: A recording unit, the recording unit is used to record the resource pool information, and the resource pool information is used to record the resources and resources that each physical server needs to run in the hardware resource pool of the public cloud data center. The instance type of the virtual instance that each physical server needs to run, and the instance type includes on-demand instance type and reserved instance type; A scheduling unit, configured to centrally schedule the virtual instance of the reserved instance type to at least one physical server in the resource pool information, so that the physical server associated with the virtual instance of the reserved instance type before scheduling can be Used by virtual instances of the On-Demand instance type. 8. The cloud management platform according to claim 7, characterized in that, the cloud management platform further comprises a receiving unit and a sending unit, The receiving unit is configured to receive a first virtual instance creation request, the first virtual instance creation request includes an instance type of the first virtual instance, and the instance type of the first virtual instance is an on-demand instance type; The recording unit is configured to update the resource pool information, and the updated resource pool information includes a record of creating the first virtual instance by the first physical server and an instance type of the first virtual instance; The sending unit is configured to send a request for creating the first virtual instance to the first physical server. 9. The cloud management platform according to claim 8, characterized in that, The receiving unit is configured to receive a second virtual instance creation request, the second virtual instance creation request includes an instance type of the second virtual instance, and the instance type of the second virtual instance is a reserved instance type; The recording unit is configured to update the resource pool information, and the updated resource pool information includes a record of creating the second virtual instance by the second physical server and an instance type of the second virtual instance. 10. The cloud management platform according to claim 9, characterized in that, The scheduling unit is configured to determine the first quantity of remaining resources recorded in the resource pool information before the virtual instance of the reserved instance type is centrally scheduled to at least one physical server in the resource pool information; The scheduling unit is configured to acquire a second quantity of remaining resources of multiple physical servers in the hardware resource pool from the hardware resource pool; The scheduling unit is configured for the cloud management platform to include the reserved resource pool information in the resource pool information when the ratio between the first quantity and the second quantity is less than or equal to a first threshold. Virtual instances of an instance type are centrally scheduled to at least one physical server. 11. The cloud management platform according to claim 9 or 10, wherein the scheduling unit is configured to periodically determine the first quantity of remaining resources recorded in the resource pool information; or, The scheduling unit is configured to determine the first quantity of remaining resources recorded in the resource pool information when the creation of the virtual instance fails. 12. The cloud management platform according to any one of claims 7 to 11, wherein the resources include virtual machines, containers, and/or bare metal servers. 13. A computing device, characterized by comprising a processor and a memory, the memory stores codes, and the processor executes the codes to implement the method according to any one of claims 1 to 6. 14. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a processor, the method according to any one of claims 1 to 6 is implemented .

Images