Cloud resource management method and device, medium and equipment

Abstract

The invention discloses a cloud resource management method and device, a medium and equipment. The method comprises the following steps: receiving a standardized resource request submitted by a user, firstly converting the standardized resource request into structured task data, then analyzing the structured task data by utilizing a preset process engine, and generating an execution process containing an atomic operation sequence. Based on a preset event-driven architecture, the execution process is distributed to the adapter cluster, the adapter cluster generates each standardized instruction according to the atomic operation sequence, adapts the instructions into an interface format which can be identified by the target platform through a preset protocol conversion module, and finally outputs the instructions to the interface of each target platform. According to the process, end-to-end automatic management from user requests to cross-platform resource operation is realized, and the efficiency and flexibility of heterogeneous cloud resource management are improved.

Description

Technical Field

[0001] The present invention relates to the field of cloud resource management, and in particular, to a cloud resource management method, apparatus, medium, and device. Background Art

[0002] With the rapid development of cloud computing technology, enterprises are increasingly adopting multi-cloud and hybrid-cloud architectures to meet different business needs. Such architectures typically include a variety of heterogeneous resources, such as public cloud platforms (e.g., Alibaba Cloud, AWS, Azure), private cloud platforms (e.g., VMware, OpenStack), containerized platforms (e.g., Kubernetes), as well as traditional physical servers and storage devices. However, current cloud resource management faces the following challenges:

[0003] System dispersion and fragmented service catalog:

[0004] Existing operation and maintenance management relies on multiple independent systems, such as monitoring systems, logging systems, configuration management systems, etc. These systems operate independently, and service entry points are dispersed, resulting in users needing to operate across multiple platforms, with low efficiency. For example, users may need to submit resource applications, view resource status, and make configuration changes on different platforms respectively, which not only increases the complexity of operations but also easily leads to human errors.

[0005] Insufficient automation capabilities:

[0006] Current operation and maintenance processes mostly rely on manual approval and operation, and end-to-end automation cannot be achieved. For example, operations such as resource application, configuration change, and resource recovery usually require manual intervention, which not only reduces operation and maintenance efficiency but also increases the risk of operation errors. In addition, the lack of automation capabilities also makes it difficult for enterprises to quickly respond to changes in business needs.

[0007] Difficulties in heterogeneous resource management:

[0008] The interfaces between different cloud platforms and operation and maintenance tools are not unified, making it difficult to achieve unified lifecycle management. For example, the API interfaces of platforms such as Alibaba Cloud and VMware are different, resulting in enterprises needing to develop multiple adapters when managing cross-platform resources, increasing development and maintenance costs. At the same time, the lack of a unified resource management framework also makes resource monitoring, auditing, and optimization complex.

[0009] Poor scalability:

[0010] Existing architectures are usually tightly coupled, and adding new services or functions requires repeated development and cannot quickly respond to changes in business needs. For example, when an enterprise needs to introduce a new cloud service or tool, it often needs to make large-scale modifications and tests to the existing system, which is not only time-consuming and laborious but may also introduce new compatibility issues.

[0011] In summary, there are many deficiencies in the prior art in terms of multi-cloud, hybrid cloud, and heterogeneous resource management, and these deficiencies result in the inability of the prior art to efficiently manage heterogeneous resources. Summary of the Invention

[0012] The present invention provides a cloud resource management method, device, medium, and equipment to solve the problem in the prior art that heterogeneous resources cannot be efficiently managed.

[0013] In a first aspect, the present application provides a cloud resource management method, including:

[0014] Receiving a standardized resource request submitted by a user;

[0015] Converting the resource request into structured task data, and parsing the structured task data according to a preset process engine to generate an execution process including an atomic operation sequence;

[0016] According to a preset event-driven architecture, distributing the execution process to an adapter cluster, so that the adapter cluster generates each standardized instruction according to the atomic operation sequence, and outputs each standardized instruction to the interfaces of each target platform through a preset protocol conversion module.

[0017] The present application realizes the efficient collection and preliminary processing of user requirements by receiving a standardized resource request submitted by a user and converting it into structured task data. On this basis, the preset process engine is used to parse the structured task data to generate an execution process including an atomic operation sequence. This process not only ensures the standardization and normalization of task data, but also provides a basis for subsequent automated execution through the definition of the atomic operation sequence. Further, based on the event-driven architecture, the execution process is distributed to the adapter cluster, and the adapter cluster generates each standardized instruction according to the atomic operation sequence, and adapts these instructions to the interfaces of different target platforms through the protocol conversion module. This series of designs enables the present application to achieve the automation and unified management of cross-platform resource operations. The present application effectively solves the problem that the prior art cannot efficiently manage heterogeneous resources.

[0018] As a preferred embodiment of the first aspect, the receiving of the standardized resource request submitted by the user is specifically:

[0019] Receiving an initial resource request submitted by the user;

[0020] Constructing the user's standardized resource form according to the initial resource request, the user's role, preset form types, and a preset historical form library;

[0021] Identify the standardized resource form to obtain a normalized resource request.

[0022] In this preferred embodiment, the present application constructs a standardized resource form by receiving an initial resource request submitted by a user and combining the user role, preset form type, and historical form library. The present application can generate personalized resource application forms for different users. This process not only reduces the repetitive work of users when filling out applications but also ensures the standardization and consistency of resource requests through standardized forms. Further, identifying the standardized resource form to obtain a normalized resource request ensures that the system can accurately parse the true needs of users and provides high-quality input data for subsequent automated processing and resource allocation. This processing flow from the initial request to the normalized request significantly improves the user experience, enhances the efficiency and accuracy of resource applications, and at the same time lays a solid foundation for realizing end-to-end automated resource management.

[0023] As a preferred embodiment of the first aspect, after receiving the initial resource request submitted by the user, it further includes:

[0024] Perform authentication management on the initial resource request according to a preset multi-factor authentication module;

[0025] Among them, the multi-factor authentication module includes one or more combinations of the following: SMS authentication, single sign-on authentication, LDAP authentication, or local user authentication;

[0026] Adjust the initial resource request permission of the user according to the user department information and user permission configuration in the preset CMDB module.

[0027] In this preferred embodiment, by introducing a multi-factor authentication module after receiving the initial resource request submitted by the user, the present application can strictly verify the user's identity and ensure that only authorized users can submit resource requests. The multi-factor authentication module supports multiple authentication methods (such as SMS authentication, single sign-on authentication, LDAP authentication, or local user authentication). This diverse authentication method not only improves the security of the system but also meets scenarios with different user environments and security requirements, enhancing the applicability and flexibility of the system. Further, by combining the user department information and user permission configuration in the CMDB module, the system can dynamically adjust the initial resource request permission of the user. This mechanism ensures that users can only request resources within their permission scope, thus effectively preventing unauthorized operations and enhancing the security and compliance of resource management.

[0028] As a preferred embodiment of the first aspect, the adapter cluster generates each standardized instruction according to the atomic operation sequence and outputs each standardized instruction to the interface of each target platform through a preset protocol conversion module, specifically as follows:

[0029] The adapter cluster receives the atomic operation sequence, and calls each adapter module according to the operation type and each target platform information in the atomic operation sequence;

[0030] According to each adapter module, convert the operation instructions in the atomic operation sequence into each standardized instruction of each target platform;

[0031] According to the preset protocol conversion module and the interface specifications of each target platform, convert the each standardized instruction into an interface call format instruction recognizable by each target platform;

[0032] Output the converted interface call format instruction to the interfaces of each target platform.

[0033] In this preferred embodiment, the present application receives the atomic operation sequence through the adapter cluster, and calls the corresponding adapter module according to the operation type and target platform information, and can accurately convert the general atomic operation instructions into standardized instructions adapted to each target platform. This process uses the preset protocol conversion module to further adapt the standardized instructions into interface call format instructions recognizable by the target platform, and finally outputs them to the target platform interface. This design not only realizes the unified operation of heterogeneous resource management platforms, but also solves the problem of interface differences between different platforms through standardized instructions and protocol conversion modules, thus significantly improving the flexibility and automation of resource management. At the same time, this hierarchical adaptation and conversion mechanism enhances the scalability and compatibility of the system. When adding or replacing a resource management platform, only the corresponding adapter module needs to be adjusted, without modifying the core process, reducing the development and maintenance costs, and improving the overall efficiency and adaptability of the system.

[0034] As a preferred embodiment of the first aspect, it further includes:

[0035] Record the operation logs and resource status change data of the adapter cluster according to the preset hierarchical decoupling architecture method;

[0036] Send the operation logs and resource status change data to a preset audit database, and display the full-link execution status and exception warning information through a preset visualization interface.

[0037] In this preferred embodiment, the present application can record the operation logs and resource status change data of the adapter cluster by adopting a preset hierarchical decoupling architecture method. This process not only ensures the transparency and traceability of system operations, but also realizes the centralized monitoring and auditing of the entire resource management process by sending these key data to a preset audit database. Further, by means of a preset visualization interface to display the full-link execution status and exception warning information, the system can provide real-time feedback on the operation progress and potential problems, enabling the operation and maintenance personnel to quickly locate and handle abnormal situations. This design significantly improves the operation and maintenance efficiency and reliability of the system, while enhancing the control ability of the resource management process and ensuring the compliance and security of resource operations.

[0038] In a second aspect, the present application provides a cloud resource management device. The cloud resource management device includes: a receiving module, an analysis module, and an output module;

[0039] The receiving module is used to receive a standardized resource request submitted by a user;

[0040] The analysis module is used to convert the resource request into structured task data, and according to a preset process engine, analyze the structured task data to generate an execution process including an atomic operation sequence;

[0041] The output module is used to distribute the execution process to an adapter cluster according to a preset event-driven architecture, so that the adapter cluster generates each standardized instruction according to the atomic operation sequence, and outputs each standardized instruction to the interfaces of each target platform through a preset protocol conversion module.

[0042] This device uses three modules to work in division and coordination to manage cloud resources more efficiently. The present application realizes the efficient collection and preliminary processing of user requirements by receiving the standardized resource request submitted by the user and converting it into structured task data. On this basis, a preset process engine is used to analyze the structured task data to generate an execution process including an atomic operation sequence. This process not only ensures the standardization and normalization of task data, but also provides a basis for subsequent automated execution through the definition of the atomic operation sequence. Further, based on the event-driven architecture, the execution process is distributed to the adapter cluster. The adapter cluster generates each standardized instruction according to the atomic operation sequence, and adapts these instructions to the interfaces of different target platforms through the protocol conversion module. This series of designs enables the present application to realize the automation and unified management of cross-platform resource operations. The present application effectively solves the problem that the prior art cannot efficiently manage heterogeneous resources.

[0043] As a preferred embodiment of the second aspect, the receiving module includes: a receiving unit, a construction unit, and an obtaining unit;

[0044] The receiving unit is configured to receive an initial resource request submitted by a user;

[0045] The constructing unit is configured to construct a standardized resource form of the user according to the initial resource request, the role of the user, various preset form types, and a preset historical form library;

[0046] The obtaining unit is configured to identify the standardized resource form to obtain a normalized resource request.

[0047] In this preferred embodiment, the present application receives an initial resource request submitted by a user, and constructs a standardized resource form in combination with the user role, preset form types, and historical form library. The present invention can generate personalized resource application forms for different users. This process not only reduces the repetitive work of users when filling out applications, but also ensures the standardization and consistency of resource requests through standardized forms. Further, identifying the standardized resource form to obtain a normalized resource request ensures that the system can accurately parse the true needs of users, providing high-quality input data for subsequent automated processing and resource allocation. This processing flow from the initial request to the normalized request significantly improves the user experience, enhances the efficiency and accuracy of resource applications, and at the same time lays a solid foundation for realizing end-to-end automated resource management.

[0048] As a preferred embodiment of the second aspect, the adapter cluster generates various standardized instructions according to the atomic operation sequence, and outputs the various standardized instructions to the interfaces of various target platforms through a preset protocol conversion module, specifically:

[0049] The adapter cluster receives the atomic operation sequence, and calls each adapter module according to the operation types and information of each target platform in the sequence;

[0050] According to each adapter module, convert the operation instructions in the atomic operation sequence into various standardized instructions of each target platform;

[0051] According to the preset protocol conversion module and the interface specifications of each target platform, convert the various standardized instructions into an interface call format recognizable by each target platform;

[0052] Output the converted interface call format to the interfaces of various target platforms.

[0053] In this preferred embodiment, the present application receives an atomic operation sequence through an adapter cluster, and calls the corresponding adapter module according to the operation type and target platform information, and can accurately convert general atomic operation instructions into standardized instructions adapted to each target platform. This process utilizes a preset protocol conversion module to further adapt the standardized instructions into interface call format instructions recognizable by the target platform, and finally outputs them to the target platform interface. This design not only realizes the unified operation of heterogeneous resource management platforms, but also solves the problem of interface differences between different platforms through standardized instructions and protocol conversion modules, thus significantly improving the flexibility and automation of resource management. At the same time, this hierarchical adaptation and conversion mechanism enhances the scalability and compatibility of the system. When adding or replacing a resource management platform, only the corresponding adapter module needs to be adjusted without modifying the core process, reducing the development and maintenance costs and improving the overall efficiency and adaptability of the system.

[0054] In a third aspect, the present application provides a computer-readable storage medium, which includes a stored computer program. When the computer program runs, it controls the device where the computer-readable storage medium is located to execute a cloud resource management method as described above. Its beneficial effects are the same as those of the cloud resource management method provided in the first aspect of the present application.

[0055] In a fourth aspect, the present application provides a terminal device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, it implements any one of the cloud resource management methods described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 : A flowchart of an embodiment of the cloud resource management method provided by the present application;

[0057] Figure 2 : A structural diagram of an embodiment of the unified operation and maintenance portal management provided by the present application;

[0058] Figure 3 : A structural diagram of an embodiment of the cloud resource management device provided by the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0059] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0060] Example 1

[0061] Please refer to Figure 1 , which is a cloud resource management method provided by an embodiment of the present invention.

[0062] In this embodiment, the process of the cloud resource management method in this application is described in detail through steps S01 - S03.

[0063] The cloud resource management of this application depends on the unified operation and maintenance portal. The unified operation and maintenance portal of this application manages the processes of each platform as Figure 2 shown. The unified operation and maintenance portal serves as the only entry for users to interact with the system. Integrate user identity authentication and permission management functions in the portal to ensure that different users can only access the resources and services within their permissions. Provide a user - friendly interface to support operations such as users submitting resource applications and operation and maintenance transaction requests.

[0064] S01: Receive the standardized resource request submitted by the user.

[0065] As a preferred embodiment of Example 1, the receiving of the standardized resource request submitted by the user is specifically:

[0066] Receive the initial resource request submitted by the user;

[0067] According to the initial resource request, the user's role, the preset various form types, and the preset historical form library, construct the user's standardized resource form;

[0068] Identify the standardized resource form to obtain the standardized resource request.

[0069] More specifically, collect user context information. When the user opens the form page, the system automatically collects the following context information. It includes:

[0070] User role: Obtained through the permission management module.

[0071] Form type: The form type selected by the user.

[0072] Current resource status: Obtain relevant information (such as the applied application system, project, etc.) from CMDB or other resource management systems.

[0073] Query the historical form library, and retrieve the records that meet the conditions from the historical form library according to the user role and form type. The retrieval logic includes:

[0074] Filter by user ID: Only retrieve the historical records of the current user. If the current user has no historical records, obtain the historical records according to the current user role.

[0075] Filter by form type: Only retrieve records related to the current form type.

[0076] Sort by time: Prefer to select the most recent operation records.

[0077] Based on the matched historical records, an initial form is automatically generated. The specific process is as follows:

[0078] Map the field values in the historical records to the corresponding fields in the new form.

[0079] Adjust some field values according to the current context information. If the current submitted application system is different from the historical records, the fields related to the application system are applied. If the user role changes, the default permission configuration is adjusted.

[0080] Pre-fill the common field values in the historical records into the new form.

[0081] The generated form will be displayed to the user, and the user can modify the pre-filled content according to actual needs. Adjust the instance specifications or storage capacity. Add new tags or description information.

[0082] When the user completes filling out the form and submits it, the system will save the data of the new form to the historical form library for future reference.

[0083] Furthermore, in the resource application module, an intelligent form generation function is implemented. According to the user role and form type, the historical form library is matched, and the most recent historical operation record in the historical library table is used to automatically generate a form and pre-fill the form information, reducing the user's input workload.

[0084] In this preferred embodiment, the present application constructs a standardized resource form by receiving the initial resource request submitted by the user and combining the user role, preset form type, and historical form library. The present application can generate personalized resource application forms for different users. This process not only reduces the repetitive work of users when filling out applications but also ensures the standardization and consistency of resource requests through standardized forms. Further, the standardized resource form is identified to obtain a standardized resource request, which ensures that the system can accurately parse the true needs of users and provides high-quality input data for subsequent automated processing and resource allocation. This processing flow from the initial request to the standardized request significantly improves the user experience, enhances the efficiency and accuracy of resource applications, and at the same time lays a solid foundation for realizing end-to-end automated resource management.

[0085] As a preferred embodiment of Embodiment 1, after receiving the initial resource request submitted by the user, it further includes:

[0086] According to the preset multi-factor authentication module, perform authentication management on the initial resource request;

[0087] Among them, the multi-factor authentication module includes one or more combinations of the following: SMS authentication, single sign-on authentication, LDAP authentication, or local user authentication;

[0088] Adjust the initial resource request permission of the user according to the user department information and user permission configuration in the preset CMDB module.

[0089] More specifically, the preset CMDB module is in the preset permission management module. The permission management module supports the dynamic permission adjustment function and supports rule-based permission changes; this module is connected to the CMDB configuration data, and according to the user's department and team, automatically grants the user different resource application permissions and approval permissions. At the same time, according to the configuration information, different resources can only be operated during certain time periods;

[0090] The permission management module realizes the connection with the CMDB data and rule-based permission changes according to the following steps:

[0091] (1) Rule definition and matching, rule creation, define permission change rules according to business requirements. For example: "When a user belongs to the R & D department, grant the permission to apply for test environment resources."

[0092] Rule engine matching, the permission management module regularly scans the resource configuration and user information in the CMDB through the rule engine, matches the users or resources that meet the rules, and grants the resources that the user can apply for and operate.

[0093] (2) Connect with the CMDB data, user information synchronization: obtain the organizational structure information such as the user's department and team from the CMDB. Resource information synchronization: obtain the attributes, status, and ownership information of the resources from the CMDB (such as the project to which the resource belongs, the dependency relationship). Event listening: capture the changes of users or resources in real time through subscribing to the event notification mechanism of the CMDB (such as a user transferring departments, a resource status change).

[0094] (3) Automatically grant permissions, application permission granting: automatically assign the application permission of specific resources according to the user's department and team information. For example: Users in the R & D center can apply for test environment resources. Users in the operation and maintenance center can apply for production environment resources. Approval permission granting: assign approval permissions to team leaders or specific roles. For example: The team leader can approve the resource applications submitted by team members.

[0095] (4) Time limit configuration, time period definition: Configure the operable time period of resources in the CMDB. For example: Resources in the production environment are only allowed to be operated during the maintenance window (such as 2:00 - 4:00 in the early morning). Permission adjustment: The permission management module dynamically adjusts the user's operation permissions according to the current time and the configured time period. If it is not within the allowed time period, the relevant permissions are automatically disabled.

[0096] (5) Permission update and synchronization, permission calculation: Calculate the user's final permissions based on the rule matching results and time limit configuration. Permission update: Apply the calculation results to the permission management system, update the user's permission configuration, and synchronize the modification.

[0097] In this preferred embodiment, by introducing a multi-factor authentication module after receiving the initial resource request submitted by the user, the present application can strictly verify the user's identity, ensuring that only authorized users can submit resource requests. The multi-factor authentication module supports multiple authentication methods (such as SMS authentication, single sign-on authentication, LDAP authentication, or local user authentication). This diverse authentication method not only improves the security of the system but also meets the scenarios of different user environments and security requirements, enhancing the applicability and flexibility of the system. Further, in combination with the user department information and user permission configuration in the CMDB module, the system can dynamically adjust the initial resource request permissions of the user. This mechanism ensures that users can only request resources within their permission scope, thus effectively preventing unauthorized operations and enhancing the security and compliance of resource management.

[0098] S02: Convert the resource request into structured task data, and parse the structured task data according to a preset process engine to generate an execution process containing an atomic operation sequence.

[0099] As a preferred embodiment of Embodiment 1, the step of converting the resource request into structured task data, and parsing the structured task data according to a preset process engine to generate an execution process containing an atomic operation sequence is specifically as follows: Process and transfer the structured data required by the user through the process engine of the process platform. The process engine automatically triggers the corresponding business process according to the demand type, driving the automation platform to perform subsequent operations. During the process transfer, the status and operation logs of each step are recorded in real time to ensure the traceability of the process.

[0100] The process engine is located between the user form and the automation platform. As a bridge connecting the user interface and the underlying automation platform, its main responsibilities include receiving requests from the user interface or API gateway, parsing the user's requirements and generating structured data, calling atomic operations to complete specific tasks, monitoring the task execution status, and feeding back the results.

[0101] The process engine converts user requirements into structured data through the following steps:

[0102] User requirements can be submitted in the form of a JSON-formatted task description by calling the RESTful API at the front end.

[0103] After receiving the user input, the process engine will convert it into structured data through the following steps:

[0104] Syntax parsing: For inputs in formats such as JSON, directly parse them into key-value pair structures.

[0105] Parameter mapping: Map the parameters provided by the user to the standard fields within the system.

[0106] The user requirements are converted into structured data, represented in JSON format. This data includes the following:

[0107] Task type: For example, creating a virtual machine, creating a database user, etc.

[0108] Target resources: The specific resources that need to be operated on (such as host IP, storage path).

[0109] Operation parameters: The detailed parameters required to execute the task (such as the number of CPU cores, memory size).

[0110] Dependency relationships: The sequential or conditional constraints between tasks.

[0111] The generated structured data will be used in the following aspects:

[0112] Atomic operation invocation: Decompose the task into a series of atomic operations and pass the parameters.

[0113] Status tracking: Record the execution status of each task for easy monitoring and rollback.

[0114] Log recording: Save the complete execution history of the task for auditing and problem troubleshooting.

[0115] The implementation method of the atomization operation: An atomic operation is an indivisible basic operation and maintenance task unit. Through in-depth analysis of the operation and maintenance scenarios, common operation and maintenance tasks are decomposed into a series of basic operations, such as service start / stop, software installation, log collection, configuration file modification, etc.

[0116] Each atomic operation is usually implemented in the form of scripts or tools. These scripts are based on Shell / Python / Powershell and are used to execute operating system-level commands, and can be distributed to the managed operating systems in the way of ANT. In addition, it can also be based on API calls to complete specific tasks (such as cloud service management) by calling the APIs of external services. Each script or tool will undergo strict testing to ensure its stable function and easy extensibility.

[0117] A unified interface specification is defined for each atomic operation. These interfaces include input parameters: clearly define the parameters that need to be provided (such as target host, path, username, etc.).

[0118] Output results: return the status code, log information or other result data of the operation.

[0119] Error handling: define the behavior in case of exceptions, such as retry mechanisms or rollback strategies.

[0120] Through the unified interface, users can easily combine different atomic operations into complex operation and maintenance processes.

[0121] Integrated into the workflow engine introduced above, it allows multiple atomic operations to be concatenated to form complex operation and maintenance tasks, and can quickly build custom workflows and execute them automatically. For example:

[0122] Atomic operation A: Check the server status.

[0123] Atomic operation B: Backup configuration files.

[0124] Atomic operation C: Update software version.

[0125] Furthermore, the execution process of each atomic operation will be detailedly recorded, including operation time, executor, input parameters, output results, error information. These logs not only help in problem troubleshooting but also can be used as an audit basis.

[0126] S03: According to the preset event-driven architecture, distribute the execution process to the adapter cluster, so that the adapter cluster generates each standardized instruction according to the atomic operation sequence, and outputs each standardized instruction to the interfaces of each target platform through a preset protocol conversion module.

[0127] As a preferred embodiment of Embodiment 1, the distributing the execution process to the adapter cluster according to the preset event-driven architecture, so that the adapter cluster generates each standardized instruction according to the atomic operation sequence, and outputs each standardized instruction to the interfaces of each target platform through a preset protocol conversion module is specifically:

[0128] To adapt to different heterogeneous resource management platforms (such as Alibaba IaaS+, VMware, Huawei FusionCompute, etc.), first abstract the functions of these platforms and define a set of general resource management interfaces. For example:

[0129] Compute resources: Create / delete virtual machines, adjust instance specifications.

[0130] Storage resources: Mount / dismount object storage or block storage.

[0131] Network resources: Configure subnets, security group rules.

[0132] Database resources: Create / delete database instances, backup and recovery.

[0133] The specific implementation details of each heterogeneous platform are encapsulated in the adapter layer, and the upper-layer process engine only needs to call the unified abstract interface.

[0134] Special adapter modules are developed for each heterogeneous resource management platform, responsible for translating the instructions of the process engine into API calls of the specific platform. The core functions of the adapter include:

[0135] Protocol conversion: Convert the standard instructions of the process engine into the API request format specific to the platform.

[0136] Error mapping: Standardize the error information returned by the platform for unified processing.

[0137] Status synchronization: Regularly obtain the resource status from the platform and feedback it to the process engine.

[0138] For example: For Alibaba Cloud IaaS+, the adapter will call its OpenAPI to manage ECS instances and RDS databases. For VMware, the adapter may use the vSphere API to operate virtual machines. For Huawei FusionCompute, the adapter interacts through its RESTful API.

[0139] To implement an efficient linkage mechanism, the system adopts an event-driven architecture. When the process engine issues an instruction, the adapter generates corresponding events and pushes them to the message queue Kafka. The specific execution logic is that the downstream automation platform consumes the events and completes the tasks, and calls the downstream heterogeneous resource management platform through the resource management interface according to the input parameters. The advantages of this architecture are: Decoupling, there is no direct dependency between the process engine and the specific resource management platform. High concurrency, multiple heterogeneous platforms can process tasks in parallel. Scalability, adding a new resource management platform only requires developing the corresponding adapter.

[0140] In this preferred embodiment, the present application receives an atomic operation sequence through an adapter cluster, and calls the corresponding adapter module according to the operation type and target platform information, which can accurately convert general atomic operation instructions into standardized instructions adapted to each target platform. This process utilizes a preset protocol conversion module to further adapt the standardized instructions into interface call format instructions recognizable by the target platform, and finally outputs them to the target platform interface. This design not only realizes the unified operation of heterogeneous resource management platforms, but also solves the problem of interface differences between different platforms through standardized instructions and protocol conversion modules, thereby significantly improving the flexibility and automation of resource management. At the same time, this hierarchical adaptation and conversion mechanism enhances the scalability and compatibility of the system. When adding or replacing a resource management platform, only the corresponding adapter module needs to be adjusted without modifying the core process, reducing the development and maintenance costs and improving the overall efficiency and adaptability of the system.

[0141] Furthermore, in order to track the execution status of cross-platform tasks, the system provides comprehensive logging and monitoring functions. These include operation logs that record the operation details of each adapter, including API call parameters and response results. Performance monitoring that statistics metrics such as task execution time and resource utilization. An alert mechanism that when detecting abnormal situations (such as insufficient resources or API timeouts), the system will immediately issue an alert notification.

[0142] In this preferred embodiment, the present application can record the operation logs and resource status change data of the adapter cluster by adopting a preset hierarchical decoupling architecture method. This process not only ensures the transparency and traceability of system operations, but also realizes the centralized monitoring and auditing of the entire resource management process by sending these key data to a preset audit database. Further, by means of a preset visualization interface to display the full-link execution status and exception alert information, the system can provide real-time feedback on the operation progress and potential problems, enabling operation and maintenance personnel to quickly locate and handle abnormal situations. This design significantly improves the operation and maintenance efficiency and reliability of the system, while enhancing the control ability over the resource management process and ensuring the compliance and security of resource operations.

[0143] This application realizes the efficient collection and preliminary processing of user requirements by receiving the standardized resource requests submitted by users and converting them into structured task data. On this basis, a preset process engine is used to parse the structured task data to generate an execution process containing an atomic operation sequence. This process not only ensures the standardization and normalization of task data, but also provides a basis for subsequent automated execution through the definition of the atomic operation sequence. Further, based on the event-driven architecture, the execution process is distributed to the adapter cluster. The adapter cluster generates each standardized instruction according to the atomic operation sequence, and adapts these instructions to the interfaces of different target platforms through the protocol conversion module. This series of designs enables this application to achieve the automation and unified management of cross-platform resource operations. This application effectively solves the problem that the prior art cannot efficiently manage heterogeneous resources.

[0144] Embodiment 2

[0145] Please refer to Figure 3 , a cloud resource management device provided by an embodiment of this application.

[0146] In this embodiment, the cloud resource management device includes a receiving module 10, an analysis module 20, and an output module 30.

[0147] The cloud resource management of this application depends on the unified operation and maintenance portal. The unified operation and maintenance portal of this application is as shown in the management processes of each platform Figure 2 . The unified operation and maintenance portal serves as the only entry for users to interact with the system. Integrate user identity authentication and permission management functions in the portal to ensure that different users can only access the resources and services within their permissions. Provide a user-friendly interface to support operations such as users submitting resource requests and operation and maintenance transaction requests.

[0148] The receiving module 10 is used to receive the standardized resource requests submitted by users.

[0149] As a preferred embodiment of Embodiment 2, the receiving the standardized resource requests submitted by users is specifically:

[0150] Receive the initial resource requests submitted by users;

[0151] According to the initial resource requests, the roles of the users, the preset various form types, and the preset historical form library, construct the standardized resource form of the users;

[0152] Identify the standardized resource form to obtain the standardized resource requests.

[0153] More specifically, collect user context information. When the user opens the form page, the system automatically collects the following context information. Among them, it includes:

[0154] User role: Obtained through the permission management module.

[0155] Form type: The form type selected by the user.

[0156] Current resource status: Obtain relevant information (such as the applied application system, project, etc.) from the CMDB or other resource management systems.

[0157] Query the historical form library and retrieve eligible records from the historical form library according to the user role and form type. The retrieval logic includes:

[0158] Filter by user ID: Only retrieve the historical records of the current user. If the current user has no historical records, then obtain the historical records according to the current user role.

[0159] Filter by form type: Only retrieve records related to the current form type.

[0160] Sort by time: Prefer to select the most recent operation record.

[0161] Based on the matched historical records, automatically generate an initial form. The specific process is as follows:

[0162] Map the field values in the historical records to the corresponding fields in the new form.

[0163] Adjust some field values according to the current context information. If the currently submitted application system is different from the historical records, then the fields related to the application system. If the user role changes, then adjust the default permission configuration.

[0164] Pre-fill the common field values in the historical records into the new form.

[0165] The generated form will be displayed to the user, and the user can modify the pre-filled content according to actual needs. Adjust the instance specifications or storage capacity. Add new tags or descriptive information.

[0166] When the user completes the form filling and submission, the system will save the data of the new form to the historical form library for future reference.

[0167] Furthermore, in the resource application module, an intelligent form generation function is implemented. According to the user role and form type, it matches the historical form library, and automatically generates a form based on the most recent historical operation record in the historical library table, pre-fills the form information, and reduces the user's input workload.

[0168] In this preferred embodiment, the present application constructs a standardized resource form by receiving the initial resource request submitted by the user and combining the user role, the preset form type, and the historical form library. The present application can generate personalized resource application forms for different users. This process not only reduces the repetitive work of users when filling out applications, but also ensures the standardization and consistency of resource requests through standardized forms. Further, the standardized resource form is identified to obtain a normalized resource request, which ensures that the system can accurately parse the true needs of users and provides high-quality input data for subsequent automated processing and resource allocation. This processing flow from the initial request to the normalized request significantly improves the user experience, improves the efficiency and accuracy of resource applications, and at the same time lays a solid foundation for realizing end-to-end automated resource management.

[0169] As a preferred embodiment of the second embodiment, after receiving the initial resource request submitted by the user, it further includes:

[0170] Performing authentication management on the initial resource request according to a preset multi-factor authentication module;

[0171] Among them, the multi-factor authentication module includes one or more combinations of the following: SMS authentication, single sign-on authentication, LDAP authentication, or local user authentication;

[0172] Adjusting the initial resource request permission of the user according to the user department information and user permission configuration in the preset CMDB module.

[0173] More specifically, the preset CMDB module is in the preset permission management module. The permission management module supports the dynamic permission adjustment function and supports rule-based permission changes; this module is connected to the CMDB configuration data, and according to the user's department and team, automatically grants the user the application permission and approval permission for different resources. At the same time, according to the configuration information, different resources can only be operated during certain time periods;

[0174] The permission management module realizes the connection with the CMDB data and rule-based permission changes according to the following steps:

[0175] (1) Rule definition and matching, rule creation, defining permission change rules according to business requirements. For example: "When a user belongs to the R & D department, grant the permission to apply for test environment resources."

[0176] Rule engine matching, the permission management module regularly scans the resource configuration and user information in the CMDB through the rule engine, matches the users or resources that meet the rules, and grants the resources that the user can apply for and operate.

[0177] (2) Connect with CMDB data and synchronize user information: Obtain organizational structure information such as the departments and teams of users from CMDB. Synchronize resource information: Obtain the attributes, status, and ownership information of resources (such as the projects to which resources belong and dependencies) from CMDB. Event monitoring: Real-time capture changes in users or resources (such as a user transferring departments or a resource status change) by subscribing to the event notification mechanism of CMDB.

[0178] (3) Automatically grant permissions. Application permission granting: Automatically assign the application permissions for specific resources according to the department and team information of the user. For example, users in the R & D center can apply for test environment resources. Users in the operation and maintenance center can apply for production environment resources. Approval permission granting: Assign approval permissions to team leaders or specific roles. For example, team leaders can approve resource applications submitted by members of their own teams.

[0179] (4) Time limit configuration. Time period definition: Configure the operable time period of resources in CMDB. For example, production environment resources are only allowed to be operated during the maintenance window (such as 2:00 - 4:00 in the early morning). Permission adjustment: The permission management module dynamically adjusts the user's operation permissions according to the current time and the configured time period. If it is not within the allowed time period, the relevant permissions are automatically disabled.

[0180] (5) Permission update and synchronization. Permission calculation: Calculate the user's final permissions according to the rule matching results and time limit configuration. Permission update: Apply the calculation results to the permission management system, update the user's permission configuration, and synchronize the modification.

[0181] In this preferred embodiment, after receiving the initial resource request submitted by the user, the present application introduces a multi-factor authentication module, which can strictly verify the user's identity to ensure that only authorized users can submit resource requests. The multi-factor authentication module supports multiple authentication methods (such as SMS authentication, single sign-on authentication, LDAP authentication, or local user authentication). This diverse authentication method not only improves the security of the system but also meets the scenarios of different user environments and security requirements, enhancing the applicability and flexibility of the system. Further, in combination with the user department information and user permission configuration in the CMDB module, the system can dynamically adjust the initial resource request permissions of users. This mechanism ensures that users can only request resources within their permission scope, thus effectively preventing unauthorized operations and enhancing the security and compliance of resource management.

[0182] The parsing module 20 is used to convert the resource request into structured task data, and parse the structured task data according to a preset process engine to generate an execution process containing an atomic operation sequence.

[0183] As a preferred embodiment of the second embodiment, the conversion of the resource request into structured task data and the parsing of the structured task data according to a preset process engine to generate an execution process including an atomic operation sequence are specifically as follows: Through the process engine of the process platform, the structured data of the user requirements is processed and transferred. The process engine automatically triggers corresponding business processes according to the demand type and drives the automation platform to execute subsequent operations. During the process transfer, the status and operation logs of each step are recorded in real time to ensure the traceability of the process.

[0184] The process engine is located between the user form and the automation platform. As a bridge connecting the user interface and the underlying automation platform, its main responsibilities include receiving requests from the user interface or API gateway, parsing user requirements and generating structured data, calling atomic operations to complete specific tasks, monitoring the task execution status and feeding back results.

[0185] The process engine converts user requirements into structured data through the following steps:

[0186] User requirements can be submitted in JSON format task descriptions by the front-end calling the RESTful API method.

[0187] After receiving the user input, the process engine will convert it into structured data through the following steps:

[0188] Syntax parsing: For inputs in formats such as JSON, directly parse them into key-value pair structures.

[0189] Parameter mapping: Map the parameters provided by the user to the standard fields inside the system.

[0190] User requirements are converted into structured data and represented in JSON format. These data include the following contents:

[0191] Task type: Such as creating a virtual machine, creating a database user, etc.

[0192] Target resource: The specific resource to be operated on (such as host IP, storage path).

[0193] Operation parameters: The detailed parameters required to execute the task (such as the number of CPU cores, memory size).

[0194] Dependency relationship: The sequence or conditional constraints between tasks.

[0195] The generated structured data will be used in the following aspects:

[0196] Atomic operation call: Decompose the task into a series of atomic operations and pass parameters.

[0197] Status tracking: Record the execution status of each task for easy monitoring and rollback.

[0198] Logging: Save the complete execution history of tasks for auditing and problem troubleshooting.

[0199] Implementation method of the atomic operation: An atomic operation is an indivisible basic operation and maintenance task unit. Through in-depth analysis of the operation and maintenance scenarios, common operation and maintenance tasks are decomposed into a series of basic operations, such as service start / stop, software installation, log collection, configuration file modification, etc.

[0200] Each atomic operation is usually implemented in the form of a script or tool. These scripts are based on Shell / Python / PowerShell, used to execute operating system-level commands, and can be distributed to the managed operating systems in the way of ANT. In addition, it can also be based on API calls to complete specific tasks (such as cloud service management) by calling the APIs of external services. Each script or tool will undergo strict testing to ensure its stable function and easy expansion.

[0201] A unified interface specification is defined for each atomic operation. These interfaces include input parameters: clearly define the parameters that need to be provided (such as target host, path, username, etc.).

[0202] Output result: Return the status code, log information or other result data of the operation.

[0203] Error handling: Define the behavior in case of exceptions, such as retry mechanism or rollback strategy.

[0204] Through the unified interface, users can easily combine different atomic operations into complex operation and maintenance processes.

[0205] Integrated into the workflow engine introduced above, allowing multiple atomic operations to be concatenated to form complex operation and maintenance tasks, and custom workflows can be quickly built and executed automatically. For example:

[0206] Atomic operation A: Check the server status.

[0207] Atomic operation B: Backup the configuration file.

[0208] Atomic operation C: Update the software version.

[0209] Furthermore, the execution process of each atomic operation will be detailedly recorded, including operation time, executor, input parameters, output results, error information. These logs not only help with problem troubleshooting but also can be used as the basis for auditing.

[0210] The output module 30 is used to distribute the execution process to the adapter cluster according to a preset event-driven architecture, so that the adapter cluster generates each standardized instruction according to the atomic operation sequence, and outputs each standardized instruction to the interfaces of each target platform through a preset protocol conversion module.

[0211] As a preferred embodiment of Embodiment 2, the distributing the execution process to the adapter cluster according to a preset event-driven architecture, so that the adapter cluster generates each standardized instruction according to the atomic operation sequence, and outputs each standardized instruction to the interfaces of each target platform through a preset protocol conversion module is specifically as follows:

[0212] In order to adapt to different heterogeneous resource management platforms (such as Alibaba IaaS+, VMware, Huawei FusionCompute, etc.), first, the functions of these platforms are abstracted, and a set of general resource management interfaces are defined. For example:

[0213] Computing resources: Create / delete virtual machines, adjust instance specifications.

[0214] Storage resources: Mount / dismount object storage or block storage.

[0215] Network resources: Configure subnets, security group rules.

[0216] Database resources: Create / delete database instances, backup and recovery.

[0217] The specific implementation details of each heterogeneous platform are encapsulated in the adapter layer, and the upper-layer process engine only needs to call the unified abstract interface.

[0218] Special adapter modules are developed for each heterogeneous resource management platform, which are responsible for translating the instructions of the process engine into API calls of specific platforms. The core functions of the adapter include:

[0219] Protocol conversion: Convert the standard instructions of the process engine into the API request format specific to the platform.

[0220] Error mapping: Standardize the error information returned by the platform for unified processing.

[0221] Status synchronization: Regularly obtain the resource status from the platform and feedback it to the process engine.

[0222] For example: For Alibaba Cloud IaaS+, the adapter will call its OpenAPI to manage ECS instances and RDS databases. For VMware, the adapter may use the vSphere API to operate virtual machines. For Huawei FusionCompute, the adapter interacts through its RESTful API.

[0223] To achieve an efficient linkage mechanism, the system adopts an event-driven architecture. When the process engine issues an instruction, the adapter generates corresponding events and pushes them to the message queue Kafka. The specific execution logic is that the downstream automation platform consumes the events and completes the tasks, and through the resource management interface, calls the downstream heterogeneous resource management platform according to the input parameters. The advantages of this architecture are: decoupling, there is no direct dependence between the process engine and the specific resource management platform; high concurrency, multiple heterogeneous platforms can process tasks in parallel; scalability, adding a new resource management platform only requires developing the corresponding adapter.

[0224] In this preferred embodiment, the present application receives the atomic operation sequence through the adapter cluster and calls the corresponding adapter module according to the operation type and target platform information, and can accurately convert the general atomic operation instruction into a standardized instruction adapted to each target platform. This process uses a preset protocol conversion module to further adapt the standardized instruction into an interface call format instruction recognizable by the target platform, and finally outputs it to the target platform interface. This design not only realizes the unified operation of the heterogeneous resource management platform, but also solves the problem of interface differences between different platforms through the standardized instruction and the protocol conversion module, thus significantly improving the flexibility and automation degree of resource management. At the same time, this hierarchical adaptation and conversion mechanism enhances the scalability and compatibility of the system, so that when adding or replacing a resource management platform, only the corresponding adapter module needs to be adjusted, without modifying the core process, reducing the development and maintenance costs, and improving the overall efficiency and adaptability of the system.

[0225] Furthermore, to track the execution status of cross-platform tasks, the system provides comprehensive logging and monitoring functions. These include operation logs, which record the operation details of each adapter, including API call parameters and response results; performance monitoring, which statistics indicators such as task execution time and resource utilization rate; and an alarm mechanism, when detecting abnormal situations (such as insufficient resources or API timeout), the system will immediately send an alarm notification.

[0226] In this preferred embodiment, the present application can record the operation logs of the adapter cluster and the resource status change data by adopting a preset hierarchical decoupling architecture method. This process not only ensures the transparency and traceability of system operations, but also realizes the centralized monitoring and auditing of the entire process of resource management by sending these key data to a preset audit database. Further, by means of a preset visual interface to display the full-link execution status and abnormal alarm information, the system can provide real-time feedback on the operation progress and potential problems, enabling operation and maintenance personnel to quickly locate and handle abnormal situations. This design significantly improves the operation and maintenance efficiency and reliability of the system, while enhancing the control ability of the resource management process, ensuring the compliance and security of resource operations.

[0227] This device uses three modules to divide labor and work in coordination, which can manage cloud resources more efficiently. This application realizes the efficient collection and preliminary processing of user requirements by receiving the standardized resource requests submitted by users and converting them into structured task data. On this basis, a preset process engine is used to parse the structured task data to generate an execution process containing an atomic operation sequence. This process not only ensures the standardization and normalization of task data, but also provides a basis for subsequent automated execution through the definition of the atomic operation sequence. Further, based on the event-driven architecture, the execution process is distributed to the adapter cluster. The adapter cluster generates each standardized instruction according to the atomic operation sequence, and adapts these instructions to the interfaces of different target platforms through the protocol conversion module. This series of designs enables this application to achieve the automation and unified management of cross-platform resource operations. This application effectively solves the problem that the prior art cannot efficiently manage heterogeneous resources.

[0228] Embodiment Three:

[0229] An embodiment of this application provides a computer-readable storage medium, where the computer-readable storage medium includes a stored computer program. Among them, when the computer program runs, it controls the device where the computer-readable storage medium is located to execute the described cloud resource management method;

[0230] Among them, for the described cloud resource management method, if it is implemented in the form of a software functional unit and used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, to implement all or part of the processes in the above embodiment methods of the present invention, it can also be completed by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement the steps of the above various method embodiments. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable medium can include: any entity or device that can carry the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electrical carrier signal, telecommunication signal, and software distribution medium, etc.

[0231] Embodiment Four

[0232] The present application provides a terminal device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, any one of the cloud resource management methods described in Embodiment 1 is implemented.

[0233] In the above specific embodiments, the purpose, technical solution, and beneficial effects of the present invention have been further described in detail. It should be understood that the above are only specific embodiments of the present invention and are not used to limit the protection scope of the present invention. In particular, for those skilled in the art, any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A cloud resource management method, characterized in that: include: Receive normalized resource requests submitted by users; Convert the resource request into structured task data, and parse the structured task data according to a preset process engine to generate an execution process including an atomic operation sequence; According to a preset event-driven architecture, the execution process is distributed to an adapter cluster, so that the adapter cluster generates various standardized instructions according to the atomic operation sequence, and outputs the various standardized instructions to the interface of each target platform through a preset protocol conversion module.

2. The cloud resource management method according to claim 1, characterized in that: The receiving of the normalized resource request submitted by the user is specifically: Receive initial resource requests submitted by users; Constructing a standardized resource form for the user according to the initial resource request, the role of the user, various preset form types, and a preset historical form library; The standardized resource form is identified to obtain a standardized resource request.

3. The cloud resource management method according to claim 1, characterized in that: After receiving the initial resource request submitted by the user, the method further includes: Performing authentication management on the initial resource request according to a preset multi-factor authentication module; Wherein, the multi-factor authentication module includes one or more combinations of the following: SMS authentication, single sign-on authentication, LDAP authentication or local user authentication; According to the user department information and user authority configuration in the preset CMDB module, the initial resource request authority of the user is adjusted.

4. The cloud resource management method according to claim 1, characterized in that: The adapter cluster generates each standardized instruction according to the atomic operation sequence, and outputs each standardized instruction to the interface of each target platform through a preset protocol conversion module, specifically: The adapter cluster receives the atomic operation sequence, and calls each adapter module according to the operation type in the atomic operation sequence and each target platform information; According to each adapter module, converting the operation instructions in the atomic operation sequence into each standardized instruction of each target platform; According to the preset protocol conversion module and the interface specifications of each target platform, the standardized instructions are converted into interface call format instructions recognizable by each target platform; Output the converted interface call format instructions to the interfaces of each target platform.

5. The cloud resource management method according to any one of claims 1 to 4, characterized in that: Also includes: According to a preset layered decoupling architecture method, recording the operation log and resource status change data of the adapter cluster; The operation log and resource status change data are sent to the preset audit database, and the full-link execution status and abnormal alarm information are displayed through a preset visual interface.

6. A cloud resource management device, characterized in that: include: Receiving module, parsing module and output module; The receiving module is used to receive the normalized resource request submitted by the user; The parsing module is used to convert the resource request into structured task data, and parse the structured task data according to a preset process engine to generate an execution process including an atomic operation sequence; The output module is used to distribute the execution process to the adapter cluster according to the preset event-driven architecture, so that the adapter cluster generates various standardized instructions according to the atomic operation sequence, and outputs the various standardized instructions to the interface of each target platform through the preset protocol conversion module.

7. The cloud resource management device according to claim 6, characterized in that: The receiving module includes: a receiving unit, a building unit and an acquiring unit; The receiving unit is used to receive an initial resource request submitted by a user; The construction unit is used to construct a standardized resource form for the user according to the initial resource request, the role of the user, various preset form types and a preset historical form library; The acquisition unit is used to identify the standardized resource form and acquire a standardized resource request.

8. The cloud resource management device according to claim 6, characterized in that: The adapter cluster generates each standardized instruction according to the atomic operation sequence, and outputs each standardized instruction to the interface of each target platform through a preset protocol conversion module, specifically: The adapter cluster receives the atomic operation sequence, and calls each adapter module according to the operation type in the sequence and each target platform information; According to each adapter module, converting the operation instructions in the atomic operation sequence into each standardized instruction of each target platform; According to the preset protocol conversion module and the interface specifications of each target platform, the standardized instructions are converted into an interface call format recognizable by each target platform; Output the converted interface call format to the interface of each target platform.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the cloud resource management method according to any one of claims 1 to 5.

10. A terminal device, characterized in that: The method comprises a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor implements the cloud resource management method according to any one of claims 1 to 5 when executing the computer program.

Images