Cluster operation and maintenance method, cluster operation and maintenance system and storage medium

Abstract

The invention provides a cluster operation and maintenance method, a cluster operation and maintenance system and a storage medium, and the method comprises the steps: determining a target node in a target cluster in response to a detected script arrangement request, obtaining the node information of the target node, determining alternative scripts in an operation and maintenance and script library according to the node information, and displaying all the alternative scripts through an operation and maintenance interface. Determining target scripts according to a selection operation executed by a user on the operation and maintenance interface, determining an execution sequence among the target scripts based on a sequence adjustment operation executed by the user to obtain script arrangement data corresponding to the target script combination, and running the target script combination according to the script arrangement data to perform operation and maintenance processing on the target node. Multi-script cluster node operation and maintenance are realized, a user does not need to manually execute each script in sequence, the node operation and maintenance cost is reduced, the operation and maintenance efficiency is improved, the operation and maintenance requirement of the user is predicted through the node information, the operation and maintenance difficulty can be further reduced, and the node operation and maintenance efficiency can be further improved.

Description

Technical Field

[0001] The present application relates to the field of cluster technology, and in particular to a cluster operation and maintenance method, a cluster operation and maintenance system, and a storage medium. Background Art

[0002] In today's information technology field, operation and maintenance automation has become a key means to improve system stability and efficiency. As the environment becomes increasingly complex, the use of automated operation and maintenance scripts is becoming more and more common. These scripts can automatically perform a series of operation and maintenance tasks, such as system updates, fault repair, performance monitoring, etc.

[0003] However, existing operation and maintenance automation systems face the following challenges and problems: the dependency management of automation scripts is complex, and operation and maintenance scripts are often not run in isolation; existing systems usually support the execution of a single script, but for complex processes involving multiple scripts, users need to execute them manually, which is not only cumbersome but also prone to errors. Summary of the invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, the present application aims to provide a cluster operation and maintenance method, a cluster operation and maintenance system and a storage medium to solve the problems in the prior art such as complex operation and maintenance script management and execution errors caused by manual execution of multiple scripts by users.

[0005] The present invention provides a cluster operation and maintenance method, which includes:

[0006] In response to detecting the scripting request, determining a target node in a target cluster, and acquiring node information of the target node;

[0007] Determine alternative scripts in the operation and maintenance script library based on the node information, and display all alternative scripts in the operation and maintenance interface;

[0008] Determine the target script according to the selection operation performed by the user in the operation and maintenance interface, and determine the execution order between the target scripts according to the sequence adjustment operation performed by the user in the operation and maintenance interface, and obtain script arrangement data corresponding to the target script combination;

[0009] The target script combination is run according to the script arrangement data to perform operation and maintenance processing on the target node through the running target script.

[0010] Optionally, after obtaining the script arrangement data corresponding to the target script combination, the method further includes:

[0011] Converting the script arrangement data into multi-branch tree structure data, and converting the multi-branch tree structure data into workflow structure data;

[0012] Generate a flowchart corresponding to the target script combination according to the workflow structure data, and display the flowchart in the operation and maintenance interface, wherein the flowchart is composed of at least one node, and the node represents the target script;

[0013] In response to detecting that a user performs a node linking operation on the flowchart, updating the flowchart based on the node linking operation to link multiple target scripts in the flowchart, wherein the link is used to specify other target scripts that need to be executed after a target script fails to execute or succeeds;

[0014] The scripting data is updated based on the updated flowchart.

[0015] Optionally, after displaying the flowchart in the operation and maintenance interface, the method further includes:

[0016] In response to detecting a user's node selection operation on the flowchart, determining all upstream branches of the currently selected node based on the flowchart;

[0017] For each of the upstream branches, determine all upstream nodes of the currently selected node according to the upstream branches, and write the currently selected node and all upstream nodes into an ancestor node list;

[0018] The nodes in the ancestor node list are deduplicated, and in the flow chart, the nodes in the ancestor node list are set to an unlinkable state.

[0019] Optionally, after running the target script combination according to the script arrangement data, the method further includes:

[0020] The execution status of each target script is displayed through the flowchart; and / or,

[0021] In response to detecting that the user performs a node viewing operation on the flowchart, script parameter information and script execution information corresponding to the currently viewed node are displayed on the operation and maintenance interface.

[0022] Optionally, determining an alternative script in an operation and maintenance script library based on the node information includes:

[0023] Selecting each operation and maintenance script that has an affiliation relationship with the target cluster from the operation and maintenance script library as a candidate script;

[0024] Among all the candidate scripts, a candidate script is determined based on at least one of the node type, historical statistical information, and node status in the node information.

[0025] Optionally, determining a candidate script from among all candidate scripts based on at least one of the node type, historical statistical information, and node status in the node information includes:

[0026] Among all candidate scripts, select candidate scripts that meet the node type;

[0027] Among the selected candidate scripts, select a candidate script according to the node load rate, node available memory and node running time in the node status, and select a candidate script according to the statistical sorting of abnormal types and the statistical sorting of operation and maintenance scripts in the historical statistical information;

[0028] The statistical ranking of the exception types is obtained by ranking according to the occurrence frequency of each historical exception type, and the statistical ranking of the operation and maintenance scripts is obtained by ranking according to the execution frequency of each historical operation and maintenance script.

[0029] Optionally, the method further includes:

[0030] In response to receiving a cluster node abnormality signal sent by the monitoring system, determining an abnormal node and an abnormality type based on the cluster node abnormality signal;

[0031] Acquire preset orchestration data corresponding to the preset script combination associated with the abnormal type, and execute the preset script combination according to the preset orchestration data to perform operation and maintenance processing on the abnormal node.

[0032] Optionally, after running the target script combination according to the script arrangement data, the method further includes:

[0033] Generate a job record corresponding to the target script combination based on the execution time, execution result and operation information of the target script combination;

[0034] The method further comprises:

[0035] In response to detecting a record query request, the corresponding job record is queried based on the execution time, execution result or operation information in the record query request, and the queried job record is displayed on the operation and maintenance interface.

[0036] The embodiment of the present application also provides a cluster operation and maintenance system, the system comprising an operation and maintenance script library, a process scheduling center and an operation and maintenance interface, wherein;

[0037] The operation and maintenance script library is used to store multiple operation and maintenance scripts;

[0038] The operation and maintenance interface is used to display information to users;

[0039] The dispatching center is used to execute the steps of the cluster operation and maintenance method provided in any embodiment of the present application.

[0040] The present application also provides an electronic device, the electronic device comprising:

[0041] Processor and memory;

[0042] The processor is used to execute the steps of the cluster operation and maintenance method provided in any embodiment of the present application by calling the program or instruction stored in the memory.

[0043] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a program or instruction, wherein the program or instruction enables a computer to execute the steps of the cluster operation and maintenance method provided by any embodiment of the present application.

[0044] In summary, the present application proposes a cluster operation and maintenance method, which responds to detecting a script orchestration request, determines the target node in the target cluster, obtains the node information of the target node, determines the alternative script in the operation and maintenance and script library according to the node information, and displays all the alternative scripts through the operation and maintenance interface, and then determines the target script according to the selection operation performed by the user in the operation and maintenance interface, and determines the execution order between the target scripts based on the sequence adjustment operation performed by the user, obtains the script orchestration data corresponding to the target script combination, runs the target script combination according to the script orchestration data, and performs operation and maintenance processing on the target node, thereby realizing multi-script cluster node operation and maintenance, without the need for users to manually execute each script in sequence, reducing the node operation and maintenance cost, and improving the operation and maintenance efficiency. Multi-script complex operation and maintenance operations are executed at one time, reducing operation time and human errors, having flexibility and scalability, supporting independent execution and combination adjustment of scripts, and being suitable for operation and maintenance requirements of clusters of different sizes and various complexities. In addition, the method predicts the user's operation and maintenance requirements through node information, and screens out alternative scripts for the user to choose, which can further reduce the operation and maintenance difficulty and improve the node operation and maintenance efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the specific implementation methods of the present application or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0046] Figure 1 It is a flow chart of a cluster operation and maintenance method provided in an embodiment of the present application;

[0047] Figure 2 It is a schematic diagram of generating a flow chart provided in an embodiment of the present application;

[0048] Figure 3It is a node schematic diagram provided in an embodiment of the present application;

[0049] Figure 4 It is a functional schematic diagram of an operation and maintenance interface provided in an embodiment of the present application;

[0050] Figure 5 It is a functional schematic diagram of a cluster operation and maintenance system provided in an embodiment of the present application;

[0051] Figure 6 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It is also necessary to explain that, for ease of description, only the parts related to the invention are shown in the accompanying drawings.

[0053] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0054] Before introducing the cluster operation and maintenance method provided in the embodiment of the present application in detail, the technical problems solved by the method are first described. In the prior art, the operation and maintenance automation system faces the following problems:

[0055] Complex dependency management of automated scripts: Operation and maintenance scripts are often not run in isolation, but need to be executed in a specific order, and there may be complex dependencies between them. For example, a script may need to rely on the output of other scripts as input. If the order or data flow of the scripts is not managed properly, it may cause system failure or operation and maintenance task failure.

[0056] Script maintenance is difficult: As operation and maintenance requirements change, scripts need to be frequently updated or maintained. Managing and maintaining a large number of scripts, especially in large systems, may lead to inconsistent script versions or configuration conflicts;

[0057] Insufficient automation of multi-script operations: Existing systems usually support the execution of a single script, but for complex processes involving multiple scripts, such as remedial operations after a script fails to execute, users need to perform them manually, which is not only cumbersome but also prone to errors;

[0058] Insufficient script execution status tracking: Existing automated operation and maintenance systems mostly use text logs to record the execution status of scripts. Although logs can provide detailed information, it is difficult for non-technical personnel to parse and understand text logs. Especially when faced with complex processes, tracking the execution status of each script may be very time-consuming and laborious;

[0059] The execution process display between scripts is not intuitive: the existing system lacks a visual display of the relationship between multiple script execution processes, which makes it difficult for operation and maintenance personnel to intuitively understand the relationship between scripts and data flow. Especially when dealing with multi-step operation and maintenance tasks, there is a lack of a unified view to display the execution status of the entire process, resulting in information asymmetry and inefficiency;

[0060] Poor operation experience: The user interface of existing systems is often complex and not intuitive. When operating and maintaining personnel execute scripts, manage tasks, and view results, they may need to go through multiple steps or switch interfaces, which not only increases the complexity of operations but may also lead to operational errors.

[0061] The need for operation and maintenance efficiency: Existing systems usually do not provide instant and interactive information display when processing script execution and result feedback. Operation and maintenance personnel need to wait for the system to complete all tasks before obtaining results. This method is inefficient when handling large-scale operation and maintenance tasks.

[0062] Therefore, in order to solve the above problems, the present application provides a cluster operation and maintenance method. Figure 1 is a flow chart of a cluster operation and maintenance method provided in an embodiment of the present application, which can be executed by a dispatching center. Figure 1 , the cluster operation and maintenance method specifically includes:

[0063] S110 . In response to detecting a scripting request, determining a target node in a target cluster, and acquiring node information of the target node.

[0064] In an embodiment of the present application, the cluster may specifically be an HPC (High Performance Computing) cluster, and the node may be a GPU (Graphics Processing Unit) host or a CPU (Central Processing Unit) host in the cluster.

[0065] The scripting request may be initiated by a user in the operation and maintenance interface. For example, the user may trigger the operation and maintenance control in the operation and maintenance interface, and then generate an operation and maintenance request for a target node in a target cluster by inputting a command line or selecting a cluster node, and display the scripting control according to the operation and maintenance request, and generate a scripting request in response to detecting that the user triggers the scripting control.

[0066] Specifically, the scripting request may carry a target cluster and a target node, wherein the target node may be a node that the user needs to maintain, and the target cluster may be a cluster to which the target node belongs. It should be noted that the number of target nodes may be one or more, and each target node may belong to the same target cluster or to different target clusters.

[0067] In an embodiment of the present application, in response to detecting a scripting request, a target node in a target cluster may be determined according to the scripting request, and node information of the target node may be obtained, wherein the node information may include node type, node status, and node statistics information.

[0068] Exemplarily, a signal may be sent to a monitoring system of a target cluster to obtain node information of a target node fed back by the monitoring system of the target cluster.

[0069] S120: Determine alternative scripts in the operation and maintenance script library based on the node information, and display all alternative scripts in the operation and maintenance interface.

[0070] Among them, the operation and maintenance script library can be composed of a large number of operation and maintenance scripts, and the operation and maintenance scripts can be used to perform operation and maintenance processing on the nodes after execution, such as shutting down the nodes, restarting the nodes, starting the nodes, checking the memory of the nodes, checking the usage rate of the nodes, etc.

[0071] Specifically, after obtaining the node information of the target node, the user's operation and maintenance needs can be predicted based on the node information, some operation and maintenance scripts can be selected from the operation and maintenance script library as alternative scripts, and all alternative scripts can be displayed in the operation and maintenance interface for user selection.

[0072] It should be noted that the purpose of determining alternative scripts in the operation and maintenance script library based on node information is: taking into account that there are many operation and maintenance functions, and for the same operation and maintenance function, different clusters or different types of nodes may need to build operation and maintenance scripts separately to ensure the normal execution of the script. Therefore, in order to quickly implement script orchestration, the user's operation and maintenance needs can also be predicted through node information, and some operation and maintenance scripts can be selected from the operation and maintenance script library and displayed to the user for selection, so as to improve the efficiency of script orchestration. At the same time, it can also avoid the situation where all operation and maintenance scripts are displayed to the user, resulting in the user's wrong selection, thereby improving the accuracy of script orchestration and avoiding node operation and maintenance errors.

[0073] In a specific implementation, determining a candidate script in an operation and maintenance script library based on node information includes the following steps:

[0074] Step 11: Select each operation and maintenance script that has an affiliation relationship with the target cluster from the operation and maintenance script library as a candidate script;

[0075] Step 12: Determine a candidate script from among all candidate scripts based on at least one of the node type, historical statistical information, and node status in the node information.

[0076] The operation and maintenance script library can store various operation and maintenance scripts and their ownership relationships in the cluster. Specifically, considering that the architectures of different clusters may be different, resulting in differences in the writing of operation and maintenance scripts, the ownership relationships of various operation and maintenance scripts can be clearly defined in the operation and maintenance script library, and the ownership relationships can refer to the clusters to which the operation and maintenance scripts are applicable.

[0077] In addition, the operation and maintenance script library can also provide parameter management, record the filling method, verification rules and other information of different types of parameters, and record the reserved variables in each operation and maintenance script. Before executing the operation and maintenance script, the reserved variables can be filled with corresponding values. For example, the function of the operation and maintenance script is to output a message on the node, then the message can be used as a reserved variable. By modifying the value of the reserved variable before execution, the content required by the user can be displayed in the node.

[0078] In step 11, each operation and maintenance script having an affiliation relationship with the target cluster, that is, the operation and maintenance script applicable to the target cluster, may be first screened out from the operation and maintenance script library as a candidate script.

[0079] Furthermore, in step 12, a candidate script can be determined from all the candidate scripts screened according to at least one of the node type, historical statistical information, and node status. The node type can be a computing node, a storage node, or a management node, etc., and different node types provide different services; the historical statistical information can be information obtained based on historical data statistics of the node, such as the number of abnormalities that occurred in the node and the statistical number of various abnormalities, the number of operations and maintenance that occurred in the node, and the statistical number of various operations and maintenance.

[0080] Exemplarily, the service provided by the target node can be determined according to the node type of the target node, and then the candidate script applicable to the service can be screened out from all the candidate scripts as the alternative script. Alternatively, the abnormality that may occur in the target node can be predicted according to the node state of the target node, and then the candidate script that can handle the abnormality can be screened out from all the candidate scripts as the alternative script. Alternatively, it can be determined that the target node performs more operations and maintenance or has more abnormalities according to the historical statistical information of the target node, and then the candidate script that performs the operations and maintenance or handles the abnormality can be screened out from the candidate scripts as the alternative script.

[0081] Through the above steps 11 and 12, some operation and maintenance scripts can be first screened out from the operation and maintenance script library according to the attribution relationship, and then the alternative scripts can be determined according to at least one of the node type, historical statistical information and node status. The user's operation and maintenance needs can be predicted based on the services provided by the target node, the abnormalities that have occurred in the history of the node, the operation and maintenance that has occurred in the history, and the abnormalities that may occur in the node in the future, thereby ensuring the comprehensiveness and accuracy of the prediction and being closer to the actual operation and maintenance needs of the operation and maintenance personnel.

[0082] With respect to the above step 12, in one example, determining a candidate script from among all candidate scripts based on at least one of the node type, historical statistical information, and node status in the node information includes the following steps:

[0083] Step 121: Filter out candidate scripts that meet the node type from among all candidate scripts;

[0084] Step 122: Select candidate scripts from among the selected candidate scripts based on the node load rate, node available memory, and node running time in the node status, and select candidate scripts based on the statistical sorting of abnormal types and the statistical sorting of operation and maintenance scripts in the historical statistical information.

[0085] Among them, the statistical sorting of exception types is obtained by sorting the occurrence frequency of each historical exception type, and the statistical sorting of operation and maintenance scripts is obtained by sorting the execution frequency of each historical operation and maintenance script.

[0086] Specifically, in step 121, candidate scripts that meet the services provided by the target node may be screened out according to the node type.

[0087] Furthermore, in step 122, from among the selected candidate scripts, the possible anomalies of the target node are predicted by the node load rate, node available memory and node running time, and then according to the predicted anomalies, the candidate script that can handle the anomalies is selected as the alternative script.

[0088] In step 122, in addition to selecting alternative scripts based on the predicted anomalies, the historical anomaly types with high occurrence frequencies can be determined based on the statistical sorting of the anomaly types in the historical statistical information, and then the candidate scripts that can handle the historical anomaly types with high occurrence frequencies can be selected from the screened candidate scripts as alternative scripts. At the same time, the historical operation and maintenance scripts with high execution frequencies can be determined based on the statistical sorting of the operation and maintenance scripts in the historical statistical information, and then the historical operation and maintenance scripts with high execution frequencies can be selected from the screened candidate scripts as alternative scripts.

[0089] Through the above steps 121-122, the operation and maintenance script that meets the node type can be selected first to avoid the problem of inapplicability of operation and maintenance scripts for different node types, and then the abnormality of the target node can be predicted by the node load rate, node available memory and node running time. The alternative script can be selected according to the abnormality. While improving the script editing efficiency, the script suitable for the node abnormality can be recommended to the user to ensure the normal operation of the target node. In addition, the operation and maintenance requirements at this time can be inferred through the historical statistical sorting of abnormality types and the statistical sorting of operation and maintenance scripts, which can make the script push more accurate and comprehensive, and further ensure the operation and maintenance reliability of the target node.

[0090] In addition, in an embodiment of the present application, for nodes newly added to the cluster, considering that their historical statistical information may be empty, in order to ensure accurate prediction of operation and maintenance needs, the above process can be implemented for old nodes, and other demand forecasting strategies can be formulated for new nodes.

[0091] For example, among all candidate scripts, an alternative script is determined based on at least one of the node type, historical statistical information and node status in the node information. It can also be: when the target node is a new node, based on the node type and node configuration information of the target node, other old nodes similar to the target node are matched in the target cluster as reference nodes, and the alternative script is determined based on the historical statistical information of the reference node and the node status of the target node.

[0092] S130, determining a target script according to a selection operation performed by a user in the operation and maintenance interface, and determining an execution order between target scripts according to a sequence adjustment operation performed by a user in the operation and maintenance interface, and obtaining script arrangement data corresponding to the target script combination.

[0093] Specifically, after displaying the candidate scripts through the operation and maintenance interface, the user can select a target script from all the candidate scripts, and the target script can be determined according to the selection operation performed by the user. The number of the target scripts can be one or more.

[0094] Furthermore, when the user selects multiple target scripts, the user can also perform a sequence adjustment operation in the operation and maintenance interface to adjust the execution order between the target scripts to construct a target script combination and obtain the script arrangement data corresponding to the target script combination.

[0095] In an embodiment of the present application, considering that when there are a large number of target scripts, directly changing the execution order of each target script on the operation and maintenance interface may not be intuitive enough for the user, and the execution logic of each target script cannot be clearly observed. Therefore, it is also possible to generate a flowchart corresponding to the target script combination after obtaining the script arrangement data corresponding to the target script combination, so as to describe the execution logic of the target script combination through the flowchart, so as to help the user understand or continue to adjust the execution order of each target script.

[0096] In a specific implementation, after obtaining the script arrangement data corresponding to the target script combination, the following steps are also included:

[0097] Step 21: convert the script arrangement data into multi-branch tree structure data, and convert the multi-branch tree structure data into workflow structure data;

[0098] Step 22: Generate a flowchart corresponding to the target script combination according to the workflow structure data, and display the flowchart in the operation and maintenance interface, wherein the flowchart is composed of at least one node, and the node represents the target script;

[0099] Step 23, in response to detecting that the user performs a node linking operation on the flowchart, updating the flowchart based on the node linking operation to link multiple target scripts in the flowchart, wherein the link is used to specify other target scripts that need to be executed after a target script fails to execute or succeeds;

[0100] Step 24: Update the script arrangement data based on the updated flowchart.

[0101] In step 21, the script arrangement data may be recorded as JSON (JavaScript Object Notation) array data, and then the script arrangement data may be converted into multi-branch tree structure data, wherein the multi-branch tree structure data may be tree structure data formed according to the execution order of the target script.

[0102] Furthermore, the multi-tree structure data can be converted into workflow structure data, specifically: first determine each node according to the multi-tree structure data, generate a node array (node ​​array), then generate an edge array (edge ​​array) according to the node array, and color each edge based on the edge array to obtain the workflow structure data.

[0103] For example, each edge set can be colored based on the branch conditions of the edge set array. For example, the edge that needs to be executed next after a node is successfully executed is rendered green, the edge that needs to be executed next after a node fails to execute is rendered red, and the edge that must be executed after a node is executed successfully or failed is rendered blue.

[0104] Furthermore, in step 22, component rendering can be performed according to the workflow structure data to generate a flowchart corresponding to the target script combination, and then the flowchart can be displayed through the operation and maintenance interface, wherein the flowchart can be a tree-structured graph in which each node represents each target script.

[0105] After displaying the flowchart, the user can perform node linking operations on the flowchart in the operation and maintenance interface, where the node linking operation can be to link one target script to another target script, indicating that another target script needs to be executed after one target script fails to execute or succeeds.

[0106] Specifically, in step 23-step 24, the flowchart can be updated according to the node linking operation performed by the user to link the target scripts in the flowchart, and then the updated flowchart can be converted into JSON array data to obtain new script arrangement data to achieve the update of the script arrangement data.

[0107] It should be noted that, in addition to the node link operation, the user can also perform node position adjustment operations, node deletion operations, node addition operations, node replacement operations, etc. in the operation and maintenance interface. Among them, the node position adjustment operation can be to change the execution order of the nodes by moving the node positions, the node deletion operation can be to delete the target script corresponding to the node, the node addition operation can be to add the target script corresponding to the node, and the node replacement operation can be to replace the target script corresponding to the node with another script.

[0108] For example, Figure 2 is a schematic diagram of generating a flow chart provided in an embodiment of the present application, such as Figure 2 As shown, first, the original data can be obtained. The original data can be understood as script arrangement data, and then data conversion is performed to obtain a standard multi-branch tree structure, and the multi-branch tree structure is hierarchically traversed, and the node coordinates are dynamically set. Then, data conversion is performed to obtain a workflow data structure. This step needs to be performed in sequence: generate a node array, generate an edge array, and color the edge.

[0109] Next, the components are rendered to obtain an interactive editing flowchart. The user can interactively edit the flowchart, including linking two nodes, dragging the position of the node to change the execution order of the corresponding target script, deleting the target script corresponding to the node, adding the target script corresponding to the node, or replacing the target script corresponding to the node with another script, etc. After the user completes the interactive editing, data conversion can be performed to convert the flowchart into the original data structure, and data submission can be performed to complete the update of the script arrangement data.

[0110] Through the above steps 21 to 24, the target script combination can be rendered as a flowchart and displayed to the user, so that the user can visually edit the script combination through the flowchart, providing the user with visual script editing interaction capabilities and supporting graphical editing. The user can build complex operation and maintenance processes by dragging and dropping, which can improve the efficiency of script editing and avoid errors in the construction of complex operation and maintenance processes.

[0111] Considering that in the process of users performing node linking operations, two unlinkable nodes may be mistakenly linked together, such as linking a node to its parent node. In order to avoid subsequent operation and maintenance failures caused by linking errors, the unlinkable nodes of each node can also be displayed to the user in the flowchart.

[0112] In one example, after displaying the flowchart in the operation and maintenance interface, the following steps are also included:

[0113] Step 221: in response to detecting a user's node selection operation on the flowchart, determining all upstream branches of the currently selected node based on the flowchart;

[0114] Step 222: for each upstream branch, determine all upstream nodes of the currently selected node according to the upstream branches, and write the currently selected node and all upstream nodes into the ancestor node list;

[0115] Step 223: deduplicate the nodes in the ancestor node list, and in the flowchart, set the nodes in the ancestor node list to an unlinkable state.

[0116] After the flowchart is displayed, if the user wants to link two nodes, he can first select one of the nodes, that is, perform a node selection operation. In step 221, if a node selection operation is detected, all upstream branches of the currently selected node can be determined from the flowchart, and the upstream branches can be branches that flow from the first node to the currently selected node.

[0117] For example, Figure 3 is a node schematic diagram provided in an embodiment of the present application, such as Figure 3As shown, the graph is a directed graph. Assuming that the currently selected node is node E, the upstream branches of node E include ABE and ACE.

[0118] Further, in step 222, for each upstream branch, all upstream nodes of the currently selected node can be extracted from the upstream branch, wherein the upstream node can be a node that the currently selected node depends on, such as the parent node of the currently selected node, the parent node of the parent node, etc. And, all upstream nodes and the currently selected node are written into an ancestor node list. The ancestor node list is used to maintain unlinkable nodes of the currently selected node.

[0119] like Figure 3 As shown, for the upstream branch ABE, the extracted upstream nodes include node A and node B, and for the upstream branch ACE, the extracted upstream nodes include node A and node C. Therefore, node A, node B and node E can be written into the ancestor node list, and node A, node C and node E can be written into the ancestor node list.

[0120] Furthermore, in step 223, the ancestor node list may be deduplicated to delete duplicate nodes therein. For example, using the above example, node A and node E are added to the ancestor node list twice, and the duplicate nodes A and E in the list may be deleted, and finally, the ancestor node list includes node A, node B, node C, and node E.

[0121] Specifically, according to the ancestor node list, the nodes in the ancestor node list in the flowchart can be set to an unlinkable state, so that the user cannot link the currently selected node with the unlinkable nodes, avoiding operation and maintenance logic errors. Using the above example, at this time, node E can be linked to node D or node F, for example, node D is executed after node E fails to execute, and node F is executed after node E succeeds.

[0122] Through the above steps 221 to 223, the unlinkable node corresponding to the user's currently selected node can be set to an unlinkable state to prevent the user from mistakenly linking a node to its parent node, the parent node of the parent node, or to itself, thereby avoiding operation and maintenance logic errors and ensuring the reliability of operation and maintenance in the process of building complex operation and maintenance processes.

[0123] S140. Run the target script combination according to the script arrangement data to perform operation and maintenance processing on the target node through the running target script.

[0124] Specifically, after obtaining the script arrangement data and before executing the target script combination, the user can also modify the value of the reserved variable in the target script in the operation and maintenance interface.

[0125] In the embodiment of the present application, the dispatch center can run the target script combination according to the script arrangement data to realize the operation and maintenance processing of each target node. For example, each target script can be executed in the order of the script arrangement data, and if there is a data dependency relationship between the target scripts, the next target script can also be executed according to the output data of the target script.

[0126] In the process of running the target script combination to perform operation and maintenance processing, the execution status of each target script can also be displayed through a flowchart, or the relevant information of each target script can be displayed to achieve visualization of the entire operation and maintenance process from orchestration to execution.

[0127] In one example, after running the target script combination according to the script arrangement data, the method further includes:

[0128] The execution status of each target script is displayed through a flowchart; and / or, in response to detecting that a user performs a node viewing operation on the flowchart, the script parameter information and script execution information corresponding to the currently viewed node are displayed on the operation and maintenance interface.

[0129] Specifically, the execution status of each target script may be displayed in the flowchart, and the execution status may be successful execution, failed execution, being executed, etc.

[0130] In addition, the user can also click on any node in the flowchart to view the relevant information of the node, that is, in response to detecting the node viewing operation, the script parameter information and script execution information corresponding to the currently viewed node can be displayed through the operation and maintenance interface. Among them, the script parameter information can be the detailed setting parameters of the script, and the script execution information can include the running log, output results, etc.

[0131] By displaying the execution status of each target script in the flowchart and displaying the corresponding script parameter information and script execution information according to the user's node viewing operation, users can intuitively understand the information in the execution process, thereby enhancing the transparency and manageability of the operation and maintenance process.

[0132] In the embodiment of the present application, in order to facilitate users to query operation and maintenance execution related information, relevant job records can also be called for display according to the user's query request. In a specific implementation, after running the target script combination according to the script arrangement data, it also includes: generating a job record corresponding to the target script combination based on the execution time, execution result and operation information of the target script combination;

[0133] The method provided in the embodiment of the present application also includes: in response to detecting a record query request, querying the corresponding job record based on the execution time, execution result or operation information in the record query request, and displaying the queried job record on the operation and maintenance interface.

[0134] The operation information may be information such as the operator. Specifically, after executing the target script combination, the target node can be restarted, shut down, started, displayed information, or a process can be shut down through the target script combination. In addition, the corresponding job records can be generated according to the execution time, execution result, and operation information, and the job records can be stored, supporting users to query the job records according to the execution time, execution result, operation information, and other dimensions.

[0135] Specifically, if it is detected that a user initiates a record query request, the corresponding job record can be queried based on the execution time, execution result or operation information in the record query request as an index, and the queried job record can be displayed through the operation and maintenance interface.

[0136] like Figure 4 As shown, Figure 4 It is a functional schematic diagram of an operation and maintenance interface provided in an embodiment of the present application, wherein the operation and maintenance interface can display each operation and maintenance script in the operation and maintenance script library, and the process template scheduling center (i.e., the scheduling center) can generate an audit record for display on the operation and maintenance interface after running the target script combination, and the workflow engine can also display the target script combination through the operation and maintenance interface after converting it into a flowchart.

[0137] Through the above implementation, it is possible to support query and export by multiple dimensions such as time, results, and executors, which is convenient for operation and maintenance personnel to check and improve the traceability of operation and maintenance work. In addition, it is also possible to support query according to operation and maintenance scripts.

[0138] In the embodiment of the present application, in addition to the user actively initiating script orchestration and executing node operation and maintenance, automatic node operation and maintenance can also be performed based on the node status detected by the monitoring system of the cluster.

[0139] In a specific implementation, the method provided in the embodiment of the present application further includes:

[0140] In response to receiving a cluster node abnormality signal sent by the monitoring system, the abnormal node and the abnormality type are determined based on the cluster node abnormality signal; the preset orchestration data corresponding to the preset script combination associated with the abnormal type is obtained, and the preset script combination is executed according to the preset orchestration data to perform operation and maintenance processing on the abnormal node.

[0141] Among them, the monitoring system can detect the status of nodes in each cluster. If an abnormal node is found, a cluster node abnormal signal can be sent to the dispatching center to notify the dispatching center to perform operation and maintenance on the abnormal node.

[0142] Specifically, if the dispatch center receives a cluster node abnormality signal sent by the monitoring system, it can first determine the abnormal node and the abnormality type corresponding to the abnormal node according to the cluster node abnormality signal, such as excessive equipment temperature, downtime, etc.

[0143] Furthermore, the dispatch center can query the preset script combination associated with the exception type and obtain the preset orchestration data corresponding to the preset script combination. The preset script combination can be a script combination pre-built by the operation and maintenance personnel for the exception type, or it can also be a script combination output by a model obtained by reinforcement learning based on the training set.

[0144] After obtaining the preset orchestration data, the dispatch center can run the preset script combination according to the preset orchestration data to implement operation and maintenance processing of abnormal nodes.

[0145] Through the above implementation, the exception can be associated with the script combination, and the associated script combination can be automatically executed when a node exception is detected without user orchestration. This can improve the node operation and maintenance efficiency during exceptions and ensure that abnormal nodes can be processed quickly to avoid affecting the service provided by the node.

[0146] In an embodiment of the present application, in addition to the user first specifying the target node and then predicting alternative scripts for the user, the user can also directly select the target script from the operation and maintenance script library, and then enter the node parameters before executing the target script to specify the target node, and then run the target script to operate and maintain the target node through the running target script.

[0147] The cluster operation and maintenance method provided in the embodiment of the present application, in response to detecting a script orchestration request, determines the target node in the target cluster, obtains the node information of the target node, determines the alternative script in the operation and maintenance and script library according to the node information, and displays all the alternative scripts through the operation and maintenance interface, and then determines the target script according to the selection operation performed by the user in the operation and maintenance interface, and determines the execution order between the target scripts based on the sequence adjustment operation performed by the user, obtains the script orchestration data corresponding to the target script combination, runs the target script combination according to the script orchestration data, so as to perform operation and maintenance processing on the target node, realizes multi-script cluster node operation and maintenance, does not require the user to manually execute each script in sequence, reduces the node operation and maintenance cost, improves the operation and maintenance efficiency, executes multi-script complex operation and maintenance operations at one time, reduces operation time and human errors, has flexibility and scalability, supports independent execution and combination adjustment of scripts, is suitable for operation and maintenance requirements of clusters of different sizes and various complexities, and the method predicts the user's operation and maintenance requirements through node information, and screens out alternative scripts for the user to choose, which can further reduce the difficulty of operation and maintenance and improve the node operation and maintenance efficiency.

[0148] The cluster operation and maintenance method provided in the embodiment of the present application has at least the following technical effects:

[0149] 1. Provide script and parameter library management methods, standardize script management, and standardize operation and maintenance operation execution process;

[0150] 2. Reduce the learning cost of operation and maintenance. The visual operation and maintenance process is intuitive and clear, and operation and maintenance personnel can quickly understand the operation and maintenance process;

[0151] 3. Improve operation and maintenance efficiency. Multiple scripts and complex operation and maintenance operations can be executed with one click. The execution status flowchart is provided to quickly locate the problem link and reduce operation time and human errors.

[0152] 4. It is flexible and scalable, supports independent execution of scripts and dynamic adjustment of script combinations, provides high flexibility and scalability, and adapts to the operation and maintenance needs of clusters of different sizes and various complexities.

[0153] An embodiment of the present application also provides a cluster operation and maintenance system, including an operation and maintenance script library, a process scheduling center and an operation and maintenance interface, wherein: the operation and maintenance script library is used to store multiple operation and maintenance scripts; the operation and maintenance interface is used to display information to users; the scheduling center is used to execute the steps of the cluster operation and maintenance method provided in any embodiment of the present application.

[0154] Specifically, the scheduling center is used to determine the target node in the target cluster in response to detecting a script orchestration request, and obtain the node information of the target node; determine the alternative scripts in the operation and maintenance script library based on the node information, and display all the alternative scripts in the operation and maintenance interface; determine the target script according to the selection operation performed by the user in the operation and maintenance interface, and determine the execution order between the target scripts according to the order adjustment operation performed by the user in the operation and maintenance interface, and obtain the script orchestration data corresponding to the target script combination; run the target script combination according to the script orchestration data, so as to perform operation and maintenance processing on the target node through the running target script.

[0155] Based on the above embodiments, optionally, the system also includes a workflow engine and a scheduling center for calling the workflow engine, and converting the script orchestration data into multi-tree structure data and the multi-tree structure data into workflow structure data through the workflow engine; generating a flowchart corresponding to the target script combination according to the workflow structure data, and displaying the flowchart in the operation and maintenance interface, wherein the flowchart is composed of at least one node, and the node represents the target script; in response to detecting that a user performs a node linking operation on the flowchart, updating the flowchart based on the node linking operation to link multiple target scripts in the flowchart, wherein the link is used to specify other target scripts that need to be executed after a target script fails to execute or succeeds; and updating the script orchestration data based on the updated flowchart.

[0156] On the basis of the above-mentioned implementation modes, optionally, the scheduling center is also used to respond to detecting a user's node selection operation on the flowchart, determine all upstream branches of the currently selected node based on the flowchart; for each of the upstream branches, determine all upstream nodes of the currently selected node according to the upstream branches, and write the currently selected node and all upstream nodes into an ancestor node list; deduplicate the nodes in the ancestor node list, and in the flowchart, set the nodes in the ancestor node list to an unlinkable state.

[0157] On the basis of the above-mentioned implementation modes, optionally, the scheduling center is also used to display the execution status of each target script through the flowchart; and / or, in response to detecting that the user performs a node viewing operation on the flowchart, display the script parameter information and script execution information corresponding to the currently viewed node on the operation and maintenance interface.

[0158] On the basis of the above-mentioned implementation modes, optionally, the scheduling center is also used to select each operation and maintenance script that has an affiliation relationship with the target cluster in the operation and maintenance script library as a candidate script; among all the candidate scripts, the candidate script is determined based on at least one of the node type, historical statistical information and node status in the node information.

[0159] On the basis of the above-mentioned implementation modes, optionally, the scheduling center is further used to screen out candidate scripts that meet the node type from all candidate scripts; among the screened candidate scripts, select the candidate script according to the node load rate, node available memory and node running time in the node status, and select the candidate script according to the statistical ranking of exception types and the statistical ranking of operation and maintenance scripts in the historical statistical information; wherein, the statistical ranking of exception types is obtained by sorting according to the occurrence frequency of each historical exception type, and the statistical ranking of operation and maintenance scripts is obtained by sorting according to the execution frequency of each historical operation and maintenance script.

[0160] On the basis of the above-mentioned implementation modes, optionally, the dispatch center is further used to determine the abnormal node and the abnormal type based on the cluster node abnormal signal in response to receiving the cluster node abnormal signal sent by the monitoring system; obtain the preset orchestration data corresponding to the preset script combination associated with the abnormal type, and execute the preset script combination according to the preset orchestration data to perform operation and maintenance processing on the abnormal node.

[0161] On the basis of the above-mentioned implementation modes, optionally, the scheduling center is also used to generate a job record corresponding to the target script combination based on the execution time, execution result and operation information of the target script combination; and, in response to detecting a record query request, query the corresponding job record based on the execution time, execution result or operation information in the record query request, and display the queried job record on the operation and maintenance interface.

[0162] The cluster operation and maintenance system provided in the embodiment of the present application can have the beneficial effects of the cluster operation and maintenance method provided in the method embodiment of the present application, which will not be described in detail here.

[0163] Figure 5 This is a functional diagram of a cluster operation and maintenance system provided by an embodiment of the present application, wherein the cluster operation and maintenance system may be composed of an operation and maintenance interface (UI), an operation and maintenance script library, a workflow engine, an audit record module, and a scheduling center. The operation and maintenance script library, the workflow engine, and the audit record module may interact with the operation and maintenance interface through a REST API or a data interface; the scheduling center may interact with the workflow engine through a REST API or a data interface, and interact with the operation and maintenance script library and the audit record module through a data stream or a message queue.

[0164] Among them, the operation and maintenance interface has the following functions: 1) Script library: supports viewing or editing scripts; 2) Parameter configuration panel: supports viewing or setting script parameters; 3) Template process display: supports script combination and interaction; 4) Execution panel: supports real-time display of job status; 5) Audit record panel: supports viewing job records.

[0165] That is, users can configure scripts and parameters on the operation and maintenance interface, and can also combine script processes through interactive methods such as dragging and clicking to build complex operation and maintenance operations, and provide query and display of job records. The operation and maintenance interface uses data interfaces, websockets, etc. to obtain and render data from each module, and is a unified data display outlet for the system. The back-end scheduling and rendering operations are fully transparent to operation and maintenance personnel, which greatly improves the efficiency of operation and analysis, lowers the technical threshold, and reduces the potential for errors in human operations.

[0166] The operation and maintenance script library mainly has the following functions: 1) Script library, which is used to store operation and maintenance scripts and record the ownership relationship of different scripts in the cluster; 2) Parameter library, which supports parameter management, records the filling method of different types of parameters, verification rules and other information, and records the reserved variables in the script. The operation and maintenance personnel can fill in the values ​​of the corresponding variables of the parameters during execution, which are used for combined calls of the template scheduling center. The script management library is one of the data cores of this system.

[0167] The audit record module mainly has the following functions: 1) Single job record; 2) Combined execution record. The system automatically records the detailed log of each script combination execution, including the parameters, execution time, execution results and other information of each script. It provides detailed audit records and supports query and export by time, script, executor and other dimensions to facilitate compliance inspection and problem tracing. The audit records are displayed in a graphical way through the workflow engine to support operation and maintenance personnel to conduct a comprehensive analysis of the job execution.

[0168] The workflow engine mainly performs the following processes: data conversion, rendering, and interaction. The dispatch center records the script arrangement data into JSON array data, and converts the original data into workflow data through the workflow engine. The workflow data is then combined and rendered into a flowchart by combining the scripts in the dispatch center. It also provides interactive capabilities and supports graphical interface editing. Complex operation and maintenance processes can be constructed by dragging and dropping.

[0169] The dispatch center mainly has the following functions: 1) combination management, supporting the creation or maintenance of script combinations; 2) execution scheduler, supporting the scheduling or execution of scripts; 3) process monitoring, supporting real-time status updates. Operation and maintenance personnel can combine multiple scripts in the workflow engine and customize the order, data flow and dependencies of script execution. When the script combination is executed, the dispatch center calls the script combination according to the process and monitors the script execution results, and writes the execution results into the audit record.

[0170] Figure 6 Schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 6 As shown, the electronic device 400 includes one or more processors 401 and a memory 402 .

[0171] The processor 401 may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 400 to perform desired functions.

[0172] The memory 402 may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 401 may run the program instructions to implement the cluster operation and maintenance method of any embodiment of the present application described above and / or other desired functions. Various contents such as initial external parameters, thresholds, etc. may also be stored in the computer-readable storage medium.

[0173] In one example, the electronic device 400 may further include: an input device 403 and an output device 404, which are interconnected via a bus system and / or other forms of connection mechanisms (not shown). The input device 403 may include, for example, a keyboard, a mouse, etc. The output device 404 may output various information to the outside, including early warning prompt information, braking force, etc. The output device 404 may include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, etc.

[0174] Of course, to simplify, Figure 6 Only some of the components related to the present application in the electronic device 400 are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to specific application conditions, the electronic device 400 may also include any other appropriate components.

[0175] In addition to the above methods and devices, the embodiments of the present application may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the cluster operation and maintenance method provided by any embodiment of the present application.

[0176] The computer program product may be written in any combination of one or more programming languages ​​to write program codes for performing the operations of the embodiments of the present application, including object-oriented programming languages, such as Java, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as an independent software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0177] In addition, an embodiment of the present application may also be a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, the processor executes the steps of the cluster operation and maintenance method provided by any embodiment of the present application.

[0178] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0179] It should be noted that the terms used in this application are only for describing specific embodiments, rather than limiting the scope of this application. As shown in the specification and claims of this application, unless the context clearly indicates an exception, the words "one", "a", "a kind of" and / or "the" do not specifically refer to the singular, but may also include the plural. The terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the presence of other identical elements in the process, method or device including the elements.

[0180] It should also be noted that the terms "center", "up", "down", "left", "right", "vertical", "horizontal", "inside", "outside", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present application. Unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", etc. should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be an indirect connection through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0181] This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and its core ideas of this application. The above is only the preferred implementation method of this application. It should be pointed out that due to the limitations of textual expression and the objective existence of infinite specific structures, ordinary technicians in this technical field can make several improvements, modifications or changes without departing from the principles of this application, and can also combine the above technical features in an appropriate manner; these improvements, modifications, changes or combinations, or the direct application of the concept and technical solution of the invention to other occasions without improvement, should be regarded as the scope of protection of this application.

Claims

1. A cluster operation and maintenance method, characterized in that: include: In response to detecting the scripting request, determining a target node in a target cluster, and acquiring node information of the target node; Determine alternative scripts in the operation and maintenance script library based on the node information, and display all alternative scripts in the operation and maintenance interface; Determine the target script according to the selection operation performed by the user in the operation and maintenance interface, and determine the execution order between the target scripts according to the sequence adjustment operation performed by the user in the operation and maintenance interface, and obtain script arrangement data corresponding to the target script combination; The target script combination is run according to the script arrangement data to perform operation and maintenance processing on the target node through the running target script.

2. The cluster operation and maintenance method according to claim 1, characterized in that: After obtaining the script arrangement data corresponding to the target script combination, it also includes: Converting the script arrangement data into multi-branch tree structure data, and converting the multi-branch tree structure data into workflow structure data; Generate a flowchart corresponding to the target script combination according to the workflow structure data, and display the flowchart in the operation and maintenance interface, wherein the flowchart is composed of at least one node, and the node represents the target script; In response to detecting that a user performs a node linking operation on the flowchart, updating the flowchart based on the node linking operation to link multiple target scripts in the flowchart, wherein the link is used to specify other target scripts that need to be executed after a target script fails to execute or succeeds; The scripting data is updated based on the updated flowchart.

3. The cluster operation and maintenance method according to claim 2, characterized in that After the flow chart is displayed in the operation and maintenance interface, the following is also included: In response to detecting a user's node selection operation on the flowchart, determining all upstream branches of the currently selected node based on the flowchart; For each of the upstream branches, determine all upstream nodes of the currently selected node according to the upstream branches, and write the currently selected node and all upstream nodes into an ancestor node list; The nodes in the ancestor node list are deduplicated, and in the flow chart, the nodes in the ancestor node list are set to an unlinkable state.

4. The cluster operation and maintenance method according to claim 2, characterized in that: After running the target script combination according to the script arrangement data, the method further includes: The execution status of each target script is displayed through the flowchart; and / or, In response to detecting that the user performs a node viewing operation on the flowchart, script parameter information and script execution information corresponding to the currently viewed node are displayed on the operation and maintenance interface.

5. The cluster operation and maintenance method according to claim 1, characterized in that: Determining an alternative script in the operation and maintenance script library based on the node information includes: Selecting each operation and maintenance script that has an affiliation relationship with the target cluster from the operation and maintenance script library as a candidate script; Among all the candidate scripts, a candidate script is determined based on at least one of the node type, historical statistical information, and node status in the node information.

6. The cluster operation and maintenance method according to claim 5, characterized in that: Among all candidate scripts, based on at least one of the node type, historical statistical information, and node status in the node information, determining the candidate script includes: Among all candidate scripts, select candidate scripts that meet the node type; Among the selected candidate scripts, select a candidate script according to the node load rate, node available memory and node running time in the node status, and select a candidate script according to the statistical sorting of abnormal types and the statistical sorting of operation and maintenance scripts in the historical statistical information; The statistical ranking of the exception types is obtained by ranking according to the occurrence frequency of each historical exception type, and the statistical ranking of the operation and maintenance scripts is obtained by ranking according to the execution frequency of each historical operation and maintenance script.

7. The cluster operation and maintenance method according to claim 1, characterized in that: The method further comprises: In response to receiving a cluster node abnormality signal sent by the monitoring system, determining an abnormal node and an abnormality type based on the cluster node abnormality signal; Acquire preset orchestration data corresponding to the preset script combination associated with the abnormal type, and execute the preset script combination according to the preset orchestration data to perform operation and maintenance processing on the abnormal node.

8. The cluster operation and maintenance method according to claim 1, characterized in that: After running the target script combination according to the script arrangement data, the method further includes: Generate a job record corresponding to the target script combination based on the execution time, execution result and operation information of the target script combination; The method further comprises: In response to detecting a record query request, the corresponding job record is queried based on the execution time, execution result or operation information in the record query request, and the queried job record is displayed on the operation and maintenance interface.

9. A cluster operation and maintenance system, characterized in that: The system includes an operation and maintenance script library, a process scheduling center and an operation and maintenance interface, wherein; The operation and maintenance script library is used to store multiple operation and maintenance scripts; The operation and maintenance interface is used to display information to users; The dispatching center is used to execute the steps of the cluster operation and maintenance method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a program or instruction, and the program or instruction enables a computer to execute the steps of the cluster operation and maintenance method according to any one of claims 1 to 8.

Images