Server operating system management platform device and application method thereof

Abstract

The invention discloses a server operating system management platform device and an application method thereof, and the server operating system management platform device comprises a front-end server, MQTT protocol middleware, a rear-end server, a database server and a cache server, the front-end server and the MQTT protocol middleware are exposed at the front end, respectively perform data interaction with the management server, and are respectively connected with the rear-end server; and the back-end server is connected with the database server and the cache server so as to realize management of the management server based on the database service support provided by the database server and the cache support provided by the cache server. The invention aims to solve the problem of centralized management of the large-scale server operating systems, realize batch management of the large-scale server operating systems and improve the operation and maintenance management efficiency.

Description

Technical Field

[0001] This invention relates to the field of server management technology, and more specifically to a server operating system management platform device and its application method. Background Technology

[0002] With the rapid development of information systems, servers, as core equipment in data centers, are crucial for the normal operation of the entire system and even the enterprise. Large platforms or enterprises often need to manage and maintain tens or even hundreds of thousands of server operating systems. However, traditional operation and maintenance methods rely on single-point remote management of server operating systems via SSH connections. This approach cannot monitor the real-time operating status of server operating systems and makes centralized management of large-scale server operating systems difficult. Therefore, it faces challenges in security, stability, and efficiency, failing to meet current operation and maintenance needs. Consequently, there is an urgent need for a platform and method capable of managing large-scale server operating systems. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a server operating system management platform device and its application method, which addresses the above-mentioned problems in the prior art. The present invention aims to solve the problem of centralized management of large-scale server operating systems, realize batch management of large-scale server operating systems, and improve the efficiency of operation and maintenance management.

[0004] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows: A server operating system management platform device, comprising: The front-end server is used to enable communication and data transfer between the management server and the back-end server. The MQTT protocol middleware is used to send tasks created by the backend server to the designated management server via the MQTT protocol, and to receive the task execution results returned by the management server and return them to the backend server. Backend servers are used to manage the managed servers; Database server, used to provide database service support for backend servers; A caching server is used to provide caching support for backend servers. The front-end server and MQTT protocol middleware are exposed on the front end to interact with the management server. The front-end server and MQTT protocol middleware are connected to the back-end server. The back-end server is connected to the database server and the cache server to manage the management server based on the database service support provided by the database server and the cache support provided by the cache server.

[0005] Furthermore, the present invention also provides an application method for the aforementioned server operating system management platform device, comprising: a backend server caching the connection status information of registered managed servers in a cache server, including whether the connection status is "connected" or "disconnected" and the last heartbeat time; then using a proxy program in the managed server to send heartbeat requests to the backend server to implement connection status management of the managed servers; and periodically monitoring the difference between the last heartbeat time of the connection status information of the registered managed servers and the current time; if the difference exceeds a preset threshold, updating the connection status information of the registered managed servers to "disconnected".

[0006] Optionally, the connection state management of the managed server using the heartbeat request sent by the agent program in the managed server to the backend server includes the following steps: S101, the backend server monitors the heartbeat requests from the proxy program forwarded by the frontend server. If a heartbeat request is detected, the process jumps to step S102; otherwise, it returns to step S101. S102, the backend server determines from the cache information of the cache server whether the management server corresponding to the heartbeat request has been registered. If it has been registered, it determines the connection status of the management server corresponding to the heartbeat request. If the connection status is connected, it updates the last heartbeat time of the management server corresponding to the heartbeat request in the cache information; if the connection status is disconnected, it updates the connection status of the management server corresponding to the heartbeat request in the cache information to connected, and updates the last heartbeat time of the management server corresponding to the heartbeat request in the cache information.

[0007] Optionally, step S102 further includes issuing an uninstallation task to the agent program of the management server corresponding to the heartbeat request through the front-end server or MQTT protocol middleware when the management server corresponding to the heartbeat request is not registered. The agent program performs self-uninstallation and returns the uninstallation task execution result when the uninstallation is completed. The back-end server records the uninstallation task execution result to the database server after receiving it.

[0008] Optionally, it also includes the following steps whereby the backend server issues management actions to the management server: S201, the backend server imports the standard library file containing management action information into the database server's database; S202, When it is necessary to send a management action to the management server, the backend server selects the management action to be sent from the database of the database server; S203, the backend server determines the CPU architecture and operating system version of the management action based on the attributes of the management action, and then determines the matching management server based on the CPU architecture and operating system version of the management action. S204, the backend server uses the MQTT protocol to send management action commands to the agent program in the server operating system of the matched management server through the MQTT protocol middleware; S205, the agent program in the matched management server processes the management action command, responds to the management action, and sends the execution result to the backend server through the MQTT protocol middleware using the MQTT protocol. S206: After receiving the execution result, the backend server saves the execution result to the database server's database.

[0009] Optionally, after step S201 and before step S202, the backend server obtains the administrator's add, delete, modify, or query operations on management action information through the frontend server, executes the administrator's add, delete, modify, or query operations on configuration items based on the management action information saved in the database server, and returns the operation results to the user or administrator.

[0010] Optionally, the management actions include one or more of the following: modifying configuration items, host registration, host scanning, patch management, custom script distribution, and log management.

[0011] Furthermore, the present invention also provides an application device for a server operating system management platform device, comprising a microprocessor and a memory interconnected thereto, wherein the microprocessor is programmed or configured to execute the application method of the server operating system management platform device.

[0012] Furthermore, the present invention also provides a computer-readable storage medium storing a computer program / instructions that are programmed or configured to execute, via a processor, the application method of the server operating system management platform device.

[0013] Furthermore, the present invention also provides a computer program product, including a computer program / instruction, which is programmed or configured to execute the application method of the server operating system management platform device via a processor.

[0014] Compared with existing technologies, this invention has the following main advantages: Addressing the problems of existing solutions using SSH remote connection for server operating system management, which is cumbersome, inefficient, error-prone, and highly dependent on maintenance personnel, failing to meet the needs of managing large-scale server operating systems, this invention's server operating system management platform includes a front-end server, an MQTT protocol middleware, a back-end server, a database server, and a cache server. The front-end server and MQTT protocol middleware are exposed at the front end to interact with the managed server, and are connected to the back-end server. The back-end server is connected to the database server and the cache server to manage the managed server based on the database service support provided by the database server and the cache support provided by the cache server. Through this architecture, it can accept registration information from a large number of managed servers, manage the connection status between a large number of managed servers and the servers (back-end server, database server, and cache server) and display it to the user in real time. It can also send tasks to designated hosts via the MQTT protocol, solving the problem of centralized management of large-scale server operating systems, achieving batch management of large-scale server operating systems, and improving operation and maintenance efficiency. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of the structure of the server operating system management platform device in an embodiment of the present invention.

[0016] Figure 2 This is a flowchart illustrating the use of heartbeat requests to manage the connection status of the managed server in an embodiment of the present invention.

[0017] Figure 3 This is a flowchart illustrating the distribution of configuration items in an embodiment of the present invention. Detailed Implementation

[0018] like Figure 1 As shown, the server operating system management platform device in this embodiment includes: The front-end server is used to enable communication and data transfer between the management server and the back-end server. The MQTT protocol middleware (MQTT Broker) is used to send tasks created by the backend server to the specified management server via the MQTT protocol, and to receive the task execution results returned by the management server and return them to the backend server. Backend servers are used to manage the managed servers; Database server, used to provide database service support for backend servers; A caching server is used to provide caching support for backend servers. The front-end server and MQTT protocol middleware are exposed at the front end to interact with the managed server. The front-end server and MQTT protocol middleware are connected to the back-end server, which in turn is connected to the database server and cache server to manage the managed server based on the database service support provided by the database server and the cache support provided by the cache server. It should be noted that the back-end server, database server, and cache server can all be single servers / virtual machines / containers or clusters of multiple servers / virtual machines / containers. For example, the back-end server is a stateless service, only performing the logical processing required for operation and maintenance, and does not store data. Therefore, any back-end server can independently complete the entire task processing flow, and the overall processing capacity of the management platform can be expanded by increasing the number of nodes in the cluster. When the database server or cache server is clustered, distributed storage can be implemented using hash mapping.

[0019] This embodiment of the server operating system management platform aims to improve the security, stability, and efficiency of server operating system operation and maintenance. It features a modular design for easy expansion and maintenance, and allows for flexible configuration of functional modules according to business needs. The platform accepts host registration and displays host connection status information in real time. It implements functions such as host registration, host scanning, patch management, configuration management, custom script distribution, and log management. The MQTT protocol is used to achieve data interaction between the managed server and the management end, completing task distribution and returning task execution results, supporting tens of thousands of servers connecting simultaneously. A database server is used to store persistent data required for platform operation, such as user information, server information, configuration information, software package information, and log information. A cache server is used to store temporary data required for platform operation, such as session information, heartbeat information, and intermediate task states, improving system access speed. This embodiment uses secure encryption to encrypt the distributed and returned information during transmission, ensuring information security during execution. This embodiment can control the server-side task distribution rate; when users simultaneously distribute a large number of tasks, the server can queue them, avoiding excessive pressure on the server and preventing system failures caused by a large number of tasks executing simultaneously. This embodiment supports high-availability deployment. The failure of some nodes does not affect the overall functionality of the system. Rolling updates are supported during system upgrades without service interruption, allowing for 24 / 7 uninterrupted operation. This embodiment enables rapid horizontal scaling, meeting the needs of large-scale server operating system management in enterprise data centers.

[0020] like Figure 2As shown, this embodiment also provides an application method for the aforementioned server operating system management platform device, including a backend server caching the connection status information of registered managed servers in a cache server, including whether the connection status is "connected" or "disconnected" and the last heartbeat time. Then, it uses an agent program (in this embodiment, the managed server operating system is managed through an agent program) in the managed server to send heartbeat requests to the backend server to achieve connection status management of the managed servers. It also periodically monitors the difference between the last heartbeat time and the current time of the connection status information of the registered managed servers. If the difference exceeds a preset threshold, the connection status information of the registered managed servers is updated to "disconnected". The server operating system management platform device of this embodiment can process server heartbeat requests. Heartbeat requests are important information for determining the server's operating status. The server maintains its connection with the management terminal by periodically sending heartbeat requests to the management terminal. Figure 2 As shown, the server operating system management platform device in this embodiment utilizes the heartbeat request sent by the agent program in the managed server to the backend server to implement the connection status management of the managed server, including the following steps: S101, the backend server monitors the heartbeat requests from the proxy program forwarded by the frontend server. If a heartbeat request is detected, the process jumps to step S102; otherwise, it returns to step S101. S102, the backend server determines from the cache information of the cache server whether the management server corresponding to the heartbeat request has been registered. If it has been registered, it determines the connection status of the management server corresponding to the heartbeat request. If the connection status is connected, it updates the last heartbeat time of the management server corresponding to the heartbeat request in the cache information; if the connection status is disconnected, it updates the connection status of the management server corresponding to the heartbeat request in the cache information to connected, and updates the last heartbeat time of the management server corresponding to the heartbeat request in the cache information.

[0021] In addition, as an optional implementation, step S102 of this embodiment also includes, when the management server corresponding to the heartbeat request is not registered, issuing an uninstallation task to the agent program of the management server corresponding to the heartbeat request through the front-end server or MQTT protocol middleware. The agent program performs self-uninstallation and returns the uninstallation task execution result when the uninstallation is completed. After receiving the uninstallation task execution result, the back-end server records it in the database server. In the above way, the requests initiated by unregistered agent programs to the back-end server can be reduced, thus reducing the consumption of server processing resources.

[0022] In addition, as an optional implementation, when the agent performs self-unloading and returns the uninstallation task execution result at the end of the uninstallation, this embodiment also includes merging the agent's self-unloading and the return of the uninstallation task execution result at the end of the uninstallation through the front-end server or MQTT protocol middleware, and then returning the merged uninstallation task execution result to the back-end server to reduce the traffic between the back-end server, the front-end server or the MQTT protocol middleware, and ensure the real-time nature of the tasks issued by the back-end server through the front-end server or the MQTT protocol middleware.

[0023] This embodiment allows the backend server to perform management actions on the management server, including one or more of the following: modifying configuration items, host registration, host scanning, patch management, custom script distribution, and log management. For example, taking configuration item modification as an example... Figure 3 As shown, this embodiment also includes the following steps whereby the backend server issues a management action (modify configuration items) to the management server: S201, the backend server imports the standard library file containing management action (modify configuration items) information into the database server's database; S202, When it is necessary to send a management action (modify configuration item) to the management server, the backend server selects the management action (modify configuration item) to be sent from the database of the database server. S203, the backend server determines the CPU architecture and operating system version of the management action (modify configuration item) based on the attributes of the management action (modify configuration item), and determines the matching management server based on the CPU architecture and operating system version of the management action (modify configuration item). S204, the backend server uses the MQTT protocol to send management action (modify configuration items) commands to the agent program in the server operating system of the matched managed server through the MQTT protocol middleware; S205, the agent program in the matched management server processes the management action (modify configuration items) command, responds to the management action (modify configuration items), and sends the execution result to the backend server via the MQTT protocol middleware using the MQTT protocol; S206: After receiving the execution result, the backend server saves the execution result to the database server's database.

[0024] like Figure 3As shown, after step S201 and before step S202 in this embodiment, the backend server obtains the administrator's (login verification required) addition, deletion, modification or query operations on management action information through the frontend server, and executes the administrator's addition, deletion, modification or query operations on configuration items according to the management action information saved in the database server, and returns the operation results to the user or administrator.

[0025] In addition, as an optional implementation, to avoid overloading and crashing the management server due to management actions being performed from the backend server to the management server, the following optimizations can be performed as needed: Optimize 'a' by improving the command format of management actions. This allows management action commands to include resource constraints (e.g., greater than, less than, or within a certain range) for resources such as CPU, memory, and I / O. This ensures that when the agent program in the matching management server processes the management action command, it only performs the action if the resource constraints are met; otherwise, it waits and makes a judgment. This approach prevents the management server from overloading and crashing due to backend servers executing management actions (modifying configuration items, host registration, host scanning, patch management, custom script distribution, and log management), thus ensuring the performance and reliability of the management server.

[0026] Optimize option b by improving the way the backend server selects management actions from the database server's database. For example, use a scheduling queue to manage this selection process, ensuring that management actions are queued according to certain rules, guaranteeing task order and fairness, and preventing some tasks from being executed first while others are delayed. Furthermore, different priorities for management actions can be set as needed, and the highest-priority action is selected from the scheduling queue for execution during each scheduling cycle.

[0027] In summary, the server operating system management platform device and its application method in this embodiment realize large-scale server operating system management functions. By managing the server operating system through an agent program, it can perform functions such as host registration, host scanning, patch management, configuration management, custom script distribution, and log management. This embodiment supports the registration and management of 200,000 servers and supports simultaneous task distribution to 10,000 servers. Furthermore, the platform can be horizontally scaled according to the actual management scale to meet management needs. The server operating system management platform device and its application method in this embodiment adopt a modular design that is easy to expand and maintain. Each functional module can be flexibly configured according to business needs. It can accept registration information from managed servers, manage the connection status between managed servers and the server-side (backend servers, database servers, and cache servers) and display it to users in real time. It can also distribute tasks to designated hosts via the MQTT protocol to achieve server operating system management, solving the problem of centralized management of large-scale server operating systems and improving operation and maintenance efficiency.

[0028] Furthermore, this embodiment also provides an application device for a server operating system management platform device, including a microprocessor and a memory interconnected, wherein the microprocessor is programmed or configured to execute the application method of the server operating system management platform device.

[0029] Furthermore, this embodiment also provides a computer-readable storage medium storing a computer program / instructions that are programmed or configured to execute the application method of the server operating system management platform device via a processor.

[0030] Furthermore, this embodiment also provides a computer program product, including a computer program / instruction, which is programmed or configured to execute the application method of the server operating system management platform device via a processor.

[0031] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process. Figure 1 One or more processes and / or boxes Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0032] The above description is merely a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of the present invention should also be considered within the scope of protection of the present invention.

Claims

1. A server operating system management platform device, characterized in that, include: The front-end server is used to enable communication and data transfer between the management server and the back-end server. The MQTT protocol middleware is used to send tasks created by the backend server to the designated management server via the MQTT protocol, and to receive the task execution results returned by the management server and return them to the backend server. Backend servers are used to manage the managed servers; Database server, used to provide database service support for backend servers; A caching server is used to provide caching support for backend servers. The front-end server and MQTT protocol middleware are exposed on the front end to interact with the management server. The front-end server and MQTT protocol middleware are connected to the back-end server. The back-end server is connected to the database server and the cache server to manage the management server based on the database service support provided by the database server and the cache support provided by the cache server.

2. An application method of the server operating system management platform device as described in claim 1, characterized in that, This involves the backend server caching the connection status information of registered managed servers in the cache server, including whether the connection status is "connected" or "disconnected" and the last heartbeat time. Then, the agent program in the managed server sends heartbeat requests to the backend server to manage the connection status of the managed server. It also periodically monitors the difference between the last heartbeat time and the current time of the connection status information of the registered managed server. If the difference exceeds a preset threshold, the connection status information of the registered managed server is updated to disconnected.

3. The application method of the server operating system management platform device according to claim 2, characterized in that, The process of using the agent program in the managed server to send heartbeat requests to the backend server to implement connection state management of the managed server includes the following steps: S101, the backend server monitors the heartbeat requests from the proxy program forwarded by the frontend server. If a heartbeat request is detected, the process jumps to step S102; otherwise, it returns to step S101. S102, the backend server determines from the cache information of the cache server whether the management server corresponding to the heartbeat request has been registered. If it has been registered, it determines the connection status of the management server corresponding to the heartbeat request. If the connection status is "connected", it updates the last heartbeat time of the management server corresponding to the heartbeat request in the cache information; if the connection status is "disconnected", it updates the connection status of the management server corresponding to the heartbeat request in the cache information to "connected" and updates the last heartbeat time of the management server corresponding to the heartbeat request in the cache information.

4. The application method of the server operating system management platform device according to claim 3, characterized in that, Step S102 also includes issuing an uninstallation task to the agent program of the management server corresponding to the heartbeat request through the front-end server or MQTT protocol middleware when the management server corresponding to the heartbeat request is not registered. The agent program performs self-uninstallation and returns the uninstallation task execution result when the uninstallation is completed. The back-end server records the uninstallation task execution result to the database server after receiving it.

5. The application method of the server operating system management platform device according to claim 2, characterized in that, It also includes the following steps where the backend server issues management actions to the management server: S201, the backend server imports the standard library file containing management action information into the database server's database; S202, When it is necessary to send a management action to the management server, the backend server selects the management action to be sent from the database of the database server; S203, the backend server determines the CPU architecture and operating system version of the management action based on the attributes of the management action, and then determines the matching management server based on the CPU architecture and operating system version of the management action. S204, the backend server uses the MQTT protocol to send management action commands to the agent program in the server operating system of the matched management server through the MQTT protocol middleware; S205, the agent program in the matched management server processes the management action command, responds to the management action, and sends the execution result to the backend server through the MQTT protocol middleware using the MQTT protocol. S206: After receiving the execution result, the backend server saves the execution result to the database server's database.

6. The application method of the server operating system management platform device according to claim 5, characterized in that, After step S201 and before step S202, the backend server obtains the administrator's add, delete, modify or query operations on management action information through the frontend server, executes the administrator's add, delete, modify or query operations on configuration items according to the management action information saved in the database server, and returns the operation results to the user or administrator.

7. The application method of the server operating system management platform device according to claim 5, characterized in that, The management actions include one or more of the following: modifying configuration items, host registration, host scanning, patch management, custom script distribution, and log management.

8. An application device for a server operating system management platform, comprising a microprocessor and a memory interconnected, characterized in that, The microprocessor is programmed or configured to perform the application method of the server operating system management platform apparatus according to any one of claims 2 to 7.

9. A computer-readable storage medium storing a computer program / instructions, characterized in that, The computer program / instructions are programmed or configured to execute, via a processor, the application method of the server operating system management platform apparatus according to any one of claims 2 to 7.

10. A computer program product comprising a computer program / instructions, characterized in that, The computer program / instructions are programmed or configured to execute, via a processor, the application method of the server operating system management platform apparatus according to any one of claims 2 to 7.

Images