Terminal multi-container application full-stack management and control tool based on domestic operating system

Abstract

The embodiment of the invention provides a terminal multi-container application full-stack management and control tool based on a domestic operating system, and belongs to the technical field of computers. The tool comprises a container full-process management module used for constructing a multi-container operation base on client equipment; deploying a system mirror image comprising multiple containers on the basis of the operation base; the intelligent monitoring and autonomous module is used for carrying out system monitoring on the basis of the deployed system mirror image; under the condition that the system alarm is monitored, determining an alarm level; and under the condition that the alarm level is greater than or equal to a preset level, restarting the corresponding container. According to the full-stack management and control tool, a unified container full-process management module is adopted as an operation base, and system mirror images of multiple containers are deployed, so that the technical defect that in the prior art, Chinese operation system container management is split is overcome.

Description

A full-stack management tool for multi-container applications on a domestically developed operating system. Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a full-stack management tool for terminal multi-container applications based on a domestically developed operating system. Background Technology

[0002] With the development of domestic technology, domestically developed operating systems have gradually begun to be applied in some technical fields. However, existing domestic operating systems suffer from insufficient adaptability. Specifically, when existing tools (such as Kubernetes) run on domestic OSes (Kylin OS, UnionTech UOS), performance losses can reach 30% to 50% due to differences in underlying mechanisms such as process scheduling and file systems, requiring complex patches for adaptation. Furthermore, the management processes of domestic operating systems are fragmented. Container lifecycle operations (installation / uninstallation) and application management (monitoring / self-healing) rely on the collaboration of multiple tools (such as kubectl + Helm), which is complex and prone to failures due to state asynchrony (such as the application not automatically restarting after a container restart). In addition, the protocol parsing efficiency of domestic operating systems is low: multi-protocol frameworks (such as Envoy) rely on regular expression matching to parse messages, resulting in a significant increase in CPU utilization on ARM architectures; performance degradation is obvious after the rule base expands, making it difficult to support the rapid protocol expansion needs of domestic scenarios. Finally, the monitoring and self-healing mechanisms of domestic operating systems are crude. Existing monitoring systems only support simple threshold-based alarms (such as CPU over-limit restarts) and cannot implement fine-grained recovery strategies. Summary of the Invention

[0003] The purpose of this invention is to provide a full-stack management tool for multi-container applications on a terminal based on a domestic operating system, which can improve upon the technical deficiencies of the domestic operating system.

[0004] To achieve the above objectives, this invention provides a terminal multi-container application full-stack management tool based on a domestic operating system, comprising: a container full-process management module, used for: building a multi-container runtime base on the client device; deploying a system image including multiple containers based on the runtime base; and an intelligent monitoring and autonomy module, used for: performing system monitoring based on the deployed system image; determining the alarm level when a system alarm is detected; and restarting the corresponding container when the alarm level is greater than or equal to a preset level.

[0005] Optionally, the container end-to-end management module includes: a Socket communication channel unit, used to establish an HTTP-based CURL socket communication link between the core backend and the current client device; and a container management unit, used to manage the status of each container.

[0006] Optionally, the container management unit includes: a request encapsulation subunit, used to fill in the HTTP request header and the JSON format request body according to the operation type of the system image; an instruction issuing subunit, used to send API requests to the core backend service of each container through the CURL socket communication link; and a status parsing subunit, used to receive the JSON response from the container and release the Socket communication channel unit upon receiving the JSON response.

[0007] Optionally, the container management unit includes: an image alignment subunit for efficient distribution and system version control based on the source files of the system image; an image management subunit for performing installation, uninstallation, start / stop, and / or enable operations on the distributed files; and a lightweight monitoring subunit for lightweight threshold monitoring of each currently running thread.

[0008] Optionally, the intelligent monitoring and autonomous module includes a service operation and maintenance unit, which includes a log management subunit, used to aggregate operation logs, system logs and business logs in real time through a distributed log collection framework.

[0009] Optionally, the service operation and maintenance unit includes a client management subunit, which is used to maintain a client connection status table based on a distributed database and dynamically count the number of online clients, connection protocol types, and device fingerprint information.

[0010] Optionally, the service operation and maintenance unit includes a service lifecycle management subunit, which is used to customize monitoring tools to perform periodic checks on each unit.

[0011] Optionally, the intelligent monitoring and autonomous module includes an IoT management and control unit, comprising: a message management subunit for filtering and distributing messages based on the MQTT protocol specification; and a connection management subunit for configuring the connection of each interface and the connection operation protocol.

[0012] On the other hand, the present invention also provides a computer device, wherein the computer device has a built-in operating system and a terminal multi-container application full-stack management tool based on any of the above-described domestic operating systems as described above.

[0013] Through the above technical solutions, the embodiments of the present invention provide a full-stack management tool for terminal multi-container applications based on a domestic operating system. This full-stack management tool uses a unified container full-process management module as the running base to deploy system images of multiple containers, thereby overcoming the technical defects of fragmented container management in existing domestic operating systems. The full-stack management tool also uses a unified intelligent monitoring and autonomous module to monitor the system status, thereby overcoming the technical problem of poor stability of the monitoring and self-healing mechanism of existing domestic operating systems.

[0014] Other features and advantages of the embodiments of the present invention will be described in detail in the following detailed description section. Attached Figure Description

[0015] The accompanying drawings are provided to further illustrate the embodiments of the present invention and constitute a part of the specification. They are used together with the following detailed description to explain the embodiments of the present invention, but do not constitute a limitation on the embodiments of the present invention. In the drawings: Figure 1 is a structural block diagram of a terminal multi-container application full-stack management tool based on a domestic operating system according to an embodiment of the present invention; Figure 2 is a structural block diagram of a container full-process management module according to an embodiment of the present invention; Figure 3 is a structural block diagram of a container management unit according to an embodiment of the present invention; Figure 4 is a structural block diagram of an intelligent monitoring and autonomous module according to an embodiment of the present invention. Detailed Implementation

[0016] The specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit the scope of the present invention.

[0017] It should be noted that the acquisition, transmission, storage, use, and processing of data in the technical solution of this application all comply with relevant laws and regulations. In the embodiments of this application, certain existing industry solutions such as software, components, and models may be mentioned. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solution of this application, and do not imply that the applicant has already used or necessarily used such solutions.

[0018] Figure 1 shows a structural block diagram of a terminal multi-container application full-stack management tool based on a domestic operating system according to an embodiment of the present invention. In Figure 1, the full-stack management tool may include a container full-process management module 10 and an intelligent monitoring and autonomy module 20. The container full-process management module 10 can be used to build a multi-container runtime platform on the client device, and deploy a system image including multiple containers based on this platform. The intelligent monitoring and autonomy module 20 can be used to perform system monitoring based on the deployed system image, determine the alarm level when system alarms are detected, and finally restart the corresponding container if the alarm level is greater than or equal to a preset level.

[0019] The full-stack management tool shown in Figure 1 overcomes the technical shortcomings of fragmented container management in existing technologies by employing a unified container end-to-end management module as the runtime foundation and deploying system images of multiple containers. Furthermore, this full-stack management tool also overcomes the technical problem of poor stability in the self-healing monitoring mechanism of existing technologies by using a unified intelligent monitoring and autonomous module to monitor the system status.

[0020] In one embodiment of the present invention, as shown in FIG2, the container end-to-end management module 10 may further include a Socket communication channel unit 11 and a container management unit 12. The Socket communication channel unit 11 can be used to establish an HTTP-based CURL socket communication link between the core backend and the current client device, thereby enabling remote communication between the core backend and the current client device. More specifically, the Socket communication channel unit 11 can perform container lifecycle management via REST API: initializing the connection: by establishing a Socket connection with the core backend service of the container ecosystem, it supports asynchronous I / O optimization of the domestic operating system kernel.

[0021] The container management unit 12 can be used to manage the state of each container, thereby enabling real-time adjustments to the system of the current client device. The specific structure of the container management unit 12 can take many forms known to those skilled in the art. In one example of the present invention, as shown in Figure 3, the container management unit 12 may include a request encapsulation subunit 12a, an instruction issuing subunit 12b, and a status parsing subunit 12c. The request encapsulation subunit 12a can be used to fill in HTTP request headers (such as authentication token, Content-Type) and a JSON-formatted request body according to the system image's operation type (create / start / stop container). The instruction issuing subunit 12b can be used to send API requests to the core backend service of each container via a CURL socket communication link. The status parsing subunit 12c can be used to receive JSON responses (such as container ID, operation status code) from the container, and upon receiving the JSON response, release the Socket communication channel unit 11. Furthermore, considering that the container management unit 12 also needs to manage the real-time status of the system image, as shown in Figure 3, the container management unit 12 can further include an image alignment subunit 12d, an image management subunit 12f, and a lightweight monitoring subunit 12g. The image alignment subunit 12d can be used for efficient distribution and system version control based on the source files of the system image. The image management subunit 12f can be used for installation, uninstallation, start / stop, and / or enable operations on the distributed files. The lightweight monitoring subunit 22g can be used for lightweight threshold monitoring of each currently running thread.

[0022] The intelligent monitoring and autonomy module 20 may include a service operation and maintenance unit 21. This service operation and maintenance unit 21 can be used to implement end-to-end service health management. The service operation and maintenance submodule focuses on three-dimensional monitoring of "logs-connections-processes" to construct a system service health assessment model. This service operation and maintenance unit 21 may further include a log management subunit 21a, a client management subunit 21b, and a service lifecycle management subunit 21c. The log management subunit 21a can be used to aggregate operation logs, system logs (kernel / service exception events), and business logs (application runtime metrics) in real time through a distributed log collection framework. Based on this log management subunit 21a, second-level log retrieval and analysis are achieved through multi-dimensional indexing (timestamp, log level, keywords), supporting filtering of key events by container ID, application name, and other conditions. For example, when a container frequently triggers memory alarms, the memory leak point of the specific process can be quickly located through the logs.

[0023] The client management subunit 21b can be used to maintain a client connection status table based on a distributed database, dynamically counting the number of online clients, connection protocol types (such as MQTT / HTTP), and device fingerprint information (such as container ID and terminal MAC address). It updates the connection status in real time through a heartbeat detection mechanism, automatically marking clients that fail to respond within a timeout period as offline and triggering alarm notifications.

[0024] The service lifecycle management subunit 21c can be used to customize monitoring tools for periodic checks on each unit. More specifically, this service lifecycle management subunit 21c can be used for periodic probing (such as sending heartbeat packets or checking process PIDs). When an abnormal service termination is detected, a preset recovery strategy is automatically triggered: first, a local service restart is attempted; if this fails, a remote restart command is initiated by reporting to the centralized management platform to ensure service availability.

[0025] Furthermore, to facilitate the management of messages within the system, as shown in Figure 4, the intelligent monitoring and autonomy module may also include an IoT management unit 22. This IoT management unit 22 can be used to ensure high-concurrency communication links, supporting the concurrent access requirements of hundreds of thousands of container nodes by optimizing the stability of MQTT communication and underlying protocol links. This IoT management unit 22 may further include a message management subunit 22a and a connection management subunit 22b. Specifically, the message management subunit 22a can be used for message filtering and distribution based on the MQTT protocol specification. Specifically, the message management subunit 22a can strictly adhere to the MQTT protocol specification, define standardized topic subscription formats, and achieve precise routing of instructions and data. Flexible message filtering and distribution are achieved through topic wildcards (such as / #, / +). The connection management subunit 22b can be used to configure the connection and connection operation protocol for each interface. Specifically, the connection management subunit 22b can implement a high-performance connection pool based on an asynchronous I / O library, dynamically maintaining the communication links with the core backend services of the container ecosystem. By using a long-connection heartbeat mechanism (such as Ping / Pong frames) to monitor link quality in real time, it provides an adaptive retransmission optimization mechanism and innovative advantages for packet loss and latency issues in weak network environments.

[0026] On the other hand, the present invention also provides a computer device, wherein the computer device has a built-in operating system and a full-stack management tool for terminal multi-container applications based on any of the aforementioned domestic operating systems. Specifically, as shown in Figure 1, the full-stack management tool may include a container full-process management module 10 and an intelligent monitoring and autonomy module 20. The container full-process management module 10 can be used to build a multi-container runtime platform on the client device, and deploy a system image including multiple containers based on this runtime platform. The intelligent monitoring and autonomy module 20 can be used to perform system monitoring based on the deployed system image, determine the alarm level when system alarms are detected, and finally restart the corresponding container if the alarm level is greater than or equal to a preset level.

[0027] The full-stack management tool shown in Figure 1 overcomes the technical shortcomings of fragmented container management in existing technologies by employing a unified container end-to-end management module as the runtime foundation and deploying system images of multiple containers. Furthermore, this full-stack management tool also overcomes the technical problem of poor stability in the self-healing monitoring mechanism of existing technologies by using a unified intelligent monitoring and autonomous module to monitor the system status.

[0028] In one embodiment of the present invention, as shown in FIG2, the container end-to-end management module 10 may further include a Socket communication channel unit 11 and a container management unit 12. The Socket communication channel unit 11 can be used to establish an HTTP-based CURL socket communication link between the core backend and the current client device, thereby enabling remote communication between the core backend and the current client device. More specifically, the Socket communication channel unit 11 can perform container lifecycle management via REST API: initializing the connection: by establishing a Socket connection with the core backend service of the container ecosystem, it supports asynchronous I / O optimization of the domestic operating system kernel.

[0029] The container management unit 12 can be used to manage the state of each container, thereby enabling real-time adjustments to the system of the current client device. The specific structure of the container management unit 12 can take many forms known to those skilled in the art. In one example of the present invention, as shown in Figure 3, the container management unit 12 may include a request encapsulation subunit 12a, an instruction issuing subunit 12b, and a status parsing subunit 12c. The request encapsulation subunit 12a can be used to fill in HTTP request headers (such as authentication token, Content-Type) and a JSON-formatted request body according to the system image's operation type (create / start / stop container). The instruction issuing subunit 12b can be used to send API requests to the core backend service of each container via a CURL socket communication link. The status parsing subunit 12c can be used to receive JSON responses (such as container ID, operation status code) from the container, and upon receiving the JSON response, release the Socket communication channel unit 11. Furthermore, considering that the container management unit 12 also needs to manage the real-time status of the system image, as shown in Figure 3, the container management unit 12 can further include an image alignment subunit 12d, an image management subunit 12f, and a lightweight monitoring subunit 12g. The image alignment subunit 12d can be used for efficient distribution and system version control based on the source files of the system image. The image management subunit 12f can be used for installation, uninstallation, start / stop, and / or enable operations on the distributed files. The lightweight monitoring subunit 22g can be used for lightweight threshold monitoring of each currently running thread.

[0030] The intelligent monitoring and autonomy module 20 may include a service operation and maintenance unit 21. This service operation and maintenance unit 21 can be used to implement end-to-end service health management. The service operation and maintenance submodule focuses on three-dimensional monitoring of "logs-connections-processes" to construct a system service health assessment model. This service operation and maintenance unit 21 may further include a log management subunit 21a, a client management subunit 21b, and a service lifecycle management subunit 21c. The log management subunit 21a can be used to aggregate operation logs, system logs (kernel / service exception events), and business logs (application runtime metrics) in real time through a distributed log collection framework. Based on this log management subunit 21a, second-level log retrieval and analysis are achieved through multi-dimensional indexing (timestamp, log level, keywords), supporting filtering of key events by container ID, application name, and other conditions. For example, when a container frequently triggers memory alarms, the memory leak point of the specific process can be quickly located through the logs.

[0031] The client management subunit 21b can be used to maintain a client connection status table based on a distributed database, dynamically counting the number of online clients, connection protocol types (such as MQTT / HTTP), and device fingerprint information (such as container ID and terminal MAC address). It updates the connection status in real time through a heartbeat detection mechanism, automatically marking clients that fail to respond within a timeout period as offline and triggering alarm notifications.

[0032] The service lifecycle management subunit 21c can be used to customize monitoring tools for periodic checks on each unit. More specifically, this service lifecycle management subunit 21c can be used for periodic probing (such as sending heartbeat packets or checking process PIDs). When an abnormal service termination is detected, a preset recovery strategy is automatically triggered: first, a local service restart is attempted; if this fails, a remote restart command is initiated by reporting to the centralized management platform to ensure service availability.

[0033] Furthermore, to facilitate the management of messages within the system, as shown in Figure 4, the intelligent monitoring and autonomy module may also include an IoT management unit 22. This IoT management unit 22 can be used to ensure high-concurrency communication links, supporting the concurrent access requirements of hundreds of thousands of container nodes by optimizing the stability of MQTT communication and underlying protocol links. This IoT management unit 22 may further include a message management subunit 22a and a connection management subunit 22b. Specifically, the message management subunit 22a can be used for message filtering and distribution based on the MQTT protocol specification. Specifically, the message management subunit 22a can strictly adhere to the MQTT protocol specification, define standardized topic subscription formats, and achieve precise routing of instructions and data. Flexible message filtering and distribution are achieved through topic wildcards (such as / #, / +). The connection management subunit 22b can be used to configure the connection and connection operation protocol for each interface. Specifically, the connection management subunit 22b can implement a high-performance connection pool based on an asynchronous I / O library, dynamically maintaining the communication links with the core backend services of the container ecosystem. By using a long-connection heartbeat mechanism (such as Ping / Pong frames) to monitor link quality in real time, it provides an adaptive retransmission optimization mechanism and innovative advantages for packet loss and latency issues in weak network environments.

[0034] Through the above technical solutions, the embodiments of the present invention provide a full-stack management tool for terminal multi-container applications based on a domestic operating system. This full-stack management tool uses a unified container full-process management module as the running base to deploy system images of multiple containers, thereby overcoming the technical defects of fragmented container management in existing domestic operating systems. The full-stack management tool also uses a unified intelligent monitoring and autonomous module to monitor the system status, thereby overcoming the technical problem of poor stability of the monitoring and self-healing mechanism of existing domestic operating systems.

[0035] 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-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0036] 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 means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0037] These 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 that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0038] 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, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0039] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0040] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0041] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0042] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0043] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A full-stack management tool for multi-container applications on a terminal based on a domestically developed operating system, characterized in that, include: The container end-to-end management module is used to: build a multi-container runtime platform on client devices; Based on the aforementioned operating platform, deploy system images including multiple containers; The intelligent monitoring and autonomy module is used to: perform system monitoring based on the deployed system image; and determine the alarm level when system alarms are detected. If the alarm level is greater than or equal to the preset level, restart the corresponding container.

2. The tool according to claim 1, characterized in that, The container end-to-end management module includes: a Socket communication channel unit, used to build an HTTP-based CURL socket communication link between the core backend and the current client device; and a container management unit, used to manage the status of each container.

3. The tool according to claim 2, characterized in that, The container management unit includes: a request encapsulation subunit, used to fill in the HTTP request header and JSON format request body according to the operation type of the system image; an instruction issuing subunit, used to send API requests to the core backend service of each container through the CURL socket communication link; and a status parsing subunit, used to receive the JSON response from the container and release the Socket communication channel unit upon receiving the JSON response.

4. The tool according to claim 2, characterized in that, The container management unit includes: an image alignment subunit for efficient distribution and system version control based on the source files of the system image; an image management subunit for performing installation, uninstallation, start / stop, and / or enable operations on the distributed files; and a lightweight monitoring subunit for lightweight threshold monitoring of each currently running thread.

5. The tool according to claim 1, characterized in that, The intelligent monitoring and autonomous module includes a service operation and maintenance unit, which includes a log management subunit, used to aggregate operation logs, system logs and business logs in real time through a distributed log collection framework.

6. The tool according to claim 5, characterized in that, The service operation and maintenance unit includes a client management subunit, which is used to maintain a client connection status table based on a distributed database and dynamically count the number of online clients, connection protocol types, and device fingerprint information.

7. The tool according to claim 6, characterized in that, The service operation and maintenance unit includes a service lifecycle management subunit, which is used to customize monitoring tools to perform periodic checks on each unit.

8. The tool according to claim 5, characterized in that, The intelligent monitoring and autonomous module includes an IoT management and control unit, comprising: a message management subunit for filtering and distributing messages based on the MQTT protocol specification; and a connection management subunit for configuring the connection of each interface and the connection operation protocol.

9. A computer device, characterized in that, The computer device has a built-in operating system and a terminal multi-container application full-stack management tool based on any one of the domestic operating systems as described in any one of claims 1 to 8.

Images