A resource management method, apparatus, and readable storage medium

Abstract

This application discloses a resource management method, apparatus, and readable storage medium, relating to the field of electronic information. Compared to previous solutions, the resource management method provided in this application pre-adapts the front-end page of the resource pool to the cloud management platform. When a user logs in on the cloud management platform, the corresponding resource pool's front-end page is opened, and the instructions from the front-end page are forwarded to the resource pool's management platform back-end. Compared to the previous method of directly retrieving data from the corresponding resource pool using the cloud management platform's back-end management module, this solution avoids data and system transformation because both the front-end and back-end are the resource pool's own front-end and back-end. The logic is simpler, and since the front-end and back-end are adapted, advanced functions are not lost, resulting in higher applicability.

Description

Technical Field

[0001] This application relates to the field of electronic information, and in particular to a resource management method, apparatus and readable storage medium. Background Technology

[0002] In recent years, with the development of cloud computing technology, many enterprises have chosen to migrate to the cloud, and managing virtualized resource pools through multi-cloud management platforms has become a common industry practice. However, currently, cloud management platforms often manage virtualized resource pools based on application programming interfaces (APIs). That is, the cloud platform maintains the functional interface related to the virtualized resource pool and manages the underlying virtualized resource pool by calling API interfaces. For example, a multi-cloud management platform from vendor A can be used to uniformly manage the resource pools of vendors B and C.

[0003] In existing management logic, vendor A's cloud management platform needs to have interfaces associated with vendors B and C simultaneously. It also needs to maintain the function lists of vendors B and C, as well as the corresponding Uniform Resource Locators (URLs) and parameters for each function's API. When managing resource pools from different vendors, or different versions of resource pools from the same vendor, the corresponding interfaces and APIs differ. The cloud management platform needs to maintain a large amount of page logic and API call logic from other vendors, resulting in complex logic. Furthermore, virtualization resource pools generally have native management interfaces, and many advanced functions cannot be fully passed to the upper-layer cloud management platform interface, leading to the loss of advanced functions and thus low applicability.

[0004] Given the aforementioned technologies, finding a resource management method that is both logically simple and highly applicable is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a resource management method, apparatus, and readable storage medium to solve the problems that cloud management platforms need to maintain a large amount of page logic and interface call logic from other vendors, which is complex. In addition, virtualization resource pools generally have native management interfaces, and many advanced functions cannot be fully transmitted to the upper-layer cloud management platform interface, resulting in the loss of advanced functions and thus low applicability.

[0006] To address the aforementioned technical problems, this application provides a resource management method applied to a cloud management platform, the method comprising:

[0007] Obtain the logged-in user information and switch to the corresponding front-end page based on the user information. The front-end page is a front-end page that is pre-built on the cloud management platform according to the corresponding resource pool.

[0008] Identify the preset identifier corresponding to the front-end page, and retrieve the resource pool corresponding to the front-end page;

[0009] The instructions entered by the user on the front-end page are sent to the back-end of the management platform of the resource pool, and the instructions are sent to the back-end of the management platform of the corresponding resource pool.

[0010] The management platform backend of the resource pool receives the processing result after processing the instruction.

[0011] Preferably, the creation of the front-end page includes:

[0012] The management platform front-end of each resource pool is trimmed and adapted, retaining only the virtualization resource management function;

[0013] Receive the front-end code of the management platform of each resource pool after it has been trimmed, and merge it with the front-end code of the cloud management platform to establish a front-end framework;

[0014] The corresponding front-end page is generated based on the front-end framework and corresponds to the management platform back-end of each resource pool.

[0015] Preferably, the user logs in via IAM, and the step of obtaining the logged-in user information and switching to the corresponding front-end page based on the user information includes:

[0016] Retrieve user information from the IAM based on the user's ID;

[0017] Identify the category of the resource pool corresponding to the user information, and determine whether there are multiple categories;

[0018] If so, switch to the selection interface of the resource pool of the category, and switch to the corresponding front-end page according to the user's selection instruction;

[0019] If not, then switch to the front-end page of the resource pool of the aforementioned category.

[0020] Preferably, identifying the preset identifier corresponding to the front-end page and retrieving the resource pool corresponding to the front-end page includes:

[0021] For different categories of resource pools, routing is performed separately to retrieve the corresponding category of the resource pool;

[0022] If there are multiple resource pools for the category, then the identifier corresponding to the front-end page is identified, and the user is switched to the front-end page corresponding to the identifier.

[0023] Preferably, it further includes:

[0024] Receive the command from the system terminal to create a tenant, and send the command to create a tenant to the management platform backend of each resource pool;

[0025] Create a tenant with the same name synchronously, associate the tenant ID with the users contained in the tenant, and create the resource quota corresponding to the tenant based on the resource pool corresponding to the users under the tenant.

[0026] Preferably, it further includes:

[0027] The system receives aggregated data, metering and billing information, and monitoring alarm information uploaded from the management platform backend of each resource pool at preset intervals.

[0028] The data summary information, metering and billing information, and monitoring and alarm information are displayed on the current front-end page of the cloud management platform so that users can centrally monitor and manage the data summary information, metering and billing information, and monitoring and alarm information.

[0029] Preferably, after receiving the data summary information, metering and billing information, and monitoring alarm information uploaded by the management platform backend of each resource pool at preset time intervals, the method further includes:

[0030] The data in the data summary information, the metering and billing information, and the monitoring and alarm information are converted into the corresponding data in the backend of the cloud management platform, and invalid data is deleted, identical data is merged, and the converted data is stored in the data storage repository.

[0031] To address the aforementioned problems, this application also provides a resource management device applied to a cloud management platform, comprising:

[0032] The acquisition module is used to acquire the login user information and select the corresponding front-end page based on the user information. The front-end page is a front-end page that is pre-built on the cloud management platform according to the corresponding resource pool.

[0033] The identification module is used to identify the preset identifier corresponding to the front-end page and retrieve the resource pool corresponding to the front-end page;

[0034] The delivery module is used to send the instructions entered by the user on the front-end page to the back-end of the management platform of the resource pool, and to send the instructions to the back-end of the management platform of the corresponding resource pool.

[0035] The receiving module is used to receive the processing result after the management platform backend of the resource pool has processed the instruction.

[0036] Preferably, the device further includes:

[0037] A creation module is used to receive commands from the system terminal to create tenants and send the commands to create tenants to the management platform backend of each resource pool.

[0038] The synchronization module is used to synchronously create tenants with the same name, associate the tenant ID with the users contained in the tenant, and create the resource quota corresponding to the tenant based on the resource pool corresponding to the users under the tenant.

[0039] Preferably, the device further includes:

[0040] The information module is used to receive data summary information, metering and billing information, and monitoring alarm information uploaded by the management platform backend of each resource pool at preset intervals;

[0041] The display module is used to display the data summary information, metering and billing information, and monitoring and alarm information on the current front-end page of the cloud management platform, so that users can centrally monitor and manage the data summary information, metering and billing information, and monitoring and alarm information.

[0042] Preferably, the device further includes:

[0043] The processing module is used to convert the data in the data summary information, the metering and billing information, and the monitoring and alarm information into the data corresponding to the backend of the cloud management platform, delete invalid data, merge identical data, and store the converted data in the data storage repository.

[0044] To address the aforementioned problems, this application also provides a resource management device, including a memory for storing computer programs;

[0045] A processor for implementing the resource management method described above when executing the computer program.

[0046] To address the aforementioned problems, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the resource management method described above.

[0047] The resource management method provided in this application is applied to a cloud management platform. It obtains logged-in user information, switches to the corresponding front-end page based on this information, identifies a preset identifier corresponding to the front-end page, retrieves the resource pool corresponding to the front-end page, and sends the user's input on the front-end page to the resource pool's management platform back-end. The method then receives the processing result from the resource pool's management platform back-end after processing the instruction. Compared to previous solutions, this application pre-tailors and adapts the resource pool's front-end page to the cloud management platform. When a user logs in to the cloud management platform, the corresponding resource pool's front-end page is opened, and the front-end page's instructions are forwarded to the resource pool's management platform back-end. Compared to the previous method of directly retrieving data from the corresponding resource pool using the cloud management platform's back-end management module, this solution avoids data and system transformation because both the front-end and back-end are the resource pool's own front-end and back-end. The logic is simpler, and since the front-end and back-end are already adapted, advanced functionality is not lost, making it highly applicable.

[0048] The resource management device and computer-readable storage medium provided in this application correspond to the resource management method described above and have the same beneficial effects. Attached Figure Description

[0049] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 A flowchart of a resource management method provided in an embodiment of this application;

[0051] Figure 2 This application provides a schematic diagram of a cloud management platform according to an embodiment of the present application.

[0052] Figure 3 A schematic diagram illustrating the workflow of a converter provided in an embodiment of this application;

[0053] Figure 4 A schematic diagram of a resource management device provided in an embodiment of this application;

[0054] Figure 5 This is a structural diagram of a resource management device provided in another embodiment of this application. Detailed Implementation

[0055] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0056] The core of this application is to provide a resource management method, apparatus, and readable storage medium to solve the problem that cloud management platforms need to maintain a large amount of page logic and interface call logic from other vendors, which is complex. In addition, virtualization resource pools generally have native management interfaces, and many advanced functions cannot be fully passed to the upper-layer cloud management platform interface, resulting in the loss of advanced functions and thus low applicability.

[0057] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0058] Figure 1 A flowchart of a resource management method provided in this application embodiment is shown below. Figure 1 As shown, the method includes:

[0059] S10: Obtain the logged-in user information and switch to the corresponding front-end page based on the user information.

[0060] The front-end page is a front-end page pre-built on the cloud management platform according to the corresponding resource pool. In this embodiment, the specific method of obtaining user information and the specific content recorded in user information are not limited. It can be understood that user information generally includes the content of the resource pool corresponding to the user.

[0061] S11: Identify the preset identifier corresponding to the front-end page and retrieve the resource pool corresponding to the front-end page;

[0062] It should be noted that the preset identifier is used to identify the resource pool corresponding to the user. In this embodiment, there are no restrictions on the creation of the preset identifier or the specific identification method. It should be noted that the resource pool here refers to all the resource pools under the cloud management platform.

[0063] S12: Send the instructions entered by the user on the front-end page to the back-end of the resource pool management platform;

[0064] It should be noted that the front-end, or website front-end, runs on client-side devices such as mobile devices, and is the webpage displayed to the user in a browser—the part used for human-computer interaction. The back-end, on the other hand, refers to the part that executes the actual instructions. This embodiment does not limit the specific resource pool distribution process.

[0065] S13: Receive the processing result after the resource pool management platform backend has completed processing the instruction.

[0066] The resource management method provided in this application is applied to a cloud management platform. It obtains logged-in user information, switches to the corresponding front-end page based on this information, identifies a preset identifier corresponding to the front-end page, retrieves the resource pool corresponding to the front-end page, and sends the user's input on the front-end page to the resource pool's management platform back-end. The method then receives the processing result from the resource pool's management platform back-end after the back-end has processed the instruction. Compared to previous solutions, this application pre-tailors and adapts the resource pool's front-end page to the cloud management platform. When a user logs in on the cloud management platform, the corresponding resource pool's front-end page is opened, and the front-end page's instructions are forwarded to the resource pool's management platform back-end. Compared to the previous method of directly retrieving data from the corresponding resource pool using the cloud management platform's back-end management module, this solution avoids data and system transformation because both the front-end and back-end are the resource pool's own front-end and back-end. The logic is simpler, and since the front-end and back-end are already adapted, advanced functionality is not lost, making it highly applicable.

[0067] The above embodiments do not limit the specific process of creating the front-end page. A preferred embodiment is provided here, in which the creation of the front-end page includes:

[0068] The management platform front-end of each resource pool is trimmed and adapted, retaining only the virtualization resource management function;

[0069] Receive the trimmed front-end code from the management platform of each resource pool and merge it with the front-end code of the cloud management platform to establish a front-end framework;

[0070] The corresponding front-end pages are generated based on the front-end framework and correspond to the back-end of the management platform for each resource pool.

[0071] Figure 2 This application provides a system schematic diagram of a cloud management platform, as shown in the embodiments of the present application. Figure 2 As shown, in this embodiment, the specific generation method and communication method of the front-end page of the cloud management platform are defined to ensure the adaptation of the final data.

[0072] The above embodiments do not limit the user information or the specific login method. A preferred solution is provided here: the user logs in via IAM, obtains the logged-in user information, and switches to the corresponding front-end page based on the user information, including:

[0073] Retrieve user information from IAM based on the user's ID; identify the category of the resource pool corresponding to the user information, and determine whether there are multiple categories;

[0074] If so, switch to the resource pool selection interface for the category, and switch to the corresponding front-end page according to the user's selection command;

[0075] If not, switch to the front-end page of the category's resource pool.

[0076] It should be noted that the Unified Identity and Access Management (IAM) service provides identity authentication and access control functions. It can manage user (such as employee, system or application) accounts and control these users' access permissions to resources under your name. The identity (ID) is a unique identifier for each user in a system. In this embodiment, user information is not limited or described in detail.

[0077] The above embodiments do not limit the specific method of identifying the identifier and retrieving the resource pool. A preferred solution is provided here, which includes identifying the preset identifier corresponding to the front-end page and retrieving the resource pool corresponding to the front-end page, including:

[0078] For different types of resource pools, routing is performed separately to retrieve the corresponding resource pool type;

[0079] If there are multiple resource pools for a category, the identifier corresponding to the front-end page will be identified, and the user will be switched to the front-end page corresponding to the identifier.

[0080] It should be noted that in this embodiment, the specific identification of the preset identifier and the retrieval of the corresponding resource pool based on the preset identifier are all performed by software, which is generally referred to in the industry as a repeater. Figure 3 This is a schematic diagram of the workflow of a converter provided in an embodiment of this application, as shown below. Figure 3 As shown, the role of the repeater is to first determine the category of the resource pool it belongs to, and then query the corresponding resource pool based on the identifier. For example, Figure 3 When the repeater receives two front-end pages, front-end page 1 and front-end page 2, it first determines whether the page belongs to category 1 or category 2, and then determines whether it belongs to any identifier based on the identifier. It should be noted that... Figure 3The present application illustrates one form of operation of a repeater. For this repeater, there may be more or fewer front-end page inputs or corresponding resource pools, which are not limited here.

[0081] Considering the difficulty of management, the preferred solutions provided here also include:

[0082] Receive the command to create a tenant from the system terminal and send the command to the management platform backend of each resource pool;

[0083] Create tenants with the same name synchronously, associate them with the tenant ID and the users contained within the tenant, and create resource quotas for the tenant based on the resource pools corresponding to the users under the tenant.

[0084] It should be noted that a tenant is a collection of users. In this embodiment, users of the same type are generally used to create a tenant.

[0085] Considering the upload and reception of data, the following preferred solutions are provided:

[0086] It receives aggregated data, metering and billing information, and monitoring alarm information uploaded from the management platform backend of each resource pool at preset intervals.

[0087] The data summary information, metering and billing information, and monitoring and alarm information are displayed on the current front-end page of the cloud management platform, so that users can centrally monitor and manage the data summary information, metering and billing information, and monitoring and alarm information.

[0088] After receiving aggregated data, metering and billing information, and monitoring alarm information uploaded from the management platform backend of each resource pool at preset intervals, the system also includes:

[0089] The data in the data summary information, metering and billing information, and monitoring and alarm information are converted into the corresponding data in the backend of the cloud management platform, invalid data is deleted, identical data is merged, and the converted data is stored in the data storage repository.

[0090] It should be noted that this embodiment proposes uploading the data of the resource pool to the corresponding cloud management platform, so as to facilitate unified management by the cloud management platform.

[0091] In the above embodiments, the resource management method has been described in detail. This application also provides embodiments corresponding to the resource management device. It should be noted that this application describes the embodiments of the device from two perspectives: one is based on the functional modules, and the other is based on the hardware.

[0092] Figure 4 A schematic diagram of a resource management device provided in an embodiment of this application is shown. The device includes:

[0093] The acquisition module 10 is used to acquire the logged-in user information and select the corresponding front-end page based on the user information. The front-end page is a front-end page that is pre-built on the cloud management platform according to the corresponding resource pool.

[0094] The identification module 11 is used to identify the preset identifier corresponding to the front-end page and retrieve the resource pool corresponding to the front-end page.

[0095] The distribution module 12 is used to distribute the instructions entered by the user on the front-end page to the back-end of the resource pool management platform and distribute the instructions to the back-end of the management platform of the corresponding resource pool.

[0096] The receiving module 13 is used to receive the processing result after the backend of the resource pool management platform has completed processing the instruction.

[0097] Preferably, the device further includes:

[0098] The creation module is used to receive commands from the system terminal to create tenants and send these commands to the management platform backend of each resource pool.

[0099] The synchronization module is used to synchronously create tenants with the same name, associate the tenant ID with the users contained in the tenant, and create the resource quota corresponding to the tenant based on the resource pool corresponding to the users under the tenant.

[0100] Preferably, the device further includes:

[0101] The information module is used to receive aggregated data, metering and billing information, and monitoring alarm information uploaded from the management platform backend of each resource pool at preset intervals.

[0102] The display module is used to display data summary information, metering and billing information, and monitoring and alarm information on the current front-end page of the cloud management platform, so that users can centrally monitor and manage the data summary information, metering and billing information, and monitoring and alarm information.

[0103] Preferably, the device further includes:

[0104] The processing module is used to convert the corresponding data in the data summary information, metering and billing information, and monitoring and alarm information into the corresponding data in the backend of the cloud management platform, delete invalid data, merge identical data, and store the converted data in the data storage repository.

[0105] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus, which will not be repeated here.

[0106] The resource management device provided in this application, applied to a cloud management platform, includes: an acquisition module, an identification module, a distribution module, and a receiving module. The interaction between these modules enables the acquisition of logged-in user information, switching to the corresponding front-end page based on this information, identifying a preset identifier corresponding to the front-end page, retrieving the resource pool corresponding to the front-end page, and distributing the user's input commands on the front-end page to the resource pool's management platform back-end. The device also receives the processing results from the resource pool's management platform back-end after the commands have been processed. Compared to previous solutions, this application pre-tailors and adapts the resource pool's front-end page to the cloud management platform. When a user logs in to the cloud management platform, the corresponding resource pool's front-end page is opened, and the commands from the front-end page are forwarded to the resource pool's management platform back-end. Compared to the previous method of directly retrieving data from the corresponding resource pool using the cloud management platform's back-end management module, this solution, where both the front-end and back-end are the resource pool's own front-end and back-end, avoids data and system transformations, resulting in simpler logic. Furthermore, because the front-end and back-end are already adapted, advanced functionality is not lost, making it highly applicable.

[0107] Figure 5 A structural diagram of a resource management device provided in another embodiment of this application is shown below. Figure 5 As shown, the resource management device includes: a memory 20 for storing computer programs;

[0108] The processor 21 is configured to implement the steps of the resource management method as described in the above embodiments when executing a computer program.

[0109] The resource management device provided in this embodiment may include, but is not limited to, smartphones, tablets, laptops, or desktop computers.

[0110] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one hardware form selected from Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as the Central Processing Unit (CPU), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a Graphics Processing Unit (GPU), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an Artificial Intelligence (AI) processor, which handles computational operations related to machine learning.

[0111] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory 20 is used to store at least the following computer program 201, which, after being loaded and executed by the processor 21, is capable of implementing the relevant steps of the resource management method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, and the storage method may be temporary or permanent storage. The operating system 202 may include Windows, Unix, Linux, etc. The data 203 may include, but is not limited to, the data involved in the resource management method.

[0112] In some embodiments, the resource management device may further include a display screen 22, an input / output interface 23, a communication interface 24, a power supply 25, and a communication bus 26.

[0113] Those skilled in the art will understand that Figure 5 The structure shown does not constitute a limitation on the resource management device and may include more or fewer components than illustrated.

[0114] The resource management device provided in this application includes a memory and a processor. When the processor executes a program stored in the memory, it can implement the following method: the resource management method involved in the above embodiments.

[0115] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus, which will not be repeated here.

[0116] The resource management device provided in this application, applied to a cloud management platform, includes a processor and a memory. When the data stored in the memory is executed by the processor, it can obtain logged-in user information, switch to the corresponding front-end page based on the user information, identify the preset identifier corresponding to the front-end page, and retrieve the resource pool corresponding to the front-end page. It then sends the user's input on the front-end page to the resource pool's management platform back-end, and receives the processing result after the resource pool's management platform back-end has processed the instruction. Compared with previous solutions, this application pre-adapts the resource pool's front-end page to the cloud management platform. When a user logs in to the cloud management platform, the corresponding resource pool's front-end page is opened, and the front-end page's instructions are forwarded to the resource pool's management platform back-end. Compared to the previous method of directly retrieving data from the corresponding resource pool using the cloud management platform's back-end management module, this solution, since both the front-end and back-end are the resource pool's own front-end and back-end, does not involve data or system transformation, making the logic simpler. Furthermore, because the front-end and back-end are adapted themselves, advanced functions are not lost, resulting in higher applicability.

[0117] Finally, this application also provides an embodiment corresponding to a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps described in the above method embodiments.

[0118] It is understood that if the methods in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and executes all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0119] Since the embodiments of the readable storage medium portion correspond to the embodiments of the method portion, the embodiments of the apparatus portion are described in the method portion description and will not be repeated here.

[0120] The computer-readable storage medium provided in this application, when the stored data is executed, can obtain logged-in user information, switch to the corresponding front-end page based on the user information, identify the preset identifier corresponding to the front-end page, retrieve the resource pool corresponding to the front-end page, send the user's input command on the front-end page to the resource pool management platform back-end, and receive the processing result after the resource pool management platform back-end has processed the command. Compared with previous solutions, this application adopts a method of pre-adapting the resource pool's front-end page to the cloud management platform. Thus, when a user logs in on the cloud management platform, the corresponding resource pool's front-end page is opened, and the commands from the front-end page are forwarded to the resource pool management platform back-end. Compared with the previous method of directly using the cloud management platform's back-end management module to retrieve data from the corresponding resource pool, since the front-end and back-end in this solution are both the resource pool's own front-end and back-end, there is no data or system transformation involved, the logic is simpler, and because the front-end and back-end are adapted themselves, advanced functions are not lost, making it highly applicable.

[0121] The resource management method, apparatus, and computer-readable storage medium provided in this application have been described in detail above. The various embodiments in the specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0122] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A resource management method, characterized in that, include: Obtain the logged-in user information and switch to the corresponding front-end page based on the user information. The front-end page is a front-end page that is pre-built on the cloud management platform according to the corresponding resource pool. Identify the preset identifier corresponding to the front-end page, and retrieve the resource pool corresponding to the front-end page; The instructions entered by the user on the front-end page are sent to the back-end of the management platform of the resource pool, and the instructions are sent to the back-end of the management platform of the corresponding resource pool. The management platform backend of the resource pool receives the processing result after processing the instruction; The user logs in via IAM, and the process of obtaining the logged-in user information and switching to the corresponding front-end page based on the user information includes: Retrieve the user information from the IAM based on the user's ID; Identify the category of the resource pool corresponding to the user information, and determine whether there are multiple categories; If so, switch to the selection interface of the resource pool of the category, and switch to the corresponding front-end page according to the user's selection instruction; If not, then switch to the front-end page of the resource pool of the aforementioned category.

2. The resource management method according to claim 1, characterized in that, The creation of the front-end page includes: The management platform front-end of each resource pool is trimmed and adapted, retaining only the virtualization resource management function; Receive the front-end code of the management platform of each resource pool after it has been trimmed, and merge it with the front-end code of the cloud management platform to establish a front-end framework; The corresponding front-end page is generated based on the front-end framework and corresponds to the management platform back-end of each resource pool.

3. The resource management method according to claim 1, characterized in that, The step of identifying the preset identifier corresponding to the front-end page and retrieving the resource pool corresponding to the front-end page includes: For different categories of resource pools, routing is performed separately to retrieve the corresponding category of the resource pool; If there are multiple resource pools for the category, then the identifier corresponding to the front-end page is identified, and the user is switched to the front-end page corresponding to the identifier.

4. The resource management method according to any one of claims 1 to 3, characterized in that, Also includes: Receive the command from the system terminal to create a tenant, and send the command to create a tenant to the management platform backend of each resource pool; Create a tenant with the same name synchronously, associate the tenant ID with the users contained in the tenant, and create the resource quota corresponding to the tenant based on the resource pool corresponding to the users under the tenant.

5. The resource management method according to claim 1, characterized in that, Also includes: The system receives aggregated data, metering and billing information, and monitoring alarm information uploaded from the management platform backend of each resource pool at preset intervals. The data summary information, the metering and billing information, and the monitoring and alarm information are displayed on the current front-end page of the cloud management platform so that the user can centrally monitor and manage the data summary information, the metering and billing information, and the monitoring and alarm information.

6. The resource management method according to claim 5, characterized in that, After receiving the aggregated data, metering and billing information, and monitoring alarm information uploaded by the management platform backend of each resource pool at preset intervals, the method further includes: The data in the data summary information, the metering and billing information, and the monitoring and alarm information are converted into the corresponding data in the backend of the cloud management platform, and invalid data is deleted, identical data is merged, and the converted data is stored in the data storage repository.

7. A resource management device, characterized in that, include: The acquisition module is used to acquire the logged-in user information and select the corresponding front-end page based on the user information. The front-end page is a front-end page that is pre-built on the cloud management platform according to the corresponding resource pool. The identification module is used to identify the preset identifier corresponding to the front-end page and retrieve the resource pool corresponding to the front-end page; The distribution module is used to distribute the instructions entered by the user on the front-end page to the back-end of the management platform of the resource pool, and to distribute the instructions to the back-end of the management platform of the corresponding resource pool. The receiving module is used to receive the processing result after the management platform backend of the resource pool has processed the instruction; The user logs in via IAM, and the module is specifically used for: Retrieve the user information from the IAM based on the user's ID; Identify the category of the resource pool corresponding to the user information, and determine whether there are multiple categories; If so, switch to the selection interface of the resource pool of the category, and switch to the corresponding front-end page according to the user's selection instruction; If not, then switch to the front-end page of the resource pool of the aforementioned category.

8. A resource management device, characterized in that, Includes memory used to store computer programs; A processor for executing the computer program to implement the steps of the resource management method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the resource management method as described in any one of claims 1 to 6.

Images