An automated operation and maintenance management system and method for operating system

By generating and managing multiple operation and maintenance models, calculating evaluation coefficients, and setting up common and backup models, the problem that traditional operation and maintenance management methods cannot handle operating system abnormalities in a timely manner is solved, automated operation and maintenance management is realized, and the system's fault tolerance capabilities are enhanced. Business continuity.

CN118245346BActive Publication Date: 2024-12-03广州市思捷计算机有限公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410403000.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-04-03
Publication Date
2024-12-03
Estimated Expiration
2044-04-03

AI Technical Summary

Technical Problem

Traditional operating system operation and maintenance management methods cannot achieve comprehensive management, especially when operating system abnormalities cannot be handled in time, resulting in system crashes or critical services unavailable, reducing work efficiency, and may trigger chain reactions.

Method used

By comprehensively considering the performance and final execution results of the operation and maintenance model during the execution process, the first operation and maintenance model, the second operation and maintenance model and the third operation and maintenance model are generated, the process evaluation coefficient and result evaluation coefficient are calculated, and common models and backup models are established. Model to ensure that tasks are not interrupted due to model failures, and realize automatic execution and event management of automated scripts.

Benefits of technology

It greatly reduces response time, realizes batch processing and automated management, reduces operation and maintenance costs, enhances the system's fault tolerance and business continuity, and provides more accurate performance evaluation and decision-making basis.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118245346B_ABST
    Figure CN118245346B_ABST
Patent Text Reader

Abstract

The present invention discloses an automated operation and maintenance management system and method for operating systems, and relates to the technical field of automated operation and maintenance management of operating systems. An automated script is written based on the calling relationship between modules and the data dependency relationship between functions to generate an operation and maintenance model; the timestamp of the automatic execution of the detection model when an event occurs is calculated to obtain the process evaluation coefficient of each operation and maintenance model; the result evaluation coefficient of each operation and maintenance model is calculated to obtain the operation and maintenance coefficient of each operation and maintenance model in combination with the process evaluation coefficient; a common model and a backup model are established based on the operation and maintenance coefficient. When an event occurs, the common model takes the event out of the queue first and decides when and how to execute the corresponding script. The configuration and quantity of the common model and the backup model are adjusted according to the personalized needs of different enterprises. When the common model cannot handle the event for some reason, the backup model quickly takes over to ensure that the task will not be interrupted due to model failure.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of automated operation and maintenance management of operating systems, and in particular to an automated operation and maintenance management system and method for operating systems. Background Art

[0002] Operating system operation and maintenance management involves multiple aspects such as system installation, configuration management, performance monitoring, and troubleshooting, and requires comprehensive monitoring and management of all aspects of the operating system. Traditional operation and maintenance methods can only perform simple system monitoring and troubleshooting, and cannot achieve comprehensive management of the operating system. At the same time, due to the complexity and diversity of operating systems, the operating system environments of different enterprises may vary greatly, so an operating system operation and maintenance management solution that can flexibly adapt to the needs of different enterprises is needed.

[0003] In the Chinese invention application with application publication number CN116088921A, an automated operation and maintenance management system and method for domestic operating systems are disclosed, including a host group management module, a host registration module, a host management module, a software warehouse module, an application installation module, a service deployment module, an integrated AD domain module, an image production module, a remote desktop module, a backup and recovery module, a resource monitoring module, and an upgrade and update module. It provides a solution for domestic Linux operating systems that is quickly deployed, easy to use, batch managed, automated, and integrated with IT systems.

[0004] In the above invention application, the real-time operation status information of the domestic operating system is analyzed and evaluated to determine the real-time operation reliability of the domestic operating system, and the domestic operating system is automatically maintained according to the real-time operation reliability. However, it only focuses on the real-time operation reliability of the domestic operating system, and does not care about how to automatically maintain the domestic operating system. When the operating system is abnormal, it cannot be handled in time, which may cause the entire system to crash or key services to be unavailable, reduce work efficiency, and may even cause a chain reaction in other related systems.

[0005] To this end, the present invention provides an automated operation and maintenance management system and method for an operating system. Summary of the invention

[0006] 1. Technical issues to be resolved

[0007] In view of the deficiencies in the prior art, the present invention provides an automated operation and maintenance management system and method for an operating system. The present invention can provide a comprehensive and objective evaluation index by comprehensively considering the performance of the operation and maintenance model during the execution process (process evaluation coefficient) and the final execution result (result evaluation coefficient), and can more accurately understand the performance of each model. The configuration and quantity of common models and backup models can be adjusted according to the personalized needs of different enterprises to adapt to different operation and maintenance needs. When the common model cannot handle the event for some reason, the backup model can also take over quickly to ensure that the task will not be interrupted due to model failure, which greatly enhances the system's fault tolerance and business continuity, thereby solving the technical problems recorded in the background technology.

[0008] (II) Technical solution

[0009] To achieve the above objectives, the present invention is implemented through the following technical solutions: an automated operation and maintenance management system and method for an operating system, comprising the following steps:

[0010] Write automation scripts based on the calling relationships between modules and the data dependencies between functions, and import the written automation scripts into Ansible, Docker, and Puppet automation tools to generate the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model;

[0011] Detect the timestamps of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when an event occurs, as well as the CPU, memory, and disk resource usage during the execution process, and calculate the process evaluation coefficient of each operation and maintenance model

[0012] Get the number of successful executions of each operation and maintenance model Total execution times Calculate the result evaluation coefficient of each operation and maintenance model Combined process evaluation coefficient Obtain the operation and maintenance coefficient of each operation and maintenance model

[0013] Based on operation and maintenance coefficient Set up a common model and a backup model. When an event occurs, the common model takes the event out of the queue first and decides when and how to execute the corresponding script.

[0014] Furthermore, the shell command is used to detect the timestamps of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when the event occurs, and the startup time is obtained. Execution time and completion time After linear normalization, the startup evaluation index of each operation and maintenance model is calculated. Execution Evaluation Index Completion Evaluation Index

[0015]

[0016] Among them, x represents the number of the operation and maintenance model, x=1, 2, 3, i represents the sequential number of the event, i=1, 2, ..., m, j represents the sequential number of the number of executions of the same event, j=1, 2, ..., n, and max() refers to the maximum value of the values ​​of the other numbers that are fixed and the number x is different.

[0017] Furthermore, use system monitoring tools to monitor the CPU, memory, and disk resource usage during the automatic execution of events in each operation and maintenance model to obtain the CPU usage rate. Memory usage and disk usage After linear normalization, the CPU usage evaluation index of each operation and maintenance model is calculated. Memory usage evaluation index and disk usage evaluation index

[0018]

[0019] The CPU usage evaluation index of each operation and maintenance model Memory usage evaluation index and disk usage evaluation index The calculation formula is as above.

[0020] Furthermore, the startup evaluation index of each operation and maintenance model is obtained Execution Evaluation Index Completion evaluation index CPU usage evaluation index Memory usage evaluation index and disk usage evaluation index After linear normalization, the process evaluation coefficients of each operation and maintenance model are calculated.

[0021]

[0022] Corresponding process evaluation coefficients of each operation and maintenance model The calculation formula is as above.

[0023] Furthermore, the number of successful executions of each operation and maintenance model is obtained based on the logs. Total execution times After linear normalization, the result evaluation coefficients of each operation and maintenance model are calculated.

[0024]

[0025] Corresponding result evaluation coefficients of each operation and maintenance model The calculation formula is as above.

[0026] Furthermore, the process evaluation coefficients of each operation and maintenance model are obtained and result evaluation coefficient After linear normalization, the operation and maintenance coefficients of each operation and maintenance model are calculated.

[0027]

[0028] The operation and maintenance coefficients of the corresponding operation and maintenance models The calculation formula is as above.

[0029] Furthermore, the operation and maintenance coefficients of each operation and maintenance model are obtained Fixed subscript i in turn to sort by size, take The operation and maintenance model corresponding to the number is the commonly used model for the event corresponding to the subscript number. The operation and maintenance model with the corresponding number is the backup model for the event with the corresponding subscript number.

[0030] Furthermore, an event queue is created to manage the triggering of events and the execution of scripts. When an event occurs, the event is added to the queue. The common model takes the event out of the queue first and decides when and how to execute the corresponding script.

[0031] Furthermore, if the common model fails to execute, the event is added to the queue again, the common model is disqualified from scheduling, and the backup model takes the event out of the queue and decides when and how to execute the corresponding script;

[0032] If the backup model still fails to execute, it will stop running and issue an operation and maintenance abnormality warning for the corresponding event.

[0033] An automated operation and maintenance management system for an operating system, comprising:

[0034] Model building module, write automation scripts according to the calling relationship between modules and the data dependency relationship between functions, import the written automation scripts into Ansible, Docker and Puppet automation tools respectively, and generate the first operation and maintenance model, the second operation and maintenance model and the third operation and maintenance model;

[0035] The operation and maintenance process analysis module detects the timestamp of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when an event occurs, as well as the CPU, memory, and disk resource usage during the execution process, and calculates the process evaluation coefficient of each operation and maintenance model

[0036] Operation and maintenance result analysis module, obtains the number of successful executions of each operation and maintenance model Total execution times Calculate the result evaluation coefficient of each operation and maintenance model

[0037] Operation and maintenance comprehensive analysis module, obtain the process evaluation coefficient of each operation and maintenance model and result evaluation coefficient Calculate the operation and maintenance coefficient of each operation and maintenance model

[0038] Priority setting module, obtains the operation and maintenance coefficient of each operation and maintenance model Sequential operation and maintenance coefficient The size of the event is determined by the common model and the backup model.

[0039] The operation and maintenance module processes events according to the priority set by the priority setting module, and issues operation and maintenance abnormality warnings for corresponding events.

[0040] (III) Beneficial effects

[0041] The present invention provides an automated operation and maintenance management system and method for an operating system, which has the following beneficial effects:

[0042] 1. Write automation scripts based on the calling relationships between modules and the data dependencies between functions, and import the written automation scripts into Ansible, Docker and Puppet automation tools respectively to generate the first operation and maintenance model, the second operation and maintenance model and the third operation and maintenance model, so that the scripts can be automatically executed when an event occurs without human intervention, thereby greatly reducing the response time, realizing batch processing and automated management, thereby reducing a large amount of manual operation and maintenance work, and reducing operation and maintenance costs.

[0043] 2. Detect the timestamps of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when the event occurs, as well as the CPU, memory, and disk resource usage during the execution process, and calculate the process evaluation coefficient of each operation and maintenance model Taking into account factors such as the execution time and resource usage of the operation and maintenance model can help you make more informed decisions when choosing an operation and maintenance model and choose the most cost-effective solution.

[0044] 3. Obtain the number of successful executions of each operation and maintenance model Total execution times Calculate the result evaluation coefficient of each operation and maintenance model Combined process evaluation coefficient Obtain the operation and maintenance coefficient of each operation and maintenance model It comprehensively considers the performance of the operation and maintenance model during the execution process (process evaluation coefficient) and the final execution result (result evaluation coefficient), and can provide a comprehensive and objective evaluation index, which can more accurately understand the performance of each model and make more informed decisions.

[0045] 4. Based on the operation and maintenance coefficient Set up a common model and a backup model. When an event occurs, the common model will take the event out of the queue first and decide when and how to execute the corresponding script. This can manage and schedule system resources more reasonably, and adjust the configuration and quantity of the common model and backup models as needed to adapt to different operation and maintenance needs. When the common model cannot handle the event for some reason, the backup model can also take over quickly to ensure that the task will not be interrupted due to model failure, greatly enhancing the system's fault tolerance and business continuity. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 A schematic diagram of a process flow of an automated operation and maintenance management method for an operating system according to the present invention;

[0047] Figure 2 The present invention is a structural diagram of an automated operation and maintenance management system for operating systems. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0049] See also Figure 1 The present invention provides an automated operation and maintenance management method for an operating system, comprising the following steps:

[0050] Step 1: Write automation scripts based on the calling relationships between modules and the data dependencies between functions, and import the written automation scripts into Ansible, Docker, and Puppet automation tools respectively to generate the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model.

[0051] The step 1 includes the following contents:

[0052] Step 101: Use code analysis tools to identify the calling relationship between modules, and use data flow analysis tools to identify the data dependency between functions, and write corresponding automation scripts based on the calling relationship between modules and the data dependency between functions, including defining the order of task execution, the functions or methods to be called, and the data to be processed.

[0053] Step 102: Import the written automation scripts into Ansible, Docker, and Puppet automation tools respectively to generate a first operation and maintenance model, a second operation and maintenance model, and a third operation and maintenance model, so that the scripts can be automatically executed when an event occurs.

[0054] It should be noted that Ansible is a powerful automation platform, mainly used for configuration management, application deployment and task automation. It uses the simple and intuitive YAML format to write configuration files. It does not require any agent to be installed on the managed machine, and communication can be achieved through SSH. Ansible can automate various tasks, such as software installation, system configuration, service management, etc., greatly improving operation and maintenance efficiency.

[0055] Docker is an open source container platform that allows developers to package applications and their dependencies into a lightweight, portable container. With Docker, operations and maintenance personnel can easily deploy and manage these containers to achieve automated operations of the operating system. Docker can ensure the consistency of applications in different environments, reduce configuration errors, and improve system reliability and stability.

[0056] Puppet uses a client-server architecture to implement configuration management and automated deployment by deploying remote agents or client programs to the controlled nodes. It provides a variety of modules and functions that can automate various system configuration tasks, such as user management, package management, file deployment, etc. Puppet also supports custom module development, which can implement specific automation tasks according to specific needs.

[0057] When using, combine the contents in steps 101 and 102:

[0058] Automation scripts are written based on the calling relationships between modules and the data dependencies between functions, and the written automation scripts are imported into Ansible, Docker and Puppet automation tools respectively to generate the first operation and maintenance model, the second operation and maintenance model and the third operation and maintenance model, so that the scripts can be automatically executed when an event occurs without human intervention, thereby greatly reducing the response time, realizing batch processing and automated management, thereby reducing a large amount of manual operation and maintenance work, and reducing operation and maintenance costs.

[0059] Step 2: Detect the timestamps of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when the event occurs, as well as the CPU, memory, and disk resource usage during the execution process, and calculate the process evaluation coefficient of each operation and maintenance model

[0060] The step 2 includes the following contents:

[0061] Step 201: Detect the timestamps of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when an event occurs through a shell command to obtain the start time. Execution time and completion time After linear normalization, the startup evaluation index of each operation and maintenance model is calculated. Execution Evaluation Index Completion Evaluation Index

[0062]

[0063] Among them, x represents the number of the operation and maintenance model, x=1, 2, 3, i represents the sequential number of the event, i=1, 2, ..., m, j represents the sequential number of the number of executions of the same event, j=1, 2, ..., n, and max() refers to the maximum value of the values ​​​​when the other numbers are fixed and the number x is different.

[0064] Step 202: Use system monitoring tools to monitor the CPU, memory, and disk resource usage during the automatic execution of each operation and maintenance model to obtain the CPU usage rate. Memory usage and disk usage After linear normalization, the CPU usage evaluation index of each operation and maintenance model is calculated. Memory usage evaluation index and disk usage evaluation index

[0065]

[0066] Additional information: Here are some common scenarios and examples for automatic execution when events occur:

[0067] File creation / modification / deletion, directory changes, regular log cleaning, report sending, delayed execution, system startup / shutdown, initialization settings, cleaning temporary files, automatically sending notifications or attempting to restart a service when a service starts, stops or crashes, triggering specific processing flows when receiving data packets from a specific IP address or port, user login / logout, completion of specific operations, etc.

[0068] Step 203: Obtain the startup evaluation index of each operation and maintenance model Execution Evaluation Index Completion evaluation index CPU usage evaluation index Memory usage evaluation index and disk usage evaluation index After linear normalization, the process evaluation coefficients of each operation and maintenance model are calculated.

[0069]

[0070] Corresponding process evaluation coefficients of each operation and maintenance model The calculation formula is as above.

[0071] When using, combine the contents in steps 201 to 203:

[0072] Detect the timestamps of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when an event occurs, as well as the CPU, memory, and disk resource usage during the execution process, and calculate the process evaluation coefficient of each operation and maintenance model Taking into account factors such as the execution time and resource usage of the operation and maintenance model can help you make more informed decisions when choosing an operation and maintenance model and choose the most cost-effective solution.

[0073] Step 3: Get the number of successful executions of each operation and maintenance model Total execution times Calculate the result evaluation coefficient of each operation and maintenance model Combined process evaluation coefficient Obtain the operation and maintenance coefficient of each operation and maintenance model

[0074] The step three includes the following contents:

[0075] Step 301: Obtain the number of successful executions of each operation and maintenance model based on the log Total execution times After linear normalization, the result evaluation coefficients of each operation and maintenance model are calculated.

[0076]

[0077] Corresponding result evaluation coefficients of each operation and maintenance model The calculation formula is as above.

[0078] Step 302: Obtain the process evaluation coefficient of each operation and maintenance model and result evaluation coefficient After linear normalization, the operation and maintenance coefficients of each operation and maintenance model are calculated.

[0079]

[0080] The operation and maintenance coefficients of the corresponding operation and maintenance models The calculation formula is as above.

[0081] When using, combine the contents in steps 301 and 302:

[0082] Get the number of successful executions of each operation and maintenance model Total execution times Calculate the result evaluation coefficient of each operation and maintenance model Combined process evaluation coefficient Obtain the operation and maintenance coefficient of each operation and maintenance model It comprehensively considers the performance of the operation and maintenance model during the execution process (process evaluation coefficient) and the final execution result (result evaluation coefficient), and can provide a comprehensive and objective evaluation index, which can more accurately understand the performance of each model and make more informed decisions.

[0083] Step 4: Based on the operation and maintenance coefficient Set up a common model and a backup model. When an event occurs, the common model takes the event out of the queue first and decides when and how to execute the corresponding script.

[0084] The step 4 includes the following contents:

[0085] Step 401: Obtain the operation and maintenance coefficient of each operation and maintenance model Fixed subscript i in turn to sort by size, take The operation and maintenance model corresponding to the number is the commonly used model for the event corresponding to the subscript number. The operation and maintenance model with the corresponding number is the backup model for the event with the corresponding subscript number.

[0086] It should be noted that Md() refers to the median.

[0087] Step 402: Create an event queue to manage event triggering and script execution. When an event occurs, the event is added to the queue. The common model takes the event out of the queue first and decides when and how to execute the corresponding script.

[0088] The event queue is a queue that stores tasks to be executed, and the tasks are executed in strict chronological order. In Flutter, the event queue is further divided into microtask queue and macrotask queue. The microtask queue is used to handle tasks that need to be executed as soon as possible, such as status updates; while the macrotask queue is used to handle more time-consuming tasks, such as network requests and file reading and writing. Whenever a communication is performed, the method-driven event adds the program handle corresponding to the event and its priority to the event program handle queue according to the type of event to be executed. This mechanism ensures that when processing complex events, the system can manage and schedule these events in an orderly and efficient manner.

[0089] Step 403: If the common model fails to execute, the event is added to the queue again, the scheduling qualification of the common model is cancelled, and the backup model takes the event out of the queue and decides when and how to execute the corresponding script.

[0090] If the backup model still fails to execute, it will stop running and issue an operation and maintenance abnormality warning for the corresponding event.

[0091] When using, combine the contents in steps 401 to 403:

[0092] Based on operation and maintenance coefficient Set up a common model and a backup model. When an event occurs, the common model will take the event out of the queue first and decide when and how to execute the corresponding script. This can manage and schedule system resources more reasonably, and adjust the configuration and quantity of the common model and backup models as needed to adapt to different operation and maintenance needs. When the common model cannot handle the event for some reason, the backup model can also take over quickly to ensure that the task will not be interrupted due to model failure, greatly enhancing the system's fault tolerance and business continuity.

[0093] See also Figure 2 The present invention provides an automated operation and maintenance management system for an operating system, comprising:

[0094] The model building module writes automation scripts based on the calling relationship between modules and the data dependency relationship between functions, and imports the written automation scripts into Ansible, Docker and Puppet automation tools respectively to generate the first operation and maintenance model, the second operation and maintenance model and the third operation and maintenance model.

[0095] The operation and maintenance process analysis module detects the timestamp of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when an event occurs, as well as the CPU, memory, and disk resource usage during the execution process, and calculates the process evaluation coefficient of each operation and maintenance model

[0096] Operation and maintenance result analysis module, obtains the number of successful executions of each operation and maintenance model Total execution times Calculate the result evaluation coefficient of each operation and maintenance model

[0097] Operation and maintenance comprehensive analysis module, obtain the process evaluation coefficient of each operation and maintenance model and result evaluation coefficient Calculate the operation and maintenance coefficient of each operation and maintenance model

[0098] Priority setting module, obtains the operation and maintenance coefficient of each operation and maintenance model Sequential operation and maintenance coefficient The size of the event is determined by the common model and the backup model.

[0099] The operation and maintenance module processes events according to the priority set by the priority setting module, and issues operation and maintenance abnormality warnings for corresponding events.

[0100] The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination thereof. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product. A person of ordinary skill in the art may appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein may be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution.

[0101] 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 on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0102] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. An automated operation and maintenance management method for an operating system, characterized in that: The steps include: Write automation scripts based on the calling relationships between modules and the data dependencies between functions, and import the written automation scripts into Ansible, Docker, and Puppet automation tools to generate the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model; Detect the timestamps of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when an event occurs, as well as the CPU, memory, and disk resource usage during the execution process, and calculate the process evaluation coefficient of each operation and maintenance model ; Use shell commands to detect the timestamps of automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when an event occurs, and obtain the startup time , Execution time and completion time After linear normalization, the startup evaluation index of each operation and maintenance model is calculated. , Execution Evaluation Index Completion Evaluation Index : in, x Indicates the number of the operation and maintenance model. , i Indicates the sequence number of the event. , j A sequential number indicating the number of times the same event is executed. , It means that the rest of the numbers are fixed, x The maximum value of different values; Use system monitoring tools to monitor the CPU, memory, and disk resource usage during the automatic execution of events in each operation and maintenance model to obtain CPU usage , memory usage and disk usage After linear normalization, the CPU usage evaluation index of each operation and maintenance model is calculated. , memory usage evaluation index and disk usage evaluation index : Get the startup evaluation index of each operation and maintenance model , Execution Evaluation Index , Completion Evaluation Index , CPU usage evaluation index , memory usage evaluation index and disk usage evaluation index , after linear normalization, the process evaluation coefficients of each operation and maintenance model are calculated : Get the number of successful executions of each operation and maintenance model Total execution times , calculate the result evaluation coefficient of each operation and maintenance model , combined with the process evaluation coefficient Obtain the operation and maintenance coefficient of each operation and maintenance model ; Obtain the number of successful executions of each operation and maintenance model based on the log Total execution times , after linear normalization, the result evaluation coefficients of each operation and maintenance model are calculated : Obtain the process evaluation coefficient of each operation and maintenance model and result evaluation coefficient , after linear normalization, the operation and maintenance coefficients of each operation and maintenance model are calculated : Based on operation and maintenance coefficient Set up a common model and a backup model. When an event occurs, the common model takes the event out of the queue first and decides when and how to execute the corresponding script.

2. The method for automated operation and maintenance management of an operating system according to claim 1, characterized in that: Get the operation and maintenance coefficient of each operation and maintenance model , fix the subscript in sequence i Sort by size, take The operation and maintenance model corresponding to the number is the commonly used model for the event corresponding to the subscript number. The operation and maintenance model with the corresponding number is the backup model for the event with the corresponding subscript number.

3. The method for automated operation and maintenance management of an operating system according to claim 2, characterized in that: Create an event queue to manage event triggering and script execution. When an event occurs, the event is added to the queue. The common model takes the event out of the queue first and decides when and how to execute the corresponding script.

4. The method for automated operation and maintenance management of an operating system according to claim 3, characterized in that: If the common model fails to execute, the event is added to the queue again, the common model is disqualified from scheduling, and the backup model takes the event out of the queue and decides when and how to execute the corresponding script; If the backup model still fails to execute, it will stop running and issue an operation and maintenance abnormality warning for the corresponding event.

5. An automated operation and maintenance management system for an operating system, used to implement the methods described in claims 1 to 4, characterized in that: include: Model building module, write automation scripts according to the calling relationship between modules and the data dependency relationship between functions, import the written automation scripts into Ansible, Docker and Puppet automation tools respectively, and generate the first operation and maintenance model, the second operation and maintenance model and the third operation and maintenance model; The operation and maintenance process analysis module detects the timestamp of the automatic execution of the first operation and maintenance model, the second operation and maintenance model, and the third operation and maintenance model when an event occurs, as well as the CPU, memory, and disk resource usage during the execution process, and calculates the process evaluation coefficient of each operation and maintenance model ; Operation and maintenance result analysis module, obtains the number of successful executions of each operation and maintenance model Total execution times , calculate the result evaluation coefficient of each operation and maintenance model ; Operation and maintenance comprehensive analysis module, obtain the process evaluation coefficient of each operation and maintenance model and result evaluation coefficient , calculate the operation and maintenance coefficient of each operation and maintenance model ; Priority setting module, obtains the operation and maintenance coefficient of each operation and maintenance model , operation and maintenance coefficient The size of the event is determined by the common model and the backup model. The operation and maintenance module processes events according to the priority set by the priority setting module, and issues operation and maintenance abnormality warnings for corresponding events.