Resource orchestration method based on cloud computing technique, and cloud management platform

Abstract

Provided in the present application is a resource orchestration method based on a cloud computing technique. The method is applied to a cloud management platform and comprises determining a resource change set and orchestration steps on the basis of a resource request, wherein at least one of the orchestration steps comprises at least one orchestration unit, the orchestration unit comprises a plurality of operations for the same type of cloud resources among cloud resources to be changed, and all of the plurality of operations for the same type of cloud resources among the cloud resources to be changed are identical. By means of aggregating identical operations for the same type of resources, a batch change for aggregated units is realized; and by means of orchestrating, on the basis of orchestration steps, cloud resources to be changed, the response pressure of a cloud resource interface is reduced, thereby improving system stability and reliability, and improving the orchestration efficiency.

Description

A resource orchestration method and cloud management platform based on cloud computing technology

[0001] This application claims priority to Chinese patent application No. 202311544616.0, filed on November 17, 2023, with the invention name “A resource orchestration method and device based on cloud computing technology”, and priority to Chinese patent application No. 202410622856.6, filed on May 16, 2024, with the invention name “A resource orchestration method and cloud management platform based on cloud computing technology”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of cloud computing technology, and in particular to a resource orchestration method and cloud management platform based on cloud computing technology. Background Art

[0003] With the increasing popularity of the Development & Operations (DevOps) model and the continuous promotion of enterprise cloud migration and cloud native demands, more and more large users have begun to migrate their businesses to the cloud and use the Infrastructure as Code (IaC) model to manage their cloud resources to achieve a higher rate of automation. Currently, in order to achieve the integration and automation of development, testing, deployment and operation and maintenance, powerful deployment systems have been built in existing technologies. In the deployment system, users can use resource templates to describe the target resource state of the cloud resources to be changed. The deployment system can then make resource changes to the resources in the deployment environment according to the obtained resource templates and the automated process.

[0004] However, when a large number of resources are deployed simultaneously, the resource orchestration system will put great pressure on the availability of downstream services, especially in high-concurrency scenarios for the same resource. The reliability of the resource orchestration system will be greatly impacted. At the same time, resource competition will increase service response latency and reduce the overall operating efficiency of the system.

[0005] Summary of the Invention

[0006] This application provides a resource orchestration method and cloud management platform based on cloud computing technology. By determining the resource change set and orchestration steps according to resource requests, and aggregating the same operations on resources of the same type, batch changes to aggregated units are achieved, thereby improving change efficiency and reducing the complexity of repeated system calls.

[0007] In a first aspect, the present application provides a resource orchestration method based on cloud computing technology. The method is applied to a cloud management platform, which is used to manage infrastructure on which cloud resources run. Specifically, the method includes the following steps: obtaining a resource request, wherein the resource request includes a target state of a target cloud resource. Furthermore, the cloud management platform determines a resource change set based on the resource request, wherein the resource change set includes a cloud resource to be changed and at least one operation for the cloud resource to be changed, wherein the current state of the cloud resource to be changed is different from the target state of the cloud resource to be changed, and the at least one operation is used to instruct the cloud resource to adjust from the current state to the target state. Furthermore, the cloud management platform determines an orchestration step based on the resource change set, wherein at least one of the orchestration steps includes at least one orchestration unit, wherein the orchestration unit includes multiple operations for the same type of cloud resource in the cloud resource to be changed, wherein each of the multiple operations for the same type of cloud resource in the cloud resource to be changed is identical. Thus, the cloud management platform orchestrates the cloud resource to be changed according to the orchestration step. In the solution provided by the present application, the cloud management platform determines the resource change set based on the obtained resource request, and then determines the orchestration step. It is worth noting that one or more of the orchestration steps include an orchestration unit, which is an execution unit for the cloud management platform to orchestrate cloud resources. When the cloud management platform orchestrates cloud resources in parallel, each orchestration unit is one path in parallel execution. The orchestration unit includes multiple operations for the same type of cloud resources in the cloud resources to be changed, and each of the multiple operations for the same type of cloud resources in the cloud resources to be changed is the same. By aggregating multiple operations for the same type of cloud resources in the cloud resources to be changed, batch calls to the same application programming interface (API) are realized, the number of calls to the same API interface is reduced, the response pressure of the cloud resource interface is reduced, the system stability and reliability are improved, and the orchestration efficiency is improved.

[0008] In conjunction with the first aspect, in a possible implementation of the first aspect, determining a resource change set based on a resource request specifically includes the following steps: determining dependent cloud resources based on the resource request, wherein at least one of the dependent cloud resources is dependent on at least one of the target cloud resources. Furthermore, determining a resource change set based on the dependent cloud resource set, wherein the resource change set includes the cloud resources to be changed and at least one operation for the cloud resources to be changed, wherein the cloud resources to be changed include the target cloud resources and the dependent cloud resources.

[0009] In the solution provided by this application, a resource request can only include the target state of the target resource. When the target state of the target resource changes, the dependent cloud resources running on the infrastructure that depend on the target resource also need to be changed and adjusted accordingly. By analyzing the resource request, the cloud management platform can simultaneously determine the dependent cloud resources and the target cloud resources, thereby determining the full set of cloud resources to be changed, improving the accuracy of cloud resource orchestration.

[0010] In combination with the first aspect, in a possible implementation of the first aspect, before determining the orchestration steps based on the resource change set, the cloud management platform determines the dependency relationship between at least one operation for the cloud resource to be changed and other operations based on the resource change set. Based on this, the orchestration steps are determined based on the resource change set. Specifically, the orchestration steps are determined based on the resource change set and the dependency relationship. The orchestration steps include a first orchestration step and a second orchestration step, wherein the first orchestration step is an orchestration step that precedes the second orchestration step.

[0011] In the solution provided by this application, in order to further determine the execution order of each step in the orchestration step, it is necessary to parse the operation of the cloud resource to be changed with other operations, determine the dependency relationship between the operations, and then determine the execution order of the orchestration steps. Therefore, the cloud management platform parses the resource change set to determine the dependency relationship between at least one operation on the cloud resource to be changed and other operations, and then determines the orchestration steps based on the resource change set and the dependency relationship. The orchestration steps obtained based on this are more accurate and take into account the dependency relationship between cloud resources and between operations on cloud resources. The system reliability is improved, while the high availability of dependent cloud resources is also improved.

[0012] In combination with the first aspect, in a possible implementation of the first aspect, the cloud management platform manages a resource change template and obtains a resource request. Specifically, the resource request input by the user according to the resource change template is obtained, and the resource request includes the target state of the target cloud resource.

[0013] In the solution provided in this application, when users need to create, delete, change, and other operations on cloud resources, they can edit or enter resource requests through the resource change template provided by the cloud management platform. The cloud management platform determines the resource request based on the content input by the user, and further determines the target cloud resources and the target status of the target cloud resources, which is conducive to improving the accuracy and efficiency of determining resource requests.

[0014] In combination with the first aspect, in a possible implementation of the first aspect, the infrastructure stores the user's resource change history record. Specifically, the cloud management platform obtains the resource change history record and determines the resource request based on the resource change history record. The resource request includes the target state of the target cloud resource.

[0015] In the solution provided in this application, the cloud management platform can store and obtain historical change records of user resource operations based on the user's authorization. For example, the user deletes some cloud resources at the end of each month and creates some cloud resources at the beginning of each month. After the cloud management platform obtains the user's authorization, it can determine the resource request based on the user's resource change history record, thereby realizing cloud resource orchestration for fixed time periods or corresponding usage records, thereby improving the configurability of the system.

[0016] In combination with the first aspect, in a possible implementation of the first aspect, the cloud management platform also manages a concurrency strategy, wherein the concurrency strategy is used to indicate the maximum number of orchestration units supported for parallel execution in each orchestration step, and the orchestration step is determined based on the resource change set and the dependency relationship. Specifically, the cloud management platform determines the orchestration step based on the resource change set, the dependency relationship, and the concurrency strategy, and the orchestration step includes a first orchestration step and a second orchestration step, wherein the maximum number of orchestration units indicated in parallel in the first orchestration step is the same as the maximum number of orchestration units executed in parallel in the second orchestration step.

[0017] In the solution provided in this application, the cloud management platform can manage concurrency strategies and concurrency based on the platform's own processing capabilities or receive user configurations. By managing concurrency strategies, it is possible to control the number of parallel execution orchestration units. When the system processing capacity is reduced, the system reliability can be ensured by adopting a strategy of reducing concurrency; when the system processing capacity is high, the cloud resource orchestration efficiency can be improved by adopting a strategy of high concurrency, thereby achieving controllable orchestration efficiency.

[0018] In combination with the first aspect, in a possible implementation of the first aspect, after the orchestration of the cloud resources to be changed is completed, the cloud management platform records status information of the cloud resources to be changed.

[0019] In the solution provided in this application, after the cloud management platform completes the orchestration of the cloud resources to be changed, it needs to record the status information of the cloud resources to be changed. When there is client access or request, the status information needs to be provided to the user for viewing, so as to achieve rapid notification and information synchronization of the client.

[0020] In combination with the first aspect, in a possible implementation of the first aspect, before determining the resource change set based on the resource template, the cloud management platform obtains the current status of the target cloud resource and determines the resource change set based on the resource request and the current status of the target cloud resource. The resource change set includes the cloud resource to be changed and at least one operation for the cloud resource to be changed.

[0021] In the solution provided by this application, the cloud management platform can determine the resource change set by obtaining the current state of the target cloud resource and comparing it with the target state of the target resource in the resource request. The current state of the target cloud resource can be obtained by querying the current state of the recorded target resource or by querying the current state of the corresponding target resource running in the infrastructure, without limitation, thereby improving the accuracy and timeliness of resource state acquisition.

[0022] The second aspect or any implementation of the second aspect is a cloud management platform implementation corresponding to the first aspect or any implementation of the first aspect. The description of the first aspect or any implementation of the first aspect is applicable to the second aspect or any implementation of the second aspect, and will not be repeated here.

[0023] In a third aspect, the present application provides a computing device cluster comprising at least one computing device, each computing device comprising a processor and a memory; the processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the above-mentioned first aspect and a method combined with any one of the implementation methods of the above-mentioned first aspect.

[0024] In a fourth aspect, the present application provides a computer program product comprising instructions, which, when executed by a computer device cluster, enables the computer device cluster to execute the above-mentioned first aspect and a method combined with any one of the implementation modes of the above-mentioned first aspect.

[0025] In a fifth aspect, the present application provides a computer-readable storage medium comprising computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the above-mentioned first aspect and a method combined with any one of the implementation methods of the above-mentioned first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG1 is a schematic diagram of an application scenario of a resource orchestration method based on cloud computing technology provided in an embodiment of the present application;

[0027] FIG2 is a schematic diagram of a cloud resource orchestration architecture provided by an embodiment of the present application;

[0028] FIG3 is a flow chart of a resource orchestration method based on cloud computing technology provided in an embodiment of the present application;

[0029] FIG4 is another flow chart of a resource orchestration method based on cloud computing technology provided in an embodiment of the present application;

[0030] FIG5 is another flow chart of a resource orchestration method based on cloud computing technology provided in an embodiment of the present application;

[0031] FIG6 is another flow chart of a resource orchestration method based on cloud computing technology provided in an embodiment of the present application;

[0032] 7 is a schematic diagram of state information of a resource orchestration method based on cloud computing technology provided in an embodiment of the present application;

[0033] FIG8 is a schematic diagram of an arrangement step of a resource arrangement method based on cloud computing technology provided in an embodiment of the present application;

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

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

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

[0037] FIG12 is a schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application;

[0038] FIG13 is a schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following is a clear and complete description of the technical solutions in the embodiments of the present application in conjunction with the accompanying drawings. Obviously, the embodiments described are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0040] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0041] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0042] First, the nouns that appear in this article are explained as follows:

[0043] Development and Operations (DevOps): DevOps is a culture and movement that integrates software development and operations. Under the DevOps model, development and operations teams are treated as one, rather than two isolated teams. Engineers from both teams collaborate across the entire software lifecycle (from development and testing to deployment and operations), developing a range of skills beyond a single function.

[0044] Resource Orchestration Engine: Resource orchestration engine, also known as Target Resource Status Based Resource Formation Engine. Using the resource orchestration engine, you can determine which resources need to be changed based on the target resource status described in the resource template (the target resource status in this application can be understood as the desired resource status), and generate the corresponding resource change sequence so that changes such as deployment, change or deletion of resources can be implemented according to the resource change sequence. The core capability of the resource orchestration engine is that users do not need to pay attention to the specific steps to reach the target resource status, but only need to describe the desired target resource status in the resource template.

[0045] Resource Template: A resource template can be understood as a text file or a collection of files used to describe the state of multiple target resources. In practical applications, resource templates can be described using Domain Specific Language (DSL) syntax.

[0046] Resource Stack: A resource stack, also known as a resource stack, is a logical management object used by users to manage physical and logical resources using the resource orchestration engine. In practical applications, a resource stack can be understood as a collection of multiple resources. When modifying resources using resource templates or performing dry runs, the resource stack can be used as the execution unit.

[0047] Resource Status: A data record used to record the status of all resources in a resource stack in the resource orchestration engine. It contains detailed information about all resources in the resource stack.

[0048] Targeted Resource Template: The target resource state refers to the target state of the resource at the end of the expected change described by the resource template. Its core point is to describe what the target state is, rather than what process is used to achieve the target state.

[0049] An Application Programming Interface (API) is a computing interface that defines the interactions between multiple software intermediaries, including the types of calls or requests that can be made, how to make them, the data formats used, and the conventions to be followed. Applications encapsulate their service capabilities into APIs through predefined functions and make them available to users through an API gateway. APIs include basic information, request paths and parameters between the frontend and backend, and the request protocol.

[0050] Cloud data center: A data center that provides cloud resources, also known as infrastructure. The infrastructure includes multiple cloud data centers, each of which includes multiple servers. Each server can provide computing, network, and storage resources.

[0051] Cloud resources: Cloud resources can be an entity used by users on the cloud platform. For example, they can be cloud instances used to provide computing, network, or storage resources, including but not limited to Elastic Cloud Servers (ECS), containers, Bare Metal Servers (BMS), etc. They can also be Virtual Private Clouds (VPCs), virtual machines, some microservice applications, or high-level data models such as security policies and DNS records.

[0052] User: The subject who uses cloud resources. Users can register accounts with cloud resource providers through browsers or other clients. The cloud resource provider will record the accounts of different users and isolate cloud resources for different users based on the accounts.

[0053] Cloud management platform: A platform provided by cloud resource providers for interacting with users. Users can register accounts on the cloud management platform and use their accounts to access cloud resources, thereby becoming cloud resource users. The cloud management platform is also used to manage infrastructure and isolate computing, network, and / or storage resources used by different users based on their accounts. The cloud management platform is also used to call corresponding cloud resources based on user input instructions to meet user usage needs.

[0054] Region: Cloud resource providers set up cloud data centers in different geographical regions. Cloud devices in cloud data centers in different regions need to communicate through remote connection gateways.

[0055] The following describes the application scenarios of the technical solutions provided in the embodiments of this application:

[0056] Please refer to FIG1 , as shown in FIG1 , which is a schematic diagram of an application scenario of a resource orchestration method based on cloud computing technology provided by an embodiment of the present application, specifically:

[0057] As shown in Figure 1, the cloud management platform 20 is used to manage infrastructure 1. Infrastructure 1 includes cloud data center clusters set up in multiple regions. The exemplary multiple regions include region 10, region 11, and region 12. Each region is equipped with a cloud data center cluster (not shown in the figure). Each cloud data center includes multiple cloud data centers. The exemplary cloud data center in region 10 includes cloud data center 101, cloud data center 102, and cloud data center 103. The cloud data center cluster located in region 11 includes cloud data center 111, cloud data center 112, and cloud data center 113. The cloud data center cluster located in region 12 includes cloud data center 121, cloud data center 122, and cloud data center 123. Each cloud data center includes multiple servers. The exemplary data center 101 includes server 1011, server 1012...

[0058] Continuing with Figure 1, a cloud management platform 20 is used to manage network infrastructure 1. Tenant A connects to the internet via client 21 and logs in to cloud management platform 20 using an account pre-registered with the cloud management platform 20 and bound to tenant A. Tenant B connects to the internet via client 22 and logs in to cloud management platform 20 using an account pre-registered with the cloud management platform 20 and bound to tenant B. Cloud management platform 20 provides a configuration interface. Tenant A accesses the configuration interface via client 21 and enters resource request 1 on the configuration interface based on a resource change template provided by the cloud management platform. Tenant B accesses the configuration interface via client 22 and enters resource request 2 on the configuration interface based on a resource change template provided by the cloud management platform. Cloud management platform 20 obtains resource request 1 from the configuration interface and orchestrates the corresponding target cloud resources based on resource request 1. Tenants A and B are users of the cloud management platform 20 provider.

[0059] For example, in a public cloud scenario, each cloud data center can be identified by an availability zone (AZ). Different availability zones correspond to different cloud data centers, and cloud data centers can be located in one or more computer rooms. In a private cloud scenario, the infrastructure is managed by the user and includes at least one cloud data center. Each cloud data center includes at least one server, and cloud resources run on the at least one server. In a hybrid cloud scenario, the public cloud infrastructure is managed by a cloud management platform provided by the cloud resource provider, while the private cloud infrastructure is managed by the user.

[0060] Exemplarily, the client 21 and the client 22 may be terminal devices such as mobile phones with Internet access capabilities, personal computers, personal digital assistants, thin clients, vehicle-mounted hosts, or other terminal devices with Internet access capabilities.

[0061] It is worth noting that the public cloud application scenario is only one application scenario of the embodiment of the present application. The embodiment of the present application can also be applied to various scenarios such as hybrid cloud and private cloud, and the embodiment of the present application can also be implemented without limitation.

[0062] Please continue to refer to FIG2 , as shown in FIG2 , FIG2 is a schematic diagram of a cloud resource orchestration architecture provided by an embodiment of the present application, specifically:

[0063] S201. The cloud management platform 20 obtains a resource request input by a user.

[0064] S202. The cloud management platform 20 analyzes the target cloud resources in the resource request and determines the cloud resources to be orchestrated.

[0065] S203. The cloud management platform 20 orchestrates the target cloud resources on the infrastructure, and calls the corresponding API interface to perform a corresponding operation on the corresponding cloud resources.

[0066] S204. After completing resource orchestration, the cloud management platform records the final resource status.

[0067] As can be seen from the above steps, the cloud management platform calls an API interface for the corresponding cloud resource based on the resource request input by the user to implement the corresponding operation. When users input a large number of resource requests simultaneously, the cloud management platform also needs to call a large number of corresponding API interfaces to implement the corresponding cloud resource operations. The massive number of API interface call requests input simultaneously will significantly impact the availability of the corresponding cloud resource. In particular, repeated operations targeting the same cloud resource will repeatedly call the same API interface, causing the API interface to experience high call pressure in a short period of time, increasing response latency, and thus affecting the stability and reliability of the entire system.

[0068] To solve the above-mentioned problem, an embodiment of the present application provides a resource orchestration method based on cloud computing technology, which is applied to a cloud management platform. Specifically, the cloud management platform obtains a resource request, wherein the resource request includes the target state of the target cloud resource. Furthermore, the cloud management platform determines a resource change set based on the resource request. The resource change set includes the cloud resource to be changed and at least one operation for the cloud resource to be changed. The current state of the cloud resource to be changed is different from the target state of the cloud resource to be changed, and the at least one operation is used to instruct the cloud resource to adjust from the current state to the target state. Furthermore, the cloud management platform determines an orchestration step based on the resource change set. At least one of the orchestration steps includes at least one orchestration unit. The orchestration unit includes multiple operations for the same type of cloud resource in the cloud resource to be changed. Each of the multiple operations for the same type of cloud resource in the cloud resource to be changed is the same. Furthermore, the cloud management platform orchestrates the cloud resource to be changed according to the orchestration step.

[0069] Therefore, by aggregating multiple operations on the same type of cloud resources in the cloud resource changes, batch calls to the same API interface are realized, the number of calls to the same API is reduced, the response pressure of the cloud resource interface is alleviated, the system stability and reliability are improved, and the orchestration efficiency is improved.

[0070] Please continue to refer to FIG3 , which is a flow chart of a resource orchestration method based on cloud computing technology provided by an embodiment of the present application, and is described in conjunction with FIG1 , specifically:

[0071] S301. Obtain a resource request, where the resource request includes a target state of a target cloud resource.

[0072] The cloud management platform 20 obtains a resource request, which can be directly input by the user through the configuration interface provided by the cloud management platform 20, or the cloud management platform 20 provides a corresponding resource change template, and the user inputs the resource request according to the resource change template. The present invention does not impose any restrictions on this.

[0073] The resource request includes the target state of the target cloud resource. The target state may be the final state of the target resource expected by the user, or an intermediate state of the target cloud resource configured by the user at a certain stage.

[0074] It's worth noting that the definition of the target state of the target cloud resource can be determined based on the user's custom configuration; the cloud management platform can also obtain the user's resource request based on the user's configuration habits and with the user's authorization. For example, a user deletes some cloud resources at the end of each month and creates some at the beginning of each month. Once the cloud management platform obtains the user's authorization, it can determine the resource request based on the user's resource change history, thereby enabling cloud resource orchestration for fixed time periods or corresponding usage records, improving the system's configurability.

[0075] S302. Determine a resource change set according to the resource request, where the resource change set includes cloud resources to be changed and at least one operation for the cloud resources to be changed.

[0076] The cloud management platform 20 determines a resource change set based on the resource request. Under normal circumstances, the cloud management platform 20 can query the operation status of the corresponding target cloud resources on the infrastructure in sequence based on the target cloud resources in the resource request, and compare the current status of the queried target cloud resources with the target status to obtain the resource change set and at least one operation for the cloud resource to be changed. The at least one operation can be creation, deletion, adjustment, etc.

[0077] In another embodiment, please see FIG4 , which is another flow chart of a resource orchestration method based on cloud computing technology provided in an embodiment of the present application, specifically:

[0078] S401. Query resource record information stored in the infrastructure, where the resource record information includes the current status of the target cloud resource.

[0079] After obtaining the resource request, the cloud management platform 20 queries the resource record information stored in the infrastructure 1. The resource record information includes the current status of the target cloud resource.

[0080] S402. Determine a resource change set according to the resource request and the current state of the target cloud resource, where the resource change set includes the cloud resource to be changed and at least one operation for the cloud resource to be changed.

[0081] The cloud management platform 20 compares the current state of the target cloud resource with the target state of the target cloud resource in the resource request to determine the cloud resource to be changed. By pre-storing the current state of the target cloud resource through the infrastructure 1 and updating it regularly, the cloud management platform can obtain the corresponding resource state information more quickly, improving system processing efficiency.

[0082] Furthermore, when the cloud resources running on infrastructure 1 have a dependency relationship with the target cloud resources in the resource request, the change in the state of the target cloud resources will also cause the dependent cloud resources that depend on the target resources to make adaptive changes to match the corresponding cloud resources and ensure the normal operation of the cloud resources.

[0083] Based on this, the application embodiment further provides an example of obtaining a full amount of cloud resources to be changed. Please refer to Figure 5, which is another flow chart of the resource orchestration method based on cloud computing technology provided by the embodiment of the present application. Specifically:

[0084] S501. Determine dependent cloud resources according to the resource request.

[0085] The cloud management platform 20 determines the dependent cloud resources that depend on the target cloud resource based on the target state of the target cloud resource included in the resource request, wherein the dependent cloud resource can be other cloud resources running on the infrastructure 1, or it can be the first target cloud resource on which the second target cloud resource in the target cloud resource depends.

[0086] S502. Determine a resource change set based on dependent cloud resources.

[0087] The cloud management platform 20 determines a resource change set based on the dependent cloud resources. Therefore, the cloud resources to be changed in the resource change set include not only the target cloud resources but also the dependent cloud resources. By determining the full set of cloud resources to be changed that require adjustment, orchestration efficiency is greatly improved when orchestrating cloud resources that include dependent resources, avoiding repeated orchestration.

[0088] In another embodiment provided herein, the cloud management platform 20 can generate a directed acyclic graph (DAG) model of a resource change set based on a resource request. The DAG model can be a model with the cloud resources to be changed as nodes and the dependencies between resources as associations. Through the DAG model, the cloud resources to be changed and at least one operation on the cloud resources to be changed in the resource change set can be identified in the form of nodes and associations, facilitating the determination of subsequent orchestration steps.

[0089] S303. Determine an orchestration step according to the resource change set, where at least one step in the orchestration step includes at least one orchestration unit, and the orchestration unit includes multiple operations for the same type of cloud resources in the cloud resources to be changed.

[0090] The cloud management platform 20 determines an orchestration step based on the resource change set, wherein at least one step in the orchestration step includes at least one orchestration unit, and the orchestration unit includes multiple operations for the same type of cloud resources in the cloud resources to be changed. For example, the same type of cloud resources in the cloud resources to be changed can be cloud resources of the same type, such as Elastic Cloud Servers (ECS), or microservice applications of the same type, etc., but this embodiment of the application is not limited to this.

[0091] Furthermore, the unit that constitutes an orchestration step is an orchestration unit, and the orchestration unit is also the operation unit that the cloud management platform 20 calls the corresponding API interface to perform operations. In the method provided in the embodiment of the present application, in the process of the cloud management platform 20 determining the orchestration step based on the resource change set, multiple operations for the same type of cloud resources in the cloud resources to be changed are aggregated into an orchestration unit, and the orchestration unit can be an aggregation unit. Among them, each of the multiple operations is the same, or multiple operations for the same type of cloud resources can be implemented by calling an API interface. So that in the process of orchestrating the orchestration unit, the corresponding orchestration operation can be completed by calling the corresponding API interface only once. Reduce the number of calls to the API interface and improve the efficiency of cloud resource orchestration.

[0092] In one embodiment provided herein, the orchestration unit includes multiple operations targeting the same type of cloud resources among the cloud resources to be changed, or at least one operation targeting the cloud resources to be changed. Simply put, in addition to including multiple operations that aggregate the same type of cloud resources among the cloud resources to be changed, the orchestration unit may also include at least one operation targeting the cloud resources to be changed. The at least one operation typically refers to one or more API calls required to implement the corresponding cloud resources to be changed during the orchestration process.

[0093] In order to further achieve accurate division of orchestration steps and orchestration units, the present application provides another embodiment. Please continue to refer to Figure 6, which is another flow chart of the resource orchestration method based on cloud computing technology provided by the present application. Specifically:

[0094] S601. Determine, based on a resource change set, a dependency relationship between at least one operation on a cloud resource to be changed and other operations.

[0095] The cloud management platform 20 determines the dependency relationship between at least one operation on the cloud resources to be changed and other operations based on the resource change set, wherein the cloud resources to be changed include target cloud resources and dependent cloud resources, and the operations on the cloud resources to be changed include one or more and there are certain dependencies.

[0096] For example, the cloud resources to be changed include a first virtual private cloud (VPC) and a first elastic cloud server (ECS). The first operation on the first VPC is create, and the second operation on the first ECS is create. Since the first ECS depends on the first VPC, the second operation depends on the first operation. Therefore, if a third operation on the first ECS is restart, the third operation depends on the first operation.

[0097] Based on this, the cloud management platform 20 prepares for resource orchestration by determining the dependency relationship between at least one operation for the cloud resources to be changed and other operations, especially for the confirmation of orchestration steps, which requires dependencies and dependent resources to determine accurate and reliable orchestration steps and orchestration units.

[0098] S602: Determine the orchestration steps based on the resource change set and dependency relationships.

[0099] In an embodiment provided by the present application, the cloud management platform 20 determines an orchestration step based on a resource change set and dependency relationships, wherein the dependency relationship between at least one operation for the cloud resource to be changed and other operations has been determined in S601, and the orchestration step is further determined in combination with the cloud resource to be changed in the resource change set, wherein at least one of the orchestration steps includes at least one orchestration unit, and the orchestration unit includes multiple operations for the same type of cloud resources in the cloud resource to be changed, and each of the multiple operations for the same type of cloud resources in the cloud resource to be changed is the same.

[0100] In one example embodiment of the present application, cloud management platform 20 determines at least one orchestration unit in at least one orchestration step as an aggregate unit based on a resource change set and dependencies. Cloud resources of the same type within the aggregate unit do not have dependencies, multiple operations do not have dependencies, and each of the multiple operations is identical. Based on this, the operation that meets this condition is determined to be an aggregate unit, and the aggregate unit becomes an orchestration unit in the orchestration step.

[0101] The cloud management platform 20 also determines that at least one orchestration unit in at least one orchestration step is an independent unit based on the resource change set and dependency relationship, wherein at least one operation for the cloud resource to be changed in the independent unit does not depend on other operations, and the cloud resource to be changed does not depend on other resources. In this case, the independent unit is an orchestration unit in the orchestration step.

[0102] The cloud management platform 20 also determines, based on the resource change set and the dependency relationships, that at least one orchestration unit in at least one orchestration step is a common unit. The common unit includes at least one operation on the cloud resource to be changed, or the operation depends on other operations on the cloud resource to be changed, or the cloud resource to be changed is a dependent resource. In this case, the common unit is an orchestration unit in the orchestration step.

[0103] Furthermore, the cloud management platform 20 determines the orchestration steps according to the dependency relationship between the target resource and dependent resources in the cloud resource to be changed and the dependency relationship between at least one operation on the cloud resource to be changed and other operations.

[0104] Exemplarily, the cloud management platform 20 determines that the first orchestration step includes a first orchestration unit, which is an independent unit; the second orchestration step includes a second orchestration unit, which is an aggregated unit; and the third orchestration step includes a third orchestration unit, which is a common unit. Operations in the common units are dependent on operations in the aggregated units, or cloud resources in the common units are dependent on cloud resources in the aggregated units.

[0105] In another example, cloud management platform 20 determines that the first orchestration step includes a first orchestration unit, which is an aggregate unit; the second orchestration step includes a second orchestration unit, which is an independent unit; and the third orchestration step includes a third orchestration unit, which is a common unit. Operations in the common unit are dependent on operations in the aggregate unit, or cloud resources in the common unit are dependent on cloud resources in the aggregate unit.

[0106] In another example, cloud management platform 20 determines that the first orchestration step includes a first orchestration unit, which is an aggregate unit; the second orchestration step includes a second orchestration unit, which is a common unit; and the third orchestration step includes a third orchestration unit, which is an independent unit. Operations in the common units are dependent on operations in the aggregate unit, or cloud resources in the common units are dependent on cloud resources in the aggregate unit.

[0107] S602'. Determine the orchestration steps based on the resource change set, dependency, and concurrency strategy.

[0108] In another embodiment provided by the present application, the cloud management platform 20 manages a concurrency strategy, which can be user-configured, or the cloud management platform 20 determines the maximum number of parallel execution orchestration units in each orchestration step based on the system's processing capabilities and the pressure conditions of the API interface, thereby achieving control over the parallel execution orchestration capability and improving the stability of the system.

[0109] Exemplarily, in combination with step S602, the cloud management platform 20 determines that the concurrency is 2 based on the API interface call response capability of the current overall system, that is, the number of ways to execute the corresponding orchestration unit in parallel is 2. The cloud management platform 20 determines that the first orchestration step includes the first orchestration unit and the second orchestration unit based on the resource change set, dependency relationship and concurrency strategy, wherein the first orchestration unit is an aggregation unit and the second orchestration unit is an independent unit, and the second orchestration step includes the third orchestration unit, which is an ordinary unit. Among them, the operations in the ordinary unit depend on the operations in the aggregation unit, or the cloud resources in the ordinary unit depend on the cloud resources in the aggregation unit. Furthermore, the cloud management platform 20 can execute the first orchestration unit and the second orchestration unit in parallel, and continue to execute the second orchestration step after the previous order is executed.

[0110] It can be seen that the orchestration task that requires three orchestration steps to complete in serial mode can greatly improve the orchestration efficiency when executed in parallel.

[0111] S304: Orchestrate the cloud resources to be changed according to the orchestration steps.

[0112] The cloud management platform 20 orchestrates the cloud resources to be changed according to the determined orchestration steps. For common units and independent units in the orchestration steps, the cloud management platform 20 calls the API interface of the corresponding orchestration unit to complete the corresponding cloud resource changes. For aggregated units, the corresponding resources within the orchestration unit can be orchestrated using the batch API interface (Batch API).

[0113] Please continue to refer to FIG. 7 , which is a schematic diagram of status information of a resource orchestration method based on cloud computing technology provided by an embodiment of the present application. Specifically:

[0114] The cloud management platform 20 analyzes the cloud resource status after the orchestration is completed, especially after batch orchestration of aggregation units, it disassembles the changed cloud resources and restores the cloud resource granularity information defined in the resource template.

[0115] Exemplarily, after cloud management platform 20 completes the orchestration of the cloud resources to be changed according to the orchestration steps, infrastructure 1 provides feedback on the batch status of the cloud resources based on the cloud resource changes. This feedback includes the resource names and corresponding statuses of the batch cloud resources of resource type A in the aggregated units, and the resource names and corresponding statuses of the cloud resources of resource type B in the independent units. Cloud management platform 20 then parses the batch status information for resource type A based on the single resource type status information defined in the resource template input by the user, obtains the corresponding cloud resources of resource type A and resource type B, and the corresponding cloud resource attributes, achieving a one-to-one correspondence, and provides feedback to the tenant.

[0116] Please continue to refer to FIG8 , which is a schematic diagram of an arrangement step of a resource arrangement method based on cloud computing technology provided by an embodiment of the present application, specifically:

[0117] The cloud management platform 20 determines a resource change set based on the resource request, wherein the cloud resources to be changed include 6 cloud resources of the same type (as shown in FIG8 , cloud resources of the same shape are cloud resources of the same type) and 12 operations for the cloud resources to be changed (the numbers shown in the figure are operations for the cloud resources to be changed). Specifically, the cloud resources to be changed targeted by operations 1 and 7 are the first type of cloud resources, the cloud resources to be changed targeted by operations 5, 8, and 9 are the second type of cloud resources, the cloud resources to be changed targeted by operations 2 and 4 are the third type of cloud resources, the cloud resources to be changed targeted by operation 6 are the fourth type of cloud resources, the cloud resources to be changed targeted by operations 3 and 10 are the fifth type of cloud resources, and the cloud resources to be changed targeted by operations 11 and 12 are the sixth type of cloud resources. It is worth noting that for cloud resources of the same type, they can be the same cloud resources or different cloud resources, and the embodiments of the present application do not limit this.

[0118] Furthermore, the cloud resources to be changed targeted by operation 3 depend on the cloud resources to be changed targeted by operation 4, operation 4 depends on operation 2, and the cloud resources to be changed targeted by operation 2 depend on the cloud resources to be changed targeted by operation 1; the cloud resources to be changed targeted by operation 5 depend on the cloud resources to be changed targeted by operation 1, the cloud resources to be changed targeted by operation 6 depend on the cloud resources to be changed targeted by operation 5, the cloud resources to be changed targeted by operation 11 depend on the cloud resources to be changed targeted by operation 6, and the cloud resources to be changed targeted by operation 8 depend on the cloud resources to be changed targeted by operation 7.

[0119] The cloud management platform 20 determines the orchestration step based on the resource change set. As shown in FIG8 , the parallelism of the orchestration step is 2, that is, the number of parallel executable orchestration units is 2. The orchestration step includes steps 1, 2, 3, 4, and 5. Step 1 includes a first orchestration unit and a second orchestration unit. The first orchestration unit includes operations 1 and 7, and the second orchestration unit includes operation 9. Operations 1 and 7 are the same operation. The first orchestration unit is an aggregated unit, and the second orchestration unit has no dependencies and is an independent unit. Step 2 includes a third orchestration unit and a fourth orchestration unit. The third orchestration unit includes operations 5 and 8, and the fourth orchestration unit includes operation 10. Operations 5 and 8 are the same operation. There is no dependency between operations 5 and 8. The first orchestration unit is an aggregation unit. At the same time, because the cloud resources to be changed targeted by operation 5 depend on the cloud resources to be changed targeted by operation 1, and the cloud resources to be changed targeted by operation 8 depend on the cloud resources to be changed targeted by operation 7, the third orchestration unit is also a common unit that depends on the first orchestration unit. The fourth orchestration unit has no dependency and is an independent unit. Step 3 includes the fifth and sixth orchestration units. The fifth orchestration unit includes operation 2. The cloud resources to be changed targeted by operation 2 depend on the cloud resources to be changed targeted by operation 1. In the case of the cloud resources to be changed targeted by operation 6, the fifth orchestration unit is a common unit that depends on the first orchestration unit. The sixth orchestration unit includes operation 6. When the cloud resources to be changed targeted by operation 6 depend on the cloud resources to be changed targeted by operation 5, the sixth orchestration unit is a common unit that depends on the third orchestration unit. Step 4 includes a seventh orchestration unit and an eighth orchestration unit, wherein the seventh orchestration unit includes operation 4. When operation 4 depends on operation 2, the seventh orchestration unit is a common unit that depends on the fifth orchestration unit. The eighth orchestration unit includes operations 11 and 12. When the cloud resources to be changed targeted by operation 11 depend on the cloud resources to be changed targeted by operation 6, and operations 11 and 12 are the same operation and there is no dependency relationship between operations 11 and 12, the eighth orchestration unit is an aggregation unit and also a common unit that depends on the sixth orchestration unit. Step 5 includes a ninth orchestration unit, which includes operation 3. When the cloud resources to be changed targeted by operation 3 depend on the cloud resources to be changed targeted by operation 4, the ninth orchestration unit is a common unit that depends on the seventh orchestration unit.

[0120] Based on the orchestration steps, the cloud management platform 20 implements the orchestration of the cloud resources to be changed according to the corresponding orchestration steps.

[0121] Through the embodiments provided in this application, it is possible to complete the resource orchestration task of 6 types of cloud resources to be changed and 12 operations with only 5 concurrent orchestration steps and 9 orchestration units, which greatly improves the resource orchestration efficiency, reduces the response pressure of the API interface during the calling process, and improves system stability.

[0122] The present application also provides a cloud management platform. Please refer to Figure 9 below, which is a schematic diagram of the structure of a cloud management platform provided by the present application. The details are as follows:

[0123] An acquisition module 901 is configured to acquire a resource request, where the resource request includes a target state of a target cloud resource.

[0124] a determination module 902 configured to determine a resource change set based on the resource request, the resource change set comprising a cloud resource to be changed and at least one operation for the cloud resource to be changed, wherein a current state of the cloud resource to be changed is different from a target state of the cloud resource to be changed, and the at least one operation is configured to instruct the cloud resource to adjust from the current state to the target state;

[0125] The determining module 902 is further configured to determine an orchestration step based on the resource change set, wherein at least one orchestration step in the orchestration step includes at least one orchestration unit, the orchestration unit includes multiple operations for the same type of cloud resources in the to-be-changed cloud resources, and each of the multiple operations for the same type of cloud resources in the to-be-changed cloud resources is identical.

[0126] The orchestration module 903 is configured to orchestrate the cloud resources to be changed according to the orchestration steps.

[0127] The recording module 904 is configured to record the status information of the cloud resources to be changed after the orchestration of the cloud resources to be changed is completed.

[0128] The acquisition module 901, determination module 902, arrangement module 903, and recording module 904 can all be implemented via software or hardware. For example, the implementation of acquisition module 901 will be described below using acquisition module 901 as an example. Similarly, the implementation of determination module 902, arrangement module 903, and recording module 904 can refer to the implementation of acquisition module 901.

[0129] As an example of a software functional unit, the acquisition module 901 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the computing instance may be one or more. For example, the acquisition module 901 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same area or in different areas. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone or in different availability zones, each availability zone including one data center or multiple geographically close data centers. Typically, a region may include multiple availability zones.

[0130] As an example of a hardware functional unit, the acquisition module 901 may include at least one computing device, such as a server. Alternatively, the acquisition module 901 may be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0131] It should be noted that, in other embodiments, the acquisition module 901 can be used to execute any step in the resource orchestration method based on cloud computing technology, the determination module 902 can be used to execute any step in the resource orchestration method based on cloud computing technology, the orchestration module 9034 can be used to execute any step in the resource orchestration method based on cloud computing technology, and the recording module 904 can be used to execute any step in the resource orchestration method based on cloud computing technology. The steps that the acquisition module 901, the determination module 902, the orchestration module 903, and the recording module 904 are responsible for implementing can be specified as needed. By having the acquisition module 901, the determination module 902, the orchestration module 903, and the recording module 904 respectively implement different steps in the resource orchestration method based on cloud computing technology, the full functionality of the cloud management platform is realized.

[0132] The above details the method, cloud management platform and system of the embodiments of the present application. In order to facilitate better implementation of the above schemes of the embodiments of the present application, correspondingly, relevant equipment for cooperating in implementing the above schemes is also provided below.

[0133] This application provides a computing device. Please refer to Figure 10 below, which is a schematic diagram of the computing device structure provided by an embodiment of this application. Computing device 900 includes a bus 907, a processor 908, a memory 906, and a communication interface 909. Processor 908, memory 906, and communication interface 909 communicate with each other via bus 907. Computing device 900 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in computing device 900.

[0134] Bus 907 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, for example. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG10 illustrates a single bus line, but this does not imply a single bus or type of bus. Bus 907 may include a path for transmitting information between various components of computing device 900 (e.g., memory 906, processor 908, and communication interface 909).

[0135] The processor 908 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0136] The memory 906 may include volatile memory, such as random access memory (RAM). The processor 908 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0137] Memory 906 stores executable program code, and processor 908 executes the executable program code to implement the functions of acquisition module 901 and determination module 902, thereby implementing the resource orchestration method based on cloud computing technology. In other words, memory 906 stores instructions for the cloud management platform to execute the resource orchestration method based on cloud computing technology.

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

[0139] Embodiments of the present application also provide a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0140] Please refer to Figure 11 below, which is a schematic diagram of the structure of a computing device cluster for a resource orchestration method based on cloud computing technology according to an embodiment of the present application. As shown in Figure 11, the computing device cluster includes at least one computing device 900. Memory 906 in one or more computing devices 900 in the computing device cluster may store instructions for executing the resource orchestration method based on cloud computing technology on the same cloud management platform.

[0141] In some possible implementations, one or more computing devices 900 in the computing device cluster may also be used to execute some of the instructions of the cloud management platform for executing the resource orchestration method based on cloud computing technology. In other words, the combination of one or more computing devices 900 can jointly execute the instructions of the cloud management platform for executing the resource orchestration method based on cloud computing technology.

[0142] It should be noted that the memory 906 in different computing devices 900 in the computing device cluster can store different instructions for executing some functions of the cloud management platform. In other words, the instructions stored in the memory 906 in different computing devices 900 can implement the functions of one or more of the acquisition module 901, determination module 902, orchestration module 903, and recording module 904.

[0143] In some possible implementations, the memory 906 of one or more computing devices 900 in the computing device cluster may also store partial instructions for executing the resource orchestration method based on cloud computing technology. In other words, the combination of one or more computing devices 900 can jointly execute the instructions for executing the resource orchestration method based on cloud computing technology.

[0144] Please refer to Figure 12 below, which is another structural diagram of a computing device cluster for the resource orchestration method based on cloud computing technology in an embodiment of the present application. As shown in Figure 12, two computing devices 900A and 900B are connected via a communication interface 909. The memory in the computing device 900A stores instructions for executing the acquisition module 901 and the recording module 904. The memory in the computing device 900B stores instructions for executing the functions of the determination module 902 and the orchestration module 903. In other words, the memories 906 of the computing devices 900A and 900B jointly store instructions for the cloud management platform to execute the resource orchestration method based on cloud computing technology.

[0145] The connection method between the computing device clusters shown in FIG12 may be based on the fact that the resource orchestration method based on cloud computing technology provided in this application requires a large amount of data transmission to the acquisition module 901 and the recording module 904. Considering the data transmission volume and to avoid overloading the computing device 900A, the functions of the determination module 902 and the orchestration module 903 are delegated to the computing device 900B.

[0146] It should be understood that the functionality of the computing device 900A shown in FIG12 may also be accomplished by multiple computing devices 900. Similarly, the functionality of the computing device 900B may also be accomplished by multiple computing devices 900.

[0147] Please refer to Figure 13 below, which is another structural diagram of a computing device cluster of a resource orchestration method based on cloud computing technology in an embodiment of the present application. In some possible implementations, one or more computing devices in the computing device cluster can be connected via a network. The network can be a wide area network or a local area network, etc. Figure 13 shows a possible implementation. As shown in Figure 13, two computing devices 900C and 900D are connected via a network. Specifically, the network is connected through a communication interface in each computing device. In this type of possible implementation, the memory 906 in the computing device 900C stores instructions for executing the acquisition module 901 and the recording module 904. At the same time, the memory 906 in the computing device 900D stores instructions for executing the determination module 902 and the orchestration module 903.

[0148] The connection method between the computing device clusters shown in Figure 13 can be based on the fact that the resource orchestration method based on cloud computing technology provided by this application requires a large amount of data transmission and needs to be connected through a network. The functions of the acquisition module 901 and the recording module 904 are relatively independent. In order to achieve the best storage and computing performance, it is considered to entrust the functions of the determination module 902 and the orchestration module 903 to the computing device 900D for execution.

[0149] It should be understood that the functionality of the computing device 900C shown in FIG13 may also be accomplished by multiple computing devices 900. Similarly, the functionality of the computing device 900D may also be accomplished by multiple computing devices 900.

[0150] In some possible implementations, the memory 906 of one or more computing devices 900 in the computing device cluster may also store partial instructions for executing the resource orchestration method based on cloud computing technology. In other words, the combination of one or more computing devices 900 can jointly execute the instructions for executing the resource orchestration method based on cloud computing technology.

[0151] The present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be executed on a computing device or stored in any available medium. When the computer program product is executed on at least one computing device, the at least one computing device executes the aforementioned resource orchestration method for a cloud management platform based on cloud computing technology.

[0152] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned resource orchestration method applied to the cloud management platform for executing cloud computing technology.

[0153] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the embodiments of the present application.

[0154] Those skilled in the art will clearly understand that the specific working process of the above-described system, cloud management platform or unit can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0155] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0156] The present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be executed on a computing device or stored in any available medium. When the computer program product is executed on at least one computing device, the at least one computing device executes the aforementioned resource orchestration method for a cloud management platform based on cloud computing technology.

[0157] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned resource orchestration method applied to the cloud management platform for executing cloud computing technology.

[0158] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the embodiments of the present application.

[0159] Those skilled in the art will clearly understand that the specific working process of the above-described system, cloud management platform or unit can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0160] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A cloud resource orchestration method based on cloud computing technology, characterized in that: The method is applied to a cloud management platform, the cloud management platform is used to manage infrastructure, and cloud resources are running on the infrastructure. The method includes: Obtaining a resource request, wherein the resource request includes a target state of a target cloud resource; Determining a resource change set according to the resource request, the resource change set including a cloud resource to be changed and at least one operation for the cloud resource to be changed, wherein a current state of the cloud resource to be changed is different from a target state of the cloud resource to be changed, and the at least one operation is used to instruct the cloud resource to be adjusted from the current state to the target state; Determine an orchestration step according to the resource change set, at least one of the orchestration steps includes at least one orchestration unit, the orchestration unit includes multiple operations for the same type of cloud resources in the to-be-changed cloud resources, and each of the multiple operations for the same type of cloud resources in the to-be-changed cloud resources is the same; The cloud resources to be changed are orchestrated according to the orchestration steps.

2. The method according to claim 1, characterized in that The determining of a resource change set according to the resource request comprises: determining dependent cloud resources according to the resource request, wherein at least one of the dependent cloud resources is dependent on at least one of the target cloud resources; A resource change set is determined according to the dependent cloud resources, wherein the resource change set includes cloud resources to be changed and at least one operation for the cloud resources to be changed, wherein the cloud resources to be changed include the target cloud resources and the dependent cloud resources.

3. The method according to claim 1 or 2, characterized in that: Before determining the orchestration step according to the resource change set, the method further includes: Determining the dependency relationship between at least one operation on the to-be-changed cloud resource and other operations according to the resource change set; the step of determining the orchestration according to the resource change set includes: The orchestration step is determined according to the resource change set and the dependency relationship, and the orchestration step includes a first orchestration step and a second orchestration step, wherein the first orchestration step is a step that is orchestrated before the second orchestration step.

4. The method according to any one of claims 1 to 3, characterized in that: The cloud management platform manages a resource change template, and the resource request acquisition includes: A resource request input by a user according to the resource change template is obtained, where the resource request includes a target state of a target cloud resource.

5. The method according to any one of claims 1 to 4, characterized in that: The infrastructure stores the resource change history of the user, and the resource acquisition request includes: Obtain the resource change history record; The resource request is determined according to the resource change history record, and the resource request includes a target state of a target cloud resource.

6. The method according to any one of claims 1 to 5, characterized in that: The cloud management platform further manages a concurrency strategy, which is used to indicate the maximum number of orchestration units supported to be executed in parallel in each orchestration step. The determining of the orchestration step according to the resource change set and the dependency relationship includes: The orchestration step is determined according to the resource change set, the dependency relationship, and the concurrency strategy, wherein the orchestration step includes the first orchestration step and the second orchestration step, wherein a maximum number of orchestration units executed in parallel in the first orchestration step is the same as a maximum number of orchestration units executed in parallel in the second orchestration step.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: When the arrangement of the cloud resources to be changed is completed, the state information of the cloud resources to be changed is recorded.

8. The method according to any one of claims 1 to 7, characterized in that Before determining a resource change set according to the resource template, the method further includes: Obtaining the current status of the target cloud resource; The determining of a resource change set according to the resource request comprises: The resource change set is determined according to the resource request and the current state of the target cloud resource, wherein the resource change set includes the cloud resource to be changed and at least one operation for the cloud resource to be changed.

9. A cloud management platform, characterized in that: The cloud management platform is used to manage infrastructure, on which cloud resources run, and the cloud management platform includes: An acquisition module, the acquisition module is used to acquire a resource request, the resource request includes a target state of a target cloud resource; A determination module is used to determine a resource change set according to the resource request, wherein the resource change set includes a resource to be changed. a cloud resource and at least one operation for the cloud resource to be changed, wherein a current state of the cloud resource to be changed is different from a target state of the cloud resource to be changed, and the at least one operation is used to instruct the cloud resource to adjust from the current state to the target state; The determining module is further configured to determine an orchestration step according to the resource change set, wherein at least one of the orchestration steps includes at least one orchestration unit, and the orchestration unit includes multiple operations for the same type of cloud resources in the to-be-changed cloud resources, and each of the multiple operations for the same type of cloud resources in the to-be-changed cloud resources is the same; An orchestration module, the orchestration module is used to orchestrate the cloud resources to be changed according to the orchestration steps.

10. The cloud management platform according to claim 9, characterized in that: The resource change set is determined according to the resource request, then: The determination module is specifically configured to determine dependent cloud resources according to the resource request, wherein at least one cloud resource among the dependent cloud resources depends on at least one cloud resource among the target cloud resources; The determination module is further used to determine a resource change set based on the dependent cloud resource set, wherein the resource change set includes cloud resources to be changed and at least one operation for the cloud resources to be changed, wherein the cloud resources to be changed include the target cloud resources and the dependent cloud resources.

11. The cloud management platform according to claim 9 or 10, characterized in that: Before determining the orchestration steps according to the resource change set, then: The determination module is further configured to determine, according to the resource change set, a dependency relationship between at least one operation on the to-be-changed cloud resource and other operations; the orchestration step is determined according to the resource change set, then: The determination module is specifically used to determine the orchestration step according to the resource change set and the dependency relationship, and the orchestration step includes a first orchestration step and a second orchestration step, wherein the first orchestration step is an orchestration step that precedes the second orchestration step.

12. The cloud management platform according to any one of claims 9 to 11, characterized in that: The cloud management platform manages resource change templates, then: The acquisition module is specifically used to acquire a resource request input by a user according to the resource change template, and the resource request includes a target state of a target cloud resource.

13. The cloud management platform according to any one of claims 9 to 12, characterized in that: The infrastructure stores the resource change history of the user, then: The acquisition module is specifically used to acquire the resource change history record of the user; The determination module is further configured to determine the resource request according to the resource change history record, wherein the resource request includes a target state of a target cloud resource.

14. The cloud management platform according to any one of claims 9 to 13, characterized in that: The cloud management platform also manages a concurrency strategy, which is used to indicate the maximum number of orchestration units supported for parallel execution in each orchestration step. The orchestration step is determined according to the resource change set and the dependency relationship. Then: The determination module is specifically used to determine the orchestration step according to the resource change set, the dependency relationship and the concurrency strategy, the orchestration step including the first orchestration step and the second orchestration step, wherein the maximum number of parallel indication orchestration units in the first orchestration step is the same as the maximum number of parallel execution orchestration units in the second orchestration step.

15. The cloud management platform according to any one of claims 9 to 14, characterized in that: The cloud management platform also includes: A recording module is used to record the status information of the cloud resources to be changed after the orchestration of the cloud resources to be changed is completed.

16. The cloud management platform according to any one of claims 9 to 15, characterized in that: Before determining the resource change set according to the resource template, the acquisition module is further used to: Obtaining the current status of the target cloud resource; The resource change set is determined according to the resource request, then: The determining module is specifically used to determine the resource change set according to the resource request and the current state of the target cloud resource, and the resource change set includes the cloud resource to be changed and at least one operation for the cloud resource to be changed.

17. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 8.

18. A computer program product comprising instructions, characterized in that When the instructions are executed by a computer device cluster, the computer device cluster is caused to perform the method according to any one of claims 1 to 8.

19. A computer-readable storage medium, characterized in that: The method comprises computer program instructions, and when the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 8.

Images