Multi-cloud resource full life cycle management method, device, equipment and storage medium

Abstract

The present invention discloses a multi-cloud resource full life cycle management method, device, equipment and storage medium, the method comprising: obtaining request parameters of a cloud resource operation request, enabling a cloud management module to verify the request parameters, and enabling the cloud management module to perform input parameter assembly after the verification is passed; enabling the cloud management module to request a first orchestration engine module or a second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module; enabling the cloud management module to construct cloud resource operation details under the cloud resource operation request after consuming the task execution result, and send the cloud resource operation details to a cloud portal through a message queue. The method disclosed in the present invention can improve resource management efficiency and accuracy, and improve the user experience of cloud resources.

Description

Technical Field

[0001] The present invention relates to the field of cloud computing technology, and in particular to a multi-cloud resource full life cycle management method, device, equipment and storage medium. Background Art

[0002] With the development of cloud computing technology, cloud service providers have begun to provide public cloud services to provide computing and storage resources to users, but public clouds may not meet specific requirements, such as data privacy and unification requirements. In order to solve these problems, multi-cloud resource lifecycle management platforms have emerged. Multi-cloud resource lifecycle management platforms allow enterprises to build and manage cloud infrastructure in their own data centers or in environments hosted by third parties. Enterprises can own and control their own hardware, network, and software resources to meet specific security, compliance, and performance requirements. As enterprises have increasing requirements for data security and compliance, the demand for multi-cloud resource lifecycle management platforms has also gradually increased. Multi-cloud resource lifecycle management platforms have become the preferred solution for many enterprises and organizations. When performing resource management, existing multi-cloud resource lifecycle management platforms require a lot of manual configuration, which is labor-intensive and error-prone, and cannot perform adaptive scheduling of the orchestration engine, resulting in low resource management efficiency and accuracy, thus affecting the user experience of cloud resources. Summary of the invention

[0003] The embodiments of the present invention provide a multi-cloud resource full life cycle management method, apparatus, device and storage medium to solve the technical problem of low resource management efficiency and accuracy in the prior art.

[0004] The technical solution of the present invention is as follows, which provides a multi-cloud resource full life cycle management method, including:

[0005] Obtaining request parameters of the cloud resource operation request, causing the cloud management module to verify the request parameters, and after the verification passes, causing the cloud management module to perform input parameter assembly;

[0006] The cloud management module requests the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module;

[0007] After consuming the task execution result, the cloud management module constructs the cloud resource operation details under the cloud resource operation request, and sends the cloud resource operation details to the cloud portal through a message queue.

[0008] Further, the cloud management module is caused to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module, including:

[0009] If the type of the cloud resource operation request is a low timeliness type, the cloud management module is made to request the first orchestration engine module, so that the first orchestration engine module performs the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module through a message queue;

[0010] If the type of the cloud resource operation request is a high-timeliness type, the cloud management module requests the second orchestration engine module, so that the second orchestration engine module executes the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module.

[0011] Furthermore, the low timeliness type includes a cloud resource creation request, a cloud resource allocation request or a cloud resource destruction request; and the high timeliness type includes a cloud resource snapshot rollback request.

[0012] Further, the cloud management module is caused to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters and generates a task execution result, including:

[0013] If the type of the cloud resource operation request is a cloud resource creation request, the cloud management module requests the first orchestration engine module, so that the first orchestration engine module performs parameter verification, task warehousing, resource orchestration, current limiting determination, and task execution according to the request parameters to generate a task execution result.

[0014] Further, the cloud management module is caused to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters and generates a task execution result, including:

[0015] If the type of the cloud resource operation request is a cloud resource reconfiguration request or a cloud resource destruction request, the cloud management module requests the first orchestration engine module, so that the first orchestration engine module performs parameter verification, task storage, resource orchestration, and task execution according to the request parameters, and generates a task execution result;

[0016] If the type of the cloud resource operation request is a cloud resource snapshot rollback request, the cloud management module requests the second orchestration engine module, so that the second orchestration engine module performs parameter verification, task warehousing, resource orchestration, and task execution according to the request parameters to generate a task execution result.

[0017] Furthermore, the method also includes: if the type of the cloud resource operation request is a cloud resource creation request, a cloud resource change request or a cloud resource destruction request, then after verification, before the cloud management module performs parameter assembly, the cloud management module is enabled to perform order warehousing and resource splitting.

[0018] Furthermore, after the verification is passed, before the cloud management module performs parameter assembly, it also includes enabling the cloud management module to execute task data storage, wherein the task data storage includes resource basic data storage or snapshot rollback task data storage; after enabling the cloud management module to construct the cloud resource operation details under the cloud resource operation request, it also includes updating the task data in the database and the status corresponding to the task data.

[0019] Another technical solution of the present invention is as follows: a multi-cloud resource full lifecycle management device is provided, including a verification assembly unit, an execution unit, and a feedback unit;

[0020] The verification assembly unit is used to obtain request parameters of the cloud resource operation request, so that the cloud management module verifies the request parameters, and after the verification passes, the cloud management module performs input parameter assembly;

[0021] The execution unit is used to enable the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module executes the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module through a message queue;

[0022] The feedback unit is used to enable the cloud management module to construct cloud resource operation details under the cloud resource operation request after consuming the task execution result, and send the cloud resource operation details to the cloud portal through the message queue.

[0023] Another technical solution of the present invention is as follows: a computer device is provided, the device comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0024] Memory, used to store computer programs;

[0025] The processor is used to implement the steps of the multi-cloud resource full life cycle management method described in any of the above technical solutions when executing the program stored in the memory.

[0026] Another technical solution of the present invention is as follows: a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the multi-cloud resource full life cycle management method as described in any of the above technical solutions are implemented.

[0027] The beneficial effects of the present invention are as follows: by obtaining request parameters of a cloud resource operation request, the cloud management module verifies the request parameters, and after the verification is passed, the cloud management module performs input parameter assembly; the cloud management module requests the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module executes the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module; after consuming the task execution result, the cloud management module constructs detailed information of the cloud resource operation under the cloud resource operation request, and sends the detailed information of the cloud resource operation to the cloud portal through a message queue, thereby realizing the full life cycle management of multi-cloud resources without a large amount of manual configuration, which can improve the efficiency and accuracy of resource management, and requests the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request to realize adaptive scheduling of the orchestration engine, which can further improve the efficiency of resource management and improve the user's experience of using cloud resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

[0029] Figure 1 A flowchart of a multi-cloud resource full lifecycle management method provided by an embodiment of the present invention;

[0030] Figure 2 A global architecture diagram of multi-cloud management provided by an embodiment of the present invention;

[0031] Figure 3 A schematic diagram of a first process flow of cloud resource operations provided by an embodiment of the present invention;

[0032] Figure 4 A second flow diagram of cloud resource operations provided by an embodiment of the present invention;

[0033] Figure 5A schematic diagram of the structure of a multi-cloud resource full lifecycle management device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0034] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0035] In the description of this application, the words "first", "second", etc. are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order. In this specification, the terms "include", "comprise", "have" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

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

[0037] Figure 1 1 is a flow chart of the multi-cloud resource full life cycle management method of an embodiment of the present invention. It should be noted that if there is substantially the same result, the multi-cloud resource full life cycle management method of the present invention is not based on Figure 1 The process sequence shown is limited. Figure 1 As shown, the multi-cloud resource full life cycle management method mainly includes the following steps:

[0038] S101, obtaining request parameters of a cloud resource operation request, verifying the request parameters, and after the verification passes, enabling the cloud management module to perform input parameter assembly;

[0039] It should be noted that the cloud management module can be a CMP (Cloud Management Platforms), which is a platform for managing various cloud environments, including public clouds, private clouds, and hybrid clouds. As a platform specifically for managing cloud environments, CMP is an indispensable part of the cloud management platform, which can provide comprehensive management functions for cloud resources.

[0040] In a specific embodiment, a multi-cloud management global architecture diagram is shown as follows: Figure 2As shown, the cloud portal includes a cloud management platform; the cloud portal and CMP communicate based on the GRPC protocol. The CMP includes a workflow-engine (i.e., the second orchestration engine module) module. The CMP can also implement functions such as order preprocessing, resource query, resource status update, parameter processing, resource operation API (Application Programming Interface), and consumption of MQ (Message Queuing) messages. The CMP communicates with the Terraform-engine module (i.e., the first orchestration engine module) through the GRPC protocol. The Terraform-engine module and the workflow-engine module can both implement functions such as resource orchestration, current limiting management, failure retry, fault recovery, state management, and task management. The Terraform-engine module and the workflow-engine module communicate with the Provider (a tool or interface) of the cloud resources through the httpClient protocol. The Provider includes but is not limited to the Panyun Provider, Tencent Cloud Provider, and Alibaba Cloud Provider. The Provider communicates with Panyun, Tencent Cloud, and Alibaba Cloud through the httpClient protocol.

[0041] In a specific embodiment, if the type of the cloud resource operation request is a cloud resource creation request, a cloud resource allocation request, or a cloud resource destruction request, a first process diagram of the cloud resource operation is as follows: Figure 3 As shown, the request parameters of the cloud resource operation request may include the parameters such as the specifications, size, image, name, password, etc. to be upgraded. Users can select the resources to be created through the cloud portal, fill in the necessary parameters such as specifications, images, names, passwords, etc. and submit them to the cloud portal. After the cloud portal backend service receives the request, it will produce the order corresponding to the resource and associate it with the order ID, and request the CMP with the overall order data as the request parameter; after the CMP service receives the request, it will perform input parameter validity verification according to the resource parameter characteristics and rules. If the verification passes, it will respond normally to the portal's current resource creation order request. If the verification fails, it will return clear input parameter problem response information. After the cloud resource creation order input parameter verification passes, the CMP will assemble the input parameters.

[0042] In an optional embodiment, the method further includes: if the type of the cloud resource operation request is a cloud resource creation request, a cloud resource change request or a cloud resource destruction request, then after verification, before the cloud management module performs parameter assembly, the cloud management module is enabled to perform order warehousing and resource splitting.

[0043] In a specific embodiment, if the type of cloud resource operation request is a cloud resource creation request, a cloud resource allocation request, or a cloud resource destruction request, then after verification is passed, before the cloud management module performs input parameter assembly, the cloud management module is caused to perform order warehousing and resource splitting, wherein resource splitting can be disassembling the order structure, and input parameter assembly can include assembling the underlying cloud resources, creating input parameters, and recording the relationship between the initial resource data (such as specifications, size) and the resources.

[0044] S102, causing the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module through a message queue;

[0045] In an optional implementation, causing the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module, including:

[0046] If the type of the cloud resource operation request is a low timeliness type, the cloud management module is made to request the first orchestration engine module, so that the first orchestration engine module performs the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module through a message queue;

[0047] If the type of the cloud resource operation request is a high-timeliness type, the cloud management module requests the second orchestration engine module, so that the second orchestration engine module executes the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module.

[0048] In a specific embodiment, for the first orchestration engine module, after generating the task execution result, the task execution result is returned to the cloud management module through the message queue. For the second orchestration engine module, after generating the task execution result, the task execution result can be directly returned to the cloud management module.

[0049] In an optional implementation, the low timeliness type includes a cloud resource creation request, a cloud resource reconfiguration request, or a cloud resource destruction request; and the high timeliness type includes a cloud resource snapshot rollback request.

[0050] In a specific embodiment, the low timeliness type may also include other types of requests, and the high timeliness type may also include other types of requests, such as password modification requests.

[0051] In a specific embodiment, the cloud management module requests the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters and generates a task execution result, including:

[0052] If the type of the cloud resource operation request is a cloud resource creation request, a cloud resource change request, or a cloud resource destruction request, the cloud management module is enabled to request the first orchestration engine module so that the first orchestration engine module executes the task according to the request parameters and generates a task execution result.

[0053] In a specific embodiment, after the cloud management module performs input parameter assembly, the cloud management module has a built-in resource orchestration engine selection strategy, and pre-sets the resource creation orchestration engine selection strategy according to the characteristics of the orchestration engine itself. If the type of the cloud resource operation request is a cloud resource creation request, the cloud management module requests the Terraform module to perform resource orchestration and creation (i.e., execute the task) according to the preset selection strategy. If the type of the cloud resource operation request is a cloud resource change request, at this time, the Terraform-engine module executes the task according to the request parameters, i.e., executes the cloud resource change task, such as changing the specification. If the type of the cloud resource operation request is a cloud resource destruction request, at this time, the Terraform-engine module executes the task according to the request parameters, i.e., executes the cloud resource deletion task.

[0054] In a specific embodiment, the cloud management module is caused to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters and generates a task execution result, including:

[0055] If the type of the cloud resource operation request is a cloud resource snapshot rollback request, the cloud management module is made to request the second orchestration engine module, so that the second orchestration engine module executes the task according to the request parameters and generates a task execution result.

[0056] In a specific embodiment, if the type of cloud resource operation request is a cloud resource snapshot rollback request, the second process diagram of the cloud resource operation is as follows: Figure 4 As shown, at this time, the workflow-engine module executes the task according to the request parameters, that is, executes the snapshot rollback task.

[0057] In an optional implementation, causing the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters and generates a task execution result, including:

[0058] If the type of the cloud resource operation request is a cloud resource creation request, the cloud management module requests the first orchestration engine module, so that the first orchestration engine module performs parameter verification, task warehousing, resource orchestration, current limiting determination, and task execution according to the request parameters to generate a task execution result.

[0059] In a specific embodiment, if the type of the cloud resource operation request is a cloud resource creation request, the CMP requests the Terraform-engine module, so that the Terraform-engine module performs parameter verification, task storage, resource scheduling, current limiting determination, and task execution according to the request parameters, and generates a task execution result, that is, the Terraform module performs resource scheduling and creation. After Terraform successfully creates resources, the task execution result (the latest details of the virtual machine) is returned to the CMP through each MQ message queue. The CMP parses the returned resource information and updates the corresponding resource data table information and resource status. At the same time, it builds detailed information of the resources under the current order, sends detailed information of the order resources (cloud resource operation details) to the MQ message queue, and the cloud portal successfully consumes the MQ message of the order, and displays the resource information of the successful application through the Web interface. At this point, the resource order class creation process is completed. If Terraform fails to create resources, it has a built-in alarm message sent to the CMP management side. After the management side detects the failure, it sends a message to the operation and maintenance management personnel to intervene and handle it.

[0060] In an optional implementation, causing the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters and generates a task execution result, including:

[0061] If the type of the cloud resource operation request is a cloud resource reconfiguration request or a cloud resource destruction request, the cloud management module requests the first orchestration engine module, so that the first orchestration engine module performs parameter verification, task storage, resource orchestration, and task execution according to the request parameters, and generates a task execution result;

[0062] If the type of the cloud resource operation request is a cloud resource snapshot rollback request, the cloud management module requests the second orchestration engine module, so that the second orchestration engine module performs parameter verification, task warehousing, resource orchestration, and task execution according to the request parameters to generate a task execution result.

[0063] In a specific embodiment, if the type of the cloud resource operation request is a cloud resource allocation request or a cloud resource destruction request, the CMP is made to request the Terraform-engine module, so that the Terraform-engine module performs parameter verification, task storage, resource orchestration, and task execution according to the request parameters, and generates a task execution result. If the type of the cloud resource operation request is a cloud resource snapshot rollback request, the CMP is made to request the workflow-engine module, so that the workflow-engine module performs parameter verification, task storage, resource orchestration, and task execution according to the request parameters, and generates a task execution result.

[0064] S103, after consuming the task execution result, the CMP constructs the cloud resource operation details under the cloud resource operation request, and sends the cloud resource operation details to the cloud portal through the message queue.

[0065] In an optional embodiment, after verification is passed and before the cloud management module performs parameter assembly, it also includes enabling the cloud management module to execute task data storage, wherein the task data storage includes resource basic data storage or snapshot rollback task data storage; after enabling the cloud management module to construct the cloud resource operation details under the cloud resource operation request, it also includes updating the task data in the database and the status corresponding to the task data.

[0066] In a specific embodiment, for cloud resource creation requests, cloud resource allocation requests or cloud resource destruction requests, the CMP execution task data is stored in the database, that is, the CMP execution resource basic data is stored in the database, that is, the resource basic data is stored in the database; for cloud resource snapshot rollback requests, the CMP execution task data is stored in the database, that is, the CMP execution snapshot rollback task data is stored in the database.

[0067] In a specific embodiment, for cloud resource allocation requests, after generating the task execution result, the order association details are sent to the message queue, the CMP consumes the messages in the message queue, and updates the task data (specification ID) in the data set and the status corresponding to the task data (updates unexecuted to completed), and sends the order information (cloud resource operation details) to the message queue, and the cloud portal consumes the order information. For cloud resource destruction requests, after generating the task execution result, the order association deletion result information is sent to the message queue, and after the CMP consumes the information, the task data in the data set and the status corresponding to the task data are updated, which may specifically include updating the deletion status and canceling the association relationship, and then sending the order information (cloud resource operation details) to the message queue, and the cloud portal consumes the order information. For cloud resource snapshot rollback requests, after generating the task execution result, the callback returns the snapshot rollback result to the CMP, and the CMP updates the task data in the data set and the status corresponding to the task data, which may specifically include updating the snapshot rollback operation record data and status, and sending the snapshot rollback operation result (cloud resource operation details) to the message queue, and the cloud portal consumes the snapshot rollback operation result.

[0068] In a specific embodiment, for a cloud resource creation request, if the CMP input parameter assembly is successful, the information on the successful receipt of the creation order is returned to the cloud portal, and if the first orchestration engine module parameter verification passes, the information on the received creation request is returned to the CMP. For a cloud resource change request, if the CMP input parameter assembly is successful, the information on the successful receipt of the change order is returned to the cloud portal, and if the first orchestration engine module parameter verification passes, the information on the received change request is returned to the CMP. For a cloud resource destruction request, if the CMP input parameter assembly is successful, the information on the successful receipt of the cancellation order is returned to the cloud portal, and if the first orchestration engine module parameter verification passes, the information on the received deletion request is returned to the CMP. For a cloud resource snapshot rollback request, if the CMP input parameter assembly is successful, the information on the successful receipt of the snapshot rollback is returned to the cloud portal.

[0069] The multi-cloud resource full life cycle management method provided by the embodiment of the present invention obtains the request parameters of the cloud resource operation request, enables the cloud management module to verify the request parameters, and after the verification is passed, enables the cloud management module to perform parameter assembly; enables the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module executes the task according to the request parameters, generates the task execution result, and returns the task execution result to the cloud management module; enables the cloud management module to construct the cloud resource operation detailed information under the cloud resource operation request after consuming the task execution result, and sends the cloud resource operation detailed information to the cloud portal through the message queue, thereby realizing the full life cycle management of multi-cloud resources without a large amount of manual configuration, which can improve the efficiency and accuracy of resource management, and requests the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request to realize adaptive scheduling of the orchestration engine, which can further improve the efficiency of resource management and improve the user's cloud resource usage experience.

[0070] The multi-cloud resource full life cycle management method provided by the embodiment of the present invention sets the orchestration engine selection strategy in a targeted manner according to the business processing speed and business user characteristics. For resource operation requests that require a quick response (for example, snapshot rollback), the workflow-engine module can be adaptively scheduled according to the orchestration strategy factor. For resource cancellation, creation, and replacement that do not require high timeliness, the Terraform-engine module is automatically scheduled according to the orchestration strategy factor to ensure the user's cloud resource usage experience. It can provide double insurance under the cloud resource life cycle management. When the Terraform-engine module service is unavailable, it can adaptively switch to the built-in workflow-engine module to ensure business stability.

[0071] The multi-cloud resource full life cycle management method provided by the embodiment of the present invention can centrally manage the resources and services of multiple cloud service providers, provide a unified control panel for them, connect different cloud vendor platforms to the multi-cloud management platform by management operations, and generate a unique access authentication key for each cloud service provider platform. Users can jump to the target cloud service provider's cloud resource management interface by selecting the corresponding cloud platform through the Web interface, thereby realizing a unified control panel for multiple cloud service provider resources. Users can manage and monitor multiple cloud environments in one interface, including virtual machines, storage, networks and other resources. If the user has running cloud resources on multiple cloud service platforms, they can switch through the tenants to see the usage of the cloud resources they manage under different tenants.

[0072] The multi-cloud resource full life cycle management method provided by the embodiment of the present invention can effectively solve the problems existing in the multi-cloud resource full life cycle management platform of large enterprises, and enable enterprises to efficiently manage and utilize multi-cloud resources throughout their life cycle, while reducing the cost of enterprise hardware resource adoption and improving the effective utilization of resources.

[0073] Since the multi-cloud management platform manages and connects to multiple cloud service providers, users can choose different cloud platforms according to their business needs, so as to manage the entire life cycle of cloud resources on the platform. Since different cloud platforms have different underlying resource operation authentication keys, when users switch to other cloud platforms, they can obtain the unique authentication key information of the underlying resources of the cloud vendor through the unique ID of the cloud platform. Therefore, under the multi-cloud management platform, users can flexibly choose and use different cloud service providers according to actual needs. It provides consistency and interoperability across cloud environments, allowing users to easily expand and migrate applications and data according to business needs.

[0074] The multi-cloud resource full life cycle management method provided by the embodiment of the present invention can help users optimize the use and cost of cloud resources. It provides resource management and automation tools, uses a visual monitoring method (prometheus) to collect and record the real-time use of each cloud resource, sets resource optimization policy rules (sets CPU, RAM, DISK usage threshold intervals) for clusters of different businesses, and automatically helps users expand or shrink cloud resources on the corresponding cloud platform according to the user-set cloud platform usage priority when the threshold is triggered, thereby helping users optimize the use and cost of cloud resources. The multi-cloud management platform can help users better manage and utilize the resources and services of multiple cloud service providers, and improve the flexibility, scalability, and cost-effectiveness of the business.

[0075] Figure 5 is a schematic diagram of the structure of a multi-cloud resource full life cycle management device according to an embodiment of the present invention. Figure 5 As shown, the multi-cloud resource full lifecycle management device 50 includes a verification assembly unit 51, an execution unit 52 and a feedback unit 53;

[0076] The verification and assembly unit 51 is used to obtain the request parameters of the cloud resource operation request, so that the cloud management module verifies the request parameters, and after the verification passes, the cloud management module performs input parameter assembly;

[0077] The execution unit 52 is used to enable the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module;

[0078] The feedback unit 53 is used to enable the cloud management module to construct cloud resource operation details under the cloud resource operation request after consuming the task execution result, and send the cloud resource operation details to the cloud portal through the message queue.

[0079] In an optional implementation, the execution unit 52 enables the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module, including:

[0080] If the type of the cloud resource operation request is a low timeliness type, the cloud management module is made to request the first orchestration engine module, so that the first orchestration engine module performs the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module through a message queue;

[0081] If the type of the cloud resource operation request is a high-timeliness type, the cloud management module requests the second orchestration engine module, so that the second orchestration engine module executes the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module.

[0082] In an optional implementation, the low timeliness type includes a cloud resource creation request, a cloud resource reconfiguration request, or a cloud resource destruction request; and the high timeliness type includes a cloud resource snapshot rollback request.

[0083] In an optional implementation, the execution unit 52 causes the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs the task according to the request parameters, and generates a task execution result, including:

[0084] If the type of the cloud resource operation request is a cloud resource creation request, the cloud management module requests the first orchestration engine module, so that the first orchestration engine module performs parameter verification, task warehousing, resource orchestration, current limiting determination, and task execution according to the request parameters to generate a task execution result.

[0085] In an optional implementation, the execution unit 52 causes the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs the task according to the request parameters, and generates a task execution result, including:

[0086] If the type of the cloud resource operation request is a cloud resource reconfiguration request or a cloud resource destruction request, the cloud management module requests the first orchestration engine module, so that the first orchestration engine module performs parameter verification, task storage, resource orchestration, and task execution according to the request parameters, and generates a task execution result;

[0087] If the type of the cloud resource operation request is a cloud resource snapshot rollback request, the cloud management module requests the second orchestration engine module, so that the second orchestration engine module performs parameter verification, task warehousing, resource orchestration, and task execution according to the request parameters to generate a task execution result.

[0088] In an optional embodiment, the multi-cloud resource full life cycle management device also includes an order processing unit. If the type of the cloud resource operation request is a cloud resource creation request, a cloud resource allocation request or a cloud resource destruction request, the order processing unit is used to enable the cloud management module to enter orders and split resources before the cloud management module performs parameter assembly after verification.

[0089] In an optional embodiment, the multi-cloud resource full life cycle management device also includes a database update unit, which is used to, after verification, enable the cloud management module to execute task data storage before the cloud management module performs parameter assembly, wherein the task data storage includes resource basic data storage or snapshot rollback task data storage; the database update unit is also used to enable the cloud management module to update the task data and the corresponding status of the task data in the database after constructing the cloud resource operation detailed information under the cloud resource operation request.

[0090] Based on the above multi-cloud resource full lifecycle management method, an embodiment of the present invention further provides a computer device, which includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus;

[0091] Memory, used to store computer programs;

[0092] The processor is configured to implement the steps of the multi-cloud resource full lifecycle management method described in any one of the above embodiments when executing the program stored in the memory.

[0093] For other details about the processor in the above-mentioned multi-cloud resource full life cycle management device implementing the above-mentioned technical solution, please refer to the description of the multi-cloud resource full life cycle management method provided in the above-mentioned invention embodiment, which will not be repeated here.

[0094] Among them, the processor can also be called CPU (Central Processing Unit), the processor may be an integrated circuit chip with signal processing capabilities; the processor can also be a general-purpose processor, DSP (Digital Signal Process), ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, among which the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0095] The embodiment of the present invention also provides a computer-readable storage medium, on which a readable computer program is stored; wherein the computer program can be stored in the above storage medium in the form of a software product, including several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, magnetic disk or optical disk, ROM (Read-Only Memory), RAM (Random Access Memory) and other media that can store program codes, or terminal devices such as computers, servers, mobile phones, and tablets.

[0096] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules 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 through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

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

[0098] In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.

[0099] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0100] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium may 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 (SSD)), etc.

[0101] The technical solution provided by the present application is introduced in detail above. The principles and implementation methods of the present application are explained by using specific examples in the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

[0102] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0103] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices and computer program products according to the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0104] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0105] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0106] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A multi-cloud resource full life cycle management method, characterized in that: The method comprises: Obtaining request parameters of the cloud resource operation request, causing the cloud management module to verify the request parameters, and after the verification passes, causing the cloud management module to perform input parameter assembly; The cloud management module requests the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module; After consuming the task execution result, the cloud management module constructs the cloud resource operation details under the cloud resource operation request, and sends the cloud resource operation details to the cloud portal through a message queue.

2. The multi-cloud resource full lifecycle management method according to claim 1, characterized in that: The method of causing the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module, including: If the type of the cloud resource operation request is a low timeliness type, the cloud management module is made to request the first orchestration engine module, so that the first orchestration engine module performs the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module through a message queue; If the type of the cloud resource operation request is a high-timeliness type, the cloud management module requests the second orchestration engine module, so that the second orchestration engine module executes the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module.

3. The multi-cloud resource full lifecycle management method according to claim 2, characterized in that: The low timeliness type includes a cloud resource creation request, a cloud resource allocation request, or a cloud resource destruction request; the high timeliness type includes a cloud resource snapshot rollback request.

4. The multi-cloud resource full lifecycle management method according to claim 3 is characterized in that: The cloud management module is caused to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters and generates a task execution result, including: If the type of the cloud resource operation request is a cloud resource creation request, the cloud management module requests the first orchestration engine module, so that the first orchestration engine module performs parameter verification, task warehousing, resource orchestration, current limiting determination, and task execution according to the request parameters to generate a task execution result.

5. The multi-cloud resource full lifecycle management method according to claim 1, characterized in that: The cloud management module is caused to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs a task according to the request parameters and generates a task execution result, including: If the type of the cloud resource operation request is a cloud resource reconfiguration request or a cloud resource destruction request, the cloud management module requests the first orchestration engine module, so that the first orchestration engine module performs parameter verification, task storage, resource orchestration, and task execution according to the request parameters, and generates a task execution result; If the type of the cloud resource operation request is a cloud resource snapshot rollback request, the cloud management module requests the second orchestration engine module, so that the second orchestration engine module performs parameter verification, task warehousing, resource orchestration, and task execution according to the request parameters to generate a task execution result.

6. The multi-cloud resource full lifecycle management method according to claim 1, characterized in that: The method also includes: if the type of the cloud resource operation request is a cloud resource creation request, a cloud resource change request or a cloud resource destruction request, then after verification, before the cloud management module performs parameter assembly, the cloud management module is caused to perform order warehousing and resource splitting.

7. The multi-cloud resource full lifecycle management method according to claim 6, characterized in that: After the verification is passed, before the cloud management module performs parameter assembly, it also includes enabling the cloud management module to execute task data storage, wherein the task data storage includes resource basic data storage or snapshot rollback task data storage; after enabling the cloud management module to construct the cloud resource operation detailed information under the cloud resource operation request, it also includes updating the task data in the database and the status corresponding to the task data.

8. A multi-cloud resource full life cycle management device, characterized in that: It includes a verification assembly unit, an execution unit and a feedback unit; The verification assembly unit is used to obtain request parameters of the cloud resource operation request, so that the cloud management module verifies the request parameters, and after the verification passes, the cloud management module performs input parameter assembly; The execution unit is used to enable the cloud management module to request the first orchestration engine module or the second orchestration engine module according to the type of the cloud resource operation request, so that the first orchestration engine module or the second orchestration engine module performs the task according to the request parameters, generates a task execution result, and returns the task execution result to the cloud management module; The feedback unit is used to enable the cloud management module to construct cloud resource operation details under the cloud resource operation request after consuming the task execution result, and send the cloud resource operation details to the cloud portal through the message queue.

9. A computer device, characterized in that: The device includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory, used to store computer programs; The processor is used to implement the steps of the multi-cloud resource full life cycle management method described in any one of claims 1 to 7 when executing the program stored in the memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the multi-cloud resource full lifecycle management method according to any one of claims 1 to 7 are implemented.

Images