Resource receiving and management method, device and equipment for multiple cloud providers, medium and program product

Abstract

The embodiment of the invention provides a resource receiving and managing method, device and equipment for multiple cloud providers, a medium and a program product. The method comprises the steps that the task state of a task list of to-be-managed resources is obtained, the task list is a set of to-be-executed tasks with a cloud account as the dimension, and the to-be-executed tasks are determined according to strategy configuration types of the to-be-managed resources and component execution logic of the strategy configuration types; if the task state is in the open state and meets the trigger execution condition, sending the to-be-executed task list to a message queue; for each to-be-executed task in the to-be-executed task list, analyzing component execution logic from the message queue to obtain component information of a to-be-executed component and resource encapsulation request information, so that the system can obtain resource data in a paging manner and perform encapsulation processing to obtain a resource management component; and according to the resource management component of each to-be-executed task, generating a resource management result. According to the method provided by the invention, the resource management synchronization efficiency and the data accuracy can be improved.

Description

Technical Field

[0001] This application relates to the field of cloud computing resource management technology, and in particular to a method, apparatus, equipment, medium and program product for managing resources from multiple cloud providers. Background Technology

[0002] Cloud computing has become an indispensable part of the business and technology strategies of many companies, offering a flexible, elastic, and self-service resource set that can quickly support the ever-changing business needs of enterprises. Enterprises typically require both the flexibility of the cloud and the security and predictability of traditional data centers, making hybrid cloud an increasingly popular IT resource management solution. Consequently, multi-cloud management platforms that can simultaneously access and manage resources from different cloud vendors have emerged.

[0003] In existing technologies, a plug-in pattern combined with a microservice architecture is typically used to interface with and adapt to heterogeneous cloud platforms. This utilizes a unified resource operation interface and view to shield the differences between underlying cloud products. Based on a unified resource definition and interface standard specification, a shielding layer is built to connect to and adapt to cloud platform software from different vendors at the bottom, while providing a consistent cloud resource operation interface at the top. This enables efficient adaptation of cloud platforms with different technologies from different cloud vendors, ensuring the flexibility and scalability of multi-cloud management software, thereby achieving sustainable management of the multi-cloud management platform.

[0004] However, existing methods are complex to configure and integrate when building structures such as shielding layers, and cannot quickly respond to changes in dynamic resources, resulting in low efficiency and poor accuracy in resource management. Summary of the Invention

[0005] This application provides a method, apparatus, device, medium, and program product for managing resources across multiple cloud providers, which addresses the problems of existing methods having complex configuration and integration processes when building shielding layers and other structures, and being unable to quickly respond to dynamic resource changes, resulting in low resource management efficiency and poor accuracy.

[0006] In a first aspect, embodiments of this application provide a method for managing resources across multiple cloud providers, including:

[0007] Get the task status of the list of tasks to be executed for resources to be managed. The list of tasks to be executed is a collection of tasks to be executed by cloud account. The tasks to be executed are obtained by parsing the strategy configuration type of the resource to be managed and the component execution logic of the strategy configuration type. The strategy configuration type is determined according to the user's resource configuration requirements.

[0008] If the task status is in the open state and the trigger execution condition is met, the list of tasks to be executed for the resources to be managed will be sent to the message queue. The trigger execution condition is either a timed execution condition or a fixed-point execution condition.

[0009] For each task in the task list, the component execution logic of the task is parsed from the message queue to obtain the component information of the component to be executed in the task. The component to be executed is the component in the task to be executed used to manage the required resources.

[0010] Based on the component information, determine the resource encapsulation request information of the component to be executed;

[0011] Based on the resource encapsulation request information, the resource data of the component to be executed is obtained from the cloud service application interface pagination, and the resource data is encapsulated to obtain the resource management component of the task to be executed.

[0012] Based on the resource management components of each task to be executed, generate the resource management results for the resources to be managed.

[0013] In one possible implementation, before obtaining the task status of the list of tasks to be executed for the resources to be managed, the method further includes:

[0014] Obtain the management strategy type of the resource to be managed, and the component execution logic corresponding to the management strategy type. The management strategy type includes the cloud provider to be managed, the version of the cloud provider to be managed, the resource pool under the version, and the cloud account in the resource pool.

[0015] The management strategy type is analyzed to obtain the initial tasks to be executed based on the cloud account.

[0016] Based on the component execution logic, determine the execution order of each component to be executed corresponding to the initial task to be executed, and obtain the task to be executed;

[0017] Based on the pending tasks of each cloud account in the management strategy type, obtain the list of pending tasks for the resources to be managed.

[0018] In one possible implementation, obtaining the component execution logic corresponding to the management strategy type includes:

[0019] Based on the management strategy type, determine the component type of the resource to be managed. The component type includes managed atomic components and managed resource relationship components.

[0020] The execution order of each component is determined based on the component type and the preset component level;

[0021] Based on the execution order of each component, generate the component execution logic corresponding to the management strategy type.

[0022] In one possible implementation, after determining the task status of the list of tasks to be executed for the resources to be managed, the method further includes:

[0023] If the task status meets the target conditions, the task of managing the resource to be managed will end. The target conditions include either the task status being closed or the task status being open and not meeting the trigger execution conditions.

[0024] In one possible implementation, based on the resource encapsulation request information, resource data of the component to be executed is obtained from the cloud service provider's application programming interface (API) pagination, and the resource data is encapsulated to obtain the resource-managed component for the task to be executed, including:

[0025] Based on the authentication information of the cloud service provider application interface in the resource encapsulation request information, a request is sent to the cloud service provider application interface through the system's internal adaptation service in order to receive the response information from the cloud service provider application interface.

[0026] Based on the pagination parameter information in the resource encapsulation request information, perform resource pagination query on the response information to obtain the paginated resource data of the component to be executed;

[0027] The paginated resource data is compared with the resource data obtained from the last request in the system, and the resource data is synchronized based on the comparison results.

[0028] When the last pagination query in the pagination parameter information ends, the resource data of the component to be executed is obtained based on the pagination resource data after the resource data is synchronized.

[0029] The resource data is encapsulated and processed to obtain the resource management component for the task to be executed.

[0030] In one possible implementation, after encapsulating the resource data and obtaining the resource management component for the task to be executed, the method further includes:

[0031] The resource data of the component to be executed is compared with the resource data previously stored in the system to determine the resource data to be deleted in this synchronization.

[0032] Delete the stored data corresponding to the resource data that was deleted in this resource data synchronization process.

[0033] Secondly, embodiments of this application provide a resource management device for multiple cloud providers, comprising:

[0034] The acquisition module is used to acquire the task status of the list of tasks to be executed for resources to be managed. The list of tasks to be executed is a collection of tasks to be executed by cloud account. The tasks to be executed are obtained by parsing the strategy configuration type of the resource to be managed and the component execution logic of the strategy configuration type. The strategy configuration type is determined according to the user's resource configuration requirements.

[0035] The sending module is used to send the list of tasks to be executed for the resources to be managed to the message queue if the task status is in the open state and the trigger execution condition is met. The trigger execution condition is either a timed execution condition or a fixed-point execution condition.

[0036] The parsing module is used to parse the component execution logic of each task in the task list from the message queue to obtain the component information of the component to be executed in the task. The component to be executed is the component in the task to be executed that is used for resource management.

[0037] The determination module is used to determine the resource encapsulation request information of the component to be executed based on the component information;

[0038] The encapsulation module is used to obtain the resource data of the component to be executed from the cloud application interface pagination according to the resource encapsulation request information, and to encapsulate the resource data to obtain the resource management component of the task to be executed.

[0039] The generation module is used to generate resource management results for resources to be managed based on the resource management components of each task to be executed.

[0040] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0041] The memory stores the instructions that the computer executes;

[0042] The processor executes computer execution instructions stored in memory to implement the first aspect and / or various possible implementations of the first aspect as described above.

[0043] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0044] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed, implements the first aspect and / or various possible implementations of the first aspect.

[0045] The multi-cloud provider resource management method, apparatus, device, medium, and program product provided in this application embodiment obtains the task status of the list of tasks to be executed for resources to be managed. The list of tasks to be executed is a collection of tasks to be executed by cloud account. Each task to be executed is obtained by parsing the policy configuration type and the component execution logic of the policy configuration type for the resource to be managed. The policy configuration type is determined according to the user's resource configuration requirements. If the task status is active and the trigger execution condition is met, the list of tasks to be executed for the resource to be managed is sent to a message queue. The trigger execution condition is a timed execution condition or a fixed-point execution condition. For each task to be executed in the list, the component execution logic of the task to be executed is parsed from the message queue to obtain the component information of the components to be executed in the task. The system identifies components used for resource management in tasks to be executed. Based on component information, it determines resource encapsulation request information for the components to be executed. According to the resource encapsulation request information, it retrieves resource data for the components to be executed from the cloud service provider's application programming interface (API) in a paginated manner, encapsulates the resource data, and obtains the resource management components for the tasks to be executed. Based on the resource management components for each task to be executed, it generates resource management results for the resources to be managed. This process utilizes automated task status monitoring and triggering mechanisms to flexibly parse task and component execution logic, enabling the system to flexibly adjust managed resources according to different strategy configuration types and user needs. Simultaneously, by using pagination and message queues to retrieve and encapsulate resource data, it ultimately generates resource management results, ensuring the sequential execution of tasks and accurate data transmission, thus achieving efficient and precise resource management. Attached Figure Description

[0046] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0047] Figure 1 A flowchart illustrating a multi-cloud provider resource management method provided in this application;

[0048] Figure 2 A flowchart illustrating another method for managing resources across multiple cloud providers provided in this application;

[0049] Figure 3 A flowchart illustrating a component management logic provided in this application;

[0050] Figure 4 A schematic diagram of the resource management device for multi-cloud providers provided in this application;

[0051] Figure 5 A schematic diagram of the structure of the electronic device provided in this application.

[0052] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0053] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0054] In existing technologies, a plug-in pattern combined with a microservices architecture is typically used to interface with and adapt to heterogeneous cloud platforms. This utilizes a unified resource operation interface and view to shield the differences between underlying cloud products. Based on unified resource definitions and interface standards, a shielding layer is built, connecting downwards to cloud platform software adapted to different vendors, and providing a consistent cloud resource operation interface upwards. This achieves efficient adaptation to cloud platforms with different vendors and technical systems, ensuring the flexibility and scalability of multi-cloud management software, thereby enabling sustainable management of the multi-cloud management platform. However, the plug-in pattern and microservices architecture require significant development and maintenance work to ensure the normal operation and compatibility of each plug-in and microservice. When adding a new cloud platform or updating the adaptation plug-in of an existing platform, a long development cycle and testing process are still required, resulting in low resource management efficiency. Furthermore, in a multi-cloud environment, when handling cross-cloud data synchronization and consistency, the distributed nature of plug-ins and microservices increases the risk of system failures and data inconsistencies, leading to inaccurate managed resources.

[0055] To address the aforementioned issues, this application provides a multi-cloud provider resource management method, apparatus, device, medium, and program product. Utilizing automated task status monitoring and triggering mechanisms, it flexibly parses task and component execution logic, enabling the system to flexibly adjust managed resources according to different strategy configuration types and user needs. By employing message queues and pagination processing to acquire and encapsulate resource data, it ultimately generates resource management results, ensuring sequential task execution and accurate data transmission, thus achieving efficient and precise resource management.

[0056] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0057] The execution entity of the multi-cloud provider resource management method provided in this application embodiment can be a server corresponding to the management platform system. The server can be a mobile phone, computer, tablet, or other device. This application embodiment does not impose any particular restrictions on the implementation method of the execution entity, as long as the execution entity can obtain the task status of the list of tasks to be executed for the resources to be managed. The list of tasks to be executed is a collection of tasks to be executed by cloud account. The tasks to be executed are obtained by parsing the policy configuration type of the resources to be managed and the component execution logic of the policy configuration type. The policy configuration type is determined according to the user's resource configuration requirements. If the task status is in the open state and the trigger execution condition is met, the list of tasks to be executed for the resources to be managed is sent to the message queue. The trigger execution condition is a timed execution condition or a fixed-point execution condition. For each task in the task list, the execution logic of the components of the task is parsed from the message queue to obtain the component information of the components to be executed in the task. The components to be executed are the components in the task that are used to manage the required resources. Based on the component information, the resource encapsulation request information of the components to be executed is determined. Based on the resource encapsulation request information, the resource data of the components to be executed is obtained from the cloud application interface pagination, and the resource data is encapsulated to obtain the resource management components of the task. Based on the resource management components of each task, the resource management result of the resources to be managed is generated.

[0058] Among them, "management" can refer to the unified management and control of resources on different cloud service providers (cloud vendors); "component" can refer to an independent module or unit in a system used to implement a specific function or task. For example, computing components include virtual machines, containers, serverless computing, etc., and network components include virtual private clouds, load balancers, etc.

[0059] Figure 1 This is a flowchart illustrating a multi-cloud provider resource management method provided in this application. The executing entity of this method can be a server storing multi-cloud provider resource management methods or other servers; this embodiment does not impose any particular limitations. Figure 1 As shown, the method may include:

[0060] S101. Obtain the task status of the list of tasks to be executed for the resources to be managed. The list of tasks to be executed is a collection of tasks to be executed by cloud account. The tasks to be executed are obtained by parsing the strategy configuration type of the resources to be managed and the component execution logic of the strategy configuration type. The strategy configuration type is determined according to the user's resource configuration requirements.

[0061] In this step, "resources to be managed" refers to resources that are not yet managed or included in the management system, and can include cloud service resources provided by various cloud providers, such as virtual machines, storage, and databases. "Cloud account" refers to a user's unique identifier on the cloud service provider's platform, used to access and manage cloud resources. "Policy configuration type" refers to different types of policy configuration methods used to meet user needs for resource configuration. "Component execution logic" refers to the specific operation steps and logical flow when executing policy configuration to ensure that resource configuration meets expectations. "Task parsing" refers to converting policy configuration types and component execution logic into specific execution tasks, thereby achieving effective resource management.

[0062] Among them, the task status of the list of tasks to be executed for resources to be managed can refer to the task's on or off status that the user has set in advance when determining the policy configuration type.

[0063] In this embodiment of the application, before obtaining the task status of the list of tasks to be executed for the resources to be managed, the method may further include:

[0064] Obtain the management strategy type of the resource to be managed, and the component execution logic corresponding to the management strategy type. The management strategy type includes the cloud provider to be managed, the version of the cloud provider to be managed, the resource pool under the version, and the cloud account in the resource pool.

[0065] The management strategy type is analyzed to obtain the initial tasks to be executed based on the cloud account.

[0066] Based on the component execution logic, determine the execution order of each component to be executed corresponding to the initial task to be executed, and obtain the task to be executed;

[0067] Based on the pending tasks of each cloud account in the management strategy type, obtain the list of pending tasks for the resources to be managed.

[0068] In this step, the management policy type can specifically refer to policy categories used for managing and configuring resources to be managed. These policies define how to manage different types of cloud resources. The management policy type can be determined by the user through the management system's interactive interface or through the management system initialization. Furthermore, when a user has a clear resource management requirement, they can select it through the management system's interactive interface. When a user wants to manage resources but doesn't know how to determine their management needs, the management system initialization defaults to managing resources across all resource pools and all cloud accounts. The components to be executed refer to the specific operations or steps that need to be performed when executing the initial tasks, used for managing the required resources.

[0069] Different cloud providers offer different services and resources, and managing these resources requires specific strategies and methods. Furthermore, cloud providers may release different versions, each with different functions and features. A single cloud provider may also have multiple resource pools to organize and manage a large number of cloud resources, improving management efficiency. Therefore, it is necessary to determine the management information of the resources to be managed within the cloud provider by selecting the cloud provider to be managed, the version of the cloud provider to be managed, and one or more resource pools under that version. This facilitates the generation of tasks to subsequently manage the resource from the cloud provider.

[0070] A cloud account is a cloud provider identifier used for accessing and managing cloud resources in a resource pool based on authentication and authorization. Each cloud account can have multiple resources. Therefore, by selecting resources under a specific cloud account in a specific resource pool under a specific cloud provider version for management, the comprehensiveness and accuracy of the management strategy can be ensured.

[0071] In one example, the cloud provider can choose cloud vendors such as China Unicom Cloud and Tencent Cloud; then determine the cloud provider version that needs to be managed; then select resources under one or more resource pools under a specified cloud provider by using resource pools as the dimension; finally, select resources under one or more cloud accounts under a specified resource pool under a specified cloud provider by using cloud accounts as the dimension.

[0072] Among these methods, analyzing the management strategy type and obtaining the initial tasks to be executed based on cloud accounts can ensure that each cloud account has corresponding management tasks.

[0073] Optionally, the execution order of each component to be executed can refer to whether the components corresponding to each resource are executed sequentially or concurrently.

[0074] Summarize the pending tasks for all cloud accounts under the management strategy type, generate a list of pending tasks for resources to be managed, and ensure that all resources to be managed have corresponding management tasks and can be managed in a unified manner.

[0075] Optionally, after obtaining the management strategy type of the resource to be managed and the component execution logic corresponding to the management strategy type, a task execution mode can be set for the resource to be managed. This allows the generated list of tasks to be executed to determine the task triggering method based on the task execution mode. For example, the task execution mode can include automatic execution (including scheduled execution and timed execution) and non-automatic execution. When non-automatic execution is selected, manual execution can be chosen. Furthermore, when the list of tasks to be executed is set to automatic execution, if a manual execution task is triggered during the non-execution period, a cooldown period can be set. That is, after the manual execution of this task list ends, it will not be automatically executed again during the cooldown period. This avoids resource conflicts and system load caused by managing the same resource in a short period of time, achieving efficient, stable, and reliable management of cloud resources.

[0076] In summary, by managing strategy types and component execution logic, cloud resources can be systematically managed and configured, ensuring consistent management operations for all cloud resources and reducing configuration inconsistencies. By generating a list of tasks to be executed, the status and progress of each task can be clearly tracked, improving management efficiency. The manual execution mode allows users to immediately execute tasks in emergencies, providing emergency handling capabilities and ensuring the timely execution of critical tasks.

[0077] In this embodiment of the application, the method for obtaining the component execution logic corresponding to the management strategy type may include:

[0078] Based on the management strategy type, determine the component type of the resource to be managed. The component type includes managed atomic components and managed resource relationship components.

[0079] The execution order of each component is determined based on the component type and the preset component level;

[0080] Based on the execution order of each component, generate the component execution logic corresponding to the management strategy type.

[0081] In this step, optionally, resource components of the same level are executed concurrently, while components of different levels are executed sequentially according to their level from smallest to largest. For example, managed atomic components can include atomic resources such as virtual machines, cloud disks, and network cards, while managed resource relationship components can include relationship components between virtual machines and cloud disks, virtual machines and network cards, etc. To improve code execution efficiency, components of the same category are set to the same level, meaning managed atomic components are executed concurrently; when executing the virtual machine and cloud disk relationship component, the virtual machine and cloud disk component tasks must be completed first before the virtual machine and cloud disk relationship component can be executed, in which case different categories of components are executed sequentially.

[0082] By using different types of components, cloud resources can be managed and configured more granularly; the execution order is determined according to the component type and preset component level to ensure that tasks are executed in the optimal order, thereby improving task execution efficiency; and the complexity and time of task execution are reduced by parallel execution, enabling the system to respond to and process tasks more quickly.

[0083] S102. If the task status is in the open state and the trigger execution condition is met, the list of tasks to be executed for the resources to be managed is sent to the message queue. The trigger execution condition is either a timed execution condition or a fixed-point execution condition.

[0084] Among these, the trigger execution condition can refer to the timed execution condition or the fixed-point execution condition that must be met when the task execution mode is automatic. Further, the timed execution condition can refer to automatically triggering task execution within a preset time interval, such as executing once every 24 hours; the fixed-point execution condition can refer to automatically triggering task execution at a preset specific time point, such as executing once at 2 AM every day. The trigger execution condition can also refer to manually triggering task execution when the task execution mode is not automatic.

[0085] Message queues are used to decouple producers and consumers, providing asynchronous communication and load balancing. In this step, when a task is in the open state and the triggering conditions are met, the list of tasks to be executed for the managed resources is sent to the message queue. This ensures that each list of tasks to be executed can be processed concurrently, and that the tasks in the list of tasks to be executed are reliably delivered and executed.

[0086] In this embodiment of the application, after determining the task status of the list of tasks to be executed for the resources to be managed, the method may further include:

[0087] If the task status meets the target conditions, the task of managing the resource to be managed will end. The target conditions include either the task status being closed or the task status being open and not meeting the trigger execution conditions.

[0088] When a task is in the active state, if the task execution mode of the task list to be executed is automatic, a scheduler can be set so that when the task is in the active state and the trigger execution conditions are not met, the scheduler can wait for a timed trigger, read the information of the task list to be executed, and automatically execute the subsequent management steps.

[0089] By checking whether the task status meets the target conditions, unnecessary managed tasks can be terminated in a timely manner, releasing resources; setting a scheduler can automatically manage the execution time and order of tasks, reducing execution errors caused by manual intervention and improving management efficiency.

[0090] S103. For each task in the task list, parse the component execution logic of the task from the message queue to obtain the component information of the component to be executed in the task. The component to be executed is the component in the task to be executed used to manage the required resources.

[0091] A message queue can be a middleware service used to store messages or tasks awaiting processing. It allows the system to process tasks asynchronously, improving responsiveness and throughput. Message queues are used in conjunction with thread pools; the message queue handles asynchronous task processing, while the thread pool executes these tasks. When a task is pushed into the message queue, threads in the thread pool can asynchronously retrieve the task from the queue and execute it. By using message queues and thread pools, the system can process individual tasks in the list of tasks to be executed more efficiently. The thread pool can reuse thread resources, and the message queue can smooth task traffic, thereby improving processing efficiency.

[0092] Component information refers to detailed information related to the component to be executed, including the component type, configuration parameters, dependencies, etc., which guides specific execution operations and ensures that the task can be executed correctly.

[0093] S104. Based on the component information, determine the resource encapsulation request information of the component to be executed.

[0094] Resource encapsulation request information can refer to request information used to obtain resource data from cloud service providers, including API (Application Programming Interface) call parameters, pagination information, etc. Furthermore, component encapsulation requirements can be determined based on component information, thereby determining the resource encapsulation request information.

[0095] S105. Based on the resource encapsulation request information, obtain the resource data of the component to be executed from the cloud service application interface pagination, encapsulate the resource data, and obtain the resource management component of the task to be executed.

[0096] Among them, the cloud service provider application programming interface (API) can be the API interface provided by the cloud service provider, allowing users to manage and operate cloud resources programmatically, thereby improving the automation and efficiency of operations.

[0097] When there is a large amount of resource data, pagination technology can be used to retrieve data in batches, reducing the amount of data in a single API call, avoiding problems caused by loading too much data at once, and improving system performance and response speed.

[0098] Resource management components can refer to encapsulated components that ensure resource data is correctly encapsulated and managed in accordance with expected strategies and requirements.

[0099] In this embodiment of the application, the method for obtaining the resource management component of the task to be executed by paginating the cloud service provider application interface according to the resource encapsulation request information and encapsulating the resource data may include:

[0100] Based on the authentication information of the cloud service provider application interface in the resource encapsulation request information, a request is sent to the cloud service provider application interface through the system's internal adaptation service in order to receive the response information from the cloud service provider application interface.

[0101] Based on the pagination parameter information in the resource encapsulation request information, perform resource pagination query on the response information to obtain the paginated resource data of the component to be executed;

[0102] The paginated resource data is compared with the resource data obtained from the last request in the system, and the resource data is synchronized based on the comparison results.

[0103] When the last pagination query in the pagination parameter information ends, the resource data of the component to be executed is obtained based on the pagination resource data after the resource data is synchronized.

[0104] The resource data is encapsulated and processed to obtain the resource management component for the task to be executed.

[0105] The authentication information of the cloud provider's application programming interface can refer to the credentials provided by the cloud provider to verify identity and permissions, such as API keys and access tokens, to ensure that the requester has the authority to access and operate cloud resources.

[0106] An adapter service can be an internal system service used to interact with external systems (such as cloud service provider APIs), sending requests and receiving responses; for example, an adapter service.

[0107] Response information can refer to the result data returned by the cloud provider API, including resource data, status information, etc., which supports subsequent data processing operations and management. Pagination parameter information can refer to the parameter information used for pagination queries, such as page number, data volume per page, etc., which is used to control the pagination behavior of API calls to ensure that complete resource data can be obtained.

[0108] In one example, if the component needs to retrieve 1000 data entries, and the paginated query retrieves 100 data entries at a time, then resource comparison is performed in increments of 100 data entries. When the comparison result indicates that the data has changed, the 100 changed data entries are sent to the message queue for data synchronization. At the same time, another 100 data entries are retrieved for resource comparison, and so on, until all 1000 data entries have been compared. The component's data is then encapsulated, and a new component task is requested.

[0109] In this step, synchronizing resource data ensures that the resource data in the system is up-to-date, thus improving data accuracy.

[0110] Therefore, by sending requests to the cloud provider's API interface through the system's internal adaptation service and receiving response information, the security of requests and the flexibility of the system are ensured. The pagination query method not only guarantees the integrity of resource data but also optimizes system performance. By comparing and synchronizing resource data, the system improves data consistency and reliability. At the end of the last pagination query, the synchronized data is summarized to ensure data integrity and processing efficiency. Finally, through standardized encapsulation, resource data is managed uniformly, enhancing data consistency and maintainability. At the same time, the encapsulated resource management component is traceable, improving the transparency of system operation and the convenience of management.

[0111] In this embodiment of the application, after encapsulating the resource data and obtaining the resource management component for the task to be executed, the method may further include:

[0112] The resource data of the component to be executed is compared with the resource data previously stored in the system to determine the resource data to be deleted in this synchronization.

[0113] Delete the stored data corresponding to the resource data that was deleted in this resource data synchronization process.

[0114] In this step, since there may be resource data synchronization issues during component data query encapsulation, in order to ensure that the database is consistent with the actual managed cloud resource environment, it is necessary to identify resource data that has been deleted during encapsulation but still exists in the database and delete it from the database.

[0115] S106. Generate resource management results for resources to be managed based on the resource management components of each task to be executed.

[0116] After each component completes execution, the system records the execution result, which may include information such as success or failure status, execution time, and output results. This provides traceability and transparency of the execution process, facilitating subsequent analysis, debugging, and optimization.

[0117] Optionally, when new cloud provider resources are already under management, only the components in the component pool need to be added, and the rest of the process remains unchanged, which greatly improves code development efficiency and maintainability.

[0118] In one example, if a new cloud provider, such as Alibaba Cloud, needs to be managed, the virtual machine, cloud disk, and network components are encapsulated and put into use using the policy type and component execution logic of this method. However, after a period of time (e.g., after six months), new requirements arise, such as managing object storage and capacity storage. In this case, the developers only need to develop new components and deploy them to the component pool. The component pool will display the cloud provider and version corresponding to the component. Then, users can select the component during policy configuration to meet the new requirements.

[0119] The multi-cloud provider resource management method provided in this application first determines the policy configuration type based on user needs, then parses and checks the status of tasks. Tasks that meet the conditions are sent to a message queue to wait for asynchronous processing. By extracting tasks from the queue and parsing the component execution logic, the system can determine the encapsulation request information of the required resources, and obtain resource data by paginating using the cloud provider's API. Finally, it encapsulates and generates resource management results, realizing an efficient and automated multi-cloud resource management process. Through steps such as task parsing, status checking, message queue, API calls, and data encapsulation, it achieves centralized management and scheduling of resources to be managed under different cloud accounts.

[0120] Figure 2 This is a flowchart illustrating another method for managing resources across multiple cloud providers, provided as an embodiment of this application. Figure 2 As shown, the method may include a synchronization strategy configuration module, a synchronization scheduling module, and a synchronization execution module. Each module is described below:

[0121] I. Synchronization Strategy Configuration Module

[0122] The synchronization strategy is obtained through page configuration or initialization, and includes the following:

[0123] 1. Select the strategy type, including: Select cloud provider, such as China Unicom Cloud or Tencent Cloud; Select version, because a cloud provider may have different versions, and the resources between different versions will be different, so you need to select the version to be managed; Select resource pool (can select all), to manage resources under a resource pool of a specified cloud provider (can select all); Select cloud account (can select all), to manage resources under a specific cloud account in a specified resource pool of a specified cloud provider (can select all).

[0124] Optionally, after selecting the management strategy type, it is stored in the `synchro_strategy_body` table, and a strategy ID is generated for subsequent manual or scheduled task queries.

[0125] 2. Select executable components for cloud services, including: selecting components and setting the execution order of components.

[0126] In one example, the component selection can choose to manage atomic resources, such as virtual machines, cloud disks, and network cards, from the underlying layer to the cloud management platform; or it can choose to manage resource relationship components, such as the relationship between virtual machines and cloud disks, or the relationship between virtual machines and network cards. The required resource management components can be flexibly configured according to user needs, improving code execution efficiency and user satisfaction.

[0127] In one example, setting the execution order of components can mean that components at the same level can be executed concurrently, thereby improving code execution efficiency. For example, setting resources such as virtual machines, cloud disks, and networks to the same level for concurrent execution improves efficiency; when executing a component related to virtual machines and cloud disks, the component tasks for virtual machines and cloud disks must be completed first before the component related to virtual machines and cloud disks can be executed. Therefore, setting levels can ensure the correctness and efficiency of resource management.

[0128] Optionally, selecting executable components from cloud providers can also include setting the data destination, such as Kafka, RabbitMQ, etc. After component selection, the strategy ID generated based on the strategy type is saved to the `synchro_strategy_unit` table. This allows for customizing the data destination, preparing for future expansion. When a management task is executed later, the strategy ID is used to retrieve the component to be executed and the relationships between components for management invocation.

[0129] 3. Select the execution method, including: scheduled execution, scheduled execution, and no automatic execution.

[0130] Optionally, after the execution method is set, it is saved to the synchro_strategy table, and the strategy type and component selection results are associated together based on the strategy ID.

[0131] II. Synchronization Scheduling Module

[0132] 1. Parse strategy types, including: obtaining a list of cloud accounts based on information such as cloud providers and resource pools, with task lists between cloud accounts being executed concurrently.

[0133] 2. Parse the execution logic of the components, including: based on the configured executable components, determine the concurrent execution of resources of the same level, and execute resources of different levels in ascending order.

[0134] 3. Assemble and record logical strategies, including: record the parsing results by cloud account and save them to the resource_sync_job_task table for task status viewing and error log viewing.

[0135] 4. Determine the policy status, including: when the status is off, the scheduling ends; when the status is on, the triggering method is divided into: timed execution, fixed-point execution, and manual execution.

[0136] Optionally, when the triggering method is automatic execution (timed execution, fixed-point execution), the scheduler is set and waits for subsequent schedulers to trigger at regular intervals; when the triggering method is not automatic execution, the scheduling ends.

[0137] 5. Automatic execution of the scheduler, including: reading information based on the scheduler settings set in the previous step, and triggering the synchronous execution module at regular intervals.

[0138] III. Synchronous Execution Module

[0139] 1. Retrieve the complete task list by strategy ID.

[0140] 2. Execute all tasks simultaneously (send the task list to the message queue).

[0141] 3. Execute component management logic, including: executing the synchronization logic of each component according to the set component execution order.

[0142] 4. Record execution information, including the execution results of each component.

[0143] 5. Execution complete.

[0144] Optionally, when the triggering method is not automatic, it can be manually triggered based on the user's manual operation on the page to ensure the timeliness of resource management.

[0145] The multi-cloud provider resource management method provided in this application adopts a rapid management approach using three modules: synchronous strategy configuration, synchronous scheduling, and synchronous execution, for managing existing multi-cloud resources. This solution first collects basic resource information by determining the cloud vendor, version, and resource pool to which the resource belongs. Next, in the synchronous scheduling phase, resource allocation strategies are refined and implemented according to preset policies. In the synchronous execution module, APIs provided by various cloud vendors (such as Alibaba Cloud) are called to acquire, process, and store resource data in the cloud management system database, and the required resource information is displayed on the page. The component-based design enhances the system's flexibility and scalability, resolving differences in interfaces, request methods, and parameters between different cloud service providers, thereby achieving effective integration and unified presentation of cross-cloud resources. Increased configuration also enhances portability; the flexibility of configuration reduces dependence on code and also reduces the difficulty of porting caused by code. Furthermore, during use, if resource shortages or excessive business pressure necessitate scaling by increasing the number of machines, this method achieves concurrent execution through a message queue mechanism, thus enabling easy resource transition.

[0146] Figure 3 A flowchart illustrating the component management logic provided in this application is shown below. Figure 3 As shown, in this embodiment... Figure 2 Based on the implementation examples, the component management logic in the multi-cloud provider resource management method is described in detail. This method includes:

[0147] 1. Upon receiving a message from the message queue, parse the components and their order to be executed. Using a thread pool, components of the same level are executed concurrently to improve management efficiency, while components of different levels are executed sequentially.

[0148] 2. Encapsulate request parameters and use the internal adapter service to call the API interface provided by the cloud provider to obtain resource list data. Optionally, query to obtain all data or query multiple times in pagination to obtain data.

[0149] When paginated queries are required, each time a certain number of data items (e.g., 100 items) are retrieved, the current data is compared with the result of the previous request to check for changes. If there are no changes, this batch of data remains unchanged and can be returned directly, improving management efficiency. If changes have occurred, this batch of data is sent to a queue for subsequent encapsulation and database processing, and then the next batch of data is requested again, which can greatly improve management efficiency. Through configuration, the size of each data request (e.g., 100 items per request) and the return conversion template can be set, reducing the amount of code development required.

[0150] 3. Perform data encapsulation and processing, store the data in the cloud management platform database, and perform batch insertion and update operations to improve management efficiency.

[0151] 4. Compare the resources queried this time with the resources queried last time, find the underlying data that has been deleted, and execute the batch deletion program.

[0152] 5. Update task status and logs for viewing on the page.

[0153] The component management logic provided in this application embodiment, since the management task is based on cloud accounts, allows for concurrent task processing using a thread pool based on message queues when a tenant of a cloud account selects multiple components. This improves management efficiency, and the execution of tasks in each message queue does not interfere with each other, ensuring the accuracy of the managed data. Components in each management task are executed concurrently or sequentially according to their execution order. When managing new cloud provider resources, only the components in the component pool need to be added; the rest of the process remains unchanged, greatly improving code development efficiency and maintainability.

[0154] Figure 4 The structural diagram of the resource management device for multi-cloud providers provided in this application is as follows: Figure 4 As shown, the multi-cloud provider resource management device 40 provided in this embodiment includes:

[0155] The acquisition module 401 is used to acquire the task status of the list of tasks to be executed for resources to be managed. The list of tasks to be executed is a collection of tasks to be executed by cloud account. The tasks to be executed are obtained by parsing the strategy configuration type of the resource to be managed and the component execution logic of the strategy configuration type. The strategy configuration type is determined according to the user's resource configuration requirements.

[0156] The sending module 402 is used to send the list of tasks to be executed for the resources to be managed to the message queue if the task status is in the open state and the trigger execution condition is met. The trigger execution condition is either a timed execution condition or a fixed-point execution condition.

[0157] The parsing module 403 is used to parse the component execution logic of each task to be executed from the message queue for each task to be executed in the task to be executed list, and obtain the component information of the component to be executed in the task to be executed, wherein the component to be executed is the component used for resource management in the task to be executed;

[0158] The determination module 404 is used to determine the resource encapsulation request information of the component to be executed based on the component information;

[0159] The encapsulation module 405 is used to obtain the resource data of the component to be executed from the cloud application interface pagination according to the resource encapsulation request information, and to encapsulate the resource data to obtain the resource management component of the task to be executed.

[0160] The generation module 406 is used to generate the resource management results of the resources to be managed based on the resource management components of each task to be executed.

[0161] In one possible implementation, the acquisition module 401 can also be used for:

[0162] Obtain the management strategy type of the resource to be managed, and the component execution logic corresponding to the management strategy type. The management strategy type includes the cloud provider to be managed, the version of the cloud provider to be managed, the resource pool under the version, and the cloud account in the resource pool.

[0163] The management strategy type is analyzed to obtain the initial tasks to be executed based on the cloud account.

[0164] Based on the component execution logic, determine the execution order of each component to be executed corresponding to the initial task to be executed, and obtain the task to be executed;

[0165] Based on the pending tasks of each cloud account in the management strategy type, obtain the list of pending tasks for the resources to be managed.

[0166] In one possible implementation, the acquisition module 401 can also be used for:

[0167] Based on the management strategy type, determine the component type of the resource to be managed. The component type includes managed atomic components and managed resource relationship components.

[0168] The execution order of each component is determined based on the component type and the preset component level;

[0169] Based on the execution order of each component, generate the component execution logic corresponding to the management strategy type.

[0170] In one possible implementation, the sending module 402 can also be used for:

[0171] If the task status meets the target conditions, the task of managing the resource to be managed will end. The target conditions include either the task status being closed or the task status being open and not meeting the trigger execution conditions.

[0172] In one possible implementation, the encapsulation module 405 can also be used for:

[0173] Based on the authentication information of the cloud service provider application interface in the resource encapsulation request information, a request is sent to the cloud service provider application interface through the system's internal adaptation service in order to receive the response information from the cloud service provider application interface.

[0174] Based on the pagination parameter information in the resource encapsulation request information, perform resource pagination query on the response information to obtain the paginated resource data of the component to be executed;

[0175] The paginated resource data is compared with the resource data obtained from the last request in the system, and the resource data is synchronized based on the comparison results.

[0176] When the last pagination query in the pagination parameter information ends, the resource data of the component to be executed is obtained based on the pagination resource data after the resource data is synchronized.

[0177] The resource data is encapsulated and processed to obtain the resource management component for the task to be executed.

[0178] In one possible implementation, the encapsulation module 405 can also be used for:

[0179] The resource data of the component to be executed is compared with the resource data previously stored in the system to determine the resource data to be deleted in this synchronization.

[0180] Delete the stored data corresponding to the resource data that was deleted in this resource data synchronization process.

[0181] The multi-cloud provider resource management device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0182] Figure 5 A schematic diagram of the structure of the electronic device provided in this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus 504.

[0183] In a specific implementation, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-described method.

[0184] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0185] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The method steps disclosed in this invention can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0186] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0187] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0188] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0189] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0190] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0191] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0192] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

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

[0194] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0195] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0196] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0197] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A multi-cloud resource onboarding method, characterized in that, The method comprises the following steps: acquiring a task state of a to-be-executed task list of a to-be-managed resource, wherein the to-be-executed task list is a set of to-be-executed tasks in a cloud account dimension, the to-be-executed task is obtained by task analysis on a component execution logic of a policy configuration type of the to-be-managed resource, and the policy configuration type is determined according to a user resource configuration requirement; if the task state is in an open state and a trigger execution condition is met, sending the to-be-executed task list of the to-be-managed resource to a message queue, wherein the trigger execution condition is a timing execution condition or a fixed-point execution condition; for each to-be-executed task in the to-be-executed task list, analyzing a component execution logic of the to-be-executed task from the message queue to obtain component information of a to-be-executed component in the to-be-executed task, wherein the to-be-executed component is a component required for managing the to-be-managed resource in the to-be-executed task; determining resource encapsulation request information of the to-be-executed component according to the component information; according to the resource encapsulation request information, obtaining resource data of the to-be-executed component from a cloud service application program interface in pages, and performing encapsulation processing on the resource data to obtain a resource management component of the to-be-executed task; generating a resource management result of the to-be-managed resource according to the resource management component of each to-be-executed task.

2. The method of claim 1, wherein, Before the step of acquiring the task state of the to-be-executed task list of the to-be-managed resource, the method further comprises the following steps: acquiring a management policy type of the to-be-managed resource and a component execution logic corresponding to the management policy type, wherein the management policy type comprises a to-be-managed cloud service, a version of the to-be-managed cloud service, a resource pool under the version, and a cloud account in the resource pool; analyzing the management policy type to obtain an initial to-be-executed task in a cloud account dimension; determining an execution order of each to-be-executed component corresponding to the initial to-be-executed task according to the component execution logic to obtain a to-be-executed task; acquiring the to-be-executed task list of the to-be-managed resource according to the to-be-executed task of each cloud account in the management policy type.

3. The method of claim 2, wherein, The step of acquiring the component execution logic corresponding to the management policy type comprises the following steps: determining a component type of the to-be-managed resource according to the management policy type, wherein the component type comprises a management atomic component and a management resource interrelation component; determining an execution order of each component according to the component type and a preset component level; generating the component execution logic corresponding to the management policy type according to the execution order of each component.

4. The method of claim 1, wherein, After the step of determining the task state of the to-be-executed task list of the to-be-managed resource, the method further comprises the following steps: if the task state meets a target condition, ending a management task of the to-be-managed resource, wherein the target condition comprises any one of the following conditions: the task state is in a closed state, and the task state is in an open state and the trigger execution condition is not met.

5. The method of claim 1, wherein, The step of obtaining the resource data of the to-be-executed component from the cloud service application program interface in pages according to the resource encapsulation request information, and performing encapsulation processing on the resource data to obtain the resource management component of the to-be-executed task comprises the following steps: According to the authentication information of the cloud merchant application interface in the resource packaging request information, a request is sent to the cloud merchant application interface through an adaptation service inside the system to receive response information of the cloud merchant application interface; According to the page parameter information in the resource packaging request information, the response information is queried for resource paging to obtain page resource data of the to-be-executed component; The page resource data is compared with resource data obtained by last request in the system, and resource data synchronization is performed according to a comparison result; When the last page query in the page parameter information ends, resource data of the to-be-executed component is obtained according to the page resource data after resource data synchronization; The resource data is packaged to obtain a resource containment component of the to-be-executed task.

6. The method of claim 5, wherein, After the resource data is packaged to obtain the resource containment component of the to-be-executed task, the method further includes: The resource data of the to-be-executed component is compared with resource data stored in the system last time, and resource data to be deleted in this resource data synchronization is determined; Storage data corresponding to the resource data to be deleted in this resource data synchronization in the system is deleted.

7. A multi-vendor resource onboarding apparatus, comprising: Comprise: An acquisition module is configured to acquire a task state of a to-be-contained resource to-be-executed task list, wherein the to-be-executed task list is a set of to-be-executed tasks of the to-be-contained resource in a cloud account dimension, the to-be-executed task is obtained by task analysis on a policy configuration type of the to-be-contained resource and component execution logic of the policy configuration type, and the policy configuration type is determined according to a user resource configuration requirement; A sending module is configured to send the to-be-contained resource to-be-executed task list to a message queue if the task state is in an open state and a trigger execution condition is met, wherein the trigger execution condition is a timing execution condition or a fixed-point execution condition; An analysis module is configured to analyze, for each to-be-executed task in the to-be-executed task list, component execution logic of the to-be-executed task from the message queue to obtain component information of a to-be-executed component in the to-be-executed task, wherein the to-be-executed component is a component for containing a required resource in the to-be-executed task; A determination module is configured to determine resource packaging request information of the to-be-executed component according to the component information; A packaging module is configured to obtain resource data of the to-be-executed component from a cloud merchant application interface in pages according to the resource packaging request information, and to package the resource data to obtain a resource containment component of the to-be-executed task; A generation module is configured to generate a resource containment result of the to-be-contained resource according to the resource containment component of each to-be-executed task.

8. An electronic device, comprising: Comprise: A memory and a processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the method in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed to implement the method in any one of claims 1-6.

10. A computer program product comprising a computer program which, when executed by a computer, implements the method of any one of claims 1 to 6.

Images