Script pushing method and system based on task center

By using a script push method and system based on a task center and adopting a C/S architecture, automated operation and maintenance of remote hosts or devices is achieved, solving the problem that traditional operation and maintenance methods cannot respond quickly and maintain efficiently, and improving operation and maintenance efficiency and management automation level.

CN118984335APending Publication Date: 2024-11-19INSPUR QILU SOFTWARE IND
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410993795.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-24
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

Traditional manual operation and maintenance methods cannot meet the needs of rapid response and efficient operation and maintenance, especially in enterprises where the complexity of IT systems is increasing, making it difficult to perform operations such as configuration, deployment, updates and troubleshooting on remote hosts or devices.

Method used

The system adopts a script push method and system based on a task center, using a C/S architecture. Script push tasks are created through the task center front-end interface, the server processes and stores the strategies, and the client executes and reports the results. It provides a RESTful API interface to achieve automated script push and management.

Benefits of technology

It has improved the automation level of system management and operation and maintenance, and enabled fast, efficient and accurate configuration, deployment, update and troubleshooting of remote hosts or devices, thereby improving operation and maintenance efficiency, reducing labor costs and simplifying management processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118984335A_ABST
    Figure CN118984335A_ABST
Patent Text Reader

Abstract

The invention discloses a script pushing method and system based on a task center, and relates to the technical field of operation and maintenance management, and the method comprises the steps that a user creates a script pushing task and configures a script pushing strategy on a front-end interface of the task center according to an actual application scene; the server processes a script pushing task created by a user through the front-end interface of the task center, and stores a script pushing strategy corresponding to the script pushing task into a database; and the client polls and sends a request to the server, obtains the script pushing task, executes the script pushing task according to the script pushing strategy, and reports an execution result of the script pushing task to the server. By using the method or the system provided by the invention, the operation and maintenance personnel only need to create the script pushing task with the set function and configure the script pushing strategy on the front-end interface of the task center, so that the automatic operation and maintenance and management of the remote terminal can be realized, the working efficiency of the operation and maintenance personnel is effectively improved, the labor cost is reduced, and the management process is simplified.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of operation and maintenance management, and in particular to a task center-based script pushing method and system. Background Art

[0002] As the scale of corporate business expands and the complexity of IT systems increases, traditional manual operation and maintenance methods can no longer meet the needs of rapid response and efficient operation and maintenance. Summary of the invention

[0003] In view of the needs and shortcomings of current technological development, the present invention provides a script push method and system based on the task center to improve the automation level of system management and operation and maintenance, and realize the configuration, deployment, update and troubleshooting operations on remote hosts or devices quickly, efficiently and accurately.

[0004] In the first aspect, the present invention provides a script push method based on a task center, and the technical solution adopted to solve the above technical problems is as follows:

[0005] A script push method based on a task center, the method adopts a C / S architecture mode, and includes the following steps:

[0006] Users create script push tasks and configure script push strategies in the front-end interface of the task center according to actual application scenarios;

[0007] The server processes the script push tasks created by users through the task center front-end interface and stores the corresponding script push strategies in the database;

[0008] The client sends a polling request to the server, obtains the script push task, executes the script push task according to the script push strategy, and reports the execution result of the script push task to the server.

[0009] Optionally, the server is responsible for processing requests from client applications, providing a RESTful API interface for the client, and interacting with the database to implement data read and write operations. The API interfaces provided by the server to the client include a script task creation interface, a script task delivery interface, a script task execution result reporting interface, and a script task execution result query interface.

[0010] The script task creation interface is responsible for receiving the script push task information configured by the user in the task center interface, verifying and integrating the incoming relevant data, obtaining the script push strategy information and storing it in the relevant data table of the database;

[0011] The script task delivery interface is responsible for filtering the script push tasks and delivering the script push tasks that meet the requirements to the target terminal;

[0012] The script task execution result reporting interface is responsible for receiving the execution results of the terminal script push task and solidifying the task execution results into the script push task result table of the database;

[0013] The script task execution result query interface is responsible for obtaining the script push task execution results of all terminals from the database, integrating the database query data and sending it to the task center.

[0014] Further optionally, the front-end interface of the task center is responsible for providing the following functions to the user: creating script tasks, editing script tasks, pausing and deleting script tasks, and querying script tasks.

[0015] Further optionally, the client is responsible for receiving the script push task sent by the server, parsing the script push strategy, completing the execution of the script push task and reporting the result;

[0016] The client implements the above operations through a script policy acquisition unit, a task status acquisition unit, an account check unit, a script creation unit, and a script execution unit, wherein:

[0017] The script strategy unit is responsible for parsing the script push strategy sent by the server, and the strategy information obtained from the parsing provides support for the operation of the script push task;

[0018] The task status acquisition unit is responsible for acquiring the working status of the current script push task to determine from which step the script push task should be executed;

[0019] The account checking unit is responsible for determining whether the execution account specified in the script push policy sent by the server exists in the client. The specific implementation process is as follows: First, the client reads the / etc / password file information. The password file records the basic attributes of each user. Second, the client extracts the user name information in the password file. Finally, the client matches the execution account attribute value in the script push policy with the extracted user name information. a) If the match is successful, it means that the user exists in the terminal and the script push task continues to be executed. b) If the match fails, it means that the user does not exist in the terminal and the script push task is terminated. The script push task fails to execute and the running result is reported to the server.

[0020] The script creation unit is responsible for creating a script file, setting permissions for the script file, and writing the script content in the script push strategy to the script file. The specific implementation process is as follows: First, the client accesses the static route of the server to obtain the script content. Second, the client uses the decryption algorithm to decode the script content and verify the integrity of the information. Finally, the client creates a script file, sets the access permissions for the script file, and writes the decrypted script content into the script file.

[0021] The script execution unit is responsible for running the script on the terminal with the specified execution account to implement specific functions. The specific implementation process is as follows: First, use context and select to implement the timeout control mechanism and start a coroutine. Secondly, determine the script type in the script push strategy in the coroutine code block: shell script or python script, call the corresponding cmd command according to the script type, and run the script with the specified execution user. Finally, when the script is executed, destroy the coroutine, release resources, and report the execution result of the script push task to the server.

[0022] Preferably, after the client reports the execution result of the script push task to the server, the progress and result of the client script execution are monitored through the script task query function of the task center front-end interface to facilitate the management and maintenance of the operation and maintenance personnel.

[0023] In a second aspect, the present invention provides a script push system based on a task center, and the technical solution adopted to solve the above technical problems is as follows:

[0024] A script push system based on a task center, the structure of which includes:

[0025] The task center module is deployed on the front end to provide a visual interface for creating script push tasks and configuring script push strategies;

[0026] The task processing module is deployed on the server side and is used to process the script push tasks created by users through the task center module and store the corresponding script push strategies in the database;

[0027] The acquisition execution module is deployed on the client and is used to poll and send requests to the server, obtain the script push task, execute the script push task according to the script push strategy, and report the execution result of the script push task to the server.

[0028] Optionally, the task processing module involved is responsible for processing requests from client applications, providing a RESTful API interface for the client, and interacting with the database to implement data read and write operations. The API interface provided by the task processing module to the client includes a script task creation interface, a script task delivery interface, a script task execution result reporting interface, and a script task execution result query interface;

[0029] The script task creation interface is responsible for receiving the script push task information configured by the user in the task center module, verifying and integrating the incoming relevant data, obtaining the script push strategy information and storing it in the relevant data table of the database;

[0030] The script task delivery interface is responsible for filtering the script push tasks and delivering the script push tasks that meet the requirements to the target terminal;

[0031] The script task execution result reporting interface is responsible for receiving the execution results of the terminal script push task and solidifying the task execution results into the script push task result table of the database;

[0032] The script task execution result query interface is responsible for obtaining the script push task execution results of all terminals from the database, integrating the database query data and sending it to the front-end task center module.

[0033] Further optionally, the visual interface of the task center module involved is responsible for providing the following functions to the user: creating script tasks, editing script tasks, pausing and deleting script tasks, and querying script tasks.

[0034] Further optionally, the acquisition execution module involved is responsible for receiving the script push task issued by the task processing module, parsing the script push strategy, completing the execution of the script push task and reporting the result;

[0035] The acquisition execution module implements the above operations through the acquisition script strategy unit, the acquisition task status unit, the account checking unit, the script creation unit and the script execution unit, wherein:

[0036] The script strategy unit is responsible for parsing the script push strategy sent by the server, and the strategy information obtained from the parsing provides support for the operation of the script push task;

[0037] The task status acquisition unit is responsible for acquiring the working status of the current script push task to determine from which step the script push task should be executed;

[0038] The account checking unit is responsible for determining whether the execution account specified in the script push policy sent by the server exists in the client. The specific implementation process is as follows: First, the client reads the / etc / password file information. The password file records the basic attributes of each user. Second, the client extracts the user name information in the password file. Finally, the client matches the execution account attribute value in the script push policy with the extracted user name information. a) If the match is successful, it means that the user exists in the terminal and the script push task continues to be executed. b) If the match fails, it means that the user does not exist in the terminal and the script push task is terminated. The script push task fails to execute and the running result is reported to the server.

[0039] The script creation unit is responsible for creating a script file, setting permissions for the script file, and writing the script content in the script push strategy to the script file. The specific implementation process is as follows: First, the client accesses the static route of the server to obtain the script content. Second, the client uses the decryption algorithm to decode the script content and verify the integrity of the information. Finally, the client creates a script file, sets the access permissions for the script file, and writes the decrypted script content into the script file.

[0040] The script execution unit is responsible for running the script on the terminal with the specified execution account to implement specific functions. The specific implementation process is as follows: First, use context and select to implement the timeout control mechanism and start a coroutine. Secondly, determine the script type in the script push strategy in the coroutine code block: shell script or python script, call the corresponding cmd command according to the script type, and run the script with the specified execution user. Finally, when the script is executed, destroy the coroutine, release resources, and report the execution result of the script push task to the server.

[0041] Preferably, after the execution module reports the execution result of the script push task to the server, the script task query function provided by the task center module monitors the progress and results of the client script execution to facilitate management and maintenance by operation and maintenance personnel.

[0042] Compared with the prior art, the script push method and system based on the task center of the present invention have the following beneficial effects:

[0043] 1. The present invention can improve the automation level of system management and operation and maintenance, and realize fast, efficient and accurate configuration, deployment, update and troubleshooting operations on remote hosts or devices; by using the method or system of the present invention, operation and maintenance personnel only need to create a script push task with set functions in the front-end interface of the task center and configure the script push strategy to realize automatic operation and management of remote terminals, effectively improve the work efficiency of operation and maintenance personnel, reduce labor costs, and simplify management processes;

[0044] 2. The present invention centrally manages script push tasks through a task center interface or module, which can realize the automation and batch processing of script push and improve push efficiency; the task center interface or module provides basic functions of creating script tasks, editing script tasks, pausing and deleting script tasks, and querying script tasks, which can facilitate users to manage and maintain script push tasks; the task center interface or module will monitor the push progress and results in real time during the script push process, and will promptly process and feedback when abnormal situations occur, to ensure the stability and reliability of the push process. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Attached Figure 1is a flow chart of a method according to Embodiment 1 of the present invention;

[0046] Attached Figure 2 is a module connection block diagram of the second embodiment of the present invention;

[0047] Attached Figure 3 is a flowchart of an implementation of an account checking unit in an embodiment of the present invention;

[0048] Attached Figure 4 is an implementation flow chart of a script creation unit in an embodiment of the present invention;

[0049] Attached Figure 5 It is an implementation flow chart of the script execution unit in an embodiment of the present invention. DETAILED DESCRIPTION

[0050] In order to make the technical solution, the technical problem solved and the technical effect of the present invention more clearly understood, the technical solution of the present invention is clearly and completely described below in conjunction with specific embodiments.

[0051] Embodiment 1:

[0052] Combined with Figure 1 This embodiment proposes a script push method based on a task center, which adopts a C / S architecture mode and includes the following steps:

[0053] S1. Users create script push tasks and configure script push strategies in the front-end interface of the task center based on actual application scenarios.

[0054] The front-end interface of the task center is responsible for providing users with the following functions: creating script tasks, editing script tasks, pausing and deleting script tasks, and querying script tasks.

[0055] S2. The server processes the script push tasks created by the user through the task center front-end interface, and stores the corresponding script push strategies in the database.

[0056] Specifically, the server is responsible for processing requests from client applications, providing the client with a RESTful-style API interface, and interacting with the database to implement data reading and writing operations. The API interfaces provided by the server to the client include a script task creation interface, a script task delivery interface, a script task execution result reporting interface, and a script task execution result query interface.

[0057] The script task creation interface is responsible for receiving the script push task information configured by the user in the task center interface, verifying and integrating the incoming relevant data, obtaining the script push strategy information and storing it in the relevant data table of the database.

[0058] The script task sending interface is responsible for screening and filtering script push tasks, and sending the script push tasks that meet the requirements to the target terminal.

[0059] The script task execution result reporting interface is responsible for receiving the execution results of the terminal script push task and solidifying the task execution results into the script push task result table of the database.

[0060] The script task execution result query interface is responsible for obtaining the script push task execution results of all terminals from the database, integrating the database query data and sending it to the task center.

[0061] S3. The client sends a polling request to the server to obtain the script push task, executes the script push task according to the script push strategy, and reports the execution result of the script push task to the server.

[0062] Specifically, the client is responsible for receiving the script push tasks sent by the server, parsing the script push strategy, and completing the execution of the script push tasks and reporting the results.

[0063] The client implements the above operations through a script policy acquisition unit, a task status acquisition unit, an account check unit, a script creation unit, and a script execution unit, wherein:

[0064] The script strategy unit is responsible for parsing the script push strategy sent by the server, and the strategy information obtained from the parsing provides support for the operation of the script push task;

[0065] The task status acquisition unit is responsible for acquiring the working status of the current script push task to determine from which step the script push task should be executed;

[0066] The account checking unit is responsible for determining whether the execution account specified in the script push policy sent by the server exists in the client. Figure 3 ,The specific implementation process is as follows: First, the client reads the / etc / password file information, which records the basic attributes of each user. Second, the client extracts the user name information in the password file. Finally, the client matches the execution account attribute value in the script push policy with the extracted user name information. a) If the match is successful, it means that the user exists in the terminal, and the script push task continues to be executed. b) If the match fails, it means that the user does not exist in the terminal, and the script push task is terminated. The script push task fails to execute, and the running result is reported to the server.

[0067] The script creation unit is responsible for creating script files, setting permissions for script files, writing the script content in the script push policy to the script file, and combining the attached Figure 4,The specific implementation process is as follows: First, the client accesses the static route of the server to obtain the ,script content. Second, the client uses a decryption algorithm to decode the script ,content and verify the integrity of the information. Finally, the client creates a script file, sets the ,access rights of the script file, and writes the decrypted script content into the ,script file.

[0068] The script execution unit is responsible for running the script on the terminal with the specified execution account to achieve specific functions. Figure 5 ,The specific implementation process is as follows: First, use context and select to implement the timeout control mechanism and start a coroutine. Secondly, determine the script type in the script push strategy in the coroutine code block: shell script or python script, call the corresponding cmd command according to the script type, and run the script as the specified execution user. Finally, when the script is executed, destroy the coroutine, release resources, and report the execution result of the script push task to the server.

[0069] After the client reports the execution result of the script push task to the server, the progress and results of the client script execution are monitored through the script task query function of the task center front-end interface to facilitate the management and maintenance of operation and maintenance personnel.

[0070] Embodiment 2:

[0071] Combined with Figure 2 This embodiment proposes a script push system based on a task center, and its structure includes:

[0072] The task center module is deployed on the front end to provide a visual interface for creating script push tasks and configuring script push strategies;

[0073] The task processing module is deployed on the server side and is used to process the script push tasks created by users through the task center module and store the corresponding script push strategies in the database;

[0074] The acquisition execution module is deployed on the client and is used to poll and send requests to the server, obtain the script push task, execute the script push task according to the script push strategy, and report the execution result of the script push task to the server.

[0075] In this embodiment, the visual interface of the task center module involved is responsible for providing the following functions to the user: creating script tasks, editing script tasks, pausing and deleting script tasks, and querying script tasks.

[0076] In this embodiment, the task processing module is responsible for processing the client application's request, providing the client with a RESTful API interface, and interacting with the database to implement data read and write operations. The API interface provided by the task processing module to the client includes a script task creation interface, a script task delivery interface, a script task execution result reporting interface, and a script task execution result query interface. Specifically:

[0077] The script task creation interface is responsible for receiving the script push task information configured by the user in the task center module, verifying and integrating the incoming relevant data, obtaining the script push strategy information and storing it in the relevant data table of the database;

[0078] The script task delivery interface is responsible for filtering the script push tasks and delivering the script push tasks that meet the requirements to the target terminal;

[0079] The script task execution result reporting interface is responsible for receiving the execution results of the terminal script push task and solidifying the task execution results into the script push task result table of the database;

[0080] The script task execution result query interface is responsible for obtaining the script push task execution results of all terminals from the database, integrating the database query data and sending it to the front-end task center module.

[0081] In this embodiment, the acquisition execution module is responsible for receiving the script push task issued by the task processing module, parsing the script push strategy, and completing the execution of the script push task and reporting the results.

[0082] The acquisition execution module implements the above operations through the acquisition script strategy unit, the acquisition task status unit, the account checking unit, the script creation unit and the script execution unit, wherein:

[0083] The script strategy unit is responsible for parsing the script push strategy sent by the server, and the strategy information obtained from the parsing provides support for the operation of the script push task;

[0084] The task status acquisition unit is responsible for acquiring the working status of the current script push task to determine from which step the script push task should be executed;

[0085] The account checking unit is responsible for determining whether the execution account specified in the script push policy sent by the server exists in the client. Figure 3,The specific implementation process is as follows: First, the client reads the / etc / password file information, which records the basic attributes of each user. Second, the client extracts the user name information in the password file. Finally, the client matches the execution account attribute value in the script push policy with the extracted user name information. a) If the match is successful, it means that the user exists in the terminal, and the script push task continues to be executed. b) If the match fails, it means that the user does not exist in the terminal, and the script push task is terminated. The script push task fails to execute, and the running result is reported to the server.

[0086] The script creation unit is responsible for creating script files, setting permissions for script files, writing the script content in the script push policy to the script file, and combining the attached Figure 4 ,The specific implementation process is as follows: First, the client accesses the static route of the server to obtain the ,script content. Second, the client uses a decryption algorithm to decode the script ,content and verify the integrity of the information. Finally, the client creates a script file, sets the ,access rights of the script file, and writes the decrypted script content into the ,script file.

[0087] The script execution unit is responsible for running the script on the terminal with the specified execution account to achieve specific functions. Figure 5 ,The specific implementation process is as follows: First, use context and select to implement the timeout control mechanism and start a coroutine. Secondly, determine the script type in the script push strategy in the coroutine code block: shell script or python script, call the corresponding cmd command according to the script type, and run the script as the specified execution user. Finally, when the script is executed, destroy the coroutine, release resources, and report the execution result of the script push task to the server.

[0088] After the execution module involved reports the execution result of the script push task to the server, the progress and results of the client script execution are monitored through the script task query function provided by the task center module to facilitate the management and maintenance of the operation and maintenance personnel.

[0089] In summary, the use of a task-centered script push method and system of the present invention can improve push efficiency and optimize task management, and realize real-time monitoring and feedback of script push status.

[0090] The above specific examples are used to explain the principles and implementation methods of the present invention in detail. These examples are only used to help understand the core technical content of the present invention. Based on the above specific embodiments of the present invention, any improvements and modifications made by technicians in this technical field without departing from the principles of the present invention should fall within the scope of patent protection of the present invention.

Claims

1. A script push method based on a task center, characterized in that: This method adopts the C / S architecture mode and includes the following steps: Users create script push tasks and configure script push strategies in the front-end interface of the task center according to actual application scenarios; The server processes the script push tasks created by users through the task center front-end interface and stores the corresponding script push strategies in the database; The client sends a polling request to the server, obtains the script push task, executes the script push task according to the script push strategy, and reports the execution result of the script push task to the server.

2. A task-centered script push method according to claim 1, characterized in that: The server is responsible for processing requests from client applications, providing a RESTful API interface for the client, and interacting with the database to implement data read and write operations. The API interfaces provided by the server to the client include the script task creation interface, script task delivery interface, script task execution result reporting interface, and script task execution result query interface. The script task creation interface is responsible for receiving the script push task information configured by the user in the task center interface, verifying and integrating the incoming relevant data, obtaining the script push strategy information and storing it in the relevant data table of the database; The script task delivery interface is responsible for filtering the script push tasks and delivering the script push tasks that meet the requirements to the target terminal; The script task execution result reporting interface is responsible for receiving the execution results of the terminal script push task and solidifying the task execution results into the script push task result table of the database; The script task execution result query interface is responsible for obtaining the script push task execution results of all terminals from the database, integrating the database query data and sending it to the task center.

3. A task-centered script push method according to claim 2, characterized in that: The front-end interface of the task center is responsible for providing users with the following functions: creating script tasks, editing script tasks, pausing and deleting script tasks, and querying script tasks.

4. The script push method based on task center according to claim 3 is characterized in that: The client is responsible for receiving the script push tasks sent by the server, parsing the script push strategy, completing the execution of the script push tasks and reporting the results; The client implements the above operations through a script policy acquisition unit, a task status acquisition unit, an account check unit, a script creation unit, and a script execution unit, wherein: The script strategy unit is responsible for parsing the script push strategy sent by the server, and the strategy information obtained from the parsing provides support for the operation of the script push task; The task status acquisition unit is responsible for acquiring the working status of the current script push task to determine from which step the script push task should be executed; The account checking unit is responsible for determining whether the execution account specified in the script push policy sent by the server exists in the client. The specific implementation process is as follows: First, the client reads the / etc / password file information. The password file records the basic attributes of each user. Second, the client extracts the user name information in the password file. Finally, the client matches the execution account attribute value in the script push policy with the extracted user name information. a) If the match is successful, it means that the user exists in the terminal and the script push task continues to be executed. b) If the match fails, it means that the user does not exist in the terminal and the script push task is terminated. The script push task fails to execute and the running result is reported to the server. The script creation unit is responsible for creating a script file, setting permissions for the script file, and writing the script content in the script push strategy to the script file. The specific implementation process is as follows: First, the client accesses the static route of the server to obtain the script content. Second, the client uses the decryption algorithm to decode the script content and verify the integrity of the information. Finally, the client creates a script file, sets the access permissions for the script file, and writes the decrypted script content into the script file. The script execution unit is responsible for running the script on the terminal with the specified execution account to implement specific functions. The specific implementation process is as follows: First, use context and select to implement the timeout control mechanism and start a coroutine. Secondly, determine the script type in the script push strategy in the coroutine code block: shell script or python script, call the corresponding cmd command according to the script type, and run the script with the specified execution user. Finally, when the script is executed, destroy the coroutine, release resources, and report the execution result of the script push task to the server.

5. A task-centered script push method according to claim 4, characterized in that: After the client reports the execution result of the script push task to the server, the progress and results of the client script execution are monitored through the script task query function of the task center front-end interface to facilitate the management and maintenance of operation and maintenance personnel.

6. A script push system based on a task center, characterized in that: Its structure includes: The task center module is deployed on the front end to provide a visual interface for creating script push tasks and configuring script push strategies; The task processing module is deployed on the server side and is used to process the script push tasks created by users through the task center module and store the corresponding script push strategies in the database; The acquisition execution module is deployed on the client and is used to poll and send requests to the server, obtain the script push task, execute the script push task according to the script push strategy, and report the execution result of the script push task to the server.

7. A task-center-based script push system according to claim 6, characterized in that: The task processing module is responsible for processing requests from client applications, providing a RESTful API interface for the client, and interacting with the database to implement data read and write operations. The API interface provided by the task processing module to the client includes a script task creation interface, a script task delivery interface, a script task execution result reporting interface, and a script task execution result query interface; The script task creation interface is responsible for receiving the script push task information configured by the user in the task center module, verifying and integrating the incoming relevant data, obtaining the script push strategy information and storing it in the relevant data table of the database; The script task delivery interface is responsible for filtering the script push tasks and delivering the script push tasks that meet the requirements to the target terminal; The script task execution result reporting interface is responsible for receiving the execution results of the terminal script push task and solidifying the task execution results into the script push task result table of the database; The script task execution result query interface is responsible for obtaining the script push task execution results of all terminals from the database, integrating the database query data and sending it to the front-end task center module.

8. A task-center-based script push system according to claim 7, characterized in that: The visual interface of the task center module is responsible for providing the following functions to users: creating script tasks, editing script tasks, pausing and deleting script tasks, and querying script tasks.

9. A task-center-based script push system according to claim 8, characterized in that: The acquisition execution module is responsible for receiving the script push task issued by the task processing module, parsing the script push strategy, completing the execution of the script push task and reporting the results; The acquisition execution module implements the above operations through an acquisition script strategy unit, an acquisition task status unit, an account checking unit, a script creation unit and a script execution unit, wherein: The script strategy unit is responsible for parsing the script push strategy sent by the server, and the strategy information obtained from the parsing provides support for the operation of the script push task; The task status acquisition unit is responsible for acquiring the working status of the current script push task to determine from which step the script push task should be executed; The account checking unit is responsible for determining whether the execution account specified in the script push policy sent by the server exists in the client. The specific implementation process is as follows: First, the client reads the / etc / password file information. The password file records the basic attributes of each user. Second, the client extracts the user name information in the password file. Finally, the client matches the execution account attribute value in the script push policy with the extracted user name information. a) If the match is successful, it means that the user exists in the terminal and the script push task continues to be executed. b) If the match fails, it means that the user does not exist in the terminal and the script push task is terminated. The script push task fails to execute and the running result is reported to the server. The script creation unit is responsible for creating a script file, setting permissions for the script file, and writing the script content in the script push strategy to the script file. The specific implementation process is as follows: First, the client accesses the static route of the server to obtain the script content. Second, the client uses the decryption algorithm to decode the script content and verify the integrity of the information. Finally, the client creates a script file, sets the access permissions for the script file, and writes the decrypted script content into the script file. The script execution unit is responsible for running the script on the terminal with the specified execution account to implement specific functions. The specific implementation process is as follows: First, use context and select to implement the timeout control mechanism and start a coroutine. Secondly, determine the script type in the script push strategy in the coroutine code block: shell script or python script, call the corresponding cmd command according to the script type, and run the script with the specified execution user. Finally, when the script is executed, destroy the coroutine, release resources, and report the execution result of the script push task to the server.

10. A task-center-based script push system according to claim 9, characterized in that: After the acquisition execution module reports the execution result of the script push task to the server, the progress and result of the client script execution are monitored through the script task query function provided by the task center module to facilitate the management and maintenance of the operation and maintenance personnel.