Resource management platform and management method

Abstract

The invention belongs to the technical field, and particularly relates to a resource management platform and management method.The resource management platform comprises an automatic operation and maintenance platform and a multi-cloud system resource pool, and the automatic operation and maintenance platform is connected with the multi-cloud system resource pool; the multi-cloud configuration has a multi-cloud system resource synchronization function and is used for synchronizing resources of different cloud platforms and different cloud accounts to the local to construct a unified data model; the relation management function is used for carrying out resource division on all resource data synchronized from a plurality of different cloud platforms, wherein the resource division comprises management of a position relation, a service relation and a label relation; the resource management function is used for being responsible for resource query display and resource and relation management in the multi-cloud system. According to the invention, the problem of resource dispersion in a multi-cloud environment can be solved, a user can quickly locate the related information of the position of the resource, and the resource data can be divided and managed.

Description

Technical Field

[0001] The present invention belongs to the technical field of resource management systems, and in particular relates to a resource management platform and a management method. Background Art

[0002] The resource management platform is a comprehensive system for centralized management and optimization of various IT resources, aiming to uniformly manage and allocate various resources of an enterprise or organization. It provides a centralized way to monitor, control and optimize the use of resources to improve resource utilization, reduce costs and ensure business continuity. As an important part of modern enterprise management, the resource management platform greatly improves the resource utilization and management efficiency of enterprises by providing comprehensive resource monitoring, scheduling, automated management, cost control and security functions.

[0003] Defects corresponding to the resource management system:

[0004] 1. Resource Dispersion and Security

[0005] In a multi-cloud environment, resources on different cloud platforms are scattered, making it difficult to quickly obtain the required resource information;

[0006] Resource security is poor. Users can obtain resources from multiple projects, which makes resource security poor and easily leads to confusion among resources of different projects.

[0007] 2. Insufficient location relationship management

[0008] The lack of records of resource location relationships is not conducive to retrieval, and there are management issues with poor resource location information, which makes it difficult for users to locate relevant information about resource locations. There is also the problem of being unable to uniformly operate specific hosts across business environments;

[0009] 3. Resource query, display and management

[0010] Resource data synchronized from multiple cloud platforms is not divided and managed, making it impossible to operate on different types of resources. Summary of the invention

[0011] The purpose of the present invention is to provide a resource management platform and management method, which can solve the problem of resource dispersion in a multi-cloud environment, facilitate users to quickly locate relevant information about the location of resources, and at the same time divide and manage resource data.

[0012] The technical solution adopted by the present invention is as follows:

[0013] A resource management platform, comprising:

[0014] Automated operation and maintenance platform and multi-cloud system resource pool:

[0015] The automated operation and maintenance platform is connected to the multi-cloud system resource pool, and the basic data required for the upper-layer business depends on the acquisition of the multi-cloud system resource pool;

[0016] When the underlying multi-cloud system resource pool is modified, the related monitoring, host, operation and other host-related information can be updated synchronously;

[0017] Multi-cloud configuration:

[0018] The multi-cloud configuration has a multi-cloud system resource synchronization function, which is used to synchronize resources under different cloud accounts on different cloud platforms to the local computer to build a unified data model;

[0019] Relationship management features:

[0020] The relationship management function is used to divide resources from all resource data synchronized from multiple different cloud platforms, including the management of location relationships, business relationships, and tag relationships;

[0021] Synchronous log module:

[0022] The synchronization log module is used to record the synchronization information, synchronization status and synchronization details of all resource points;

[0023] Resource management functions:

[0024] The resource management function is responsible for querying and displaying resources and managing resources and relationships in a multi-cloud system. Resources in a resource pool have no relationship attributes, and users can only view resources under their own projects. By default, resources in a resource pool are searched through global search, dynamic rules, and resource list operations related to adding resources.

[0025] The upper-level business includes publishing systems, building monitoring dashboards, and daily operations;

[0026] The host data required for the release system is obtained from the multi-cloud system resource pool;

[0027] The host data for building the monitoring dashboard is obtained from the multi-cloud system resource pool;

[0028] The target host selected for daily operations is obtained from the multi-cloud system resource pool;

[0029] The data required for project cost calculation and resource reduction is obtained from the multi-cloud system resource pool;

[0030] The strong dependency model ensures data accuracy and ensures that the basic data obtained by the upper-level business is consistent with the data in the multi-cloud system resource pool.

[0031] The multi-cloud configuration obtains cloud resource data through SDK / API of different cloud vendors and places it in a resource pool, so as to enable upper-layer services and external APIs to be processed based on a unified data model, provide a unified data format, and support automatic resource synchronization and manual resource synchronization.

[0032] Automatic resource synchronization: after adding a cloud account, the operation and maintenance platform will automatically synchronize resources with the cloud platform, and the synchronization period can be customized by the user. It also supports temporary closure of the synchronization task by changing the automatic synchronization interval to 0 or selecting the corresponding task on the queue status page to close the synchronization. View all scheduled tasks on the queue status page.

[0033] Manual resource synchronization is to synchronize a resource type under a single cloud account separately in the operation and maintenance platform. All synchronization processes of all resources are viewed through log records. At the same time, the synchronization status of specific resources and specific status of specific vendors can be filtered according to cloud vendors, resource types and synchronization status.

[0034] In terms of location relationship management, the location, as the location of the resource, is fixed and is generated when the asset is created. The platform only needs to record it for retrieval;

[0035] The business relationship management aspect is used to retrieve resources based on business. The business relationship is constructed as a tree structure. It is recommended to construct the business relationship according to the architecture of project (root directory) → environment (formal / test) → cluster → module to realize classified retrieval and management of resources.

[0036] The tag relationship management aspect is used to search hosts across businesses, thereby achieving unified search and related operation execution of specific resources in different business environments.

[0037] When viewing synchronization logs, you can filter based on cloud accounts to view only the synchronization information of a specified cloud account.

[0038] When viewing synchronization logs, you can filter based on cloud resources to view only the synchronization information of specified cloud resources.

[0039] When viewing the synchronization log, you can filter based on the synchronization status, including failure, success, and in progress.

[0040] The global search function retrieves matching items from all resources based on keywords. Since resources from various cloud platforms are integrated, inputting a single IP address can search for corresponding hosts from different cloud platforms.

[0041] The resource list function is designed to provide clear, accurate and easy-to-use resource data. It builds clear resource data through association relationships. The resource list is based on business relationship display. By default, all resources under the business are displayed. Click on the relationship tree node to view the resources under the corresponding node. It also provides classification and fuzzy search.

[0042] There are two ways to add resources under the node: one is to add the required resources and tag them through the add button on the resource list page, and only one can be added at a time; the other is to add resources in batches with the help of dynamic rules;

[0043] Edit and delete resources in the resource list. Since resource attributes are synchronized from the cloud and fixed, only resource business attributes and tags can be edited. When resources go offline, they are not directly deleted from the resource list but marked as expired. Users need to delete them manually to ensure resource accuracy.

[0044] The dynamic rule function matches the corresponding resources in the resource pool according to the defined rules and labels these resources or adds business relationships. The three elements that constitute the dynamic rules are the resource pool, rules and operations. The dynamic rules do not take effect immediately after they are added. You must first confirm whether the resources matched by the rules meet your expectations. If the resource naming is not standardized, unexpected resources may be matched. There is a refresh button on the rule list page. After clicking refresh, the matched resources will be retrieved first, and the rules will be applied after confirming that they meet your expectations.

[0045] The resources in the resource pool have no business relationship. If a resource belongs to a business, it will be kicked out of the resource pool. The dynamic rule only matches resources that have no business relationship.

[0046] The rule is a condition for matching resources in the resource pool, which mainly includes the resource type to be matched, the field of the resource to be matched, the matching operator, and the matching content body;

[0047] There are two main operations, namely tagging resources and adding business relationships to resources.

[0048] A resource management method, the specific steps are as follows:

[0049] Step 1: When the basic resources of the project change, update the data in the multi-cloud system resource pool in a timely manner; when the underlying multi-cloud system resource pool is modified, trigger the relevant mechanism to synchronize the corresponding monitoring, host, job and other information;

[0050] Step 2: Support viewing synchronization details, which at least include synchronization information, synchronization status and synchronization details of resource points;

[0051] Step 3: During resource synchronization, the resource data of the corresponding cloud platform is obtained by calling the SDK / API of different cloud vendors and stored in the resource pool to synchronize the multi-cloud system resources to the local to build a unified data model, so that the upper-layer business and external API can process based on the unified data model and output a unified and clear data format;

[0052] Step 3.1: Automatic resource synchronization stage. After adding the cloud account, the operation and maintenance platform will automatically synchronize cloud platform resources. The synchronization period can be defined by the user. If you need to temporarily stop the synchronization task, set the automatic synchronization interval to 0 or close the synchronization of the corresponding task on the queue status page. You can also view all scheduled tasks on the queue status page.

[0053] Step 3.2: When synchronizing resources manually, a separate synchronization operation is performed on a certain resource type of a single cloud account under multiple cloud platform accounts in the operation and maintenance platform. Detailed log records are available for viewing during the entire resource synchronization process. At the same time, the synchronization details of a specific vendor, specific resource, or specific status can be filtered based on the cloud vendor, resource type, and synchronization status.

[0054] Step 4: When managing all resource data synchronized across multiple cloud platforms, record the location of resources through location relationship management for easy retrieval; implement business-based resource retrieval by building a tree-like business relationship of project (root directory) → environment (official / test) → cluster → module; implement cross-business retrieval of hosts and execute corresponding tasks through tag relationship management;

[0055] Step 5: When managing resources in a multi-cloud system, use the resource pool to store synchronized resources on the cloud. Users can view resources in isolation by project, retrieve resources across cloud platforms through global search, add resources with the help of the add button on the resource list page or dynamic rules, and edit and delete resources in the resource list. At the same time, dynamic rules are used to match resources in the resource pool according to defined conditions and perform corresponding operations. After the dynamic rules are added, they must be confirmed that the matching resources meet expectations before they take effect.

[0056] A computer-readable storage medium stores a computer program, and the computer program implements a resource management method when executed by a processor.

[0057] A computer program product comprises a computer program, wherein the computer program implements a resource management method when executed by a processor.

[0058] The technical effects achieved by the present invention are:

[0059] (1) The present invention solves the problem of resource dispersion in a multi-cloud environment, synchronizes resources from different cloud platforms to a resource pool, and implements unified management; ensures that users can only view resources under their own projects, ensures the security and isolation of resource access, and avoids confusion of resources between different projects; provides a global search function, which facilitates users to quickly locate specific resources from a large number of synchronized resources; provides two ways to add resources: an add button on the resource list page and a dynamic rule, to meet the different needs of users for adding single resources and adding batches of resources; stipulates that after resources go offline, they are only marked as expired and need to be manually deleted to prevent accidental deletion of important resources, and at the same time clearly states that only business attributes and tags can be edited to ensure the stability of key resource attributes; solves the risk that dynamic rules may take effect immediately after being added, and ensures the accuracy of rule application by first searching for matching resources and then confirming whether the rules are applied.

[0060] (2) The present invention solves the problem of resource location information management by recording resource location relationships to facilitate retrieval and enable users to quickly locate information related to the location of resources; constructs a tree-like business relationship for business-based resource retrieval to solve the problem of resource classification retrieval and make resource management more in line with business logic; implements cross-business retrieval of hosts and batch executes commands through tags to solve the problem of unified operation of specific hosts in cross-business environments, such as checking the openness of ports.

[0061] (3) The present invention can divide and manage resource data synchronized from multiple cloud platforms, solve the problem of resource classification management, and facilitate the management and operation of different types of resources; it is clear that the location relationship is generated and fixed when the asset is created, and no additional management is required, which solves the problem of unnecessary operational burden in location relationship management; it is recommended to build business relationships according to project-environment-cluster-module, solve the standardization problem of business relationship construction, and make resource management more orderly; it realizes cross-business host retrieval and task execution through label relationships, and solves the problem of unified management and operation of resources in cross-business environments.

[0062] (4) The present invention solves the core issues of resource management in a multi-cloud environment, including resource presentation and relationship maintenance, by querying and displaying resources in a multi-cloud system and managing resources and relationships. It realizes searching and matching resources in all resources based on keywords, solving the problem of quickly locating resources in the integrated multi-cloud resources. It provides operations such as adding, editing, and deleting resources, solving the problems of adding resources individually and in batches, editing resource attributes, and processing resources offline, thereby ensuring the accuracy of resource data. It solves the problems of batch resource management and dynamic adjustment of business relationships by defining rules to match resources and tag or add business relationships, while avoiding incorrect application of rules through a rule confirmation mechanism. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1is a schematic diagram of location relationship management in relationship management provided by an embodiment of the present invention;

[0064] Figure 2 is a schematic diagram of business relationship management in the relationship management provided by an embodiment of the present invention;

[0065] Figure 3 is a schematic diagram of tag relationship management in the relationship management provided by an embodiment of the present invention;

[0066] Figure 4 It is a schematic diagram of synchronizing resources on a resource pool cloud provided by an embodiment of the present invention;

[0067] Figure 5 This is a display diagram of a global search interface provided by an embodiment of the present invention;

[0068] Figure 6 It is an interface display diagram of resource relationships in a resource list provided by an embodiment of the present invention;

[0069] Figure 7 This is an interface display diagram for adding resources under a node provided by an embodiment of the present invention;

[0070] Figure 8 is a flow chart of performing relationship matching using dynamic rules provided by an embodiment of the present invention;

[0071] Fig. 9 This is a diagram showing an operation interface for labeling resources and adding business relationships provided by an embodiment of the present invention;

[0072] Fig.10 is a display diagram of a dynamic rule management interface provided by an embodiment of the present invention;

[0073] Fig.11 It is a display diagram of the dynamic rule refresh interface provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0074] In order to make the purpose and advantages of the present invention more clearly understood, the present invention is specifically described below in conjunction with embodiments. It should be understood that the following text is only used to describe one or several specific embodiments of the present invention, and does not strictly limit the scope of protection of the specific claims of the present invention.

[0075] like Figure 1-Figure 11 As shown, a resource management platform includes:

[0076] Automated operation and maintenance platform and multi-cloud system resource pool:

[0077] The automated operation and maintenance platform is connected to the multi-cloud system resource pool. As the basic resource database, the most important thing for the multi-cloud system resource pool is to ensure the accuracy of the data. To achieve this goal, we adopted a strong dependency model to ensure the accuracy of the data and ensure that the basic data obtained by the upper-level business is consistent with the data in the multi-cloud system resource pool.

[0078] The upper-level business includes publishing systems, building monitoring dashboards, and daily operation tasks. The basic data required by the upper-level business depends on the multi-cloud system resource pool. For example, the host data required for publishing the system is obtained from the multi-cloud system resource pool; the host data for building the monitoring dashboard is obtained from the multi-cloud system resource pool; the target host selected for daily operations is obtained from the multi-cloud system resource pool; the data required for project cost calculation and resource reduction is obtained from the multi-cloud system resource pool;

[0079] When the underlying multi-cloud system resource pool is modified, the related monitoring, host, operation and other host-related information can be updated synchronously.

[0080] According to the above content, all operations on the host depend on the multi-cloud system resource pool. A series of strong dependencies ensure that everyone will update the multi-cloud data in time when the basic resources of the project change. When our underlying multi-cloud system resource pool is modified, the corresponding host-related monitoring, host, job, etc. will be updated synchronously;

[0081] The resource pool includes resources such as servers, databases, and load balancing. These are all synchronized from the cloud platform to the resource pool. After that, our monitoring, tasks, jobs, and other operations will all rely on the resources in these resource pools.

[0082] Multi-cloud configuration:

[0083] Multi-cloud configuration has the function of synchronizing multi-cloud system resources, which is used to synchronize resources under different cloud accounts on different cloud platforms to the local computer to build a unified data model;

[0084] Multi-cloud configuration obtains cloud resource data through SDK / API of different cloud vendors and places it in the resource pool, so that upper-layer services and external APIs can be processed based on a unified data model and provide a unified data format. Multi-cloud configuration also supports automatic resource synchronization and manual resource synchronization.

[0085] Automatic resource synchronization: after adding a cloud account, the operation and maintenance platform will automatically synchronize resources with the cloud platform, and the synchronization period can be customized by the user. It also supports temporary closure of the synchronization task by changing the automatic synchronization interval to 0 or selecting the corresponding task on the queue status page to close the synchronization. View all scheduled tasks on the queue status page.

[0086] Manual resource synchronization is to synchronize a resource type under a single cloud account separately in the operation and maintenance platform. All synchronization processes of all resources are viewed through log records. At the same time, the synchronization status of specific resources and specific status of specific vendors can be filtered according to cloud vendors, resource types and synchronization status.

[0087] Synchronous log module:

[0088] The synchronization log module is used to record the synchronization information, synchronization status and synchronization details of all resource points;

[0089] When viewing synchronization logs, you can filter based on cloud accounts to view only the synchronization information of a specified cloud account.

[0090] When viewing synchronization logs, you can filter based on cloud resources to view only the synchronization information of specified cloud resources.

[0091] When viewing the synchronization log, you can filter based on the synchronization status, including failure, success, and in progress.

[0092] According to the above content, resource synchronization will synchronize resources under different cloud accounts on different cloud platforms to the local computer for unified data model construction. Both upper-level services and external APIs can be processed based on the unified data model, thus providing a unified and clear data format. The main work in this process is to obtain cloud resource data through the SDK / API of different cloud vendors. The obtained resources belong to the resource pool.

[0093] Automatic resource synchronization operation: Create a new cloud account. The main function of this step is to receive the cloud account-related data entered by the user and then insert it into the database. The cloud account-related data includes name, manufacturer, AccessID, SecretKey, synchronization resource type and synchronization time interval, etc. All information serves to verify the account and synchronize resources. When the cloud account data is saved, the post_save signal will be triggered, and this signal will automatically create a periodic task for resource synchronization. The above is that when we add a cloud account, a periodic task for resource synchronization will be automatically created. That is to say, when the user adds the cloud account, the operation and maintenance platform will automatically synchronize resources with the cloud platform without our management. The synchronization time period is customized by the user. If you want to temporarily close the synchronization task, you can change the automatic synchronization interval to 0, or select the corresponding task on the queue status page to close the synchronization. At the same time, you can view all scheduled tasks on the queue status page.

[0094] Manual resource synchronization operation: Users will synchronize resources under multiple cloud platform accounts on the operation and maintenance platform. In some cases, users only need to synchronize a certain resource type under a certain account. For example, after modifying the resources on the cloud, users want to see the attribute changes of the resources on the platform immediately. In this case, they need to manually synchronize a resource under a certain account. All synchronization processes of all resources can be viewed through detailed log records. Of course, because the synchronization log also records the cloud vendor, resource type and synchronization status, you can also filter and view the synchronization status of specific vendors, specific resources and specific status based on these dimensions.

[0095] Relationship management features:

[0096] The relationship management function is used to divide resources from all resource data synchronized from multiple different cloud platforms, including the management of location relationships, business relationships, and tag relationships;

[0097] In terms of location relationship management, location, as the location of resources, is fixed and is generated when assets are created. The platform only needs to record it for retrieval;

[0098] In terms of business relationship management, it is used to retrieve resources based on business. Business relationships are constructed in a tree structure. It is recommended to construct business relationships according to the architecture of project (root directory) → environment (formal / test) → cluster → module to achieve classified retrieval and management of resources.

[0099] In terms of tag relationship management, it is used to search hosts across businesses, enabling unified search and related operation execution of specific resources in different business environments.

[0100] According to the above content, because the resources themselves are independent, and users may use multiple cloud platforms and multiple cloud products in one project, these resources should appear to be integrated together, so that multi-cloud platforms can be managed more conveniently and clearly;

[0101] The location relationship is the location of the resource, for example, Alibaba Cloud (manufacturer) → Alibaba Cloud Games (account) → Shanghai (region) → Availability Zone F (availability zone). The location relationship is generally fixed and is generated when the asset is created. We do not need to manage it additionally. We only need to record it for easy retrieval. For example, to find all LBs located in Shanghai, please refer to the attached document for details. Figure 1 ;

[0102] Business relationships are the most commonly used in daily work. In most cases, we need to retrieve resources based on business. Some CMDB systems have the concept of service tree, and business relationships are similar to it. Business relationships are usually tree-like. It is recommended to build business relationships based on project (root directory) → environment (formal / test) → cluster → module. For details, please refer to the attached Figure 2 ;

[0103] Although business relationships are very useful, they still have their limitations. For example, if you need to batch execute commands for both the test and formal environments, you need to search for hosts across businesses. Therefore, label relationships come into being. Labels are global and not limited by business. You can label all types of resources. For example, you can add labels based on the system: centos6, centos7, linux, windows, etc., and add labels based on services: nginx, tomcat, php, jdk, nodejs, etc. In this way, you can obtain all resources containing the linux label to execute the task of checking whether port 22 is open. For details, please refer to the attached Figure 3 .

[0104] Resource management functions:

[0105] The resource management function is responsible for querying and displaying resources and managing resources and relationships in a multi-cloud system. Resources in a resource pool have no relationship attributes, and users can only view resources under their own projects. By default, resources in a resource pool are searched through global search, dynamic rules, and resource list operations related to adding resources.

[0106] According to the above content, the resource pool is actually a virtual pool. The resources in the resource pool have no relationship attributes. For details, please refer to the attached Figure 4 Since all resources are isolated based on projects, that is, users can only view resources under their own projects, and cannot view and use resources under projects other than their own, resources in the resource pool cannot be found by default. They can only be found in global search, dynamic rules, and adding resources in the resource list.

[0107] The global search function retrieves matching items from all resources based on keywords. Since the resources of various cloud platforms are integrated, entering a single IP address can find the corresponding host from different cloud platforms.

[0108] According to the above content, global search is to retrieve matches from all resources based on keywords. It is often necessary to query which project a certain IP belongs to, who is maintaining and deploying what service, etc. For details, please refer to the attached Figure 5 When there are few resources, a simple team, and stable operation and maintenance personnel, you may be able to determine the IP ownership by memory. However, when there are many resources and a complex team, it is not easy to quickly locate the IP. At this time, global search is very useful because all cloud platform resources are integrated together. Therefore, by entering a single IP through global search, the host corresponding to this IP address will be found one by one on different cloud platforms.

[0109] The resource list function aims to provide clear, accurate and easy-to-use resource data. It builds clear resource data through association relationships. The resource list is based on business relationship display. By default, all resources under the business are displayed. Click the relationship tree node to view the resources under the corresponding node. It also provides classification and fuzzy search.

[0110] There are two ways to add resources under a node: one is to add the required resources and tag them through the Add button on the resource list page. Only one resource can be added at a time. The other is to add resources in batches using dynamic rules.

[0111] Edit and delete resources in the resource list. Because resource attributes are synchronized from the cloud and fixed, only the business attributes and tags of resources can be edited. When a resource goes offline, it is not directly deleted from the resource list but marked as expired. Users need to delete it manually to ensure resource accuracy.

[0112] According to the above content, the multi-cloud system aims to provide clear, accurate and easy-to-use resource data. Clear resource data can be constructed through association relationships, and the resource list provides an interface display for this clear resource relationship. The three types of multi-cloud association relationships are mentioned in the relationship management function. The resource list is displayed based on the most commonly used business relationships. For details, please refer to the attached Figure 6 , Figure 6 The left side of the diagram shows the business relationship tree, and the right side shows specific resources. By default, all resources under the business are displayed. Clicking a relationship tree node can view the resources under the corresponding node. It also provides classification and fuzzy search to quickly retrieve resource data.

[0113] There are two ways to add resources under a node. Please refer to the attached Figure 7 ;

[0114] Resources can also be edited and deleted in the resource list. Since resource attributes are fixedly synchronized from the cloud, they cannot be modified. Only the business attributes and tags of the resources can be edited. When resources go offline, they are not directly deleted from the resource list. They will be marked as expired and need to be deleted manually by the user. This is to ensure that all resources in the resource list are confirmed and to provide guarantee for the accuracy of the resources.

[0115] The dynamic rule function matches the corresponding resources in the resource pool according to the defined rules and labels these resources or adds business relationships. The three elements that constitute the dynamic rules are the resource pool, rules, and operations. The dynamic rules do not take effect immediately after they are added. You must first confirm whether the resources matched by the rules meet your expectations. If the resource naming is not standardized, unexpected resources may be matched. There is a refresh button on the rule list page. After clicking refresh, the matched resources will be retrieved first, and the rules will be applied after confirming that they meet your expectations.

[0116] According to the above content, resources themselves are independent, but various relationship processing is usually added during use. How to add relationships to resources? In addition to adding / editing resources in the resource list, you can also use dynamic rules. This is also the main method used in daily resource management and maintenance. Dynamic rules are mainly used to add tags or business relationships to resources in the resource pool in batches. For the relationship matching process, please refer to the attached Figure 8 ;

[0117] The resources in the resource pool have no business relationship. If a resource belongs to a business, it will be kicked out of the resource pool. Dynamic rules only match resources that have no business relationship. This is mainly to ensure the accuracy of resource relationships and avoid the situation where the resources confirmed by user A are covered by B's dynamic rules.

[0118] Rules are conditions for matching resources in the resource pool, mainly including the resource type to be matched, the field to be matched, the matching operator and the matching content. The resource types mainly include server, MySQL, etc. Of course, one rule can also match all types of resources. The matching field defaults to the resource name, and matching is based on the resource name. Therefore, this requires users to be standardized when naming resources, otherwise this dynamic rule cannot be matched in batches. There are five main operators supported, namely, containment, equality, starts with..., ends with... and regular matching. Simple naming specifications can be matched through operators such as containment, while regular matching can achieve more complex matching;

[0119] There are two main operations: tagging resources and adding business relationships to resources. For details, please refer to the attached Fig. 9 .

[0120] Dynamic rules do not take effect immediately after they are added. You must first know which resources your rules will match and whether they are consistent with your expectations. If the user's resource naming is not standardized, it is normal for the rules to match resources that do not meet your expectations. Therefore, standardized resource naming is a prerequisite for dynamic rules. For details, please refer to the attached Fig.10 ;

[0121] There is a refresh button on the rule list page. The refresh button is used to apply the rules. When you click refresh, the rules will not be applied immediately. Instead, the matching resources will be retrieved first. If you are sure that the matched resources meet your expectations, you can confirm the application. For details, please refer to the attached Fig.11 .

[0122] For details of the working principle of the present invention, please refer to the resource management method below.

[0123] A resource management method, the specific steps are as follows:

[0124] Step 1: When the basic resources of the project change, update the data in the multi-cloud system resource pool in a timely manner; when the underlying multi-cloud system resource pool is modified, trigger the relevant mechanism to synchronize the corresponding monitoring, host, job and other information;

[0125] Step 2: Support viewing synchronization details, which at least include synchronization information, synchronization status and synchronization details of resource points;

[0126] Step 3: During resource synchronization, the resource data of the corresponding cloud platform is obtained by calling the SDK / API of different cloud vendors and stored in the resource pool to synchronize the multi-cloud system resources to the local to build a unified data model, so that the upper-layer business and external API can process based on the unified data model and output a unified and clear data format;

[0127] Step 3.1: Automatic resource synchronization stage. After adding the cloud account, the operation and maintenance platform will automatically synchronize cloud platform resources. The synchronization period can be defined by the user. If you need to temporarily stop the synchronization task, set the automatic synchronization interval to 0 or close the synchronization of the corresponding task on the queue status page. You can also view all scheduled tasks on the queue status page.

[0128] Step 3.2: When synchronizing resources manually, a separate synchronization operation is performed on a certain resource type of a single cloud account under multiple cloud platform accounts in the operation and maintenance platform. Detailed log records are available for viewing during the entire resource synchronization process. At the same time, the synchronization details of a specific vendor, specific resource, or specific status can be filtered based on the cloud vendor, resource type, and synchronization status.

[0129] Step 4: When managing all resource data synchronized across multiple cloud platforms, record the location of resources through location relationship management for easy retrieval; implement business-based resource retrieval by building a tree-like business relationship of project (root directory) → environment (official / test) → cluster → module; implement cross-business retrieval of hosts and execute corresponding tasks through tag relationship management;

[0130] Step 5: When managing resources in a multi-cloud system, use the resource pool to store synchronized resources on the cloud. Users can view resources in isolation by project, retrieve resources across cloud platforms through global search, add resources with the help of the add button on the resource list page or dynamic rules, and edit and delete resources in the resource list. At the same time, dynamic rules are used to match resources in the resource pool according to defined conditions and perform corresponding operations. After the dynamic rules are added, they must be confirmed that the matching resources meet expectations before they take effect.

[0131] A computer readable storage medium implements a resource management method when a computer program is executed by a processor.

[0132] A computer program product implements a resource management method when the computer program is executed by a processor.

[0133] The above is only a preferred embodiment of the present invention. It should be noted that, for those skilled in the art, several improvements and modifications can be made without departing from the principles of the present invention, and these improvements and modifications should also be considered as the protection scope of the present invention. The structures, devices and operating methods not specifically described and explained in the present invention shall be implemented according to the conventional means in the art unless otherwise specified and limited.

Claims

1. A resource management platform, characterized in that: include: Automated operation and maintenance platform and multi-cloud system resource pool: The automated operation and maintenance platform is connected to the multi-cloud system resource pool, and the basic data required for the upper-layer business depends on the acquisition of the multi-cloud system resource pool; When the underlying multi-cloud system resource pool is modified, the related monitoring, host, operation and other host-related information can be updated synchronously; Multi-cloud configuration: The multi-cloud configuration has a multi-cloud system resource synchronization function, which is used to synchronize resources under different cloud accounts on different cloud platforms to the local computer to build a unified data model; Relationship management features: The relationship management function is used to divide resources from all resource data synchronized from multiple different cloud platforms, including the management of location relationships, business relationships, and tag relationships; Synchronous log module: The synchronization log module is used to record the synchronization information, synchronization status and synchronization details of all resource points; Resource management functions: The resource management function is responsible for querying and displaying resources and managing resources and relationships in a multi-cloud system. Resources in a resource pool have no relationship attributes, and users can only view resources under their own projects. By default, resources in a resource pool are searched through global search, dynamic rules, and resource list operations related to adding resources.

2. A resource management platform according to claim 1, characterized in that: The upper-level business includes publishing systems, building monitoring dashboards, and daily operations; The host data required for the release system is obtained from the multi-cloud system resource pool; The host data for building the monitoring dashboard is obtained from the multi-cloud system resource pool; The target host selected for daily operations is obtained from the multi-cloud system resource pool; The data required for project cost calculation and resource reduction is obtained from the multi-cloud system resource pool; The strong dependency model ensures data accuracy and ensures that the basic data obtained by the upper-level business is consistent with the data in the multi-cloud system resource pool.

3. A resource management platform according to claim 1, characterized in that: The multi-cloud configuration obtains cloud resource data through SDK / API of different cloud vendors and places it in a resource pool, so as to enable upper-layer services and external APIs to be processed based on a unified data model, provide a unified data format, and support automatic resource synchronization and manual resource synchronization. Automatic resource synchronization: after adding a cloud account, the operation and maintenance platform will automatically synchronize resources with the cloud platform, and the synchronization period can be customized by the user. It also supports temporary closure of the synchronization task by changing the automatic synchronization interval to 0 or selecting the corresponding task on the queue status page to close the synchronization. View all scheduled tasks on the queue status page. Manual resource synchronization is to synchronize a resource type under a single cloud account separately in the operation and maintenance platform. All synchronization processes of all resources are viewed through log records. At the same time, the synchronization status of specific resources and specific status of specific vendors can be filtered according to cloud vendors, resource types and synchronization status.

4. A resource management platform according to claim 1, characterized in that: In terms of location relationship management, the location is the location of the resource, which is fixed and generated when the asset is created. The platform only needs to record it for retrieval; The business relationship management aspect is used to retrieve resources based on business. The business relationship is constructed as a tree structure. It is recommended to construct the business relationship according to the architecture of project (root directory) → environment (formal / test) → cluster → module to realize classified retrieval and management of resources. The tag relationship management aspect is used to search hosts across businesses, thereby achieving unified search and related operation execution of specific resources in different business environments.

5. A resource management platform according to claim 1, characterized in that: When viewing synchronization logs, you can filter based on cloud accounts to view only the synchronization information of a specified cloud account. When viewing synchronization logs, you can filter based on cloud resources to view only the synchronization information of specified cloud resources. When viewing the synchronization log, you can filter based on the synchronization status, including failure, success, and in progress.

6. A resource management platform according to claim 1, characterized in that: The global search function retrieves matching items from all resources based on keywords. Since resources of various cloud platforms are integrated, inputting a single IP address can search for corresponding hosts from different cloud platforms. The resource list function is designed to provide clear, accurate and easy-to-use resource data. It builds clear resource data through association relationships. The resource list is based on business relationship display. By default, all resources under the business are displayed. Click on the relationship tree node to view the resources under the corresponding node. It also provides classification and fuzzy search. There are two ways to add resources under the node: one is to add the required resources and tag them through the add button on the resource list page, and only one can be added at a time; the other is to add resources in batches with the help of dynamic rules; Edit and delete resources in the resource list. Since resource attributes are synchronized from the cloud and fixed, only resource business attributes and tags can be edited. When resources go offline, they are not directly deleted from the resource list but marked as expired. Users need to delete them manually to ensure resource accuracy. The dynamic rule function matches the corresponding resources in the resource pool according to the defined rules and labels these resources or adds business relationships. The three elements that constitute the dynamic rules are the resource pool, rules and operations. The dynamic rules do not take effect immediately after they are added. You must first confirm whether the resources matched by the rules meet your expectations. If the resource naming is not standardized, unexpected resources may be matched. There is a refresh button on the rule list page. After clicking refresh, the matched resources will be retrieved first, and the rules will be applied after confirming that they meet your expectations.

7. A resource management platform according to claim 6, characterized in that: The resources in the resource pool have no business relationship. If a resource belongs to a business, it will be kicked out of the resource pool. The dynamic rule only matches resources that have no business relationship. The rule is a condition for matching resources in the resource pool, which mainly includes the resource type to be matched, the field of the resource to be matched, the matching operator, and the matching content body; There are two main operations, namely tagging resources and adding business relationships to resources.

8. A resource management method, based on the resource management platform according to any one of claims 1 to 7, characterized in that: The specific steps are as follows: Step 1: When the basic resources of the project change, update the data in the multi-cloud system resource pool in a timely manner; when the underlying multi-cloud system resource pool is modified, trigger the relevant mechanism to synchronize the corresponding monitoring, host, job and other information; Step 2: Support viewing synchronization details, which at least include synchronization information, synchronization status and synchronization details of resource points; Step 3: During resource synchronization, the resource data of the corresponding cloud platform is obtained by calling the SDK / API of different cloud vendors and stored in the resource pool to synchronize the multi-cloud system resources to the local to build a unified data model, so that the upper-layer business and external API can process based on the unified data model and output a unified and clear data format; Step 3.1: Automatic resource synchronization stage. After adding the cloud account, the operation and maintenance platform will automatically synchronize cloud platform resources. The synchronization period can be defined by the user. If you need to temporarily stop the synchronization task, set the automatic synchronization interval to 0 or close the synchronization of the corresponding task on the queue status page. You can also view all scheduled tasks on the queue status page. Step 3.2: When synchronizing resources manually, a separate synchronization operation is performed on a certain resource type of a single cloud account under multiple cloud platform accounts in the operation and maintenance platform. Detailed log records are available for viewing during the entire resource synchronization process. At the same time, the synchronization details of a specific vendor, specific resource, or specific status can be filtered based on the cloud vendor, resource type, and synchronization status. Step 4: When managing all resource data synchronized across multiple cloud platforms, record the location of resources through location relationship management for easy retrieval; implement business-based resource retrieval by building a tree-like business relationship of project (root directory) → environment (official / test) → cluster → module; implement cross-business retrieval of hosts and execute corresponding tasks through tag relationship management; Step 5: When managing resources in a multi-cloud system, use the resource pool to store synchronized resources on the cloud. Users can view resources in isolation by project, retrieve resources across cloud platforms through global search, add resources with the help of the add button on the resource list page or dynamic rules, and edit and delete resources in the resource list. At the same time, dynamic rules are used to match resources in the resource pool according to defined conditions and perform corresponding operations. After the dynamic rules are added, they must be confirmed that the matching resources meet expectations before they take effect.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method described in claim 8 is implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method described in claim 8 is implemented.

Images