CN116489017A - Operation and maintenance management method and device - Google Patents

Abstract

The application provides an operation and maintenance management method and device, which can improve the efficiency of operation and maintenance management and realize the batch delivery function in operation and maintenance management tasks. The method comprises the following steps: acquiring configuration information of at least one node control in a first scenario to be executed, wherein the node control is a visualized node control; according to the configuration information of at least one node control, executing a first task of operation and maintenance management on a target server by executing a first scenario according to the connection sequence of the at least one node control; if the first scenario includes at least one sub scenario, executing a first task of operation and maintenance management on the target server by executing the first scenario includes: according to configuration information of at least one child node control in the child scenario to be executed, executing corresponding steps in the first task by executing the child scenario according to the connection sequence of the at least one child node control, wherein the child node control is a visualized node control.

Description

Operation and maintenance management method and device

Technical Field

The application relates to the technical field of server operation and maintenance, in particular to an operation and maintenance management method and device.

Background

With the continuous development of information technology, the business accepted by enterprises is gradually complex, and the demands of users on the business are gradually diversified, so that the servers required by the enterprises are also more and more. In order to ensure the quality of the provided service, the enterprise needs to perform operation and maintenance management on each server. The operation and maintenance management comprises the work of multiple aspects such as resource monitoring, business inspection, software deployment, service monitoring, software upgrading and the like.

When running and maintaining management is performed on a large number of servers at present, running and maintaining personnel are required to manually upload scripts for running and maintaining management on each server and drive the scripts to execute corresponding work. This approach wastes a lot of manpower, making the operation and maintenance management less efficient and costly.

Disclosure of Invention

The application provides an operation and maintenance management method and device, which can improve the efficiency of operation and maintenance management and realize the batch delivery function in operation and maintenance management tasks.

In a first aspect, the present application provides an operation and maintenance management method, including:

acquiring configuration information of at least one node control in a first scenario to be executed, wherein the node control is a visualized node control;

according to the configuration information of at least one node control, executing a first task of operation and maintenance management on a target server by executing a first scenario according to the connection sequence of the at least one node control;

if the first scenario includes at least one sub scenario, executing a first task of operation and maintenance management on the target server by executing the first scenario includes:

according to configuration information of at least one child node control in the child scenario to be executed, executing corresponding steps in the first task by executing the child scenario according to the connection sequence of the at least one child node control, wherein the child node control is a visualized node control.

In one example, the configuration information includes a type of node control and/or configuration parameters, the type of node control including one or more of the following types:

a start node control, an end node control, an approval task node control, a manual task node control, a script task node control, an exclusive branch node control, a parallel branch node control and a subtotal node control.

In one example, before executing the first task of the operation and maintenance management on the target server according to the connection sequence of the at least one node control according to the configuration information of the at least one node control visualized in the first scenario to be executed, the method further includes:

in response to an instruction for editing a script, displaying a first operation interface for editing the script, wherein the first operation interface comprises a plurality of visualized node controls, and the plurality of node controls comprise at least one node control;

determining at least one node control in response to a first selection instruction of the at least one node control;

configuring at least one node control in response to a first configuration instruction for the at least one node control;

and determining the first scenario according to the at least one node control.

In one example, the at least one node control includes a first node control, and if the type of the first node control is a child script node, configuring the at least one node control includes configuring the first node control, the configuring the first node control includes:

responding to a first display instruction for configuring the first node control, displaying a second operation interface, wherein the second operation interface is a lower-level interface of the first operation interface and comprises a plurality of visualized child node controls;

responding to a second selection instruction of at least one child node control in a plurality of child node controls displayed in a second operation interface, and determining the at least one child node control;

configuring a first node control by configuring at least one child node control, wherein determining a first scenario according to the at least one node control comprises:

and determining the child scenario to be executed according to the first node control.

In one example, the at least one node control includes a second node control that performs a first task of operation and maintenance management on the target server by executing the first scenario, including:

if the type of the second node control is a manual task node control, determining a first account according to configuration information of the second node control;

Sending indication information for executing the task of the second node control to a responsible person to which the first account belongs;

and determining whether to execute the next node control or stop executing the first scenario according to the instruction information fed back by the responsible person whether to complete the task of the second node control.

In one example, the at least one node control includes a second node control that performs a first task of operation and maintenance management on the target server by executing the first scenario, including:

if the type of the second node control is an approval task node control, determining a second account according to configuration information of the second node control;

sending the content to be approved to an approver to which the second account belongs;

and determining whether to execute the next node control or whether to stop executing the first scenario according to approval opinions fed back by the approver.

In one example, the at least one node control includes a second node control that performs a first task of operation and maintenance management on the target server by executing the first scenario, including:

if the type of the second node control is a parallel branch node control, determining that the execution sequence of a plurality of node controls associated with the second node control is parallel execution;

if the type of the second node control is an exclusive branch node control, determining that the execution sequence of the plurality of node controls associated with the second node control is executed sequentially;

Executing the plurality of node controls according to the execution sequence of the plurality of node controls.

In one example, after performing the first task of operation and maintenance management on the target server by executing the first scenario, the method further comprises:

determining an association relation according to the first script and the first task;

and when the script corresponding to the first task is arranged next time, acquiring the first script according to the association relation and the first task.

In one example, performing a first task of operation and maintenance management on a target server by executing a first scenario includes:

if the executing third node control fails to execute, acquiring first information causing the third node control to execute failure;

and changing the display state of the third node control and displaying the first information to the user.

In a second aspect, the present application provides an operation and maintenance management device, where the operation and maintenance management device includes a processor, and the processor is configured to obtain configuration information of at least one node control in a first scenario to be executed, where the node control is a visualized node control;

the processor is further used for executing a first task of operation and maintenance management on the target server by executing a first scenario according to the configuration information of the at least one node control and the connection sequence of the at least one node control;

If the first scenario includes at least one sub scenario, executing a first task of operation and maintenance management on the target server by executing the first scenario includes:

according to configuration information of at least one child node control in the child scenario to be executed, executing corresponding steps in the first task by executing the child scenario according to the connection sequence of the at least one child node control, wherein the child node control is a visualized node control.

In the embodiment of the application, according to configuration information of at least one node control in a first scenario to be executed, a first task of operation and maintenance management is executed on a target server by executing the first scenario according to a connection sequence of the at least one node control. When the configuration information of the node control comprises the script and a plurality of associated target servers, after the operation and maintenance personnel trigger the execution of the first scenario, the first task of operation and maintenance management can be executed on the plurality of target servers in batches, so that the operation and maintenance personnel are prevented from uploading the script on each server. And the visualized node control enables the first scenario to be arranged simply and easily, and improves the efficiency of scenario arrangement.

Further, the sub scenario node control is used for executing corresponding steps in the tasks corresponding to the affiliated scenario by executing the sub scenario. When the steps of the operation and maintenance management task are numerous, by setting a plurality of sub-script node controls, each sub-script node control executes one step of the task, and if one step is executed, the step with the problem can be accurately positioned, so that the problem can be effectively solved in time. In addition, the setting of the sub-script node controls can enable the script to meet certain special scene requirements, for example, when a certain component is deployed, a plurality of installation steps are needed, the deployment of the component can be realized by setting a plurality of sub-script node controls to execute in sequence, and each sub-script node control executes one installation step.

Drawings

In order to more clearly illustrate the technical solutions of the present application, the drawings that are needed in the embodiments will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.

FIG. 1 is a schematic diagram of an operation and maintenance management system according to an exemplary embodiment of the present application;

FIG. 2 is a schematic diagram of a first operation interface for editing a scenario according to an exemplary embodiment of the present application;

FIG. 3 is a schematic diagram of a first operator interface for composing a script according to another exemplary embodiment of the present application;

FIG. 4 is a schematic diagram of an application scenario of an exclusive branch node control according to an exemplary embodiment of the present application;

FIG. 5 is a schematic diagram of an application scenario of an example parallel branch node control provided in an exemplary embodiment of the present application;

FIG. 6 is a schematic diagram of an operation and maintenance flow provided in an exemplary embodiment of the present application;

FIG. 7 is a schematic flow chart diagram of an operation and maintenance management method according to an exemplary embodiment of the present application;

FIG. 8 is a schematic diagram of another operation and maintenance flow provided in an exemplary embodiment of the present application;

FIG. 9 is a schematic diagram of an operation and maintenance management device according to an exemplary embodiment of the present application;

FIG. 10 is a schematic diagram of a display interface of a display of an operation and maintenance management device according to an exemplary embodiment of the present application;

FIG. 11 is a schematic diagram of another operation and maintenance flow provided in an exemplary embodiment of the present application.

Detailed Description

Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for the purpose of illustrating the present application and are not to be construed as limiting the present application. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.

As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless expressly stated otherwise, as understood by those skilled in the art. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. The term "and/or" as used herein includes all or any element and all combination of one or more of the associated listed items.

In order to improve the efficiency of operation and maintenance management, as shown in fig. 1, an example of an operation and maintenance management system architecture is provided, where the system architecture includes a service layer 101, a service layer 102, an interface layer 103, a script layer 104, a data layer 105, and a resource layer 106.

The business layer 101 is configured to provide operation and maintenance management tasks to users, including a batch delivery task, etc., where the batch delivery task is capable of deploying new services or new functions of services in batches into a server, the tasks include, but are not limited to, batch software upgrades, batch program deployments, patch batch delivery upgrades, and batch installation components (the components may be database components, microservices components, big data components, etc.).

In one example, the business layer presents a first operation interface to the user, who can complete the batch delivery task by composing a script on the first operation interface and then triggering execution of the script. The first operation interface comprises a plurality of visualized node controls, and a user can generate a script by dragging the node controls to be executed to an editable area of the first operation interface and configuring each node control to be executed.

The service layer 102 is configured to provide services to the service layer for scheduling, so as to support implementation of tasks in the service layer. The service layer comprises script engine scheduling service, stable scheduling service, flow engine scheduling service and the like. The active scheduling service can provide functions such as batch system configuration, batch program deployment, batch operation commands and the like, and meanwhile, various common basic modules are provided for simplifying the writing of operation and maintenance scripts. The Anstable scheduling service is also used for scheduling Anstable scripts, and the script engine scheduling service is used for scheduling scripts other than the Anstable scripts. The flow engine scheduling service is used for triggering each node control to execute according to the arranged sequence.

Based on the service layer described above, a first operation interface for orchestrating a scenario for performing a batch delivery task is introduced, the first operation interface being implemented based on a Security Orchestration Automation and Response (SOAR) technique, as shown in fig. 2, the type of node control displayed by the first operation interface comprising one or more of the following types:

a start node control, an end node control, an approval task node control, a manual task node control, a script task node control, an exclusive branch node control, a parallel branch node control and a subtotal node control.

The following describes various types of node controls:

(1) The start node control is used for starting the script operation to trigger the execution of the subsequent node control in the script.

(2) The ending node control is used for stopping the script operation and can timely release resources occupied by the script operation.

(3) The approval task node control is used for issuing the task to be approved to an approver, and after the approval by the approver is finished and is confirmed on line, the operation of the follow-up node control is carried out, so that the on-line approval process of the approval task is realized. Compared with the mode that an approval task is interfered by an operation and approval person and an approval person off line, the approval person replies confirmation to the operation and approval person after approval is completed, and the operation of the approval task flow is quickened by setting the approval task node control.

(4) The manual task node control is used for sending tasks to be completed and time limit for completing the tasks to the responsible person, and then running the follow-up node control after the responsible person confirms the completion of the tasks, so that the time for the responsible person and the responsible person corresponding to the on-line management task to complete the tasks is realized.

(5) The script task node control is used for executing tasks corresponding to the script by calling the script. Wherein each script is used to implement a function.

Illustratively, as shown in FIG. 3, the script task node control includes, but is not limited to, the following modules: the system comprises a script classification module, a script name module, an associated resource module, a node control Identification (ID) module, a node control name module, a timeout time module, an engine Application (APP) ID module and an input parameter module.

The script classification module is used for providing the types of scripts for users to select by calling the script engine management module, and the script engine management module is used for storing and managing different types of scripts.

The types of scripts include, but are not limited to, a resource monitoring class, a data backup class, a business patrol class, a data extraction class, an operation and maintenance control class, and a notification class.

The script name module is used for displaying the script name under the script type selected by the user to the user by calling the script engine management module so as to allow the user to select a specific script, and calling corresponding script scheduling services in the service layer according to the script name, wherein the script scheduling services comprise but are not limited to script engine scheduling services and active scheduling services.

The associated resource module is used for displaying the network address of the server for script execution to the user for selection by the user. When a user selects multiple network addresses in an associated resource module, scripts can be executed for multiple target servers to achieve mass delivery.

The node control ID module is used for displaying the identification of the script task node control.

The node control name module is used for acquiring and displaying the node control name input by the user.

The overtime module is used for acquiring the time length input by the user, determining whether the execution of the node control belonging to the time length is finished, and if the execution is finished, determining that the node control belonging to the time length is not overtime; if the execution is not finished, determining that the execution of the node control fails, and displaying warning information indicating the execution failure of the node control to the user.

The engine APP ID module is used for determining which engine is used for executing the application according to the engine APP ID input by a user under the condition that the script called by the script task node control needs to call the engine application of distributed deployment. The engine is illustratively a server.

(6) The input parameter module is used for displaying parameter names required by script operation, so that a user inputs corresponding parameter values according to the parameter names, and sends the parameter values to corresponding script scheduling services in the service layer. Such that the script scheduling service invokes the script with the parameter values.

For example, for a script task node control for file delivery, as shown in fig. 3, names of parameters requiring user input are shown to include "source file path", "file server internet protocol (internet protocol, IP)" and "upload path", and an area for acquiring parameters input by the user is shown after each name. The "source file path" refers to a path storing a file to be issued, "the" file server IP "refers to a server storing a file to be issued, and the" upload path "refers to a path storing a file to be issued by a target server.

(7) The exclusive branch node control is used for indicating that the execution sequence of the associated plurality of node controls is executed in sequence, and whether the condition of executing the node control is met or not can also be determined before each node control is executed, and if yes, the node control is executed continuously. According to the method and the device, the condition that execution of a plurality of script task node controls needs to be strictly according to the execution conditions and the execution sequence is considered, the exclusive branch node controls are arranged, and the plurality of script task node controls can be orderly executed. As shown in fig. 4, the application scenario of the exclusive branch node control is that the first script task node control and the second script task node control associated with the exclusive branch node control cannot be executed in parallel. If the configuration file needs to be modified, executing a first script task node control to execute a configuration file modification task, and then executing a second script task node control to execute a media replacement task; and if the configuration file does not need to be modified, executing the second script task node control to execute the media replacement task.

(8) The parallel branch node control is used for indicating that the execution sequence of the plurality of associated node controls is parallel execution, so that the efficiency of scenario execution can be improved, and resources can be fully utilized. As shown in fig. 5, the application scenario of the parallel branch node control is that the execution sequence of the two sub scenario task node controls associated with the parallel branch node control is parallel execution.

(9) The child script node control is configured to present a second operation interface including a plurality of visualized child node controls to a user, so that the user can edit the child script by dragging the target child node control to the editable area and configuring the target child node control. The second operation interface is a lower interface of the first operation interface. The sub scenario node control is used for executing corresponding steps in the tasks corresponding to the affiliated scenario by executing the sub scenario. When the steps of the operation and maintenance management task are numerous, by setting a plurality of sub-script node controls, each sub-script node control executes one step of the task, and if one step is executed, the step with the problem can be accurately positioned, so that the problem can be effectively solved in time. In addition, the setting of the sub-script node controls can enable the script to meet certain special scene requirements, for example, when a certain component is deployed, a plurality of installation steps are needed, the deployment of the component can be realized by setting a plurality of sub-script node controls to execute in sequence, and each sub-script node control executes one installation step.

The types and functions of the child node controls of the second operation interface are referred to in the description of the node controls of the first operation interface, and are not described herein.

The first operation interface further includes a connection node control, where the connection node control is used to connect the two node controls, and control an execution sequence of the two node controls through a scheduling service of the flow engine.

Based on the first operation interface, the application provides a scenario determination method, which comprises the following steps:

in response to an instruction for editing a script, displaying a first operation interface for editing the script, wherein the first operation interface comprises a plurality of visualized node controls;

at least one node control is determined in response to a first selection instruction for at least one node control of the plurality of node controls.

Configuring at least one node control in response to a first configuration instruction for at least one node control in the plurality of node controls;

and determining the first scenario according to the at least one node control.

The first selection instruction comprises a selection node control and is dragged into an editable area of the first operation interface.

In one example, the at least one node control includes a first node control, and if the type of the first node control is a child script node, configuring the at least one node control includes configuring the first node control, the configuring the first node control includes:

Responding to a first display instruction for configuring the first node control, displaying a second operation interface, wherein the second operation interface is a lower-level interface of the first operation interface and comprises a plurality of visualized child node controls;

responding to a second selection instruction of at least one child node control in a plurality of child node controls displayed in a second operation interface, and determining the at least one child node control;

configuring a first node control by configuring at least one child node control, wherein determining a first scenario according to the at least one node control comprises:

and determining the child scenario to be executed according to the first node control.

The second selection instruction comprises selecting a child node control and dragging the child node control to an editable area of the second operation interface.

Through the visual script arrangement operation interface, the example enables a user (namely an operation and maintenance personnel) to timely carry out organization arrangement through dragging node controls according to different operation and maintenance management tasks, and finally all the node controls are connected and configured to finish arrangement of different scripts. The method is simple and easy to operate, and efficiency of editing the script by the user is improved.

The interface layer 103 is used to provide an interface to the dispatch services of the service layer. The interface layer 103 includes, but is not limited to, a flow engine interface, and the flow engine scheduling service implements executing each node control according to the arrangement order of the node controls by calling the flow engine interface.

The script layer 104 is configured to provide scripts that can be scheduled by the script scheduling service to the service layer.

Illustratively, the script layer 104 stores and manages different types of scripts via a script engine management module.

Based on the script engine management module and the script engine scheduling service, the application provides an operation and maintenance flow embodiment from uploading the script to calling the script to returning the operation and maintenance result. As shown in fig. 6, first, the operator uploads the script to the script engine management module, and needs to configure the script, where the configuration content includes one or more of the following:

(1) The input parameters comprise parameter names required by script operation, attributes, indexes and the like of resources required by script operation. The parameter names required by script operation comprise a source file path, a file server IP, an uploading path and the like, and an input parameter module in a script task node is used for displaying the parameter names required by script operation.

Attributes of resources required for script operation include account numbers, passwords, ports, and the like. After a user selects a network address of a target server in an associated resource module in the script task node control, the script task node control automatically acquires the related attribute of the target server according to the attribute of the resource required by script operation and sends the related attribute to a script engine scheduling service as an input parameter.

The metrics include memory usage, cpu usage, disk usage, the number of transmission control protocol (transmission control protocol, TCP) surviving connections, etc.

(2) Output parameters, i.e. contents that the script execution needs to output, such as execution state of the script, execution result, failure cause, etc.

Then, after the operator configures the script at the script task node control, the script task node control executes the script by scheduling a service through the script engine.

And finally, displaying the operation and maintenance result to the operation and maintenance personnel through the end node control.

The data layer 105 is configured to provide data of the target server, such as resource data of the target server, configuration data of the target server, index data of the target server, and the like, to the interface layer and the service layer. Wherein the resource data includes a network address and the like, and the configuration data includes operation resource data, storage resource data and the like. The index data includes the highest memory usage of the target server, the highest CPU usage, the highest disk usage, the highest number of TCP surviving connections, etc.

Resource layer 106 provides support for various resources and related middleware for the overall system architecture. For example, the resource layer includes a target server.

In the above embodiment, a unified management and scheduling platform is provided for operation and maintenance management tasks through a designed operation and maintenance management architecture. Therefore, operation and maintenance personnel can be supported to simply drag and configure each visualized node control according to operation and maintenance management tasks, and script arrangement is realized. And furthermore, scripts are set through script task node controls and at least one target server is associated, batch delivery is realized, the operation and maintenance management efficiency is improved, and the operation and maintenance personnel are prevented from manually uploading the scripts for operation and maintenance management on each server.

Based on the above operation and maintenance management system architecture, the present application provides an operation and maintenance management method, which is applied to a scenario editing device that provides a first operation interface for a user, as shown in fig. 7, and the method includes:

s210, acquiring configuration information of at least one node control in a first scenario to be executed, wherein the node control is a visualized node control.

Illustratively, the configuration information includes a type of node control and configuration parameters.

Illustratively, the configuration parameters of the start node control include node ID, node name, preset time to start execution, etc.

Illustratively, the configuration parameters of the end node control include a node ID, a node name, an operation and maintenance result display form, and the like, wherein the operation and maintenance result display form includes a text form, a chart form, a list form, and the like.

Illustratively, the configuration parameters of the approval task node control include node name, approval person account number, content to be approved, approval time limit, and the like.

Illustratively, the configuration parameters of the manual task node control include node name, responsible person account number, content of the task, task execution time limit, and the like.

Illustratively, the configuration parameters of the script task node control include node name, script classification, script name, associated resources, input parameters, timeout time, and the like.

Illustratively, the configuration parameters of the exclusive branch node control include a node name or the like.

Illustratively, the configuration parameters of the parallel branch node control include node name, etc.

The configuration parameters of the child scenario branch node controls include the configuration parameters of each child node control, and the configuration parameters of each type of child node control refer to the configuration parameters of each type of node control in the scenario, which are not described herein.

S220, executing a first task of operation and maintenance management on the target server by executing the first scenario according to the configuration information of the at least one node control and the connection sequence of the at least one node control.

S230, if the first scenario includes at least one sub scenario, executing a first task of operation and maintenance management on the target server by executing the first scenario includes:

According to configuration information of at least one child node control in the child scenario to be executed, executing corresponding steps in the first task by executing the child scenario according to the connection sequence of the at least one child node control, wherein the child node control is a visualized node control.

In the above example, according to the configuration information of at least one node control in the first scenario to be executed, the first task of operation and maintenance management is executed on the target server by executing the first scenario according to the connection sequence of the at least one node control. When the configuration information of the node control comprises the script and a plurality of associated target servers, after the operation and maintenance personnel trigger the execution of the first scenario, the first task of operation and maintenance management can be executed on the plurality of target servers in batches, so that the operation and maintenance personnel are prevented from uploading the script on each server. And the visualized node control enables the first scenario to be arranged simply and easily, and improves the efficiency of scenario arrangement.

Further, the sub scenario node control is used for executing corresponding steps in the tasks corresponding to the affiliated scenario by executing the sub scenario. When the steps of the operation and maintenance management task are numerous, by setting a plurality of sub-script node controls, each sub-script node control executes one step of the task, and if one step is executed, the step with the problem can be accurately positioned, so that the problem can be effectively solved in time. In addition, the setting of the sub-script node controls can enable the script to meet certain special scene requirements, for example, when a certain component is deployed, a plurality of installation steps are needed, the deployment of the component can be realized by setting a plurality of sub-script node controls to execute in sequence, and each sub-script node control executes one installation step.

In one example, before presenting the first operation interface for composing the scenario in response to the instruction to compose the scenario, the operation and maintenance management method further includes:

acquiring the type of the operation and maintenance management task;

and determining the type of the script according to the type of the operation and maintenance management task, so that the subsequent operation and maintenance management personnel can upload the script according to the type of the script, and the management of the script is facilitated.

For example, the types of batch delivery tasks include batch software upgrades, batch program deployments, patch batch delivery upgrades, and batch installation components. The type of script for the batch delivery task is determined according to the type of the batch delivery task and comprises batch software upgrading, batch program deployment, patch batch delivery upgrading and batch installation components.

The following describes the execution of different types of node controls.

In one example, the at least one node control includes a second node control that performs a first task of operation and maintenance management on the target server by executing the first scenario, including:

if the type of the second node control is a manual task node control, determining a first account according to configuration information of the second node control;

sending indication information for executing the task of the second node control to a responsible person to which the first account belongs;

And determining whether to execute the next node control or stop executing the first scenario according to the instruction information fed back by the responsible person whether to complete the task of the second node control.

For example, if the indication information indicates that the responsible person does not complete the task and the node control to be executed is set after the second node control, it is determined that the next node control is not executed. And sending the instruction information of executing the task of the second node control to the responsible person to which the first account belongs again, and then determining whether to execute the next node control or stop executing the first scenario again according to the instruction information fed back by the responsible person whether to complete the task of the second node control.

For example, if the indication information indicates that the responsible person does not complete the task and no node control to be executed is set after the second node control, it is determined that execution of the first scenario is not stopped. And sending the instruction information of executing the task of the second node control to the responsible person to which the first account belongs again, and then determining whether to execute the next node control or stop executing the first scenario again according to the instruction information fed back by the responsible person whether to complete the task of the second node control.

For example, if the indication information indicates that the responsible person completes the task and the node control to be executed is set after the second node control, it is determined to execute the next node control.

For example, if the indication information indicates that the responsible person completes the task and no node control to be executed is set after the second node control, it is determined to stop executing the first scenario.

In the above example, by sending the task to be completed and the time limit for completing the task to the responsible person, the responsible person confirms the completion of the task and then runs the subsequent node control, so that the time for the responsible person corresponding to the on-line management task and the responsible person to complete the task is realized.

In one example, the at least one node control includes a second node control that performs a first task of operation and maintenance management on the target server by executing the first scenario, including:

if the type of the second node control is an approval task node control, determining a second account according to configuration information of the second node control;

Sending the content to be approved to an approver to which the second account belongs;

and determining whether to execute the next node control or whether to stop executing the first scenario according to approval opinions fed back by the approver.

The approval opinion fed back by the approver is, for example, approval or disapproval of the execution.

For example, if the approval opinion fed back by the approver is to be executed in agreement, the node control to be executed is set after the second node control, and the next node control is determined to be executed.

For example, if the approval opinion fed back by the approver is not to be executed, and the node control to be executed is set after the second node control, it is determined that the next node control is not executed.

The above example realizes the on-line auditing flow of the approval task by issuing the task to be approved to the approver, and after the approval by the approver is completed and confirmed on line, running the subsequent node control. Compared with the mode that an approval task is interfered by an operation and approval person and an approval person off line, the approval person replies confirmation to the operation and approval person after approval is completed, and the operation of the approval task flow is quickened by setting the approval task node control.

In one example, the at least one node control includes a second node control that performs a first task of operation and maintenance management on the target server by executing the first scenario, including:

If the type of the second node control is a parallel branch node control, determining that the execution sequence of a plurality of node controls associated with the second node control is parallel execution;

if the type of the second node control is an exclusive branch node control, determining that the execution sequence of the plurality of node controls associated with the second node control is executed sequentially;

and executing the plurality of node controls according to the execution sequence of the plurality of node controls.

In the above example, by determining whether the type of the second node control is a parallel branch node control or an exclusive branch node control, the execution sequence of the plurality of node controls associated with the second node control is determined, so that the requirement of sequentially executing the plurality of node controls or executing the plurality of node controls in parallel is satisfied, and the corresponding operation and maintenance management task requirement can be adapted.

In one example, after performing the first task of operation and maintenance management on the target server by executing the first scenario, the method further comprises:

determining an association relation according to the first script and the first task;

and when the script corresponding to the first task is arranged next time, acquiring the first script according to the association relation and the first task.

For example, as shown in fig. 8, in order to improve the operation and maintenance management efficiency, the application uses the created script or sub-script as a template to associate and manage with the corresponding task, so as to form a reusable policy library. The sharing of multiple parties may then be performed by importing templates into the policy repository or exporting the policy repository.

In addition, templates in the policy repository may also be pre-stored scripts with unassociated resources and unconfigured input parameters and output parameters, such templates defining the steps and types of scripts required to complete the corresponding tasks, and specific input parameters and output parameters may be configured later as needed.

In the above example, by creating the association relationship between the first scenario and the first task, in the process of arranging the subsequent scenario, the corresponding scenario or sub scenario can be extracted from the policy library according to the task requirement of operation and maintenance management, and the operation and maintenance management task can be carried out as early as possible or after modification as required, thereby improving the operation and maintenance management efficiency.

In order to monitor the execution state (the execution state includes execution success or failure) of the node control in the scenario, an implementation manner of executing the first task of the operation and maintenance management on the target server by executing the first scenario includes:

if the executing third node control fails to execute, acquiring first information causing the third node control to execute failure;

and changing the display state of the third node control, and displaying the first information to a user.

Wherein changing the display state of the third node control comprises:

The display color of the third node control is changed from the first color to the second color, or the shape of the third node control is changed from the first shape to the second shape.

Illustratively, the implementation of the first task of performing the operation and maintenance management on the target server by executing the first scenario further includes:

and displaying a first selection control, wherein the first selection control is used for enabling a user to select to pause the execution of the first scenario or terminate the execution of the first scenario.

Illustratively, if the executing third node control is executed successfully and the next node control is set after the third node control, executing the next node control.

For example, if the executing third node control is executed successfully and the next node control is not set after the third node control, the executing of the first scenario is stopped.

In the above example, by monitoring the execution state of the node control in the scenario, if the node control fails to execute, the first information causing the third node control to execute failure can be timely obtained, the display state of the third node control is changed, so that an operator can conveniently and timely locate the node control which fails to execute, and the node control is correspondingly processed according to the first information.

Based on the above operation and maintenance management method, the present application provides an operation and maintenance management device, as shown in fig. 9, where the device includes a processor, where the processor is configured to obtain configuration information of at least one node control in a first scenario to be executed;

the processor is further configured to execute a first task of operation and maintenance management on the target server by executing the first scenario according to the configuration information of the at least one node control and the connection sequence of the at least one node control;

if the first scenario includes at least one sub scenario, the executing the first task of the operation and maintenance management on the target server by executing the first scenario includes:

according to configuration information of at least one child node control in the child scenario to be executed, executing corresponding steps in the first task by executing the child scenario according to the connection sequence of the at least one child node control, wherein the child node control is a visualized node control.

In one example, the configuration information includes a type of node control and configuration parameters, the type of node control including one or more of the following types:

a start node control, an end node control, an approval task node control, a manual task node control, a script task node control, an exclusive branch node control, a parallel branch node control and a subtotal node control.

In one example, the operation and maintenance management device further comprises a display;

the processor responds to an instruction for editing the script, controls the display to display a first operation interface for editing the script, wherein the first operation interface comprises a plurality of visualized node controls, and the plurality of node controls comprise at least one node control;

the processor is used for responding to a first selection instruction of the at least one node control, and determining the at least one node control;

the processor is used for responding to a first configuration instruction of the at least one node control and configuring the at least one node control;

the processor determines a first scenario from the at least one node control.

For example, as shown in fig. 10, the first operation interface displayed by the display is an interface for implementing a delivery management function under a batch delivery task, and the display may also respectively display interfaces for implementing a classification management function, a file uploading function, a template management function, a process monitoring function, and a manual task function under a batch delivery task.

The processor realizes the classification management function by the following method: before displaying a first operation interface for editing a scenario in response to an instruction to edit the scenario:

acquiring the type of the operation and maintenance management task;

And determining the type of the script according to the type of the operation and maintenance management task, so that the subsequent operation and maintenance management personnel can upload the script according to the type of the script, and the management of the script is facilitated.

The processor realizes the file uploading function by providing the user with a service for uploading the script according to the type of the script.

The processor realizes the template management function by the following method:

determining an association relation according to the first script and the first task; and when the script corresponding to the first task is arranged next time, acquiring the first script according to the association relation and the first task.

The processor realizes the process monitoring function by the following method:

if the executing third node control fails to execute, acquiring first information causing the third node control to execute failure;

changing the display state of the third node control, and controlling the display to display the first information to the user.

The processor displays task information sent by the manual task node control to the account of the user through the manual task function interface, and if the user finishes the task, the processor feeds back indication information of the completion of the task to the manual task node control.

Based on the above functions of implementing the batch delivery task, the present application provides an example of a flow embodiment for executing the batch delivery task, as shown in fig. 11:

(1) The processor responds to the configuration instruction of the script type divided by the user according to the type of the batch delivery task through the interface of the classification management function.

(2) The processor receives a script of a certain type uploaded by a user through an interface of a file uploading function.

(3) And the processor responds to instructions that the user composes the script and then executes the script through an interface of the delivery management function, and executes node controls such as a manual task node control, an approval task node control and the like.

(4) The processor responds to the instruction of the user to generate the template for the created script or sub-script through the interface of the template management function, stores the script or sub-script as the template, and provides the function of managing the templates.

(5) The processor monitors the execution state of each node control in real time through the interface of the process monitoring function, and if the node control fails to execute, the processor displays corresponding prompt information to the user.

In one example, the at least one node control includes a first node control, and if the type of the first node control is a child script node, configuring the at least one node control includes configuring the first node control, and the processor configures an implementation of the first node control includes:

the processor responds to a first display instruction for configuring the first node control, controls the display to display a second operation interface, wherein the second operation interface is a lower-level interface of the first operation interface, and comprises a plurality of visualized child node controls;

The processor responds to a second selection instruction of at least one child node control in the plurality of child node controls displayed in the second operation interface, and determines the at least one child node control;

the processor configures a first node control by configuring at least one child node control, wherein determining a first scenario according to the at least one node control comprises:

and determining the child scenario to be executed according to the first node control.

In one example, the at least one node control comprises a second node control, and the implementation of the processor to perform the first task of operation and maintenance management on the target server by executing the first scenario comprises:

if the type of the second node control is a manual task node control, determining a first account according to configuration information of the second node control;

sending indication information for executing the task of the second node control to a responsible person to which the first account belongs;

and determining whether to execute the next node control or stop executing the first scenario according to the instruction information fed back by the responsible person whether to complete the task of the second node control.

In one example, the at least one node control comprises a second node control, and the implementation of the processor to perform the first task of operation and maintenance management on the target server by executing the first scenario comprises:

If the type of the second node control is an approval task node control, determining a second account according to configuration information of the second node control;

sending the content to be approved to an approver to which the second account belongs;

and determining whether to execute the next node control or whether to stop executing the first scenario according to approval opinions fed back by the approver.

In one example, the at least one node control comprises a second node control, and the implementation of the processor to perform the first task of operation and maintenance management on the target server by executing the first scenario comprises:

if the type of the second node control is a parallel branch node control, determining that the execution sequence of a plurality of node controls associated with the second node control is parallel execution;

if the type of the second node control is an exclusive branch node control, determining that the execution sequence of the plurality of node controls associated with the second node control is executed sequentially;

executing the plurality of node controls according to the execution sequence of the plurality of node controls.

Other implementation manners and effects of the device refer to descriptions in the operation and maintenance management method, and are not described herein.

The basic principles of the present application have been described above in connection with specific embodiments, however, it should be noted that the advantages, benefits, effects, etc. mentioned in the present application are merely examples and not limiting, and these advantages, benefits, effects, etc. are not to be considered as necessarily possessed by the various embodiments of the present application. Furthermore, the specific details disclosed herein are for purposes of illustration and understanding only, and are not intended to be limiting, as the application is not intended to be limited to the details disclosed herein as such.

It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the flowcharts of the figures may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily being sequential, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.

The block diagrams of the devices, apparatuses, devices, systems referred to in this application are only illustrative examples and are not intended to require or imply that the connections, arrangements, configurations must be made in the manner shown in the block diagrams. As will be appreciated by one of skill in the art, the devices, apparatuses, devices, systems may be connected, arranged, configured in any manner. Words such as "including," "comprising," "having," and the like are words of openness and mean "including but not limited to," and are used interchangeably therewith. The terms "or" and "as used herein refer to and are used interchangeably with the term" and/or "unless the context clearly indicates otherwise. The term "such as" as used herein refers to, and is used interchangeably with, the phrase "such as, but not limited to.

It is also noted that in the apparatus, devices and methods of the present application, the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent to the present application.

The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the application. Thus, the present application is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The foregoing description has been presented for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of the application to the form disclosed herein. Although a number of example aspects and embodiments have been discussed above, a person of ordinary skill in the art will recognize certain variations, modifications, alterations, additions, and subcombinations thereof.

Claims (10)

1. An operation and maintenance management method, comprising:

acquiring configuration information of at least one node control in a first scenario to be executed, wherein the node control is a visualized node control;

According to the configuration information of the at least one node control, executing a first task of operation and maintenance management on a target server by executing the first scenario according to the connection sequence of the at least one node control;

if the first scenario includes at least one sub scenario, the executing the first task of the operation and maintenance management on the target server by executing the first scenario includes:

and executing corresponding steps in the first task by executing the child scenario according to configuration information of at least one child node control in the child scenario to be executed and the connection sequence of the at least one child node control, wherein the child node control is a visualized node control.

2. The method of claim 1, wherein the configuration information includes a type of node control and/or configuration parameters, the type of node control including one or more of the following types:

a start node control, an end node control, an approval task node control, a manual task node control, a script task node control, an exclusive branch node control, a parallel branch node control and a subtotal node control.

3. The method of claim 2, wherein prior to performing a first task of operation and maintenance management on a target server by executing the first scenario in a connection order of the at least one node control according to configuration information of the at least one node control, the method further comprises:

In response to an instruction for editing a script, displaying a first operation interface for editing the script, wherein the first operation interface comprises a plurality of visualized node controls, and the plurality of node controls comprise the at least one node control;

determining the at least one node control in response to a first selection instruction of the at least one node control;

configuring the at least one node control in response to a first configuration instruction for the at least one node control;

and determining the first scenario according to the at least one node control.

4. The method of claim 3, wherein the at least one node control comprises a first node control, and wherein if the type of the first node control is a child script node, the configuring the at least one node control comprises configuring the first node control, the configuring the first node control comprises:

responding to a first display instruction for configuring the first node control, displaying a second operation interface, wherein the second operation interface is a lower-level interface of the first operation interface, and comprises the visualized multiple child node controls;

determining at least one child node control in a plurality of child node controls displayed in the second operation interface in response to a second selection instruction of the at least one child node control;

Configuring the first node control by configuring the at least one child node control, wherein the determining the first scenario according to the at least one node control includes:

and determining the sub-scenario to be executed according to the first node control.

5. The method of any of claims 2-4, wherein the at least one node control comprises a second node control, the performing a first task of operation and maintenance management on a target server by executing the first scenario comprising:

if the type of the second node control is a manual task node control, determining a first account according to configuration information of the second node control;

sending indication information for executing the task of the second node control to a responsible person to which the first account belongs;

and determining whether to execute the next node control or stop executing the first scenario according to the instruction information fed back by the responsible person whether to complete the task of the second node control.

6. The method of any of claims 2-4, wherein the at least one node control comprises a second node control, the performing a first task of operation and maintenance management on a target server by executing the first scenario comprising:

If the type of the second node control is an approval task node control, determining a second account according to configuration information of the second node control;

transmitting the content to be approved to an approver to which the second account belongs;

and determining whether to execute the next node control or stop executing the first scenario according to the approval opinion fed back by the approver.

7. The method of any of claims 2-4, wherein the at least one node control comprises a second node control, the performing a first task of operation and maintenance management on a target server by executing the first scenario comprising:

if the type of the second node control is a parallel branch node control, determining that the execution sequence of a plurality of node controls associated with the second node control is parallel execution;

if the type of the second node control is an exclusive branch node control, determining that the execution sequence of the plurality of node controls associated with the second node control is executed sequentially;

and executing the plurality of node controls according to the execution sequence of the plurality of node controls.

8. The method of claim 3 or 4, wherein after the performing of the first task of operation and maintenance management on the target server by executing the first scenario, the method further comprises:

Determining an association relation according to the first script and the first task;

and when the script corresponding to the first task is scheduled next time, acquiring the first script according to the association relation and the first task.

9. The method of any of claims 1-4, wherein the performing a first task of operation and maintenance management on a target server by executing the first scenario comprises:

if the executing third node control fails to execute, acquiring first information causing the third node control to execute failure;

and changing the display state of the third node control, and displaying the first information to a user.

10. The operation and maintenance management device is characterized by comprising a processor, wherein the processor is used for acquiring configuration information of at least one node control in a first scenario to be executed, and the node control is a visualized node control;

the processor is further configured to execute a first task of operation and maintenance management on the target server by executing the first scenario according to the configuration information of the at least one node control and according to the connection sequence of the at least one node control;

if the first scenario includes at least one sub scenario, the executing the first task of the operation and maintenance management on the target server by executing the first scenario includes:

And executing corresponding steps in the first task by executing the child scenario according to configuration information of at least one child node control in the child scenario to be executed and the connection sequence of the at least one child node control, wherein the child node control is a visualized node control.