Middleware management system and method, storage medium and computer program product

Abstract

The invention discloses a middleware management system and method, a storage medium and a computer program product. The method comprises the steps that a middleware control module is used for receiving a middleware operation instruction initiated by a target object; determining a deployment mode of the target middleware according to the running state information in the middleware operation instruction, wherein the type of the deployment mode comprises a container cloud deployment mode, a virtual machine deployment mode or a physical machine deployment mode; determining a target middleware resource management module corresponding to the deployment mode of the target middleware from a plurality of middleware resource management modules, and sending the middleware operation instruction to the target middleware resource management module; and the target middleware resource management module is used for executing corresponding management operation on the resource information of the target middleware according to the operation information in the middleware operation instruction. According to the method and the device, the technical problem that all middleware in different deployment modes in a network cannot be managed in a centralized manner in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a middleware management system and method, a storage medium, and a computer program product. Background Art

[0002] Middleware is software commonly used in various computer systems, including distributed cache middleware (such as Redis), distributed messaging and streaming computing middleware (such as Kafka), etc. These middleware are often incubated in the open source community and enter the mature stage after multiple version iterations, thus being widely used in the industry. At present, middleware software can be run in a variety of ways, such as host deployment, virtual machine deployment, and container deployment. Therefore, the unified resource management methods for specific middleware usually include the following:

[0003] (1) The resource supply department shall uniformly install and deploy middleware software, uniformly carry out capacity management, configuration management, operation and maintenance management and other operational work, and provide resources to users in a tenant manner, hereinafter referred to as the multi-tenant model;

[0004] (2) The resource supply department provides a unified installation template, and the user deploys and manages the resources according to the installation template after the resources are ready, which is hereinafter referred to as the independent operation mode;

[0005] (3) The resource supply department shall uniformly carry out resource management, deployment, operation and other activities, and open API (Application Programming Interface) functions based on middleware capabilities. Users shall directly call the API to complete the use of the middleware platform, which is hereinafter referred to as the serverless model.

[0006] In these three modes, the basic idea is a top-down management mode, that is, the unified supply of resources must be improved before unified management can be achieved. Since resources are highly dynamic with the iteration of the middleware software itself, on the one hand, it is a lot of work to integrate and benchmark the resources of the middleware in general scenarios; on the other hand, the integration, benchmarking and upgrading work needs to be continued and iterated, which will generate additional maintenance workload.

[0007] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0008] The embodiments of the present application provide a middleware management system and method, storage medium, and computer program product to at least solve the technical problem that related technologies cannot centrally manage all middlewares with different deployment modes in a network.

[0009] According to one aspect of an embodiment of the present application, a middleware management system is provided, comprising: the middleware management system comprises: a middleware control module, and multiple middleware resource management modules matching different deployment modes of the middleware, wherein the middleware control module is used to receive a middleware operation instruction initiated by a target object, wherein the middleware operation instruction carries at least operation information of the target object on the target middleware and running status information of the target middleware, and the running status information includes at least one of the following: process identifier, port number, service status; determining the deployment mode of the target middleware according to the running status information in the middleware operation instruction, wherein the types of deployment modes include: container cloud deployment mode, virtual machine deployment mode or physical machine deployment mode; determining the target middleware resource management module corresponding to the deployment mode of the target middleware from multiple middleware resource management modules, and sending the middleware operation instruction to the target middleware resource management module; the target middleware resource management module is used to perform corresponding management operations on the resource information of the target middleware according to the operation information in the middleware operation instruction, wherein the resource information includes at least one of the following: middleware version information, parameter configuration file information, running status information.

[0010] Optionally, the target middleware resource management module is a first middleware resource management module corresponding to the container cloud deployment method, wherein the first middleware resource management module is used to determine the target operation unit for managing the target middleware based on the middleware operation instruction, wherein the first middleware resource management module includes: multiple operation units for managing multiple middleware of different types and versions deployed in a container image manner; and a target operation unit for responding to the middleware operation instruction to perform corresponding management operations on the resource information of the target middleware.

[0011] Optionally, the middleware control module is also used to determine an operation script template corresponding to the operation information in the middleware operation instruction from a preset operation script library, and fill the operation status information of the target middleware into the operation script template to obtain a target operation script, wherein the operation script library stores multiple operation information and corresponding operation script templates, and the operation information includes at least one of the following: a new operation, an operation status change operation; sending the target operation script to the target middleware resource management module; the target middleware resource management module is also used to execute the target operation script to perform corresponding management operations on the resource information of the target middleware.

[0012] Optionally, the target middleware resource management module is a second middleware resource management module corresponding to the physical machine deployment method, wherein the second middleware resource management module is used to determine the first target agent unit used to manage the target middleware based on the target operation script, wherein the second middleware resource management module includes: multiple first agent units for managing multiple middleware deployed in the form of software packages and / or operating system images, and each first agent unit is deployed in the same resource space as the corresponding middleware; the first target agent unit is used to execute the target operation script to perform corresponding management operations on the resource information of the target middleware.

[0013] Optionally, the target middleware resource management module is a third middleware resource management module corresponding to the virtual machine deployment method, and the target operation script also includes: an access password for the target object to access the operating system where the target middleware is located, wherein the third middleware resource management module is used to determine the second target agent unit for managing the target middleware based on the target operation script, wherein the third middleware resource management module includes: at least one second agent unit for managing at least one middleware deployed in the form of a software package and / or an operating system image, and each second agent unit is deployed in the same resource space as the corresponding middleware; a second target agent unit is used to determine whether the target object has management operation permissions for the target middleware; if the target object has management operation permissions for the target middleware, execute the target operation script to perform corresponding management operations on the resource information of the target middleware.

[0014] Optionally, the middleware control module is also used to obtain access passwords for multiple users to access the operating systems where multiple middlewares managed by the second agent units in the third middleware resource management module are located; encrypt each access password using a preset encryption key to obtain a corresponding encrypted ciphertext; transmit the encrypted ciphertext corresponding to the access password for each user to access the operating system where each middleware is located to the second agent unit to which each middleware belongs; each second agent unit is also used to decrypt the encrypted ciphertext corresponding to the access password for the user to access the operating system where the corresponding middleware is located using a preset decryption method to obtain the access password for the user to access the operating system where the corresponding middleware is located, and re-encrypt the access password for the user to access the operating system where the corresponding middleware is located according to a customized encryption method to obtain a new encrypted ciphertext and store it.

[0015] Optionally, the middleware operation instructions and the target operation script also include: an access password for the target object to access the operating system where the target middleware is located, wherein the second target agent unit is also used to decrypt the new encrypted ciphertext corresponding to the access password for the target object to access the operating system where the target middleware is located, and determine whether the decrypted access password matches the access password in the target operation script. When the decrypted access password matches the access password in the target operation script, it is determined that the target object has management operation permissions for the target middleware.

[0016] According to another aspect of an embodiment of the present application, a middleware management method is also provided, which is applied to the above-mentioned middleware control module, including: receiving a middleware operation instruction initiated by a target object, wherein the middleware operation instruction carries at least operation information of the target object on the target middleware and running status information of the target middleware, and the running status information includes at least one of the following: process identifier, port number, service status; determining the deployment mode of the target middleware according to the running status information in the middleware operation instruction, wherein the types of deployment modes include: container cloud deployment mode, virtual machine deployment mode or physical machine deployment mode; determining a target middleware resource management module corresponding to the deployment mode of the target middleware from multiple middleware resource management modules, and sending the middleware operation instruction to the target middleware resource management module, wherein the multiple middleware resource management modules are respectively matched to different deployment modes, and the target middleware resource management module is used to perform corresponding management operations on the resource information of the target middleware according to the operation information in the middleware operation instruction, and the resource information includes at least one of the following: middleware version information, parameter configuration file information, running status information.

[0017] According to another aspect of an embodiment of the present application, a non-volatile storage medium is further provided, the non-volatile storage medium including a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned middleware management method by running the computer program.

[0018] According to another aspect of an embodiment of the present application, a computer program product is further provided. The computer program product includes a stored computer program, wherein the computer program implements the above-mentioned middleware management method when executed by a processor.

[0019] In an embodiment of the present application, first, the middleware control module receives the middleware operation instruction initiated by the target object, wherein the middleware operation instruction carries at least the operation information of the target object on the target middleware and the running status information of the target middleware, and the running status information includes at least one of the following: process identifier, port number, service status; then, the middleware control module determines the deployment mode of the target middleware according to the running status information in the middleware operation instruction, wherein the types of deployment modes include: container cloud deployment mode, virtual machine deployment mode or physical machine deployment mode; then, the middleware control module determines the target middleware resource management module corresponding to the deployment mode of the target middleware from multiple middleware resource management modules, and sends the middleware operation instruction to the target middleware resource management module; finally, the target middleware resource management module performs corresponding management operations on the resource information of the target middleware according to the operation information in the middleware operation instruction, wherein the resource information includes at least one of the following: middleware version information, parameter configuration file information, running status information. Therefore, the embodiments of the present application realize unified management of middleware resources under different deployment modes by adopting intelligent identification and adaptation of middleware resource management operations under different deployment modes, thereby achieving the purpose of simplifying the operation and maintenance process, improving management efficiency and enhancing resource control capabilities, and thus solving the technical problem that related technologies cannot centrally manage all middleware with different deployment modes in the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] Figure 1 is a schematic diagram of the structure of an optional middleware management system according to an embodiment of the present application;

[0022] Figure 2 is a schematic diagram of the structure of another optional middleware management system according to an embodiment of the present application;

[0023] Figure 3 is a schematic diagram of an optional middleware management interface in a virtual machine deployment manner according to an embodiment of the present application;

[0024] Figure 4 is a schematic diagram of an overview dashboard of an optional middleware control module according to an embodiment of the present application;

[0025] Figure 5 is a schematic diagram of an optional performance overview of a Redis instance according to an embodiment of the present application;

[0026] Figure 6It is a schematic diagram of an optional process of analyzing the abnormality of a middleware instance according to an embodiment of the present application;

[0027] Figure 7 is a flow chart of an optional middleware management method according to an embodiment of the present application;

[0028] Figure 8 It is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] In addition, the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. For example, an interface is set up between this system and the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0032] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0033] Middleware: It is a type of software between the application system and the system software. It uses the basic services (functions) provided by the system software to connect the various parts of the application system or different applications on the network, and can achieve the purpose of resource sharing and function sharing. Therefore, middleware can be regarded as an independent system software service program. Distributed application software uses this software to share resources between different technologies. Middleware is located above the operating system, network and database of the client server to manage computing resources and network communications. The overall role is to provide an operating and development environment for the application software at the upper layer, helping users to flexibly and efficiently develop and integrate complex application software.

[0034] Example 1

[0035] According to an embodiment of the present application, an embodiment of a middleware management system is provided. Figure 1 is a schematic diagram of the structure of an optional middleware management system according to an embodiment of the present application, such as Figure 1 As shown, the system 10 includes: a middleware control module 12, and multiple middleware resource management modules 14 that match different deployment modes of the middleware. The middleware control module 12 and the multiple middleware resource management modules 14 can manage the middleware according to the following interactive process, including:

[0036] First, the middleware control module 12 may first receive the middleware operation instruction initiated by the target object. The middleware operation instruction at least carries the operation information of the target object on the target middleware and the operation status information of the target middleware, and the operation status information includes at least one of the following: process ID, port number, service status;

[0037] Next, the middleware control module 12 determines the deployment mode of the target middleware according to the running status information in the middleware operation instruction, wherein the types of deployment modes include: container cloud deployment mode, virtual machine deployment mode or physical machine deployment mode;

[0038] Then, the middleware control module 12 determines the target middleware resource management module 14 corresponding to the deployment mode of the target middleware from the multiple middleware resource management modules 14, and sends the middleware operation instruction to the target middleware resource management module 14i;

[0039] Finally, the target middleware resource management module 14i is used to perform corresponding management operations on the resource information of the target middleware according to the operation information in the middleware operation instruction, wherein the resource information includes at least one of the following: middleware version information, parameter configuration file information, and operation status information.

[0040] That is to say, the above-mentioned middleware control module 12 interacts with the user to receive the operation information of the specified middleware sent by the user, and determines the deployment method of the user-specified middleware according to the pre-set deployment methods of different middlewares, and uses the corresponding middleware resource management module to manage the user-specified middleware, thereby realizing automatic perception of all middleware resources scattered on various network nodes on the network and centralized management of these middleware resources.

[0041] In order to facilitate the understanding of the principle of the above-mentioned middleware management system to manage middleware, Figure 2 The schematic diagram of the architecture of the middleware management system shown in the figure illustrates the functions and structures of the above modules.

[0042] Specifically, the middleware control module 12, namely Figure 2 The middleware management and control platform C is a user interaction component in the middleware management system 10. It not only undertakes the responsibility of observing, managing and controlling all middleware resources in multiple middleware resource management modules 14 (that is, each controlled object reports its own operating status, configuration information, management status and other data to the middleware management and control platform C in real time or regularly), but also can provide managers with resource status display, centralized operation and management and other functions.

[0043] Generally speaking, the cloud management platform itself has the function of aggregating resource management, so the middleware control module 12 (i.e., the middleware management control platform C) can implement the corresponding functions by organizing and calling the specific API of the cloud management platform. For example, the middleware control module 12 cyclically calls the interface provided by the cloud management platform, and simultaneously obtains the operating configuration parameters of all certain middleware resources under certain specific namespaces. For different types of middleware resources, their operating modes and operating interfaces are quite different. Therefore, if the middleware control module 12 provides similar functions for the management of different middleware resources, or provides information aggregated from different middleware information, it is necessary to logically combine the APIs for different middleware resources on the middleware control module 12.

[0044] Specifically, the middleware control module 12 may first receive the middleware operation instruction initiated by the target object. The middleware operation instruction at least carries the operation information of the target object on the target middleware (such as creating a middleware instance, deleting a middleware instance, modifying middleware configuration parameters, etc.), the running status information of the target middleware, and the running status information includes but is not limited to: process identifier (i.e., process name), port number, service status (i.e., whether the middleware component is enabled), etc.

[0045] Next, after receiving the middleware operation instruction sent by the target object, the middleware control module 12 may parse the instruction to obtain the operation information and running status information therein.

[0046] Then, the middleware control module 12 determines the deployment mode of the target middleware according to the running status information in the middleware operation instruction, wherein the types of deployment modes include: container cloud deployment mode, virtual machine deployment mode or physical machine deployment mode.

[0047] Since the running status information may contain identifiers specific to different deployment methods (or deployment environments), such as namespaces, labels, annotations, etc., these identifiers may be specific to container cloud deployment, such as Kubernetes namespaces and labels, or custom labels used for resource identification in virtual machine or physical machine environments. Therefore, if the running status information contains identifiers specific to container cloud, such as Kubernetes namespaces, service names, container images, and version information, the middleware control module 12 identifies that the target middleware is deployed in a container cloud; if the running status information contains identification information of the virtual machine, such as the virtual machine ID, metadata of the virtual machine management platform (such as OpenStack), and the virtual machine IP address, the module 12 identifies that the target middleware is deployed in a virtual machine; if the running status information directly relates to information about the host, such as the host name, host IP address, operating system process information, etc., and these information do not point to resource identifiers of any container cloud or virtual machine platform, the middleware control module 12 can determine that the target middleware is deployed in a physical machine.

[0048] It should be noted that module 12 may also check the API of the container cloud platform to confirm whether the target object exists in the resource list of the container cloud platform to further verify its deployment method. Alternatively, the virtual machine resource database may be checked to verify whether the target object is registered and running on the corresponding virtual machine resource platform.

[0049] Finally, the middleware control module 12 determines the target middleware resource management module corresponding to the deployment mode of the target middleware from the multiple middleware resource management modules, and sends the middleware operation instruction to the target middleware resource management module 14i.

[0050] That is, once the middleware control module 12 determines the deployment mode of the target middleware, it will continue to determine the target middleware resource management module 14i corresponding to the deployment mode of the target middleware, and send the middleware operation instruction to the target middleware resource management module 14i.

[0051] In an exemplary embodiment, if multiple business applications in a distributed system rely on the middleware Redis (a powerful memory data structure storage, usually used as a database, cache and message agent) to store and retrieve key data, these Redis instances may be deployed in different containers and managed by Kubernetes (i.e., container orchestration platform). Business application administrators or system operation and maintenance personnel can submit an operation instruction through the user interface or API of the container cloud platform to adjust the configuration of a specific Redis instance, such as increasing the memory allocation of the Redis instance, and the operation instruction contains at least operation information and operation status information, wherein the operation information can be "increase memory allocation"; the operation status information can clearly indicate that the process ID of the target Redis instance is 1234, the port number is 6379, the current service status is running, the namespace of Kubernetes, etc. Then, the middleware control module 12 receives and parses the instruction, and identifies that the Redis deployment method is a container cloud deployment method by analyzing the Kubernetes namespace in the running status information, so a request to adjust resources is sent to the middleware resource management module corresponding to the container cloud deployment method, and the specific request is to increase the memory resources of the target Redis instance.

[0052] Optionally, the plurality of middleware resource management modules 14 include: a first middleware resource management module 141 corresponding to the container cloud deployment mode, that is, Figure 2 The container cloud resource operation platform in the container, such as the container cloud management platform based on K8S. Among them, container cloud deployment refers to the deployment of middleware software through container images. Therefore, the first middleware resource management module includes: multiple operation units 141m (m∈[1,M]) for managing multiple middleware of different types and versions deployed in the form of container images, that is, Figure 2 Operator is an extension software of Kubernetes. It can extend the standard API of Kubernetes through CRD (Custom Resource Definition) to provide more advanced automated operation and management functions for specific applications or services.

[0053] Therefore, the middleware resources deployed in the container cloud mode provide a custom interface that can be operated and observed externally for general middleware resources in the orchestration definition stage through user resource definition CRD and other methods. After the user-defined resource (Custom Resource, CR) is injected into the first middleware resource management module 141 (i.e., the container cloud resource operation platform), it is called by the first middleware resource management module 141 (such as K8S calling through apiserver), and its custom extended functional scope (such as the start and stop, expansion and contraction of middleware components, data migration operations, etc.) is integrated with the middleware control module 12 to complete the control instructions issued by the middleware control module, and remotely operate various types of middleware objects through the interface of the first middleware resource management module 141. At the same time, multiple operation units 141m (i.e., the Operator of each middleware resource) can each monitor the user-defined resource events of the controlled middleware, such as resource creation and destruction, operation status change, error handling, tuning, etc., and respond to these user-defined resource events to make predetermined actions. That is, multiple operation units 141m implement interaction with user-defined resource events to automatically manage and operate the resources of the middleware they control. For example, when an operation unit monitors the custom resource creation event of the distributed cache middleware Redis it manages, it is responsible for implementing the specific logic of the creation through the controller.

[0054] In addition, different types and versions of middleware resources can write user resource definitions and operators with similar target functions but different implementation methods, thus forming the cloud middleware operator group B. The organizational management responsibilities of the cloud middleware operator group B are completed by the container cloud resource operation platform D (i.e., the first middleware resource management module). Through B, the cloud middleware operator group can automatically complete the full life cycle management and status observation of custom resources based on the general middleware through API operations.

[0055] Specifically, if the target middleware resource management module 14i is the first middleware resource management module 141 corresponding to the container cloud deployment mode, it can perform corresponding management operations on the middleware according to the following steps, including:

[0056] Step 1: The first middleware resource management module 141 first determines the target operation unit 141m for managing the target middleware according to the middleware operation instruction;

[0057] Step 2: The target operation unit 141m responds to the middleware operation instruction to perform corresponding management operations on the resource information of the target middleware.

[0058] Optionally, the multiple middleware resource management modules 14 include: a second middleware resource management module 142 corresponding to the physical machine deployment method, that is, a physical machine (or host machine). Among them, the physical machine deployment method is that the middleware is directly deployed on the host, and because the host resources are relatively abundant, a host can deploy multiple types of middleware at the same time. Therefore, the second middleware resource management module 142 includes multiple first agent units 142n (n∈[1,N]) for managing multiple middleware deployed in the form of software packages and / or operating system images. In addition, each first agent unit 142n is deployed in the same resource space as the controlled middleware, that is, each first agent unit 142n and the controlled object "middleware software" can be in the same user group with the same permissions, or a user group with a higher permission level, so that the first agent unit 142n can access the relevant files involved in the controlled object.

[0059] Specifically, if the target middleware resource management module 14i is the second middleware resource management module 142 corresponding to the physical machine deployment mode, it can perform corresponding management operations on the middleware according to the following steps, including:

[0060] Step 1: The middleware control module 12 can first determine the operation script template corresponding to the operation information in the middleware operation instruction from the preset operation script library, and fill the operation status information of the target middleware into the corresponding position in the operation script template to obtain the target operation script that can be recognized by the operating system on the physical machine. Among them, the above-mentioned operation script library stores a plurality of pre-defined operation information and corresponding operation script templates, and the operation information includes but is not limited to: new operation, operation status change operation, parameter adjustment operation, recovery operation, upgrade operation, etc. For example, for the operation of creating a new Redis instance, module 12 will search for the script template of "creating a new Redis instance" and fill in parameters such as version number, memory size, disk path, network port, etc. to obtain the target operation script.

[0061] Step 2: The middleware control module 12 sends the target operation script to the second middleware resource management module 142. The target operation script can be sent to the second middleware resource management module via a network protocol (such as HTTP, gRPC);

[0062] Step 3: The second middleware resource management module 142 determines the first target agent unit 142n for managing the target middleware according to the target operation script;

[0063] Step 4: The first target agent unit 142n executes the target operation script to perform corresponding management operations on the resource information of the target middleware, such as creating, restarting, and modifying configuration.

[0064] Optionally, the plurality of middleware resource management modules 14i include: a third middleware resource management module 143 corresponding to the virtual machine deployment mode, namely Figure 2 The physical machine deployment method is that the middleware software is deployed through a software package or an operating system image, and is operated and orchestrated through the virtual machine resource operation platform. However, since the virtual machine has fewer resources that can be run and its responsibilities are relatively simple, only one or a few middleware software are run in most scenarios. Therefore, the third middleware resource management module 143 includes: at least one second agent unit 143k (k∈[1,K]) for managing at least one middleware deployed in the form of a software package and / or an operating system image. In addition, each second agent unit 143k is deployed in the same resource space as the controlled middleware, that is, each second agent unit 143k and the controlled object "middleware software" can be in the same user group with the same permissions, or in a user group with a higher permission level, so that the second agent unit 143k can access the relevant files involved in the controlled object.

[0065] Specifically, if the target middleware resource management module 14i is the third middleware resource management module 143 corresponding to the virtual machine deployment mode, it can perform corresponding management operations on the middleware according to the following steps, including:

[0066] Step 1: The middleware control module 12 can first determine the operation script template corresponding to the operation information in the middleware operation instruction from the preset operation script library, and fill the operation status information of the target middleware into the corresponding position in the operation script template to obtain the target operation script that can be recognized by the operating system on the physical machine. Among them, the above-mentioned operation script library stores a plurality of pre-defined operation information and corresponding operation script templates, and the operation information includes but is not limited to: new operation, operation status change operation, parameter adjustment operation, recovery operation, upgrade operation, etc.

[0067] Step 2: The middleware control module 12 sends the target operation script to the third middleware resource management module 143. The target operation script can be sent to the third middleware resource management module via a network protocol (such as a hypertext transfer protocol HTTP, etc.);

[0068] Step 3: The third middleware resource management module 143 determines the second target agent unit 143k for managing the target middleware according to the target operation script;

[0069] Step 4: The second target agent unit 143k determines whether the target object has management operation authority for the target middleware;

[0070] Step 5: When the target object has the management operation authority for the target middleware, the second target agent unit 143k executes the target operation script to perform corresponding management operations on the resource information of the target middleware.

[0071] That is to say, if a target middleware software needs to be deployed in the virtualized operating system, a second agent unit 143k (i.e. Figure 2 The centralized middleware management application agent A) is configured to run in the same user environment as the proxied target middleware software, so that the second agent unit 143k can perform operations such as file reading and writing, status acquisition and control on the target middleware software through operating system command lines, scripts, etc. For example, a user clicks an operation button on the middleware control module 12, such as "obtain configuration information of the target middleware software". At this time, the middleware control module 12 can convert the operation action into an operation number, and find the corresponding operation script or operation command line according to the operation number, and send it to the second agent unit 143k, and the second agent unit 143k executes it. It should be noted that the correspondence between the operation number and the operation action (script / instruction line) is generally maintained on the middleware control module 12, and the second agent unit 143k can supplement the input of the local system environment variables into the script or instruction.

[0072] In addition, the extended functional scope of the second agent unit 143k is integrated with the middleware control module 12, completing the control instructions issued by the middleware control module 12, and operating the remote call interface of the second agent unit 143k to operate the middleware in the same resource space as the second agent unit 143k. Therefore, the second agent unit 143k can assume the responsibility of a bridge between the middleware control module 12 and the controlled middleware resources. That is, the second agent unit 143k can use certain authority requirements and control logic to perform resource management (including creation, migration and deletion, etc.), parameter inspection and configuration, and operation status control on the controlled object "middleware" through user instructions, and actively report the static configuration data and dynamic operation data of the middleware to the middleware control module 12 on a regular basis.

[0073] Therefore, when the target middleware resource management module 14i is the second middleware resource management module 142 and the third middleware resource management module 143, the middleware control module 12 can intelligently select and generate operation scripts for specific operations and specific middleware resources, ensuring that the operation instructions are accurately executed while maintaining the consistency and standardization of the operations. This mechanism improves the automation of middleware management, reduces the workload of operation and maintenance, and also enhances the flexibility and scalability of the middleware control module 12 when processing middleware resources of different types and deployment methods.

[0074] Furthermore, for middleware deployed in a virtual machine manner, in order to securely access such middleware resources, the user passwords of the operating systems where the middleware is deployed need to be centrally configured by the middleware control module 12 in advance and stored in encrypted form on each second agent unit 143k. Therefore, the middleware control module 12 and each second agent unit 143k can obtain the user access password according to the following interactive process, including:

[0075] First, the middleware control module 12 obtains access passwords (ie, user accounts and passwords for logging into corresponding operating systems) for multiple users to access the operating systems where multiple middlewares managed by the second agent units in the third middleware resource management module are located.

[0076] Next, the middleware control module 12 encrypts each access password using a preset encryption key to obtain a corresponding encrypted ciphertext.

[0077] Then, the middleware control module 12 transmits the encrypted ciphertext corresponding to the access password of each user to access the operating system where each middleware is located to the second agent unit 143k to which each middleware belongs.

[0078] Finally, for each second agent unit 143k, the second agent unit 143k can use a preset decryption method to decrypt the encrypted ciphertext corresponding to the access password for the user to access the operating system where the corresponding middleware is located, obtain the access password for the user to access the operating system where the corresponding middleware is located, and re-encrypt the access password for the user to access the operating system where the corresponding middleware is located according to a customized encryption method, obtain a new encrypted ciphertext and store it.

[0079] The above encryption key and decryption key are obtained by an encryption method (such as self-signed certificate verification) pre-negotiated between the middleware control module 12 and each second agent unit 143k. Therefore, the encryption key and decryption key between the middleware control module 12 and each second agent unit can be the same or different. Similarly, the customized encryption methods of each second agent unit 143k can be the same or different.

[0080] Generally, each second agent unit 143k may store the obtained new encrypted ciphertext, and directly decrypt and unload it locally when in use, so as to be used when the second agent unit 143k executes the operation script.

[0081] Specifically, when the target middleware resource management module 14i is the second middleware resource management module 142 and the third middleware resource management module 143, the middleware operation instruction obtained by the middleware control module 12 also includes the target access password for the target object to access the operating system where the target middleware is located. Then the target operation script written by the middleware control module 12 according to the middleware operation instruction also includes the target access password for the target object to access the operating system where the target middleware is located.

[0082] In this case, the second agent unit 143k can use the above-mentioned pre-stored new encrypted ciphertext to perform permission authentication in the following method, including: the second target agent unit first decrypts the new encrypted ciphertext corresponding to the access password of the target object to the operating system where the target middleware is located; then determines whether the decrypted access password matches the access password in the target operation script. If the decrypted access password matches the access password in the target operation script, it is determined that the target object has management operation permissions for the target middleware.

[0083] That is to say, the second agent unit 143k has full access to any required data of the proxied middleware resources. If the middleware resources actively sensed by the second agent unit 143k have been configured with passwords, the user usually needs to confirm the password on the middleware control module 12, put it into unified management, and transmit it to the centralized middleware management application agent A for storage in encrypted form.

[0084] In addition, according to the requirements of the full life cycle management, the second agent unit 143k can also pull the standard middleware resource version from the middleware control module 12 according to the user's instructions, and deploy it in the local path of the second agent unit 143k, so as to realize the operations such as upgrading and automatic update deployment on the original basis, such as Figure 3 shown.

[0085] Furthermore, after managing all the middleware resources in the network through the above-mentioned proxy units and operation units, the middleware control module 12, as a user interaction component, can also provide an overview dashboard of various middlewares, wherein the overview dashboard counts and displays the instance quantity distribution, controller quantity and status distribution, proxy software quantity and status distribution, etc. of middlewares such as Redis, Kafka, ElasticSearch, MySQL, etc. through multi-dimensional statistics, such as Figure 4As shown. The middleware in the above overview dashboard can exist in various deployment modes. For example, Redis can be in stand-alone, master-slave, sentinel or cluster mode. It can also be deployed in containerization, virtualization, etc. Regardless of the operation mode, users can clearly understand the scale and usage of various middleware in the current infrastructure, which is convenient for overall grasp of resource allocation and provides accurate data support for subsequent resource planning, expansion or reduction.

[0086] in addition, Figure 5 is an optional performance overview diagram of a Redis instance, such as Figure 5 As shown. The performance overview includes collecting Redis information from each cluster in the form of cloud operators and off-cloud agents, integrating and presenting key status information of all Redis instances in the cluster. It intuitively displays the instance distribution, version distribution, and physical resource usage, including core resource indicators such as the total CPU, total memory, and total hard disk of all instances. This enables centralized, efficient, and detailed management of Redis instances. At the same time, the performance overview chart can systematically collect and extract real-time monitoring data for each Redis instance, and highlight the top 10 performance indicators, including CPU (central processing unit) usage, memory usage, memory usage, number of connections, number of requests, and network bandwidth usage, which facilitates administrators to grasp the hot Redis instances in the cluster in real time, and can also effectively warn of performance anomalies and explore potential optimization space.

[0087] At the same time, considering the existing middleware (such as Redis instance) operation and maintenance management system, due to the fact that the parameter configuration of the middleware instance may be significantly different from the verified parameter baseline during the actual operation, and this difference may lead to performance degradation, resource waste and even system stability risks. However, there is currently a lack of effective management tools and means to conduct a comprehensive review and precise correction of parameter configuration. To this end, the middleware control module 12 can also display the predefined parameter templates of each middleware, and the parameter template can be customized according to the actual scenario requirements of the user; at the same time, the middleware control module 12 can also fill in the configuration parameters pulled from the operation unit Operator B and the centralized middleware management application agent A into the corresponding parameter template, so as to systematically compare the batch parameters of each middleware (such as cache elimination parameters, data retention backup parameters, queue length, etc.), and display the comparison results of the batch parameters of each middleware with the corresponding middleware baseline, so as to intuitively display the configuration differences of each middleware in different parameters.

[0088] Among them, the associated parameter baseline templates of each middleware instance are based on best practices and experience summaries (i.e., defined by expert experience and combined with industry experience), and are intended to provide a benchmark reference for the rapid deployment and maintenance of middleware instances, ensuring that the preset service performance standards and resource utilization efficiency can be achieved in different scenarios. In addition, considering the diversity of the actual environment and the personalized needs of the business, it also supports managers to flexibly customize the parameter baseline templates according to specific business scenarios and actual load characteristics to create custom templates that meet their own needs. This can take into account both standardization and adapting to changing application requirements, making the middleware instance parameter configuration more accurate and controllable, and effectively reducing the risks and problems caused by improper parameter settings.

[0089] In addition, the middleware control module 12 systematically reveals the differences in parameter configurations by comparing and analyzing all the globally running middleware instances or some specified middleware instances with their associated parameter baseline templates or specific parameter sets one by one, and generates a detailed difference comparison report and parameter difference details for each instance level. The specific process is as follows: Figure 6 As shown in the figure, administrators can not only easily find out which instances have deviated from the optimal parameter configuration baseline, but also quickly identify specific parameter differences to make targeted optimization adjustments to ensure that middleware instances always maintain an efficient, stable, and secure operating state. This solves the technical problem of the existing middleware operation and maintenance management system that there is no rationality verification and potential problems for the parameter configuration of the running instance.

[0090] In summary, the middleware management system 10 provided in the embodiment of the present application has the following advantages over the traditional middleware management system:

[0091] (1) The middleware management system 10 provided in the embodiment of the present application can centrally and uniformly manage middleware resources of various deployment modes such as container cloud deployment and virtual machine deployment, and these resources can be centrally observed and operated, and provide users with a consistent operation experience;

[0092] (2) The middleware management system 10 provided in the embodiment of the present application can manage other middleware resources that are originally outside the middleware control plane C, and bring the previously existing "wild" resources into unified management through automatic perception and active registration;

[0093] (3) The operation units and proxy units in the middleware management system 10 provided in the embodiment of the present application are more universal, so there is no need to maintain multiple versions for different types of middleware, which makes the control plane have stronger management capabilities for each unit. Therefore, the middleware management system provided in the embodiment of the present application is more efficient in management scenarios with large-scale middleware usage, a large number of versions, and a wide variety of middleware.

[0094] In addition, based on the above-mentioned middleware management system 10, the embodiment of the present application also provides a method embodiment of the middleware management method applied to the above-mentioned middleware control module 12. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here.

[0095] Figure 7 is a flow chart of an optional middleware management method according to an embodiment of the present application, such as Figure 7 As shown, the method at least includes steps S702-S707, wherein:

[0096] Step S702: receiving a middleware operation instruction initiated by the target object.

[0097] In the technical solution provided in step S702, the middleware operation instruction carries at least the operation information of the target object on the target middleware and the running status information of the target middleware, and the running status information includes at least one of the following: process identifier, port number, service status.

[0098] Step S704: determining the deployment mode of the target middleware according to the running status information in the middleware operation instruction.

[0099] In the technical solution provided in step S704, the types of the above-mentioned deployment methods include: container cloud deployment method, virtual machine deployment method or physical machine deployment method.

[0100] Step S707 , determining a target middleware resource management module corresponding to the deployment mode of the target middleware from among the multiple middleware resource management modules, and sending the middleware operation instruction to the target middleware resource management module.

[0101] In the technical solution provided in step S707, multiple middleware resource management modules are matched to different deployment modes. The target middleware resource management module is used to perform corresponding management operations on the resource information of the target middleware according to the operation information in the middleware operation instruction, and the resource information includes at least one of the following: middleware version information, parameter configuration file information, and operation status information.

[0102] Based on the scheme defined by the above steps S702 to S707, it can be known that, in an embodiment, the middleware control module uses the middleware control module to intelligently identify and adapt middleware resource management operations under different deployment modes, thereby achieving the technical effect of unified middleware resource management across container clouds, virtual machines and physical machine deployment environments, and achieving the purpose of simplifying the operation and maintenance process, improving management efficiency and enhancing resource control capabilities.

[0103] Example 2

[0104] According to an embodiment of the present application, a non-volatile storage medium is further provided, in which a program is stored, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the middleware management method in Example 1.

[0105] According to an embodiment of the present application, a computer program product is also provided. The computer program product includes a stored computer program, wherein the middleware management method in Embodiment 1 is implemented when the computer program is executed by a processor.

[0106] According to an embodiment of the present application, a processor is also provided, which is used to run a program, wherein the middleware management method in Example 1 is executed when the program is running.

[0107] According to an embodiment of the present application, an electronic device is also provided, wherein the electronic device includes one or more processors; a memory for storing one or more programs, and when the one or more programs are executed by one or more processors, the one or more processors are implemented to run the programs, wherein the program is configured to execute the middleware management method in the above-mentioned embodiment 1 when running.

[0108] Optionally, when the computer program is running, the following steps are executed: receiving a middleware operation instruction initiated by a target object, wherein the middleware operation instruction carries at least operation information of the target object on the target middleware and running status information of the target middleware, and the running status information includes at least one of the following: process identifier, port number, service status; determining a deployment mode of the target middleware according to the running status information in the middleware operation instruction, wherein the types of deployment modes include: container cloud deployment mode, virtual machine deployment mode or physical machine deployment mode; determining a target middleware resource management module corresponding to the deployment mode of the target middleware from multiple middleware resource management modules, and sending the middleware operation instruction to the target middleware resource management module, wherein the multiple middleware resource management modules are respectively matched to different deployment modes, and the target middleware resource management module is used to perform corresponding management operations on the resource information of the target middleware according to the operation information in the middleware operation instruction, and the resource information includes at least one of the following: middleware version information, parameter configuration file information, running status information.

[0109] As an optional implementation, the electronic device may be in the form of a mobile terminal, a computer terminal or a similar computing device. Figure 8 FIG. 1 shows a hardware structure block diagram of an electronic device for implementing a middleware management method. Figure 8As shown, the electronic device 80 may include one or more (802a, 802b, ..., 802n are used to illustrate) processors 802 (the processor 802 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 804 for storing data, and a transmission device 806 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 8 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 8 More or fewer components as shown, or with Figure 8 Different configurations are shown.

[0110] It should be noted that the one or more processors 802 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the electronic device 80. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0111] The memory 804 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the middleware management method in the embodiment of the present application. The processor 802 executes various functional applications and data processing by running the software programs and modules stored in the memory 804, that is, realizing the vulnerability detection method of the above-mentioned application. The memory 804 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 804 may further include a memory remotely arranged relative to the processor 802, and these remote memories may be connected to the electronic device 80 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0112] The transmission device 806 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the electronic device 80. In one example, the transmission device 806 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 806 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0113] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the electronic device 80 .

[0114] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0115] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0116] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0117] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed over multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0118] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0119] If the integrated unit 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, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0120] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A middleware management system, characterized in that: The middleware management system includes: a middleware control module, and multiple middleware resource management modules matching different deployment modes of the middleware, wherein: The middleware control module is used to receive a middleware operation instruction initiated by a target object, wherein the middleware operation instruction carries at least operation information of the target object on the target middleware and operation status information of the target middleware, and the operation status information includes at least one of the following: process ID, port number, service status; determine the deployment mode of the target middleware according to the operation status information in the middleware operation instruction, wherein the types of the deployment modes include: container cloud deployment mode, virtual machine deployment mode or physical machine deployment mode; determine the target middleware resource management module corresponding to the deployment mode of the target middleware from the multiple middleware resource management modules, and send the middleware operation instruction to the target middleware resource management module; The target middleware resource management module is used to perform corresponding management operations on the resource information of the target middleware according to the operation information in the middleware operation instruction, wherein the resource information includes at least one of the following: middleware version information, parameter configuration file information, and operation status information.

2. The system according to claim 1, characterized in that The target middleware resource management module is a first middleware resource management module corresponding to the container cloud deployment mode, wherein: The first middleware resource management module is used to determine a target operation unit for managing the target middleware according to the middleware operation instruction, wherein the first middleware resource management module includes: a plurality of operation units for managing a plurality of middlewares of different types and versions deployed in a container image manner; The target operation unit is used to respond to the middleware operation instruction to perform corresponding management operations on the resource information of the target middleware.

3. The system according to claim 1, characterized in that The middleware control module is further used to determine an operation script template corresponding to the operation information in the middleware operation instruction from a preset operation script library, and fill the operation status information of the target middleware into the operation script template to obtain a target operation script, wherein the operation script library stores a plurality of operation information and corresponding operation script templates, and the operation information includes at least one of the following: a new operation, an operation status change operation; and send the target operation script to the target middleware resource management module; The target middleware resource management module is further used to execute the target operation script to perform corresponding management operations on the resource information of the target middleware.

4. The system according to claim 3, characterized in that The target middleware resource management module is a second middleware resource management module corresponding to the physical machine deployment mode, wherein: The second middleware resource management module is used to determine a first target agent unit for managing the target middleware according to the target operation script, wherein the second middleware resource management module includes: a plurality of first agent units for managing a plurality of middleware deployed in the form of software packages and / or operating system images, and each of the first agent units is deployed in the same resource space as the corresponding middleware; The first target agent unit is used to execute the target operation script to perform corresponding management operations on the resource information of the target middleware.

5. The system according to claim 3, characterized in that The target middleware resource management module is a third middleware resource management module corresponding to the virtual machine deployment mode, and the target operation script also includes: an access password for the target object to access the operating system where the target middleware is located, wherein: The third middleware resource management module is used to determine a second target agent unit for managing the target middleware according to the target operation script, wherein the third middleware resource management module includes: at least one second agent unit for managing at least one middleware deployed in the form of a software package and / or an operating system image, and each of the second agent units is deployed in the same resource space as the corresponding middleware; The second target agent unit is used to determine whether the target object has management operation authority for the target middleware; if the target object has management operation authority for the target middleware, execute the target operation script to perform corresponding management operations on the resource information of the target middleware.

6. The system according to claim 5, characterized in that The middleware control module is further used to obtain access passwords for multiple users to access the operating systems where multiple middlewares are located and which are respectively managed by the second agent units in the third middleware resource management module; encrypt each of the access passwords using a preset encryption key to obtain a corresponding encrypted ciphertext; and transmit the encrypted ciphertext corresponding to the access passwords for each of the users to access the operating systems where each of the middlewares is located to the second agent units to which each of the middlewares belongs; Each second agent unit is also used to decrypt the encrypted ciphertext corresponding to the access password of the user to access the operating system where the corresponding middleware is located using a preset decryption method, obtain the access password of the user to access the operating system where the corresponding middleware is located, and re-encrypt the access password of the user to access the operating system where the corresponding middleware is located according to a custom encryption method, obtain a new encrypted ciphertext and store it.

7. The system according to claim 6, characterized in that The middleware operation instruction and the target operation script also include: an access password for the target object to access the operating system where the target middleware is located, wherein: The second target agent unit is also used to decrypt the new encrypted ciphertext corresponding to the access password of the target object to access the operating system where the target middleware is located, and determine whether the decrypted access password matches the access password in the target operation script. If the decrypted access password matches the access password in the target operation script, it is determined that the target object has management operation permissions for the target middleware.

8. A middleware management method, characterized in that: Applicable to the above middleware control module, including: Receive a middleware operation instruction initiated by a target object, wherein the middleware operation instruction carries at least operation information of the target object on the target middleware and operation status information of the target middleware, and the operation status information includes at least one of the following: process ID, port number, service status; Determining the deployment mode of the target middleware according to the running status information in the middleware operation instruction, wherein the type of the deployment mode includes: container cloud deployment mode, virtual machine deployment mode or physical machine deployment mode; Determine a target middleware resource management module corresponding to the deployment method of the target middleware from multiple middleware resource management modules, and send the middleware operation instruction to the target middleware resource management module, wherein the multiple middleware resource management modules are respectively matched to different deployment methods, and the target middleware resource management module is used to perform corresponding management operations on the resource information of the target middleware according to the operation information in the middleware operation instruction, and the resource information includes at least one of the following: middleware version information, parameter configuration file information, and operation status information.

9. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a computer program, wherein the device where the non-volatile storage medium is located executes the middleware management method according to claim 8 by running the computer program.

10. A computer program product, characterized in that include: A computer program, wherein when the computer program is executed by a processor, the middleware management method according to claim 8 is implemented.

Images