Cloud instance management method based on cloud management platform and cloud management platform

Abstract

The invention discloses a cloud instance management method based on a cloud management platform and the cloud management platform, cloud instances of tenants can be recycled in a targeted manner according to recycling requirements of the tenants, so that the service of the tenants can be completed, and the use cost of the tenants can be saved. The method comprises the steps that a cloud management platform obtains configuration information of a to-be-created cloud instance input by a tenant from a cloud instance configuration interface, wherein the configuration information is used for indicating the specification of the cloud instance and a recycling condition for the cloud instance; the cloud management platform selects a physical server of an available capacity support specification based on the configuration information, and creates a cloud instance in the physical server, the cloud instance being used for providing a cloud service for the tenant; if the available capacity of the physical server is lower than or equal to the capacity threshold value, the cloud management platform recycles the cloud instance under the condition that the recycling condition is met.

Description

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on June 28, 2023, with application number 202310777321.1 and invention name “A resource management method and cloud management platform based on cloud management platform”, all contents of which are incorporated by reference in this application. Technical Field

[0002] The embodiments of the present application relate to the field of cloud technology, and in particular to a cloud instance management method based on a cloud management platform and a cloud management platform. Background Art

[0003] When providing cloud instances to tenants, the cloud management platform can classify cloud instances into stable cloud instances and unstable cloud instances according to their stability. Compared with stable cloud instances, unstable cloud instances are usually cheaper and can be recovered by the cloud management platform after being sold to tenants.

[0004] When tenants need to use cloud instances provided by the cloud service system to complete their own business, in order to save costs, tenants can apply for unstable cloud instances from the cloud management platform in the cloud service system. After receiving the tenant's request, the cloud management platform can create dedicated unstable cloud instances for the tenant to process the tenant's business through these unstable cloud instances, thereby providing cloud services to the tenant.

[0005] In the above process, once the cloud management platform finds that the cloud instance needs to be recycled, even if the tenant's unstable cloud instance is still processing the tenant's business, the cloud management platform will also recycle these unstable cloud instances. This will cause the tenant's business to be incomplete, and the tenant will also pay a certain cost, resulting in a poor tenant experience. Summary of the invention

[0006] The embodiment of the present application provides a cloud instance management method and a cloud management platform based on a cloud management platform, which can perform targeted recycling of tenants' cloud instances according to the tenants' recycling requirements, thereby not only completing the tenants' business but also saving the tenants' usage costs.

[0007] A first aspect of an embodiment of the present application provides a cloud instance management method based on a cloud management platform, the method comprising:

[0008] When a tenant wants to create a (unstable) cloud instance, the cloud management platform can provide a cloud instance configuration interface to the client used by the tenant, so that the tenant can send the configuration information of the cloud instance to be created to the cloud instance configuration interface, so that the cloud management platform receives the configuration information of the cloud instance sent by the tenant through the cloud instance configuration interface. The configuration information is used to indicate the specifications of the cloud instance set by the tenant and the recycling conditions of the cloud instance set by the tenant.

[0009] After obtaining the configuration information of the cloud instance, the cloud management platform can parse the configuration information of the cloud instance to obtain the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant. Then, the cloud management platform can select a physical server with available capacity that supports the specifications of the cloud instance required by the tenant, and create a tenant-specific cloud instance in the physical server, so that these cloud instances can provide cloud services for the tenant.

[0010] In the process of tenant-specific cloud instances running tenants' businesses, once the available capacity of the physical servers used to deploy these cloud instances is lower than or equal to the capacity threshold, it means that the available capacity of the physical servers is insufficient. Therefore, the cloud management platform can recycle the tenant-specific cloud instances to solve the problem of insufficient available capacity of the physical servers if the recycling conditions of the cloud instances set by the tenants are met.

[0011] It can be seen from the above method that when a tenant needs to create a cloud instance, the configuration information of the cloud instance to be created can be input into the cloud instance configuration interface provided by the cloud management platform. The configuration information is used to indicate the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant. After obtaining the configuration information of the cloud instance required by the tenant, the cloud management platform can select a physical server with available capacity that supports the specifications of the cloud instance required by the tenant based on the configuration information, and create a tenant-specific cloud instance in the physical server. These cloud instances can provide cloud services for the tenant. In the process of these cloud instances providing cloud services to tenants, if the available capacity of the physical servers where these cloud instances are deployed is lower than or equal to the capacity threshold, the cloud management platform can recycle these cloud instances if the recycling conditions are met. In the above process, the cloud management platform has a recycling customization function for cloud instances, which allows tenants to customize the recycling conditions of cloud instances. Then, after the tenant has customized the recycling conditions for the cloud instance it needs, when the cloud management platform needs to recycle the tenant's cloud instance, the cloud management platform can follow the recycling conditions customized by the tenant for the cloud instance, that is, according to the tenant's recycling requirements, to carry out targeted recycling of the tenant's cloud instance. This can not only complete the tenant's business, but also save the tenant's usage costs.

[0012] In a possible implementation, the cloud management platform obtains the configuration information of the cloud instance to be created input by the tenant from the cloud instance configuration interface, including: the cloud management platform provides the tenant with a recycling condition range through the cloud instance configuration interface; the cloud management platform obtains the configuration information of the cloud instance to be created input by the tenant from the cloud instance configuration interface, and the configuration information is used to indicate the specifications of the cloud instance and the recycling conditions for the cloud instance selected by the tenant from the recycling condition range. In the aforementioned implementation, after the cloud management platform provides the cloud instance configuration interface to the tenant, the cloud instance configuration interface can display a recycling condition range for the tenant to select, so after the tenant browses the recycling condition range displayed by the cloud instance configuration interface, the tenant can select the recycling condition of the cloud instance required by the tenant from the recycling condition range and input it into the cloud instance configuration interface. At the same time, the tenant can also select the specification of the cloud instance required by the tenant and input it into the cloud instance configuration interface. In this way, the cloud instance configuration interface can be based on the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant, as the configuration information of the cloud instance required by the tenant, and send the configuration information of the cloud instance to the cloud management platform. It can be seen that the cloud management platform provides tenants with the function of customizing recycling conditions for cloud instances by providing a range of recycling conditions, which can meet tenants' needs for customizing recycling conditions for unstable cloud instances.

[0013] In one possible implementation, the recycling condition range includes at least one of the following: a protection period range, a recycling notification duration range, a usage duration range, and a recycling rate range. In the aforementioned implementation, the recycling condition range includes one or more of a protection period range, a recycling notification duration range, a usage duration range, and a recycling rate range, wherein the protection period range may include multiple different protection periods, the recycling notification duration range may include multiple different recycling notification durations, the usage duration range may include multiple different usage durations, and the recycling rate range may include multiple different recycling rates. It can be seen that the cloud management platform provides tenants with multiple protection periods, multiple recycling notification durations, multiple usage durations, multiple recycling rates, etc., to choose from, in order to meet tenants' recycling condition customization requirements for cloud instances.

[0014] In one possible implementation, the recycling condition includes at least one of the following: the protection period of the cloud instance, the recycling notification duration of the cloud instance, the usage duration of the cloud instance, and the recycling rate of the cloud instance. In the aforementioned implementation, since the cloud management platform displays one or more of the protection period range, recycling notification duration range, usage duration range, recycling rate range, etc. to the tenant through the cloud instance configuration interface, the tenant can select the protection period of the cloud instance required by the tenant from the multiple protection periods included in the protection period range, and / or select the recycling notification duration of the cloud instance required by the tenant from the multiple recycling notification durations included in the recycling notification duration range, and / or select the usage duration of the cloud instance required by the tenant from the multiple usage durations included in the protection period range, and / or select the recycling rate of the cloud instance required by the tenant from the multiple recycling rates included in the protection period range. It can be seen from this that tenants can choose the protection period, recycling notification period, usage period and recycling rate of the cloud instance they need from the multiple protection periods, multiple recycling notification periods, multiple usage periods and multiple recycling rates provided by the cloud management platform, and can customize the recycling conditions for the cloud instance.

[0015] In a possible implementation, there are multiple cloud instances, and the cloud management platform recycles the cloud instances when the recycling conditions are met, including: the cloud management platform determines at least one recyclable cloud instance from the multiple cloud instances, wherein the at least one cloud instance satisfies at least one of the following: at least one cloud instance is outside the protection period of at least one cloud instance, the usage time of at least one cloud instance is less than or equal to the usage time threshold, and the ratio of at least one cloud instance to multiple cloud instances is less than or equal to the recycling rate; the cloud management platform calculates the recycling notification time of the first moment and the at least one cloud instance to obtain the second moment, notifies the tenant at the first moment that the at least one cloud instance is about to be recycled, and recycles the at least one cloud instance at the second moment. In the above implementation, it is assumed that there are multiple tenant-specific cloud instances created by the cloud management platform, and the recycling conditions set by the tenant for the multiple cloud instances include one or more of the protection period of the multiple cloud instances, the recycling notification time of the multiple cloud instances, the usage time of the multiple cloud instances, and the recycling rate of the multiple cloud instances. Then, based on the recycling conditions set by the tenant for the multiple cloud instances, the cloud management platform can select at least one recyclable cloud instance from the multiple cloud instances, and the at least one cloud instance selected by the cloud management platform satisfies at least one of the following: the at least one recyclable cloud instance is outside its own protection period. The usage time of the at least one recyclable cloud instance is less than or equal to the usage time threshold. The ratio of the at least one recyclable cloud instance to the multiple cloud instances is less than or equal to the recycling rate, for example, the ratio between the number of the at least one recyclable cloud instance and the number of the multiple cloud instances is less than or equal to the recycling rate, and for example, the ratio between the core time of the at least one recyclable cloud instance used by the tenant and the core time of the multiple cloud instances used by the tenant is less than or equal to the recycling rate, etc. After determining the at least one recyclable cloud instance, the cloud management platform can calculate the first moment and the recycling notification time of the at least one cloud instance to obtain at least one second moment. Then, the cloud management platform can notify the tenant at the first moment that the at least one cloud instance is about to be recycled, and recycle the at least one recyclable cloud instance accordingly at at least one second moment. It can be seen from this that when the cloud management platform determines that a tenant's cloud instance needs to be recycled, it can strictly follow the recycling conditions customized by the tenant to complete the recycling of the cloud instance.

[0016] In a possible implementation, the method further includes: the cloud management platform provides the price of the cloud instance to the tenant through the cloud instance purchase interface, and the price is obtained based on the recycling conditions; the cloud management platform obtains the purchase request for the cloud instance input by the tenant from the cloud instance purchase interface, and the purchase request is used to indicate that the tenant agrees to the price; the cloud management platform selects a physical server with available capacity supporting the specification based on the configuration information, including: the cloud management platform selects a physical server with available capacity supporting the specification based on the purchase request and the configuration information. In the aforementioned implementation, after obtaining the configuration information of the cloud instance, the cloud management platform can parse the configuration information of the cloud instance, so as to obtain the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant, so the cloud management platform can calculate the recycling conditions of the cloud instance required by the tenant, so as to obtain the price of the cloud instance required by the tenant. After obtaining the price, the cloud management platform can provide the tenant with a cloud instance purchase interface, and the cloud instance purchase interface can display the price of the cloud instance required by the tenant, so that the tenant can consider whether to purchase the cloud instance at the price. After the tenant browses the price of the cloud instance required by the tenant displayed on the cloud instance purchase interface through the client, if the tenant agrees to the price after consideration, the tenant can input a purchase request to the cloud instance purchase interface to indicate that the tenant agrees to the price, so that the cloud management platform receives the purchase request input by the tenant through the cloud instance purchase interface. After receiving the purchase request, the cloud management platform can determine based on the purchase request that the tenant has agreed to the price of the cloud instance required by the tenant, so the cloud management platform can select a physical server with available capacity that supports the specifications of the cloud instance required by the tenant from the multiple physical servers it manages, and create the cloud instance required by the tenant in the physical server. It can be seen from this that after the cloud management platform determines the recycling conditions customized by the tenant for its cloud instance, it can calculate the price of the cloud instance according to the recycling conditions, and after the tenant agrees to the price, the cloud management platform can create a cloud instance for the tenant.

[0017] In one possible implementation, a cloud instance is a physical server, a virtual machine, or a container.

[0018] A second aspect of an embodiment of the present application provides a cloud management platform, which includes: a first acquisition module, used to obtain configuration information of a cloud instance to be created input by a tenant from a cloud instance configuration interface, the configuration information is used to indicate the specifications of the cloud instance and the recycling conditions for the cloud instance; a creation module, used to select a physical server with available capacity supporting the specifications based on the configuration information, and create a cloud instance in the physical server, the cloud instance is used to provide cloud services to the tenant; a recycling module, used to recycle the cloud instance if the available capacity of the physical server is lower than or equal to the capacity threshold and the recycling conditions are met.

[0019] It can be seen from the above cloud management platform that when a tenant needs to create a cloud instance, the configuration information of the cloud instance to be created can be input into the cloud instance configuration interface provided by the cloud management platform. The configuration information is used to indicate the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant. After obtaining the configuration information of the cloud instance required by the tenant, the cloud management platform can select a physical server with available capacity that supports the specifications of the cloud instance required by the tenant based on the configuration information, and create a tenant-specific cloud instance in the physical server. These cloud instances can provide cloud services for the tenant. In the process of these cloud instances providing cloud services to tenants, if the available capacity of the physical servers where these cloud instances are deployed is lower than or equal to the capacity threshold, the cloud management platform can recycle these cloud instances if the recycling conditions are met. In the above process, the cloud management platform has a recycling customization function for cloud instances, which allows tenants to customize the recycling conditions of cloud instances. Then, after the tenant has customized the recycling conditions for the cloud instance it needs, when the cloud management platform needs to recycle the tenant's cloud instance, the cloud management platform can follow the recycling conditions customized by the tenant for the cloud instance, that is, according to the tenant's recycling requirements, to carry out targeted recycling of the tenant's cloud instance. This can not only complete the tenant's business, but also save the tenant's usage costs.

[0020] In a possible implementation, the recycling condition includes at least one of the following: a protection period of the cloud instance, a recycling notification duration of the cloud instance, a usage duration of the cloud instance, and a recycling rate of the cloud instance.

[0021] In one possible implementation, there are multiple cloud instances, and a recycling module is used to: determine at least one recyclable cloud instance from the multiple cloud instances, wherein the at least one cloud instance satisfies at least one of the following: the at least one cloud instance is outside the protection period of the at least one cloud instance, the usage time of the at least one cloud instance is less than or equal to the usage time threshold, and the ratio of the at least one cloud instance to the multiple cloud instances is less than or equal to the recycling rate; calculate the recycling notification time of the first moment and the at least one cloud instance to obtain the second moment, notify the tenant at the first moment that the at least one cloud instance is about to be recycled, and recycle the at least one cloud instance at the second moment.

[0022] In one possible implementation, the first acquisition module is used to: provide a recycling condition range to the tenant through a cloud instance configuration interface; obtain configuration information of the cloud instance to be created input by the tenant from the cloud instance configuration interface, the configuration information being used to indicate the specifications of the cloud instance, and the recycling conditions for the cloud instance selected by the tenant from the recycling condition range.

[0023] In a possible implementation, the recycling condition range includes at least one of the following: a protection period range, a recycling notification duration range, a usage duration range, and a recycling rate range.

[0024] In one possible implementation, the cloud management platform also includes: a second acquisition module, used to: provide the price of the cloud instance to the tenant through the cloud instance purchase interface, the price is obtained based on the recycling conditions; obtain the purchase request for the cloud instance input by the tenant from the cloud instance purchase interface, the purchase request is used to indicate that the tenant agrees to the price; a creation module, used for the cloud management platform to select a physical server with available capacity supporting specifications based on the purchase request and configuration information.

[0025] In one possible implementation, a cloud instance is a physical server, a virtual machine, or a container.

[0026] A third aspect of an embodiment of the present application provides a computing device cluster, the computing device cluster includes at least one computing device, each computing device includes a processor and a memory: the memory is used to store instructions; the processor is used to enable the computing device cluster to execute the method described in the first aspect or any possible implementation method of the first aspect according to the instructions.

[0027] A fourth aspect of an embodiment of the present application provides a computer storage medium, which stores one or more instructions. When the instructions are executed by one or more computers, the one or more computers implement the method described in the first aspect or any possible implementation method of the first aspect.

[0028] A fifth aspect of the embodiments of the present application provides a computer program product, which stores instructions. When the instructions are executed by a computer, the computer implements the method described in the first aspect or any possible implementation method of the first aspect.

[0029] In an embodiment of the present application, when a tenant needs to create a cloud instance, the configuration information of the cloud instance to be created can be input into the cloud instance configuration interface provided by the cloud management platform. The configuration information is used to indicate the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant. After obtaining the configuration information of the cloud instance required by the tenant, the cloud management platform can select a physical server whose available capacity supports the specifications of the cloud instance required by the tenant based on the configuration information, and create a tenant-specific cloud instance in the physical server. These cloud instances can provide cloud services to the tenant. In the process of these cloud instances providing cloud services to tenants, if the available capacity of the physical servers on which these cloud instances are deployed is less than or equal to the capacity threshold, the cloud management platform can recycle these cloud instances if the recycling conditions are met. In the aforementioned process, the cloud management platform has a recycling customization function for cloud instances, which allows tenants to customize the recycling conditions of cloud instances. Then, after the tenant has customized the recycling conditions for the cloud instance it needs, when the cloud management platform needs to recycle the tenant's cloud instance, the cloud management platform can follow the recycling conditions customized by the tenant for the cloud instance, that is, according to the tenant's recycling requirements, to carry out targeted recycling of the tenant's cloud instance. This can not only complete the tenant's business, but also save the tenant's usage costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A schematic diagram of the structure of a cloud service system provided in an embodiment of the present application;

[0031] Figure 2 A flowchart of a cloud instance management method based on a cloud management platform provided in an embodiment of the present application;

[0032] Figure 3 A schematic diagram of the recycling notification duration provided in an embodiment of the present application;

[0033] Figure 4 A schematic diagram of an application example of a cloud instance management method based on a cloud management platform provided in an embodiment of the present application;

[0034] Figure 5a A schematic diagram of another application example of the cloud instance management method based on the cloud management platform provided in an embodiment of the present application;

[0035] Figure 5b A schematic diagram of another application example of the cloud instance management method based on the cloud management platform provided in an embodiment of the present application;

[0036] Figure 6 A schematic diagram of the structure of the cloud management platform provided in the embodiment of the present application;

[0037] Figure 7 A schematic diagram of a structure of a computing device provided in an embodiment of the present application;

[0038] Figure 8 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0039] Fig. 9 A schematic diagram of computer devices in a computer cluster provided in an embodiment of the present application being connected via a network. DETAILED DESCRIPTION

[0040] The embodiment of the present application provides a cloud instance management method and a cloud management platform based on a cloud management platform, which can perform targeted recycling of tenants' cloud instances according to the tenants' recycling requirements, thereby not only completing the tenants' business but also saving the tenants' usage costs.

[0041] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0042] When providing tenants with various cloud instances such as physical servers, virtual machines, and containers, the cloud management platform can classify cloud instances into stable cloud instances and unstable cloud instances according to their stability. The price of stable cloud instances is usually higher, and after being sold to tenants, the cloud management platform cannot recover them on its own, while the price of unstable cloud instances is usually lower, and after being sold to tenants, the cloud management platform can recover them on its own.

[0043] When tenants need to use cloud instances provided by the cloud service system to complete their own business, in order to save costs, tenants can choose unstable cloud instances to cope with their own business peaks. Based on this, tenants can send requests to the cloud management platform in the cloud service system to apply for unstable cloud instances. After receiving the tenant's request, the cloud management platform can create exclusive unstable cloud instances for the tenant, so as to process the tenant's business through these unstable cloud instances. In this way, unstable cloud instances can successfully provide cloud services for tenants.

[0044] In the above process, once the cloud management platform finds that the cloud instance needs to be recycled, even if the tenant's unstable cloud instance is still processing the tenant's business, the cloud management platform will also recycle these unstable cloud instances. This will cause the tenant's business to be incomplete, and the tenant will also pay a certain cost, resulting in a poor tenant experience.

[0045] In order to solve the above problems, an embodiment of the present application provides a cloud instance management method based on a cloud management platform, which can be implemented through the cloud management platform in the cloud service system. Figure 1 A schematic diagram of the structure of the cloud service system provided in the embodiment of the present application is as follows: Figure 1 As shown in the figure, the cloud service system includes the infrastructure that can provide cloud services and the cloud management platform that manages these infrastructures. The cloud management platform and infrastructure are introduced separately below:

[0046] The cloud management platform can coordinate and manage multiple physical servers in the entire cloud service system (for example, select a physical server from multiple physical servers and create a cloud instance on the physical server), and can also be open to tenants outside the system and respond to their requests. For example, the cloud management platform can provide various interfaces such as login interface, cloud instance configuration interface and cloud instance purchase structure for access by the tenant's client (for example, the terminal device used by the tenant or the browser on the terminal device, etc.). Among them, the cloud management platform can authenticate the tenant's client through the login interface, and after the identity authentication is successful, the tenant's client can be allowed to log in to the cloud management platform. The cloud management platform can also allow the tenant's client to send configuration information for (unstable) cloud instances to the cloud management platform through the cloud instance configuration interface, and the cloud management platform can also allow the tenant's client to send a purchase request for (unstable) cloud instances to the cloud management platform through the cloud purchase interface. Therefore, the cloud management platform can select a physical server for the tenant based on the configuration information of the purchase request sent by the tenant, and create one or more exclusive (unstable) cloud instances for the tenant on the physical server. Then, these cloud instances can run corresponding applications or microservices to process the user's business, thereby meeting the user's business processing needs.

[0047] The infrastructure includes multiple physical servers that can be selected by the cloud management platform. For any one of the multiple physical servers, the central processing unit (CPU), graphics processing unit (GPU), memory, network card and other components owned by the physical server, that is, the resources owned by the physical server, can also be called the capacity of the physical server. Excluding the used capacity of the physical server, the available capacity of the physical server can be used to create a stable cloud instance, and can also be used to create an unstable cloud instance. It should be noted that in the embodiments of the present application, the available capacity of the physical server involved below usually refers to the available capacity used to create an unstable cloud instance, and the cloud instance involved below usually refers to the unstable cloud instance, which will not be repeated later.

[0048] Furthermore, multiple physical servers in the infrastructure may be set up in the same site or in different sites, where the site may be presented in a variety of ways: for example, the site may be a region in the infrastructure. For another example, the site may be an availability zone in the infrastructure. For another example, the site may also be an edge site or a central cloud site in the infrastructure, and so on.

[0049] Furthermore, the cloud instance created by the cloud management platform on the physical server can be presented in a variety of ways: for example, the cloud management platform can directly use the physical server as a cloud instance. For another example, the cloud management platform can use virtualization technology to create virtual machines (VMs) on the physical server, and these virtual machines can be used as cloud instances. For another example, the cloud management platform can use virtualization technology to create containers (docker) on the physical server, and these containers can be used as cloud instances. For another example, the cloud management platform can use virtualization technology to create micro virtual machines (microVMs) on the physical server, and these micro virtual machines can be used as cloud instances, and so on.

[0050] Since the configuration information includes the recycling conditions set by the tenant for the cloud instance, when the cloud management platform needs to actively recycle the cloud instance, it can recycle the cloud instance according to the tenant's instructions and ensure that the recycling conditions set by the tenant are met, thereby ensuring the tenant's experience. Figure 2 This section describes the process. Figure 2 A flow chart of a cloud instance management method based on a cloud management platform provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the method includes:

[0051] 201. The cloud management platform obtains configuration information of the cloud instance to be created input by the tenant from the cloud instance configuration interface. The configuration information is used to indicate the specifications of the cloud instance and the recycling conditions for the cloud instance.

[0052] In this embodiment, when a tenant needs to create an unstable cloud instance due to business needs, the cloud management platform can provide a cloud instance configuration interface (for example, a cloud instance configuration interface, etc.) to the client used by the tenant, so that the tenant can send the configuration information of the (unstable) cloud instance to be created to the cloud instance configuration interface through the client, so that the cloud management platform receives the configuration information of the cloud instance sent by the tenant's client through the cloud instance configuration interface, and the configuration information is used to indicate the specifications of the cloud instance set by the tenant and the recycling conditions of the cloud instance set by the tenant. Among them, the specifications of the cloud instance refer to the available capacity occupied by the cloud instance on the physical server when the cloud management platform creates the cloud instance on the physical server (including the number of CPUs, GPUs, and memory occupied by the cloud instance, etc.). The recycling conditions of the cloud instance refer to the conditions that the cloud management platform needs to meet when determining that the cloud instance needs to be actively recycled.

[0053] Specifically, the cloud management platform can obtain the configuration information of the cloud instance in the following ways:

[0054] (1) After the cloud management platform provides the cloud instance configuration interface to the tenant's client, the cloud instance configuration interface can display a range of recycling conditions for the tenant to choose from. Therefore, after the tenant browses the range of recycling conditions displayed by the cloud instance configuration interface through the client, the tenant can select the recycling conditions of the cloud instance required by the tenant (that is, the cloud instance to be created) from the recycling condition range and input it into the cloud instance configuration interface through the client. At the same time, the tenant can also select the specifications of the cloud instance required by the tenant and input it into the cloud instance configuration interface through the client. In this way, the cloud instance configuration interface can use the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant as the configuration information of the cloud instance required by the tenant, and send the configuration information of the cloud instance to the cloud management platform.

[0055] More specifically, the range of recycling conditions displayed to tenants by the cloud instance configuration interface can be presented in the following ways:

[0056] The recycling condition range includes at least one of the following: a protection period range, a recycling notification duration range, a usage duration range, and a recycling rate range. Among them, the protection period range may include multiple different protection periods (these multiple protection periods may be continuous or discontinuous), the recycling notification duration range may include multiple different recycling notification durations (these multiple recycling notification durations may be continuous or discontinuous), the usage duration range may include multiple different usage durations (these multiple usage durations may be continuous or discontinuous), and the recycling rate range may include multiple different recycling rates (these multiple recycling rates may be continuous or discontinuous). The following is an introduction to the definitions of protection period, recycling notification duration, usage duration, and recycling rate:

[0057] (1) Protection period refers to the duration of stable supply of cloud instances that the cloud management platform can guarantee. It should be noted that if a cloud instance is within its protection period, the cloud management platform will try not to recycle (interrupt or release) the cloud instance. If a cloud instance is outside its protection period, the cloud management platform can recycle the cloud instance. It can be seen that the cloud management platform will give priority to reclaiming cloud instances outside the protection period. Generally speaking, the price of a cloud instance is proportional to its protection period, that is, the longer the protection period of a cloud instance, the higher the price of the cloud instance, and the shorter the protection period of a cloud instance, the lower the price of the cloud instance.

[0058] (2) Recycling notification duration refers to the time it takes for the cloud management platform to notify tenants in advance when recycling cloud instances. It should be noted that after the cloud management platform determines that a cloud instance needs to be recycled, it can try to notify tenants at a certain time and recycle the cloud instance at another time. The interval between these two times is the recycling notification duration of the cloud instance. Generally, the price of a cloud instance is proportional to the recycling notification duration of the cloud instance, that is, the longer the recycling notification duration of the cloud instance, the higher the price of the cloud instance, and the shorter the recycling notification duration of the cloud instance, the lower the price of the cloud instance.

[0059] (3) Usage duration refers to the maximum duration that a tenant uses a purchased cloud instance. It should be noted that the longer the usage duration of a cloud instance, the less likely the cloud management platform is to recycle such cloud instances. The shorter the usage duration of a cloud instance, the more likely the cloud management platform is to recycle such cloud instances. It can be seen that the cloud management platform will give priority to reclaiming cloud instances with shorter usage durations. Generally, the price of a cloud instance is proportional to the usage duration of the cloud instance, that is, the longer the usage duration of a cloud instance, the higher the price of the cloud instance, and the shorter the usage duration of a cloud instance, the lower the price of the cloud instance.

[0060] (4) The recovery rate (also called the interruption rate or release rate) refers to the probability that the cloud instance purchased by the tenant will be recovered. It should be noted that the cloud management platform will usually recover the cloud instance while trying to meet the recovery rate. Generally speaking, the price of the cloud instance is inversely proportional to the recovery rate of the cloud instance, that is, the lower the recovery rate of the cloud instance, the higher the price of the cloud instance, and the higher the recovery rate of the cloud instance, the lower the price of the cloud instance.

[0061] More specifically, the reclaim conditions set by a tenant for its required cloud instance can be presented in the following ways:

[0062] Since the cloud management platform displays one or more of the protection period range, recycling notification duration range, usage duration range, and recycling rate range to tenants through the cloud instance configuration interface, the tenant can perform one or more of the following operations: (1) Select the protection period of the cloud instance required by the tenant from the multiple protection periods included in the protection period range. (2) Select the recycling notification duration of the cloud instance required by the tenant from the multiple recycling notification durations included in the recycling notification duration range. (3) Select the usage duration of the cloud instance required by the tenant from the multiple usage durations included in the protection period range. (4) Select the recycling rate of the cloud instance required by the tenant from the multiple recycling rates included in the protection period range.

[0063] Since the number of cloud instances required by a tenant can be one or more, if the tenant requires more than one cloud instance, the protection periods selected by the tenant for the multiple cloud instances can be the same or different. Similarly, the recycling notification durations selected by the tenant for the multiple cloud instances can be the same or different. Similarly, the usage durations selected by the tenant for the multiple cloud instances can be the same or different. It is worth noting that regardless of whether the tenant requires one or more cloud instances, the tenant usually selects only one recycling rate for the cloud instance, because the recycling rate is set for all the cloud instances required by the tenant as a whole.

[0064] Based on this, after selecting and obtaining one or more of the cloud instance protection period required by the tenant, the cloud instance recycling notification duration required by the tenant, the cloud instance usage duration required by the tenant, and the cloud instance recycling rate required by the tenant, and after selecting and obtaining the cloud instance specifications required by the tenant, the tenant can input the selected information into the cloud instance configuration interface through the client. In this way, the cloud instance configuration interface can use this information as the configuration information of the cloud instance required by the tenant, and send the cloud instance configuration information to the cloud management platform.

[0065] For example, if a tenant needs to create virtual machines 1, 2, and 3, after logging into the cloud management platform, the cloud management platform can provide the tenant with a virtual machine configuration interface, which displays the protection period range, recycling notification duration range, usage duration range, and recycling rate range. Among them, the protection period range is 1 hour to 3 hours, the recycling notification duration range is 1 minute to 1 hour, the usage duration range is 5 hours to 10 hours, and the recycling rate range is 1% to 50%.

[0066] Then, in the virtual machine configuration interface, the tenant can set the protection period of virtual machine 1 and virtual machine 2 to 1 hour, the protection period of virtual machine 3 to 3 hours, set the recycling notification duration of virtual machine 1, virtual machine 2 and virtual machine 3 to 30 minutes, set the usage time of virtual machine 1 to 2 hours, the usage time of virtual machine 2 to 3 hours, the usage time of virtual machine 3 to 5 hours, and set the recycling rate of virtual machine 1, virtual machine 2 and virtual machine 3 to 40%. In addition, the tenant can also set the specifications of virtual machine 1, virtual machine 2 and virtual machine 3 in the virtual machine configuration interface.

[0067] In this way, the virtual machine configuration interface can generate configuration information for the three virtual machines based on the specifications, protection period, recycling notification duration, usage duration and recycling rate set by the tenant for the three virtual machines, and send it to the cloud management platform.

[0068] 202. Based on the configuration information, the cloud management platform selects a physical server with available capacity supporting the specification, and creates a cloud instance in the physical server. The cloud instance is used to provide cloud services to the tenants.

[0069] After obtaining the configuration information of the cloud instance, the cloud management platform can parse the configuration information of the cloud instance to obtain the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant. Then, the cloud management platform can select a physical server with available capacity that supports the specifications of the cloud instance required by the tenant from the multiple physical servers it manages, and create a tenant-specific cloud instance in the physical server. Therefore, these cloud instances can run the tenant's business, thereby meeting the tenant's business needs (that is, these cloud instances can successfully provide cloud services for the tenant).

[0070] Specifically, the cloud management platform can create the cloud instances required by tenants in the following ways:

[0071] (1) After obtaining the configuration information of the cloud instance, the cloud management platform can parse the configuration information of the cloud instance to obtain the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant (including one or more of the protection period of the cloud instance required by the tenant, the recycling notification duration of the cloud instance required by the tenant, the usage time of the cloud instance required by the tenant, and the recycling rate of the cloud instance required by the tenant). Therefore, the cloud management platform can calculate the recycling conditions of the cloud instance required by the tenant to obtain the price of the cloud instance required by the tenant.

[0072] (2) After obtaining the price, the cloud management platform can provide the tenant's client with a cloud instance purchase interface (for example, a cloud instance purchase window that pops up on the cloud instance configuration interface). The cloud instance purchase interface can display the price of the cloud instance required by the tenant so that the tenant can consider whether to purchase the cloud instance at that price.

[0073] (3) After the tenant browses the price of the cloud instance required by the tenant displayed on the cloud instance purchase interface through the client, if the tenant agrees to the price after consideration, the tenant can input a purchase request to the cloud instance purchase interface through the client to indicate that the tenant agrees to the price, so that the cloud management platform receives the purchase request input by the tenant through the client through the cloud instance purchase interface. If the tenant disagrees with the price after consideration, the tenant can input an adjustment request to the cloud instance purchase interface through the client to indicate that the tenant disagrees with the price, so that the cloud management platform receives the adjustment request input by the tenant through the client through the cloud instance purchase interface. Therefore, the cloud management platform can adjust the original price based on the adjustment request to obtain the new price of the cloud instance required by the tenant, and provide the adjusted new price to the tenant until the purchase request input by the tenant is received.

[0074] (4) After receiving the purchase request, the cloud management platform can determine based on the purchase request that the tenant has agreed to the price of the cloud instance it needs. Therefore, the cloud management platform can select a physical server with available capacity that supports the specifications of the cloud instance required by the tenant from the multiple physical servers it manages, and create the cloud instance required by the tenant in the physical server.

[0075] 203. If the available capacity of the physical server is less than or equal to the capacity threshold, the cloud management platform recycles the cloud instance if the recycling conditions are met.

[0076] In the process of tenant-specific cloud instances running tenants' businesses, once the available capacity of the physical servers used to deploy these cloud instances is lower than or equal to the capacity threshold (the size of the threshold can be set according to actual needs and is not restricted here), it means that the available capacity of the physical server is insufficient. Therefore, the cloud management platform can recycle the tenant-specific cloud instances if the recycling conditions of the cloud instances set by the tenants are met, thereby releasing the capacity occupied by the recycled cloud instances to solve the problem of insufficient available capacity of the physical servers.

[0077] Specifically, the cloud management platform can reclaim cloud instances in the following ways:

[0078] (1) Assume that the cloud management platform has multiple cloud instances created exclusively for tenants, and the recycling conditions set by the tenants for these multiple cloud instances include one or more of the protection period of these multiple cloud instances, the recycling notification duration of these multiple cloud instances, the usage duration of these multiple cloud instances, and the recycling rate of these multiple cloud instances. Then, based on the recycling conditions set by the tenants for these multiple cloud instances, the cloud management platform can select at least one cloud instance that can be recycled from these multiple cloud instances, and the at least one cloud instance selected by the cloud management platform satisfies at least one of the following: (1) The at least one cloud instance that can be recycled is outside its own protection period. (2) The usage duration of the at least one cloud instance that can be recycled is less than or equal to the usage duration threshold (the size of the threshold can be set according to actual needs and is not limited here), that is, the multiple cloud instances are sorted from short to long according to the usage duration, and the at least one cloud instance that can be recycled is ranked first. (3) The ratio of the at least one recyclable cloud instance to the multiple cloud instances is lower than or equal to the recycling rate. Here, "ratio lower than or equal to the recycling rate" may refer to: the ratio between the number of the at least one recyclable cloud instance and the number of the multiple cloud instances is lower than or equal to the recycling rate; or the ratio between the time when the tenant uses the core of the at least one recyclable cloud instance and the time when the tenant uses the core of the multiple cloud instances is lower than or equal to the recycling rate, etc.

[0079] (2) Figure 3 As shown ( Figure 3 A schematic diagram of the recycling notification duration provided in the embodiment of the present application) After determining at least one cloud instance that can be recycled, the cloud management platform can calculate the recycling notification duration of the first moment and at least one cloud instance to obtain at least one second moment. Then, the cloud management platform can notify the tenant at the first moment that at least one cloud instance is about to be recycled, and recycle the at least one recyclable cloud instance accordingly at at least one second moment.

[0080] Still as in the above example, when the cloud management platform determines that virtual machine 1, virtual machine 2 and virtual machine 3 need to be recycled, at this time, virtual machine 1, virtual machine 2 and virtual machine 3 have all been running for 1.5 hours, and virtual machine 1 and virtual machine 2 are both outside their own protection period. However, if the cloud management platform recycles virtual machine 1 and virtual machine 2 at the same time, the recycling rate at this time is 66.7%, which is much greater than 40%. Then, the cloud management platform can choose to recycle only virtual machine 1 (because the usage time of virtual machine 1 is less than that of virtual machine 2), and the recycling rate at this time is 33.3%, which is less than 40%. After determining the recycling decision, let the current time be 10:00. Since the recycling notification time of virtual machine 1 is 30 minutes, the cloud management platform can determine that the recycling time of virtual machine 1 is 10:30, so the cloud management platform can notify the tenant at 10:00 that virtual machine 1 is about to be recycled, and recycle virtual machine 1 at 10:30.

[0081] In order to further understand the cloud instance management method based on the cloud management platform provided in the embodiment of the present application, the method is further introduced below in combination with multiple application examples. Figure 4 A schematic diagram of an application example of a cloud instance management method based on a cloud management platform provided in an embodiment of the present application, such as Figure 4 As shown, the application examples include:

[0082] 1. Tenants select unstable cloud instances as the products they need based on their own business characteristics, and input the product configuration information into the cloud management platform. The cloud management platform can calculate the price of the product based on the configuration information through the price calculation module and provide it to the tenant for review.

[0083] 2. After the tenant agrees to the price, he or she can enter a purchase request for the product into the control panel.

[0084] 3. The cloud management platform can verify the tenant's permissions in the permission verification module and verify the tenant's quota in the quota verification module. After both are passed, the configuration information can be stored in the database.

[0085] 4. The cloud management platform can apply for physical resources for deploying tenant-specific products and running tenants' businesses through the resource management center.

[0086] 5. When the capacity management center finds that the available capacity of physical resources is insufficient, it notifies the cloud management platform.

[0087] 6. The cloud management platform queries the configuration information in the database, then specifies the recycling strategy according to the configuration information, and then notifies the tenant that the product is about to be recycled. During the period between notification and recycling, the tenant will no longer issue new tasks to ensure that the tenant's existing tasks are completed. Finally, the cloud management platform can recycle the tenant's products to release the corresponding resources.

[0088] Figure 5a A schematic diagram of another application example of the cloud instance management method based on the cloud management platform provided in the embodiment of the present application is as follows: Figure 5a As shown, the application examples include:

[0089] Take the big data business scenario where tenants use unstable cloud instances customized on demand as an example.

[0090] In this big data scenario, the distribution of tenants’ task execution time is as follows: Figure 4 As shown in the figure, the longest execution time of the tenant's task in this scenario is 22 minutes. The tenant can choose the recycling notification time of unstable cloud instances to be 25 minutes. Since the tenant has no requirements for the recycling rate and protection period, within the selection range provided by the cloud management platform, the tenant can choose the highest recycling rate and the shortest protection period for the unstable cloud instance. In this way, the tenant can meet the business requirements while achieving the lowest usage cost.

[0091] Figure 5b A schematic diagram of another application example of the cloud instance management method based on the cloud management platform provided in the embodiment of the present application is as follows: Figure 5b As shown, the application examples include:

[0092] Take a website business scenario as an example. In this scenario, the website's access to users is within 1 second. In order to cope with traffic peaks, the website will dynamically use unstable cloud instances when the number of user visits exceeds a certain amount.

[0093] In this website scenario, in order to ensure user experience and the success rate of user access, the website hopes that the recovery rate of the unstable cloud instance used can be at a lower level. Within the selection range provided by the cloud management platform, the website can choose the lowest recovery rate, the shortest recovery notification duration, and the shortest protection period for the unstable cloud instance. In this way, the website can achieve the lowest usage cost while meeting business requirements.

[0094] In an embodiment of the present application, when a tenant needs to create a cloud instance, the configuration information of the cloud instance to be created can be input into the cloud instance configuration interface provided by the cloud management platform. The configuration information is used to indicate the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant. After obtaining the configuration information of the cloud instance required by the tenant, the cloud management platform can select a physical server whose available capacity supports the specifications of the cloud instance required by the tenant based on the configuration information, and create a tenant-specific cloud instance in the physical server. These cloud instances can provide cloud services to the tenant. In the process of these cloud instances providing cloud services to tenants, if the available capacity of the physical servers on which these cloud instances are deployed is less than or equal to the capacity threshold, the cloud management platform can recycle these cloud instances if the recycling conditions are met. In the aforementioned process, the cloud management platform has a recycling customization function for cloud instances, which allows tenants to customize the recycling conditions of cloud instances. Then, after the tenant has customized the recycling conditions for the cloud instance it needs, when the cloud management platform needs to recycle the tenant's cloud instance, the cloud management platform can follow the recycling conditions customized by the tenant for the cloud instance, that is, according to the tenant's recycling requirements, to carry out targeted recycling of the tenant's cloud instance. This can not only complete the tenant's business, but also save the tenant's usage costs.

[0095] The above is a detailed description of the cloud instance management method based on the cloud management platform provided in the embodiment of the present application. The cloud management platform provided in the embodiment of the present application will be introduced below. Figure 6 A schematic diagram of the structure of the cloud management platform provided in the embodiment of the present application is shown in FIG. Figure 6 As shown, the cloud management platform includes:

[0096] A first acquisition module 601 is used to acquire configuration information of a cloud instance to be created input by a tenant from a cloud instance configuration interface, wherein the configuration information is used to indicate specifications of the cloud instance and recycling conditions for the cloud instance;

[0097] A creation module 602 is used to select a physical server whose available capacity supports the specification based on the configuration information, and create the cloud instance in the physical server, where the cloud instance is used to provide cloud services for the tenant;

[0098] The recycling module 603 is used to recycle the cloud instance if the available capacity of the physical server is lower than or equal to the capacity threshold and the recycling condition is met.

[0099] In an embodiment of the present application, when a tenant needs to create a cloud instance, the configuration information of the cloud instance to be created can be input into the cloud instance configuration interface provided by the cloud management platform. The configuration information is used to indicate the specifications of the cloud instance required by the tenant and the recycling conditions of the cloud instance required by the tenant. After obtaining the configuration information of the cloud instance required by the tenant, the cloud management platform can select a physical server whose available capacity supports the specifications of the cloud instance required by the tenant based on the configuration information, and create a tenant-specific cloud instance in the physical server. These cloud instances can provide cloud services to the tenant. In the process of these cloud instances providing cloud services to tenants, if the available capacity of the physical servers on which these cloud instances are deployed is less than or equal to the capacity threshold, the cloud management platform can recycle these cloud instances if the recycling conditions are met. In the aforementioned process, the cloud management platform has a recycling customization function for cloud instances, which allows tenants to customize the recycling conditions of cloud instances. Then, after the tenant has customized the recycling conditions for the cloud instance it needs, when the cloud management platform needs to recycle the tenant's cloud instance, the cloud management platform can follow the recycling conditions customized by the tenant for the cloud instance, that is, according to the tenant's recycling requirements, to carry out targeted recycling of the tenant's cloud instance. This can not only complete the tenant's business, but also save the tenant's usage costs.

[0100] In a possible implementation, the recycling condition includes at least one of the following: a protection period of the cloud instance, a recycling notification duration of the cloud instance, a usage duration of the cloud instance, and a recycling rate of the cloud instance.

[0101] In one possible implementation, there are multiple cloud instances, and the recycling module 603 is used to: determine at least one recyclable cloud instance from the multiple cloud instances, wherein the at least one cloud instance satisfies at least one of the following: the at least one cloud instance is outside the protection period of the at least one cloud instance, the usage time of the at least one cloud instance is less than or equal to the usage time threshold, and the ratio of the at least one cloud instance to the multiple cloud instances is less than or equal to the recycling rate; calculate the recycling notification time of the first moment and the at least one cloud instance to obtain the second moment, notify the tenant at the first moment that the at least one cloud instance is about to be recycled, and recycle the at least one cloud instance at the second moment.

[0102] In one possible implementation, the first acquisition module 601 is used to: provide a recycling condition range to the tenant through a cloud instance configuration interface; obtain configuration information of the cloud instance to be created input by the tenant from the cloud instance configuration interface, the configuration information is used to indicate the specifications of the cloud instance, and the recycling conditions for the cloud instance selected by the tenant from the recycling condition range.

[0103] In a possible implementation, the recycling condition range includes at least one of the following: a protection period range, a recycling notification duration range, a usage duration range, and a recycling rate range.

[0104] In one possible implementation, the cloud management platform also includes: a second acquisition module, used to: provide the price of the cloud instance to the tenant through the cloud instance purchase interface, the price is obtained based on the recycling conditions; obtain the purchase request for the cloud instance input by the tenant from the cloud instance purchase interface, the purchase request is used to indicate that the tenant agrees to the price; create module 602, for the cloud management platform to select a physical server with available capacity supporting specifications based on the purchase request and configuration information.

[0105] In one possible implementation, a cloud instance is a physical server, a virtual machine, or a container.

[0106] It should be noted that the information interaction, implementation process, etc. between the modules / units of the above-mentioned device are based on the same concept as the method embodiment of the present application, and the technical effects they bring are the same as those of the method embodiment of the present application. For specific contents, please refer to the description in the method embodiment shown above in the embodiment of the present application, and will not be repeated here.

[0107] See also Figure 7 , Figure 7 A schematic diagram of a computing device provided in an embodiment of the present application. Figure 7As shown, the computing device 700 (which can be used to present the aforementioned cloud management platform) includes: a processor 701, a memory 702, a communication interface 703 and a bus 704. The processor 701, the memory 702 and the communication interface 703 are coupled via a bus (not marked in the figure). The memory 702 stores instructions. When the execution instructions in the memory 702 are executed, the computing device 700 executes the method executed by the cloud management platform in the above method embodiment.

[0108] The computing device 700 may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASIC), or one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0109] The processor 701 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0110] The memory 702 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0111] The memory 702 stores executable program codes, and the processor 701 executes the executable program codes to respectively implement the functions of the first acquisition module, the creation module, and the recovery module, thereby implementing the cloud instance management method based on the cloud management platform. That is, the memory 702 stores instructions for executing the cloud instance management method based on the cloud management platform.

[0112] The communication interface 703 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 700 and other devices or a communication network.

[0113] In addition to the data bus, the bus 704 may also include a power bus, a control bus, a status signal bus, etc. The bus may be a peripheral component interconnect express (PCIe) bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus may be divided into an address bus, a data bus, a control bus, etc.

[0114] See also Figure 8 , Figure 8 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application. Figure 8 As shown, the computing device cluster 800 includes at least one computing device 700 .

[0115] like Figure 8 As shown, the computing device cluster 800 includes at least one computing device 700. The memory 702 in one or more computing devices 700 in the computing device cluster 800 may store the same instructions for executing the above-mentioned cloud instance management method based on the cloud management platform.

[0116] In some possible implementations, the memory 702 of one or more computing devices 700 in the computing device cluster 800 may also respectively store some instructions for executing the cloud instance management method based on the cloud management platform. In other words, the combination of one or more computing devices 700 may jointly execute the cloud instance management method based on the cloud management platform.

[0117] It should be noted that the memory 702 in different computing devices 700 in the computing device cluster 800 can store different instructions, which are respectively used to execute part of the functions of the above-mentioned cloud management platform. That is, the instructions stored in the memory 702 in different computing devices 700 can implement the functions of one or more modules of the first acquisition module, the creation module, the recycling module, etc.

[0118] In some possible implementations, one or more computing devices 700 in the computing device cluster 800 may be connected via a network, which may be a wide area network or a local area network.

[0119] See also Fig. 9 , Fig. 9 A schematic diagram of computer devices in a computer cluster provided in an embodiment of the present application being connected via a network. Fig. 9 As shown, two computing devices 700A and 700B are connected via a network. Specifically, they are connected to the network via a communication interface in each computing device.

[0120] In a possible implementation, the memory in the computing device 700A stores instructions for executing the functions of the first acquisition module, the second acquisition module, etc. Meanwhile, the memory in the computing device 700B stores instructions for executing the functions of the creation module, the recycling module, etc.

[0121] It should be understood that Fig. 9 The functions of the computing device 700A shown in FIG. 7 may also be completed by multiple computing devices. Similarly, the functions of the computing device 700B may also be completed by multiple computing devices.

[0122] The embodiment of the present application also relates to a computer storage medium, in which a program for signal processing is stored. When the program is run on a computer, the computer executes the following steps: Figure 2 The steps performed by the cloud management platform in the illustrated embodiment.

[0123] The present application also relates to a computer program product, which stores instructions, which, when executed by a computer, enable the computer to execute the following Figure 2 The steps performed by the cloud management platform in the illustrated embodiment.

[0124] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0125] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0126] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0127] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0128] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A cloud instance management method based on a cloud management platform, characterized in that: The method comprises: The cloud management platform obtains configuration information of the cloud instance to be created input by the tenant from the cloud instance configuration interface, wherein the configuration information is used to indicate the specifications of the cloud instance and the recycling conditions for the cloud instance; The cloud management platform selects a physical server whose available capacity supports the specification based on the configuration information, and creates the cloud instance in the physical server, where the cloud instance is used to provide cloud services for the tenant; If the available capacity of the physical server is lower than or equal to the capacity threshold, the cloud management platform recycles the cloud instance if the recycle condition is met.

2. The method according to claim 1, characterized in that The recycling condition includes at least one of the following: a protection period of the cloud instance, a recycling notification duration of the cloud instance, a usage duration of the cloud instance, and a recycling rate of the cloud instance.

3. The method according to claim 2, characterized in that There are multiple cloud instances, and when the recycling condition is met, the cloud management platform recycles the cloud instance, including: The cloud management platform determines at least one cloud instance that can be recycled from the multiple cloud instances, wherein the at least one cloud instance satisfies at least one of the following conditions: the at least one cloud instance is outside a protection period of the at least one cloud instance, a usage time of the at least one cloud instance is less than or equal to a usage time threshold, and a ratio of the at least one cloud instance to the multiple cloud instances is less than or equal to the recycling rate; The cloud management platform calculates the first moment and the recycling notification duration of the at least one cloud instance to obtain a second moment, notifies the tenant at the first moment that the at least one cloud instance is about to be recycled, and recycles the at least one cloud instance at the second moment.

4. The method according to any one of claims 1 to 3, characterized in that: The cloud management platform obtains configuration information of the cloud instance to be created input by the tenant from the cloud instance configuration interface, including: The cloud management platform provides the tenant with a range of recycling conditions through a cloud instance configuration interface; The cloud management platform obtains configuration information of the cloud instance to be created input by the tenant from the cloud instance configuration interface, wherein the configuration information is used to indicate the specifications of the cloud instance and the recycling condition for the cloud instance selected by the tenant from the recycling condition range.

5. The method according to claim 4, characterized in that The recycling condition range includes at least one of the following: a protection period range, a recycling notification duration range, a usage duration range, and a recycling rate range.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The cloud management platform provides the tenant with a price for the cloud instance through a cloud instance purchase interface, where the price is obtained based on the recycling condition; The cloud management platform obtains a purchase request for the cloud instance input by the tenant from the cloud instance purchase interface, where the purchase request is used to indicate that the tenant agrees to the price; The cloud management platform selects a physical server whose available capacity supports the specification based on the configuration information, including: The cloud management platform selects a physical server whose available capacity supports the specifications based on the purchase request and the configuration information.

7. The method according to any one of claims 1 to 6, characterized in that: The cloud instance is a physical server, a virtual machine or a container.

8. A cloud management platform, characterized in that: The cloud management platform includes: A first acquisition module, configured to acquire configuration information of a cloud instance to be created input by a tenant from a cloud instance configuration interface, wherein the configuration information is used to indicate specifications of the cloud instance and recycling conditions for the cloud instance; A creation module, configured to select a physical server whose available capacity supports the specification based on the configuration information, and to create the cloud instance in the physical server, wherein the cloud instance is used to provide cloud services for the tenant; The recycling module is used to recycle the cloud instance if the available capacity of the physical server is lower than or equal to a capacity threshold and if the recycling condition is met.

9. The cloud management platform according to claim 8, characterized in that: The recycling condition includes at least one of the following: a protection period of the cloud instance, a recycling notification duration of the cloud instance, a usage duration of the cloud instance, and a recycling rate of the cloud instance.

10. The cloud management platform according to claim 9, characterized in that: The number of the cloud instances is multiple, and the recycling module is used to: Determine at least one cloud instance that can be recycled from the multiple cloud instances, wherein the at least one cloud instance satisfies at least one of the following conditions: the at least one cloud instance is outside the protection period of the at least one cloud instance, the usage time of the at least one cloud instance is less than or equal to a usage time threshold, and the ratio of the at least one cloud instance to the multiple cloud instances is less than or equal to the recycling rate; The first moment and the recycling notification duration of the at least one cloud instance are calculated to obtain a second moment, the tenant is notified at the first moment that the at least one cloud instance is about to be recycled, and the at least one cloud instance is recycled at the second moment.

11. The cloud management platform according to any one of claims 8 to 10, characterized in that: The first acquisition module is used to: providing a recycling condition range to the tenant via a cloud instance configuration interface; The configuration information of the cloud instance to be created input by the tenant is obtained from the cloud instance configuration interface, wherein the configuration information is used to indicate the specification of the cloud instance and the recycling condition for the cloud instance selected by the tenant from the recycling condition range.

12. The cloud management platform according to claim 11, characterized in that: The recycling condition range includes at least one of the following: a protection period range, a recycling notification duration range, a usage duration range, and a recycling rate range.

13. The cloud management platform according to any one of claims 8 to 12, characterized in that: The cloud management platform further includes: a second acquisition module, configured to: provide the tenant with a price of the cloud instance through a cloud instance purchase interface, wherein the price is obtained based on the recycling condition; and obtain a purchase request for the cloud instance input by the tenant from the cloud instance purchase interface, wherein the purchase request is used to indicate that the tenant agrees to the price; The creation module is used for the cloud management platform to select a physical server whose available capacity supports the specifications based on the purchase request and the configuration information.

14. The cloud management platform according to any one of claims 8 to 13, characterized in that: The cloud instance is a physical server, a virtual machine or a container.

15. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each computing device including a processor and a memory: The memory is used to store instructions; The processor is configured to cause the computing device cluster to execute the method according to any one of claims 1 to 7 according to the instructions.

16. A computer storage medium, characterized in that: The computer storage medium stores one or more instructions, which, when executed by one or more computers, enable the one or more computers to implement the method of any one of claims 1 to 7.

17. A computer program product, characterized in that The computer program product stores instructions, and when the instructions are executed by a computer, the computer implements the method according to any one of claims 1 to 7.

Images