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

Abstract

The present application discloses a cloud management platform-based cloud instance management method and a cloud management platform. Cloud instances of tenants can be targetedly recycled according to recycling requirements of the tenants, thereby completing services of tenants, and also saving use costs of tenants. The method of the present application comprises: a cloud management platform acquires, from a cloud instance configuration interface, configuration information of a cloud instance to be created input by a tenant, wherein the configuration information is used for indicating the specification of the cloud instance and a recycling condition for the cloud instance; on the basis of the configuration information, the cloud management platform selects a physical server having the available capacity supporting the specification, and creates the cloud instance in the physical server, wherein the cloud instance is used for providing a cloud service for the tenant; if the available capacity of the physical server is lower than or equal to a capacity threshold, the cloud management platform recycles the cloud instance when the recycling condition is satisfied.

Description

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

[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, entitled “A resource management method and cloud management platform based on cloud management platform”, and claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 28, 2023, with application number 202311278787.3, entitled “A cloud instance management method and cloud management platform based on cloud management platform”, the entire contents of which are incorporated by reference into 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 categorize them into stable and unstable cloud instances based on their stability. Unstable cloud instances are typically cheaper than stable cloud instances and can be reclaimed 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 operations, they can request unstable cloud instances from the cloud management platform within the cloud service system to save costs. Upon receiving the tenant's request, the cloud management platform can create dedicated unstable cloud instances for the tenant, using these unstable cloud instances to handle the tenant's business operations and thus provide 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 recycle these unstable cloud instances. This will cause the tenant's business to be incomplete, and the tenant will also incur certain costs, resulting in a poor tenant experience.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide 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. This not only completes the tenants' business but also saves the tenants' usage costs.

[0008] 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:

[0009] When a tenant wants to create an (unstable) cloud instance, the cloud management platform can provide a cloud instance configuration interface to the client used by the tenant, so 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.

[0010] After obtaining the cloud instance configuration information, the cloud management platform can parse it to determine the cloud instance specifications and the required cloud instance reclaim conditions. The cloud management platform can then select a physical server with available capacity that supports the required cloud instance specifications and create a tenant-specific cloud instance on that physical server, allowing these cloud instances to provide cloud services to the tenant.

[0011] 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 if the recycling conditions of the cloud instances set by the tenants are met to solve the problem of insufficient available capacity of the physical servers.

[0012] 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 tenant-specific cloud instances 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 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 not only completes the tenant's business, but also saves the tenant's usage costs.

[0013] In one possible implementation, the cloud management platform obtains configuration information for a cloud instance to be created, input by a tenant, from a cloud instance configuration interface. The cloud management platform provides the tenant with a range of recycling conditions via the cloud instance configuration interface. The cloud management platform obtains the configuration information for the cloud instance to be created, input by the tenant, from the cloud instance configuration interface, where the configuration information indicates the specifications of the cloud instance and the recycling conditions for the cloud instance selected by the tenant from the range of recycling conditions. In the aforementioned implementation, after the cloud management platform provides the cloud instance configuration interface to the tenant, the cloud instance configuration interface may display a range of recycling conditions for the tenant to select. Therefore, after browsing the range of recycling conditions displayed by the cloud instance configuration interface, the tenant may select the recycling conditions for the cloud instance desired by the tenant from the range of recycling conditions and input them into the cloud instance configuration interface. The tenant may also select the specifications of the cloud instance desired by the tenant and input them into the cloud instance configuration interface. In this manner, the cloud instance configuration interface may, based on the tenant's desired cloud instance specifications and the tenant's desired recycling conditions, use these as the tenant's desired cloud instance configuration information and send the cloud instance configuration information 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.

[0014] 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 the protection period range, the recycling notification duration range, the usage duration range, and the recycling rate range, wherein the protection period range may include multiple protection periods that are different from each other, the recycling notification duration range may include multiple recycling notification durations that are different from each other, the usage duration range may include multiple usage durations that are different from each other, and the recycling rate range may include multiple recycling rates that are different from each other. It can be seen that the cloud management platform provides tenants with multiple protection periods, multiple recycling notification durations, multiple usage durations, and multiple recycling rates, etc., for them to choose from, in order to meet tenants' customization needs for recycling conditions for cloud instances.

[0015] In one possible implementation, the recycling conditions include 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, and recycling rate range to the tenant through the cloud instance configuration interface, the tenant can select the required protection period of the cloud instance from the multiple protection periods included in the protection period range, and / or select the required recycling notification duration of the cloud instance from the multiple recycling notification durations included in the recycling notification duration range, and / or select the required usage duration of the cloud instance from the multiple usage durations included in the protection period range, and / or select the required recycling rate of the cloud instance 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, recycling notification period, usage period and recycling rate provided by the cloud management platform, and can customize the recycling conditions for the cloud instance.

[0016] In one possible implementation, there are multiple cloud instances, and the cloud management platform recycles the cloud instances when 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 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 time of 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. In the aforementioned implementation, it is assumed that the cloud management platform has multiple tenant-specific cloud instances, and the recycling conditions set by the tenant for these multiple cloud instances include one or more of the protection period of these multiple cloud instances, the recycling notification time of these multiple cloud instances, the usage time of these multiple cloud instances, and the recycling rate of these multiple cloud instances. Based on the reclaim conditions set by the tenant for the multiple cloud instances, the cloud management platform may select at least one reclaimable cloud instance from the multiple cloud instances. The at least one cloud instance selected by the cloud management platform satisfies at least one of the following conditions: the at least one reclaimable cloud instance is outside its protection period; the usage duration of the at least one reclaimable cloud instance is less than or equal to a usage duration threshold; and the ratio of the at least one reclaimable cloud instance to the total number of cloud instances is less than or equal to the reclaim rate. For example, the ratio of the number of the at least one reclaimable cloud instance to the number of the multiple cloud instances is less than or equal to the reclaim rate; or the ratio of the core time the tenant uses for the at least one reclaimable cloud instance to the core time the tenant uses for the multiple cloud instances is less than or equal to the reclaim rate. After determining the at least one reclaimable cloud instance, the cloud management platform may calculate the first time and the reclaim notification duration of the at least one cloud instance to obtain at least one second time. The cloud management platform may then notify the tenant at the first time that the at least one cloud instance is about to be reclaimed and, accordingly, reclaim the at least one reclaimable cloud instance at the at least one second time. This shows 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.

[0017] In one possible implementation, the method further includes: 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 conditions; 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 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 to obtain the specifications of the cloud instance required by the tenant and the recycling conditions 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. After obtaining the price, the cloud management platform can provide the tenant with a cloud instance purchase interface, which 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. 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. 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. 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. After the tenant agrees to the price, the cloud management platform can create a cloud instance for the tenant.

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

[0019] 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 being 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 being 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.

[0020] It can be seen from the above-mentioned 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 tenant-specific cloud instances 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 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 not only completes the tenant's business, but also saves the tenant's usage costs.

[0021] In one 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.

[0022] In one possible implementation, there are multiple cloud instances, and the 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 a 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.

[0023] 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, where 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.

[0024] 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.

[0025] 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, where 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, where the purchase request is used to indicate that the tenant agrees to the price; and 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.

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

[0027] A third aspect of an embodiment of the present application provides a computing device cluster, which 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 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.

[0028] 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.

[0029] 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.

[0030] 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 with available capacity that supports the specifications of the cloud instance required by the tenant based on the configuration information, and create tenant-specific cloud instances 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 on which 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 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 not only completes the tenant's business, but also saves the tenant's usage costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] FIG1 is a schematic diagram of the structure of a cloud service system provided in an embodiment of the present application;

[0032] FIG2 is a flow chart of a cloud instance management method based on a cloud management platform according to an embodiment of the present application;

[0033] FIG3 is a schematic diagram of the recycling notification duration provided by an embodiment of the present application;

[0034] FIG4 is 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;

[0035] FIG5a is 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] FIG5 b is 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;

[0037] FIG6 is a schematic diagram of the structure of a cloud management platform provided in an embodiment of the present application;

[0038] FIG7 is a schematic diagram of a structure of a computing device provided in an embodiment of the present application;

[0039] FIG8 is a schematic diagram of a structure of a computing device cluster provided in an embodiment of the present application;

[0040] FIG9 is a schematic diagram of computer devices in a computer cluster provided by an embodiment of the present application being connected via a network. DETAILED DESCRIPTION

[0041] The embodiments of the present application provide 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. This not only completes the tenants' business but also saves the tenants' usage costs.

[0042] 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 are not necessarily 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, and this is merely a way of distinguishing the objects of the same attributes when describing them 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.

[0043] When cloud management platforms provide tenants with various cloud instances, such as physical servers, virtual machines, and containers, they can categorize cloud instances into stable and unstable instances based on their stability. Stable cloud instances are typically more expensive and, after being sold to tenants, the cloud management platform cannot automatically reclaim them. Unstable cloud instances, on the other hand, are typically cheaper and can be reclaimed by the cloud management platform after being sold to tenants.

[0044] When tenants need to use cloud instances provided by the cloud service system to complete their own business, they can choose unstable cloud instances to save costs and cope with their business peaks. To do this, the tenant sends a request to the cloud management platform within the cloud service system to request an unstable cloud instance. Upon receiving the request, the cloud management platform creates a dedicated unstable cloud instance for the tenant, allowing them to handle their business. This allows the unstable cloud instance to successfully provide cloud services to the tenant.

[0045] 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 recycle these unstable cloud instances. This will cause the tenant's business to be incomplete, and the tenant will also incur certain costs, resulting in a poor tenant experience.

[0046] To address the above issues, the present invention provides a cloud instance management method based on a cloud management platform. This method can be implemented through the cloud management platform in a cloud service system. Figure 1 is a schematic diagram of the structure of the cloud service system provided by the present invention. As shown in Figure 1, the cloud service system includes an infrastructure that can provide cloud services and a cloud management platform that manages these infrastructures. The cloud management platform and infrastructure are introduced below:

[0047] The cloud management platform can coordinate the management of multiple physical servers across the entire cloud service system (e.g., selecting a specific physical server from among multiple physical servers and creating a cloud instance on that physical server). It 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 a login interface, a cloud instance configuration interface, and a cloud instance purchase structure, for access by tenant clients (e.g., a terminal device used by the tenant or a browser on the terminal device). The cloud management platform can authenticate the tenant client through the login interface and, upon successful authentication, allow the tenant client to log in to the cloud management platform. The cloud management platform can also allow the tenant client to send configuration information for (unstable) cloud instances to the cloud management platform through the cloud instance configuration interface. Furthermore, the cloud management platform can allow the tenant client to send purchase requests for (unstable) cloud instances to the cloud management platform through the cloud instance purchase interface. Based on the configuration information in the purchase request, the cloud management platform can select a physical server for the tenant and create one or more (unstable) cloud instances dedicated to the tenant on that physical server. These cloud instances can then run corresponding applications or microservices to process the user's business, thereby meeting the user's business processing needs.

[0048] 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 capacity that has been used in 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 this part of 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.

[0049] Furthermore, multiple physical servers in the infrastructure can be located in the same site or different sites. A site can be represented in various ways: for example, a site can be a region in the infrastructure, an availability zone in the infrastructure, an edge site in the infrastructure, or a central cloud site.

[0050] Furthermore, the cloud instances 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. In another example, the cloud management platform can use virtualization technology to create virtual machines (VMs) on the physical server, and these VMs can serve as cloud instances. In another example, the cloud management platform can use virtualization technology to create containers (Docker) on the physical server, and these containers can serve as cloud instances. In another example, the cloud management platform can use virtualization technology to create microVMs on the physical server, and these microVMs can serve as cloud instances, and so on.

[0051] 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 follow the tenant's instructions and recycle the cloud instance after ensuring that the recycling conditions set by the tenant are met, thereby ensuring the tenant's experience. In order to further understand the workflow of the cloud management platform, the following will introduce the process in conjunction with Figure 2. Figure 2 is a flow chart of the cloud instance management method based on the cloud management platform provided in an embodiment of the present application. As shown in Figure 2, the method includes:

[0052] 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.

[0053] 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 it is necessary to actively recycle the cloud instance.

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

[0055] (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 recycling condition range 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 them 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 them 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.

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

[0057] 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:

[0058] (1) Protection period refers to the duration of stable supply of cloud instances guaranteed by the cloud management platform. It should be noted that when a cloud instance is within its protection period, the cloud management platform will try not to recycle (interrupt or release) the cloud instance. When a cloud instance is outside its protection period, the cloud management platform can recycle the cloud instance. Therefore, the cloud management platform will prioritize reclaiming cloud instances outside the protection period. Generally, the price of a cloud instance is proportional to its protection period. That is, the longer the protection period, the higher the price of the cloud instance, and the shorter the protection period, the lower the price of the cloud instance.

[0059] (2) Recycling notification duration refers to the length of time the cloud management platform needs to notify tenants in advance when recycling a cloud instance. 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.

[0060] (3) Usage duration refers to the maximum duration that a tenant uses a purchased cloud instance. It should be noted that the longer a cloud instance is used, the less likely the cloud management platform is to recycle such cloud instances. The shorter a cloud instance is used, the more likely the cloud management platform is to recycle such cloud instances. This indicates that the cloud management platform prioritizes reclaiming cloud instances with shorter usage durations. Generally, the price of a cloud instance is proportional to its usage duration, meaning that the longer the cloud instance is used, the higher its price, and the shorter the cloud instance is used, the lower its price.

[0061] (4) The recovery rate (also known as the interruption rate or release rate) refers to the probability that a cloud instance purchased by a tenant will be recovered. It should be noted that the cloud management platform will usually recycle cloud instances while trying to meet the recovery rate. Generally, the price of a 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.

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

[0063] 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 the tenant 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.

[0064] Since the number of cloud instances required by a tenant can be one or more, if the tenant requires multiple cloud instances, 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.

[0065] Based on this, after selecting one or more of the following: the desired cloud instance protection period, the desired cloud instance reclaim notification duration, the desired cloud instance usage duration, and the desired cloud instance reclaim rate, and after selecting the desired cloud instance specifications, the tenant can input this selected information into the cloud instance configuration interface through the client. The cloud instance configuration interface can then use this information as the desired cloud instance configuration information and send it to the cloud management platform.

[0066] For example, suppose a tenant needs to create VM 1, VM 2, and VM 3. After logging into the cloud management platform, the cloud management platform provides the tenant with a VM configuration interface that displays the protection period range, recycling notification time range, usage time range, and recycling rate range. The protection period range is 1 to 3 hours, the recycling notification time range is 1 minute to 1 hour, the usage time range is 5 to 10 hours, and the recycling rate range is 1% to 50%.

[0067] Then, on the VM configuration page, the tenant can set the protection period for VM 1 and VM 2 to 1 hour, the protection period for VM 3 to 3 hours, set the recycle notification time for VM 1, VM 2, and VM 3 to 30 minutes, set the usage time for VM 1 to 2 hours, the usage time for VM 2 to 3 hours, the usage time for VM 3 to 5 hours, and set the recycle rate for VM 1, VM 2, and VM 3 to 40%. Furthermore, the tenant can also set the specifications for VM 1, VM 2, and VM 3 on the VM configuration page.

[0068] 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.

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

[0070] After obtaining the cloud instance configuration information, the cloud management platform can parse it to determine the cloud instance specifications and reclaim conditions required by the tenant. The cloud management platform can then select a physical server with available capacity that supports the tenant's cloud instance specifications from among the multiple physical servers it manages, and create a tenant-specific cloud instance on that physical server. These cloud instances can then run the tenant's business, thereby meeting the tenant's business needs (i.e., successfully providing cloud services to the tenant).

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

[0072] (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.

[0073] (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.

[0074] (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 with 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 with 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. 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.

[0075] (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 required by the tenant. 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.

[0076] 203. 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 recycling conditions are met.

[0077] In the process of running the tenant's business on the tenant's exclusive cloud instance, once the available capacity of the physical server 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's exclusive cloud instance if the recycling conditions of the cloud instance set by the tenant are met, thereby releasing the capacity occupied by the recycled cloud instance to solve the problem of insufficient available capacity of the physical server.

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

[0079] (1) Assume that the cloud management platform has multiple tenant-specific cloud instances, and the recycling conditions set by the tenant 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 tenant for these multiple cloud instances, the cloud management platform can select at least one recyclable cloud instance from these multiple cloud instances. The at least one cloud instance selected by the cloud management platform satisfies at least one of the following: (1) The at least one recyclable cloud instance is outside its own protection period. (2) The usage duration of the at least one recyclable cloud instance 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 recyclable cloud instance 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 mean: 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 cores of the at least one recyclable cloud instance and the time when the tenant uses the cores of the multiple cloud instances is lower than or equal to the recycling rate, etc.

[0080] (2) As shown in FIG3 (FIG3 is a schematic diagram of the recycling notification duration provided in an embodiment of the present application), after determining at least one recyclable cloud instance, the cloud management platform may calculate the recycling notification duration of the first moment and the at least one cloud instance to obtain at least one second moment. Then, the cloud management platform may notify the tenant at the first moment that the at least one cloud instance is about to be recycled, and accordingly recycle the at least one recyclable cloud instance at the at least one second moment.

[0081] Continuing with the above example, when the cloud management platform determines that VMs 1, 2, and 3 need to be reclaimed, they have all been running for 1.5 hours. Both VMs 1 and 2 are outside their protection periods. However, if the cloud management platform reclaims both VMs 1 and 2, the reclaim rate is 66.7%, far greater than 40%. Therefore, the cloud management platform can choose to reclaim only VM 1 (because its usage time is less than VM 2's), resulting in a reclaim rate of 33.3%, less than 40%. After determining the reclaim decision, let's assume the current time is 10:00. Since the reclaim notification duration for VM 1 is 30 minutes, the cloud management platform determines that VM 1 will be reclaimed at 10:30. Therefore, the cloud management platform notifies the tenant of the upcoming reclaim of VM 1 at 10:00 and reclaims VM 1 at 10:30.

[0082] To further understand the cloud instance management method based on the cloud management platform provided by the embodiment of the present application, the method is further introduced below with reference to multiple application examples. FIG4 is a schematic diagram of an application example of the cloud instance management method based on the cloud management platform provided by the embodiment of the present application. As shown in FIG4, the application example includes:

[0083] 1. Based on their business characteristics, tenants select unstable cloud instances as their required products and input the product configuration information into the cloud management platform. The cloud management platform can calculate the product price based on the configuration information through the price calculation module and provide it to the tenant for review.

[0084] 2. After the tenant agrees to the price, they can enter a purchase request for the product into the control panel.

[0085] 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.

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

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

[0088] 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 free up corresponding resources.

[0089] FIG5a is 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. As shown in FIG5a , the application example includes:

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

[0091] Figure 4 shows the distribution of tenant task execution times in this big data scenario. The longest tenant task execution time in this scenario is 22 minutes. Tenants can choose a 25-minute reclaim notification period for unstable cloud instances. Since tenants have no requirements for the reclaim rate or protection period, they can choose the highest reclaim rate and shortest protection period for unstable cloud instances within the range of options provided by the cloud management platform. This way, tenants can meet their business needs while achieving the lowest cost.

[0092] FIG5 b is 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. As shown in FIG5 b , the application example includes:

[0093] Take a website business scenario as an example. In this scenario, the website's user access 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.

[0094] In this website scenario, to ensure a good user experience and guaranteed access success, the website wants to maintain a low recovery rate for the unstable cloud instances it uses. Within the options provided by the cloud management platform, the website can select the lowest recovery rate, shortest recovery notification duration, and shortest protection period for the unstable cloud instances. This way, the website can achieve the lowest cost while meeting business requirements.

[0095] 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 with available capacity that supports the specifications of the cloud instance required by the tenant based on the configuration information, and create tenant-specific cloud instances 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 on which 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 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 not only completes the tenant's business, but also saves the tenant's usage costs.

[0096] 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 is a structural diagram of the cloud management platform provided in the embodiment of the present application. As shown in Figure 6, the cloud management platform includes:

[0097] A first acquisition module 601 is 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;

[0098] A creation module 602 is configured 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;

[0099] The recycling module 603 is configured 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.

[0100] 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 with available capacity that supports the specifications of the cloud instance required by the tenant based on the configuration information, and create tenant-specific cloud instances 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 on which 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 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 not only completes the tenant's business, but also saves the tenant's usage costs.

[0101] In one 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.

[0102] 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 a 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.

[0103] 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.

[0104] 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.

[0105] 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, where 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, where the purchase request is used to indicate that the tenant agrees to the price; and create module 602, used for the cloud management platform to select a physical server with available capacity supporting specifications based on the purchase request and configuration information.

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

[0107] 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 no further details will be given here.

[0108] Please refer to Figure 7, which is a schematic diagram of the structure of a computing device provided in an embodiment of the present application. As shown in Figure 7, 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 labeled 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.

[0109] 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 (ASICs), one or more digital signal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For example, when a unit in the apparatus can be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

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

[0111] Memory 702 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. Nonvolatile memory may be read-only memory (ROM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may be 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 DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0112] Memory 702 stores executable program code. Processor 701 executes this executable program code to implement the functions of the aforementioned first acquisition module, creation module, and recovery module, thereby implementing the aforementioned cloud instance management method based on the cloud management platform. In other words, memory 702 stores instructions for executing the aforementioned cloud instance management method based on the cloud management platform.

[0113] 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.

[0114] In addition to the data bus, bus 704 may also include a power bus, a control bus, and a status signal bus. The bus may be a Peripheral Component Interconnect Express (PCIe) bus, an Extended Industry Standard Architecture (EISA) bus, a unified bus (Ubus or UB), a Compute Express Link (CXL), or a Cache Coherent Interconnect for Accelerators (CCIX). Buses can be categorized as address buses, data buses, and control buses.

[0115] Please refer to FIG8 , which is a schematic diagram of a computing device cluster provided in an embodiment of the present application. As shown in FIG8 , the computing device cluster 800 includes at least one computing device 700 .

[0116] 8 , 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.

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

[0118] It should be noted that the memory 702 in different computing devices 700 in the computing device cluster 800 may store different instructions, each for executing a portion of the functions of the aforementioned cloud management platform. In other words, the instructions stored in the memory 702 in different computing devices 700 may implement the functions of one or more modules such as the first acquisition module, the creation module, and the recycling module.

[0119] 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.

[0120] Please refer to Figure 9, which is a schematic diagram of computer devices in a computer cluster provided by an embodiment of the present application being connected via a network. As shown in Figure 9, two computing devices 700A and 700B are connected via a network. Specifically, each computing device is connected to the network via a communication interface.

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

[0122] It should be understood that the functions of the computing device 700A shown in Figure 9 may also be completed by multiple computing devices. Similarly, the functions of the computing device 700B may also be completed by multiple computing devices.

[0123] An 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 steps executed by the cloud management platform in the embodiment shown in Figure 2.

[0124] An embodiment of the present application also relates to a computer program product, which stores instructions that, when executed by a computer, enable the computer to execute the steps performed by the cloud management platform in the embodiment shown in FIG2 .

[0125] Those skilled in the art will 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.

[0126] In the several embodiments provided in this 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 merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, 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.

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

[0128] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0129] 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 for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

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