A Method, Device, Equipment and Medium for Selecting a Resource Pool Based on a Micro Front-End Architecture

Abstract

The present application discloses a method, device, equipment and medium for selecting a resource pool based on a micro-frontend architecture, which relates to the technical field of cloud computing. Applied to a cloud management platform, the method includes: obtaining user information in the main application through an ajax interface; judging whether the user identity is an operation and maintenance user according to the user information; if the user identity is an operation and maintenance user, judging whether there is resource pool information in the database of the cloud management platform and whether the routing source is a third-party sub-application; setting a switching resource pool window containing the resource pool information of the third-party sub-application at the top of the navigation bar; when there is no resource pool information in the database and the routing source is not a third-party sub-application, entering the resource pool selection page. At this time, the operation of selecting the resource pool is transferred to the resource pool selection page, avoiding compressing the limited display space of the top navigation bar, confusing with other dropdown boxes in the top navigation bar, and reducing the user experience.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and particularly to a method, device, equipment and medium for selecting a resource pool based on a micro-frontend architecture. Background Art

[0002] The Cloud Management Platform (CMP) is a unified management platform for data center resources, which can manage multiple open-source or heterogeneous cloud computing applications or products. The micro-frontend architecture is divided into a main application and multiple sub-applications. The main application is responsible for user login and the display of public content within the platform; the sub-applications are responsible for the display of specific content. In the cloud management platform, the resource pool is the entry point for accessing various heterogeneous basic application platforms in the system. The integrated operation and maintenance capabilities provided by the cloud management platform are used to monitor and alarm various resource data within the resource pool. Therefore, before entering the operation and maintenance system of the cloud management platform, the operation and maintenance user needs to select the resource pool to be used. The existing method of selecting the resource pool is to place it in the top navigation bar and display it through a drop-down selection box for users to select. Such a method not only compresses the limited display space of the top navigation bar, but also causes confusion with other drop-down boxes in the top navigation bar, reducing the user experience. Among them, the most important thing is that under the micro-frontend architecture, various third-party systems need to be integrated within the cloud management platform (such as third-party system physical facility monitoring, etc.). However, there is no resource pool for the third-party systems on the operation and maintenance side within the cloud management platform. At this time, placing the selection of switching the resource pool and the menu of the third-party system in the same top navigation bar will cause confusion for users to operate, reduce the usability of the product, and at the same time reduce the user experience.

[0003] In view of the above existing problems, seeking how to improve the user experience is a problem that those skilled in the art are trying their best to solve. Summary of the Invention

[0004] The purpose of this application is to provide a method, device, equipment and medium for selecting a resource pool based on a micro-frontend architecture, which is used to avoid compressing the limited display space of the top navigation bar, causing confusion with other drop-down boxes in the top navigation bar, and reducing the user experience.

[0005] To solve the above technical problems, this application provides a method for selecting a resource pool based on a micro-frontend architecture, which is applied to a cloud management platform and includes:

[0006] Obtain user information in the main application through an ajax interface;

[0007] Judge whether the user identity is an operation and maintenance user according to the user information;

[0008] If the user identity is an operation and maintenance user, it is determined whether the resource pool information is contained in the database of the cloud management platform and whether the routing source is a third-party sub-application; the resource pool switching window containing the resource pool information of the third-party sub-application is set at the top of the navigation bar;

[0009] When the database does not contain resource pool information and the routing source is not a third-party sub-application, enter the resource pool selection page; the resource pool selection page contains resource pool information and the entry of the resource pool.

[0010] Preferably, when the database does not contain resource pool information and the routing source is not a third-party sub-application, after entering the resource pool selection page, it further includes:

[0011] Display the resource pool information table through a table;

[0012] Obtain the resource pool information selected by the operation and maintenance user, store the resource pool information in the database, and return to the step of obtaining user information in the main application through the ajax interface.

[0013] Preferably, after obtaining the resource pool information selected by the operation and maintenance user and storing the resource pool information in the database, it further includes:

[0014] Display the menu information of the sub-application and the resource pool switching window.

[0015] Preferably, the resource pool information is displayed in the resource pool switching window in the form of a pop-up window.

[0016] Preferably, when the database contains resource pool information and the routing source is not a third-party sub-application, access the sub-application in the database of the cloud management platform.

[0017] Preferably, when the database does not contain resource pool information and the routing source is a third-party sub-application, access the third-party sub-application.

[0018] Preferably, the resource pool switching window is displayed as a switching identifier.

[0019] To solve the above technical problems, the present application also provides a resource pool selection device based on a micro-frontend architecture, which is applied to the above-mentioned resource pool selection method based on a micro-frontend architecture and includes:

[0020] An acquisition module for obtaining user information in the main application through an ajax interface;

[0021] A first judgment module for judging whether the user identity is an operation and maintenance user according to the user information;

[0022] A second judgment module, configured to, if the user identity is an operation and maintenance user, determine whether the resource pool information exists in the database of the cloud management platform and whether the routing source is a third-party sub-application; set the resource pool switching window containing the third-party sub-application resource pool information at the top of the navigation bar;

[0023] An entry module, configured to enter the resource pool selection page when the resource pool information does not exist in the database and the routing source is not a third-party sub-application; the resource pool selection page contains resource pool information and an entry to the resource pool.

[0024] To solve the above technical problems, the present application also provides a resource pool selection device based on a micro-frontend architecture, including:

[0025] A memory, configured to store a computer program;

[0026] A processor, configured to point to the computer program to implement the steps of the above-mentioned resource pool selection method based on the micro-frontend architecture.

[0027] To solve the above technical problems, the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned entire resource pool selection method based on the micro-frontend architecture are implemented.

[0028] The present application discloses a resource pool selection method, device, device, and medium based on a micro-frontend architecture, which relates to the field of cloud computing technology. When applied to a cloud management platform, the method includes: obtaining user information in the main application through an ajax interface; determining whether the user identity is an operation and maintenance user according to the user information; if the user identity is an operation and maintenance user, determining whether the resource pool information exists in the database of the cloud management platform and whether the routing source is a third-party sub-application; setting the resource pool switching window containing the third-party sub-application resource pool information at the top of the navigation bar; when the resource pool information does not exist in the database and the routing source is not a third-party sub-application, entering the resource pool selection page. At this time, the operation of selecting the resource pool is transferred to the resource pool selection page, avoiding compressing the limited display space of the top navigation bar, confusing with other dropdown boxes in the top navigation bar, and reducing the user experience.

[0029] The present application also provides a resource pool selection device, device, and medium based on a micro-frontend architecture, with the same effect. Description of the Drawings

[0030] To more clearly illustrate the embodiments of the present application, the following will briefly introduce the drawings required in the embodiments. Obviously, the following-described drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0031] Figure 1 The display screen of the resource pool selection method based on the micro-frontend architecture provided by the embodiment of the present application;

[0032] Figure 2 A flowchart of a resource pool selection method based on the micro-frontend architecture provided by the embodiment of the present application;

[0033] Figure 3 Another flowchart of a resource pool selection method based on the micro-frontend architecture provided by the embodiment of the present application;

[0034] Figure 4 The structural diagram of a resource pool selection device based on the micro-frontend architecture provided by the embodiment of the present application;

[0035] Figure 5 Another structural diagram of a resource pool selection device based on the micro-frontend architecture provided by the embodiment of the present application. Detailed implementation manners

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

[0037] The core of the present application is to provide a resource pool selection method, device, equipment and medium based on the micro-frontend architecture, which can avoid compressing the limited display space of the top navigation bar, confusing with other drop-down boxes in the top navigation bar, and reducing the user experience.

[0038] In order to enable those skilled in the art to better understand the solution of the present application, the present application will be further described in detail below in conjunction with the accompanying drawings and specific implementation manners.

[0039] The Cloud Management Platform (CMP) is a unified management platform for data center resources and can manage multiple open-source or heterogeneous cloud computing applications or products. The micro-frontend architecture consists of a main application and multiple sub-applications. The main application is responsible for user login and the display of public content within the platform; the sub-applications are responsible for the display of specific content. In the cloud management platform, the resource pool is the entry point for accessing various heterogeneous basic application platforms in the system. The integrated operation and maintenance capabilities provided by the cloud management platform are used to monitor and alarm various resource data within the resource pool. Therefore, before entering the operation and maintenance system of the cloud management platform, the operation and maintenance user needs to select the resource pool to be used. Among them, the micro-frontend architecture is a Web front-end architecture of microservices. It applies the concept of microservices to the browser side and transforms the Web application from a single monolithic application into an application aggregated by multiple small front-end applications; it can be understood that a Web server generally refers to a website server, which is a program residing on a certain type of computer on the Internet. It can process requests from Web clients such as browsers and return corresponding responses, or it can place website files for all users to browse; it can also place data files for all users to download and view. The three most mainstream Web servers currently are Apache, Nginx, and IIS. In the micro-frontend architecture, each front-end application can be developed, deployed, and run independently, thus improving the development and maintenance efficiency of the entire software system. In this application, the third-party system mentioned is different from other platform systems outside the cloud management platform. Under the micro-frontend architecture, various third-party systems can be more quickly and conveniently integrated within the cloud management platform.

[0040] Figure 1 This is the display screen of the resource pool selection method based on the micro-frontend architecture provided by the embodiment of this application. As Figure 1 shown, in this application, the resource pool switching window containing third-party system resource pool information is set at the top of the left navigation bar. Among them, the resource pool switching window can be represented by a switching identifier, and this switching identifier can be represented by various obvious icons, for example: a red round button; it should be noted that in this embodiment, the icon shape, color, etc. of the switching identifier are not limited. The above-mentioned red round button is only one of many embodiments and does not limit the switching identifier. The switching identifier can determine its implementation method according to the specific implementation scenario. It should be noted that the width, length, etc. of the navigation bar are not limited, and the user can determine its implementation method according to the implementation scenario. To solve the above technical problems, this application also provides a resource pool selection method based on the micro-frontend architecture. Figure 2 This is the flowchart of a resource pool selection method based on the micro-frontend architecture provided by the embodiment of this application. As Figure 2 shown, when this method is applied to the cloud management platform, it includes:

[0041] S20: Obtain user information in the main application through an ajax interface.

[0042] It should be noted that in this embodiment, the method of obtaining user information is not limited to through an ajax interface, and it can also be an IIC interface. Although the above two interfaces are given, it can be understood that in actual applications, the type of this interface is not limited to the above two interfaces, and the type of interface can be determined according to specific implementation manners. Among them, the user information received by the interface can be "the user identity is an operation and maintenance user", or it can be a binary data string representing that the user identity information is an operation and maintenance user. There is no limit to the number of digits of this data string, which can be 2 digits, 4 digits, 8 digits, etc., and can be represented as "00", "0110", "11001011", etc. It should be noted that the above-mentioned data strings are only several of many embodiments, and do not limit the types and representation forms of the data strings. In addition, there is no limit to the types of user information, which can be user types, user accounts, etc.

[0043] S21: Judge whether the user identity is an operation and maintenance user according to the user information.

[0044] Based on the above embodiment, when the representation form of the user information is "the user identity is an operation and maintenance user", the keyword "operation and maintenance user" can be judged; when the representation form of the user information is a data string of 2 digits, 4 digits, or 8 digits, the number of occurrences of "0" or / and "1" in the data string can be judged. Similarly, the above-mentioned judgment methods are only several of many embodiments, and do not limit the judgment methods.

[0045] S22: If the user identity is an operation and maintenance user, then judge whether the database of the cloud management platform contains resource pool information and whether the routing source is a third-party sub-application.

[0046] At the same time, set the resource pool switching window containing the resource pool information of the third-party sub-application at the top of the navigation bar. Based on the above embodiment, display the resource pool switching window at the top of the left navigation bar for the user to find and click in the display page.

[0047] S23: When the database does not contain resource pool information and the routing source is not a third-party sub-application, enter the resource pool selection page.

[0048] It should be noted that the resource pool selection page contains resource pool information and a resource pool entry.

[0049] Transfer the operation of selecting the resource pool to the resource pool selection page, avoiding compressing the limited display space of the top navigation bar, confusing with other dropdown boxes in the top navigation bar, and reducing the user experience.

[0050] Figure 3 Another flowchart of the resource pool selection method based on the micro-frontend architecture provided by the embodiments of the present application. On the basis of the above embodiments, as a more optimal embodiment, as Figure 3 shown, according to step S22 above, there will also be corresponding steps in the following situations:

[0051] S33: When the database contains resource pool information and the routing source is not a third-party sub-application, access the sub-applications in the database of the cloud management platform.

[0052] S34: When the database does not contain resource pool information and the routing source is a third-party sub-application, access the third-party sub-application.

[0053] It also realizes convenient access to the sub-applications and third-party sub-applications in the database of the cloud management platform.

[0054] On the basis of the above embodiments, as a more optimal embodiment, when the database does not contain resource pool information and the routing source is not a third-party sub-application, after entering the resource pool selection page, it further includes:

[0055] S30: Display the resource pool information table through a table.

[0056] On the resource pool selection page, the information of the resource pool is displayed in detail in the form of a table, and a link entry is set at the resource pool name. When the user clicks on a certain resource pool name, it will jump to the resource pool clicked by the user. It should be noted that displaying the resource pool information table in the form of a table is for the user to find the resource pool information more conveniently and quickly, but it does not mean that only displaying it in a table has the above effect. In this embodiment, it can also be displayed in other formats of tables, as long as it can facilitate the user to find and click to select the required resource pool. The format of the table is not limited and can be determined according to the specific implementation scenario. It should be noted that when displaying the resource pool information, the resource pool information is displayed in a pop-up window in the resource pool switching window.

[0057] It should be noted that only after selecting the required resource pool on the resource pool selection page can the next step be entered, otherwise, it will stay on the resource pool selection page all the time. However, it does not rule out that the user can exit the entire cloud management platform through the total close button.

[0058] S31: Obtain the resource pool information selected by the user and store the resource pool information in the database.

[0059] Storing the resource pool information that does not exist in the database of the cloud management platform into the database can enable the user to directly enter the required resource pool when entering the database of the cloud management platform to select the same resource pool next time, without having to select again, thus enhancing the user experience. It should be noted that the resource pool information includes clusterId, clusterType, and clusterName.

[0060] After storing the resource pool information into the database, return to step S20.

[0061] Based on the above embodiments, as a more optimal embodiment, after obtaining the resource pool information selected by the user and storing the resource pool information into the database, it further includes:

[0062] S32: Display the menu information of the sub-application and the resource pool switching window.

[0063] After selecting the required resource pool on the resource pool selection page, the display page will be refreshed, and the menu of the main application and the business content within the sub-application will be reloaded. This facilitates the user to browse the page in a more direct way and enhances the user experience.

[0064] Based on all the above embodiments, after the operation and maintenance user logs in to the cloud management system, first, it will call the interface through ajax to obtain the relevant information of the user, and judge whether there is resource pool information and the routing source in the database. If there is no resource pool information in the database and the routing source is not a third-party system (that is, the routing source is the routing of the internal data path of the cloud management platform), then enter the resource pool selection page. If it is judged that there is resource pool information in the database or the routing source is from a third-party system, then access the inside of the sub-application in the cloud management platform and display the business content and menu information of the sub-application, etc. The resource pool selection page contains the resource pool information of all resource pools. The user can select the required resource pool information and access the sub-application after clicking on the resource pool name. When the user accesses the sub-application for business operations, the resource pool can be switched through the resource pool switching window. This window is designed at the top of the left navigation bar of the cloud management platform and defaults to display the information of the currently selected resource pool. It also supports the user to pop up the resource pool selection pop-up page by clicking a button to guide the user to switch the resource pool. After the user selects a certain resource pool, it will be judged again whether the resource pool information exists and whether it comes from a third-party system. At this time, it is inevitable that the resource pool exists, so it will directly jump to the sub-application.

[0065] This application abandons the form of switching resource pools in the dropdown box placed in the top navigation bar of the cloud management platform and changes it to designing a resource pool selection page in the main application for users to select resource pools. This solution can not only free up the limited space of the top navigation bar, but also avoid confusion with other dropdown boxes in the navigation bar (such as the multi-region selection box), improving usability. In addition, it also enhances the importance of the resource pool in the operation and maintenance system. Instead of defaulting to giving users a resource pool after entering the cloud management platform, users log in to the cloud management platform and first select the resource pool, making the business logic clearer and easier to understand. Another point is that now under the micro-frontend architecture, various third-party sub-applications are integrated. This invention can better decouple the third-party sub-applications from the resource pool, enabling users not to be restricted by the resource pool when using third-party sub-applications and also enhancing the user experience.

[0066] In the above embodiments, the method for selecting a resource pool based on the micro-frontend architecture is described in detail. This application also provides corresponding embodiments of the device for selecting a resource pool based on the micro-frontend architecture. It should be noted that this application describes the embodiments of the device part from two perspectives, one is from the perspective of functional modules, and the other is from the perspective of hardware.

[0067] Figure 4 This is a structural diagram of a device for selecting a resource pool based on the micro-frontend architecture provided by an embodiment of this application. As Figure 4 shown, this application also provides a device for selecting a resource pool based on the micro-frontend architecture, including:

[0068] An acquisition module 40, configured to acquire user information in the main application through an ajax interface;

[0069] A first judgment module 41, configured to judge whether the user identity is an operation and maintenance user according to the user information;

[0070] A second judgment module 42, configured to, if the user identity is an operation and maintenance user, judge whether the database of the cloud management platform contains resource pool information and whether the routing source is a third-party sub-application; set the resource pool switching window containing the third-party sub-application resource pool information at the top of the navigation bar;

[0071] An entry module 43, configured to enter the resource pool selection page when the database does not contain resource pool information and the routing source is not a third-party sub-application; the resource pool selection page contains resource pool information and the entry of the resource pool.

[0072] In addition, this application also includes the following modules:

[0073] A first display module, configured to display the resource pool information table through a table.

[0074] A storage module, which is used to obtain the resource pool information selected by the operation and maintenance user, store the resource pool information in the database, and return to the acquisition module.

[0075] A second display module, which is used to display the menu information of the sub-application and the resource pool switching window.

[0076] A third display module, which is used to display the resource pool information in the resource pool switching window in the form of a pop-up window.

[0077] A database access sub-application module, which is used to access the sub-application in the database of the cloud management platform when the database contains resource pool information and the routing source is not a third-party sub-application.

[0078] A third-party sub-application access module, which is used to access the third-party sub-application when the database does not contain resource pool information and the routing source is a third-party sub-application.

[0079] A fourth display module, which is used to display the resource pool switching window as a switching identifier.

[0080] Since the embodiments in the device part correspond to the embodiments in the method part, for the embodiments in the device part, please refer to the description of the embodiments in the method part, which will not be elaborated here for the time being.

[0081] Based on all the above modules, after the operation and maintenance user logs in to the cloud management system, first, relevant information of the user will be obtained through an ajax call interface, and it will be judged whether there is resource pool information and the routing source in the database. If there is no resource pool information in the database and the routing source is not a third-party system (that is, the routing source is the routing of the internal data path of the cloud management platform), then enter the resource pool selection page. If it is judged that there is resource pool information in the database or the routing source is from a third-party system, then access the sub-application inside the cloud management platform and display the business content and menu information of the sub-application, etc. The resource pool information of all resource pools is contained in the resource pool selection page. The user can select the required resource pool information and access the sub-application after clicking the resource pool name. When the user accesses the sub-application for business operations, the resource pool can be switched through the resource pool switching window. This window is designed at the top of the left navigation bar of the cloud management platform, and the information of the currently selected resource pool is displayed by default. It also supports the user to pop up the resource pool selection pop-up page by clicking a button to guide the user to switch the resource pool. After the user selects a certain resource pool, it will be judged again whether the resource pool information exists and whether it comes from a third-party system. At this time, the existence of the resource pool is inevitable, so it will directly jump to the sub-application.

[0082] This application abandons the form of switching resource pools in the dropdown box placed in the top navigation bar of the cloud management platform and changes it to design a resource pool selection page in the main application for users to select resource pools. This solution can not only free up the limited space in the top navigation bar but also avoid confusion with other dropdown boxes in the navigation bar (such as the multi-region selection box), improving usability. In addition, it also enhances the importance of the resource pool in the operation and maintenance system. Instead of defaulting to a resource pool for users after entering the cloud management platform, users log in to the cloud management platform and first select the resource pool, making the business logic clearer and easier to understand. Another point is that under the current micro-frontend architecture, various third-party sub-applications are integrated. This invention can better decouple the third-party sub-applications from the resource pool, so that users are no longer restricted by the resource pool when using third-party sub-applications, and it also improves the user experience.

[0083] Figure 5 Another device structure diagram for resource pool selection based on the micro-frontend architecture provided by the embodiments of this application is as Figure 5 shown. The device for resource pool selection based on the micro-frontend architecture includes:

[0084] A memory 50 for storing computer programs;

[0085] A processor 51 for implementing the steps of the resource pool selection method based on the micro-frontend architecture mentioned in the above embodiments when executing the computer program.

[0086] The device for resource pool selection based on the micro-frontend architecture provided in this embodiment may include but is not limited to smartphones, tablets, laptop computers, or desktop computers, etc.

[0087] Among them, the processor 51 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 51 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 51 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the wake state, also known as the central processing unit (CPU); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 51 may be integrated with a graphics processing unit (GPU), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 51 may further include an artificial intelligence (AI) processor, and the AI processor is used to process computational operations related to machine learning.

[0088] The memory 50 may include one or more computer-readable storage media, and the computer-readable storage media may be non-transitory. The memory 50 may further include high-speed random access memory and non-volatile memory, such as one or more disk storage devices and flash storage devices. In this embodiment, the memory 50 is at least used to store a computer program. After the computer program is loaded and executed by the processor 51, the relevant steps of the resource pool selection method based on the micro-frontend architecture disclosed in any of the foregoing embodiments can be implemented. In addition, the resources stored in the memory 50 may further include an operating system and data, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system may include Windows, Unix, Linux, etc. The data may include, but is not limited to, the resource pool selection method based on the micro-frontend architecture, etc.

[0089] In some embodiments, the resource pool selection device based on the micro-frontend architecture may further include a display screen, an input / output interface, a communication interface, a power supply, and a communication bus.

[0090] Those skilled in the art can understand that Figure 5 the structure shown in

[0091] The device for selecting resources based on a micro-frontend architecture provided by an embodiment of the present application includes a memory 50 and a processor 51. When the processor 51 executes the program stored in the memory 50, it can implement the method for selecting resources based on a micro-frontend architecture.

[0092] Finally, the present application also provides an embodiment corresponding to a computer-readable storage medium. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps recorded in the above method embodiment are implemented.

[0093] It can be understood that if the method in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of this 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 various embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs that can store program codes.

[0094] The above has introduced in detail a method, device, equipment, and medium for selecting resources based on a micro-frontend architecture provided by the present application. The various embodiments in the specification are described in a progressive manner, and the key point of each embodiment is to illustrate the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method part. It should be noted that for those of ordinary skill in the art in this technical field, without departing from the principle of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

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

Claims

1. A method for selecting a resource pool based on a micro-frontend architecture, characterized in that Applied to a cloud management platform, including: Obtain user information in the main application through an ajax interface; Judge whether the user identity is an operation and maintenance user according to the user information; If the user identity is the operation and maintenance user, judge whether the resource pool information is contained in the database of the cloud management platform and whether the routing source is a third-party sub-application; set the switching resource pool window containing the resource pool information of the third-party sub-application at the top of the navigation bar; When the resource pool information is not contained in the database and the routing source is not the third-party sub-application, enter the resource pool selection page; the resource pool selection page contains the resource pool information and the entry of the resource pool.

2. The method for selecting a resource pool based on a micro-frontend architecture according to claim 1, wherein When the resource pool information is not contained in the database and the routing source is not the third-party sub-application, after entering the resource pool selection page, it further includes: Display the resource pool information table through a table; Obtain the resource pool information selected by the operation and maintenance user and store the resource pool information in the database, and return to the step of obtaining user information in the main application through the ajax interface.

3. The method for selecting a resource pool based on a micro-frontend architecture according to claim 2, wherein After obtaining the resource pool information selected by the operation and maintenance user and storing the resource pool information in the database, it further includes: Display the menu information of the sub-application and the switching resource pool window.

4. The method for selecting a resource pool based on a micro-frontend architecture according to claim 3, wherein Display the resource pool information in the switching resource pool window in a pop-up window.

5. The method for selecting a resource pool based on a micro-frontend architecture according to claim 1, wherein When the resource pool information is contained in the database and the routing source is not the third-party sub-application, access the sub-application in the database of the cloud management platform.

6. The method for selecting a resource pool based on a micro-frontend architecture according to claim 1, wherein When the resource pool information is not contained in the database and the routing source is the third-party sub-application, access the third-party sub-application.

7. The method for selecting a resource pool based on a micro-frontend architecture according to claim 1, wherein The switching resource pool window is displayed as a switching identifier.

8. A resource pool selection device based on a micro-frontend architecture, characterized in that, Applied to the resource pool selection method based on the micro-frontend architecture according to any one of claims 1 to 7, including: An acquisition module for obtaining user information in the main application through an ajax interface; A first judgment module for judging whether the user identity is an operation and maintenance user according to the user information; A second judgment module for, if the user identity is the operation and maintenance user, judging whether the resource pool information is contained in the database of the cloud management platform and whether the routing source is a third-party sub-application; setting the switching resource pool window containing the resource pool information of the third-party sub-application at the top of the navigation bar; An entry module for entering the resource pool selection page when the resource pool information is not contained in the database and the routing source is not the third-party sub-application; the resource pool selection page contains the resource pool information and the entry of the resource pool.

9. A device for selecting resources based on a micro-frontend architecture, characterized in that, Including: A memory for storing a computer program; A processor for implementing the steps of the resource pool selection method based on the micro-frontend architecture according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor, the steps of the resource pool selection method based on the micro-frontend architecture according to any one of claims 1 to 7 are implemented.

Images