System maintenance method, device, equipment and storage medium

Abstract

The present application discloses a system maintenance method, device, equipment and storage medium, which relates to the field of virtualization technology, including: adding its own IP address to the target cluster, determining the main maintenance node from the cluster nodes; receiving a deployment command to deploy a hyper-converged system, and entering the daily maintenance mode; the deployment command is generated by the main maintenance node based on the system deployment toolkit and cluster deployment rule package sent by the manufacturer and customer; when a hyper-converged system fails, repair it according to the preset maintenance rule package; when the repair is successful, the repair process as the repair plan to be confirmed is sent to the manufacturer and customer, and the preset maintenance rule package is updated after the manufacturer and customer confirm the repair plan to be confirmed. When a system failure is detected, repair is performed based on the manufacturer's maintenance rule package, and the repair process is returned to the manufacturer for confirmation and then the maintenance rule package is updated, so as to build a self-maintenance system that can automatically repair and reduce labor costs.

Description

Technical Field

[0001] The present invention relates to the field of virtualization technology, and in particular to a system maintenance method, device, equipment and storage medium. Background Art

[0002] As virtualization and cloud computing technologies mature, more and more enterprises are turning to hyper-converged products to meet their growing information needs, thanks to their advantages, such as the highly integrated resource integration. Hyper-converged systems integrate traditional computing, storage, and networking functions into the software of each server, forming a hyper-converged cluster via a physical network. However, this architecture also has significant disadvantages. First, the highly coupled product architecture makes troubleshooting more difficult for operations and maintenance personnel, resulting in a loss of time and money for users. This, in turn, requires manufacturers to spend more money and effort to train operations and maintenance personnel, increasing system costs.

[0003] Current hyper-converged systems lack self-maintenance mechanisms and rely on constant monitoring by operations and maintenance personnel. If a fault occurs and on-site maintenance personnel are unable to resolve it, significant losses may have already occurred by the time the capable personnel begin to address it. Furthermore, most current automated operations and maintenance systems, while ensuring system stability, achieve self-healing by restarting services related to the fault. However, most faults cannot be resolved simply by restarting services. Therefore, ensuring fault recovery in hyper-converged systems without human intervention is an urgent problem in this field. Summary of the Invention

[0004] In view of this, the present invention aims to provide a system maintenance method, apparatus, device, and storage medium. When a system failure is detected, repairs are performed based on the manufacturer's maintenance rule package. The repair process is then returned to the manufacturer for confirmation and the maintenance rule package is updated. This constructs a self-maintenance system capable of automatic repairs, reducing labor costs and potential losses. The specific solution is as follows:

[0005] In a first aspect, the present application provides a system maintenance method, which is applied to any cluster node, comprising:

[0006] Add its own IP address to the target cluster so that the target cluster can determine the master maintenance node from all cluster nodes based on all received IP addresses;

[0007] Receive the deployment command sent by the master maintenance node to deploy the hyper-converged system, and enter the preset daily maintenance mode after the hyper-converged system deployment is completed; the deployment command is generated by the master maintenance node using its own corresponding self-maintenance interface based on the system deployment toolkit and cluster deployment rule package sent by the manufacturer customer received by the master maintenance node;

[0008] When a failure occurs in the hyper-converged system, the hyper-converged system is repaired according to a preset maintenance rule package of the manufacturer and customer corresponding to the hyper-converged system;

[0009] When the repair is successful, the repair process as the repair plan to be confirmed is sent to the manufacturer customer, and after the manufacturer customer confirms and approves the repair plan to be confirmed, the preset maintenance rule package is updated using the repair plan to be confirmed.

[0010] Optionally, adding the own IP address to the target cluster includes:

[0011] Obtain a login request for its own self-maintenance interface, and obtain an address addition request after agreeing to the login request;

[0012] Respond to the address adding request to add its own IP address to the target cluster.

[0013] Optionally, after adding the own IP address to the target cluster so that the target cluster determines the master maintenance node from all cluster nodes according to all received IP addresses, the method further includes:

[0014] When the master maintenance node fails and goes offline, the target node is determined from the currently operating slave maintenance nodes through the target cluster and according to a preset algorithm, and the IP address of the target node is updated to the IP address of the master maintenance node, so that the target node is used as the new master maintenance node;

[0015] After the repair of the master maintenance node is completed, the master maintenance node is adjusted to a slave maintenance node through the target cluster.

[0016] Optionally, receiving a deployment command sent by the master maintenance node to perform hyper-converged system deployment includes:

[0017] Detecting the deployment process of the hyper-converged system and, when the deployment of the hyper-converged system fails, performing deployment and repair according to the repair solution in the cluster deployment rule package;

[0018] If the cluster deployment rule package does not contain a repair solution for the problem corresponding to the current hyper-converged system deployment failure, information prompting manual repair will be displayed through its own self-maintenance interface.

[0019] Optionally, receiving a deployment command sent by the master maintenance node to deploy a hyper-converged system, and entering a preset daily maintenance mode after the hyper-converged system deployment is completed, includes:

[0020] Monitoring various working states of the hyper-converged system according to the cluster deployment rule package;

[0021] When the monitoring determines that the various working states are normal, the deployment of the hyper-converged system is determined to be complete, and a prompt message for manual confirmation of whether the deployment is successful is triggered by using its own self-maintenance interface;

[0022] If an instruction indicating successful deployment is received, the system enters the preset daily maintenance mode, imports the preset maintenance rule package sent by the manufacturer customer corresponding to the hyper-converged system through its own self-maintenance interface, and configures the system alarm function using the preset maintenance rule package;

[0023] If an instruction indicating that the deployment has failed is received, an updated cluster deployment rule package is received so as to redeploy the hyper-converged system based on the updated cluster deployment rule package.

[0024] Optionally, when a failure occurs in the hyper-converged system, repairing the hyper-converged system according to a preset maintenance rule package of a manufacturer and customer corresponding to the hyper-converged system includes:

[0025] When a failure occurs in the hyper-converged system, the real-time working status of the monitored system is analyzed, and based on the failure problem obtained after the analysis, a query is made as to whether there is a corresponding target repair rule in the preset maintenance rule package;

[0026] If it exists, the target repair rule is used to repair the hyper-converged system; if it does not exist, the corresponding fault alarm information is sent through the system alarm function to remind maintenance personnel to perform repairs.

[0027] Optionally, after the repair process as the repair solution to be confirmed is sent to the manufacturer customer when the repair is successful, the following further comprises:

[0028] If no message is received from the manufacturer customer confirming the pending repair plan within a preset time period, the pending repair plan is saved in a local preset system maintenance rule database.

[0029] In a second aspect, the present application provides a system maintenance device, which is applied to any cluster node and includes:

[0030] A node determination module is used to add its own IP address to the target cluster so that the target cluster can determine the master maintenance node from all cluster nodes based on all received IP addresses;

[0031] A system deployment module is configured to receive a deployment command from the master maintenance node to perform hyper-converged system deployment and enter a preset daily maintenance mode after the hyper-converged system deployment is completed; the deployment command is generated by the master maintenance node using its own corresponding self-maintenance interface based on a system deployment toolkit and cluster deployment rule package sent by the manufacturer and customer and received by the master maintenance node;

[0032] A system repair module is used to repair the hyper-converged system according to a preset maintenance rule package of the manufacturer and customer corresponding to the hyper-converged system when a failure occurs in the hyper-converged system;

[0033] The rule package update module is used to send the current repair process as the repair plan to be confirmed to the manufacturer customer when the repair is successful, and update the preset maintenance rule package using the repair plan to be confirmed after the manufacturer customer confirms and approves the repair plan to be confirmed.

[0034] In a third aspect, the present application provides an electronic device comprising a processor and a memory; wherein the memory is used to store a computer program, and the computer program is loaded and executed by the processor to implement the aforementioned system maintenance method.

[0035] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program, which implements the aforementioned system maintenance method when executed by a processor.

[0036] In this application, its own IP address is added to the target cluster so that the target cluster determines the main maintenance node from all cluster nodes based on all the received IP addresses; receives the deployment command sent by the main maintenance node to deploy the hyper-converged system, and enters the preset daily maintenance mode after the hyper-converged system deployment is completed; the deployment command is generated by the main maintenance node using its own corresponding self-maintenance interface based on the system deployment toolkit and cluster deployment rule package sent by the manufacturer customer received by the main maintenance node; when the hyper-converged system fails, the hyper-converged system is repaired according to the preset maintenance rule package of the manufacturer customer corresponding to the hyper-converged system; when the repair is successful, the current repair process as the repair plan to be confirmed is sent to the manufacturer customer, and after the manufacturer customer confirms and approves the repair plan to be confirmed, the preset maintenance rule package is updated using the repair plan to be confirmed. Through the above technical solution, this application can repair the system based on the manufacturer's maintenance rule package when a system failure is detected after the hyper-converged system is deployed, and reply the repair process to the manufacturer for confirmation and then update the maintenance rule package to automatically repair the system when encountering the same failure. In this way, a self-maintenance system that can automatically repair most system failures without human intervention is gradually built, reducing manual monitoring costs and possible losses caused by the operation and maintenance personnel's failure to repair the system in a timely manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0038] Figure 1 A flow chart of a system maintenance method provided for this application;

[0039] Figure 2 A specific system maintenance method flow chart provided for this application;

[0040] Figure 3 A specific system maintenance method flow chart provided for this application;

[0041] Figure 4 A specific system maintenance method flow chart provided for this application;

[0042] Figure 5 A schematic diagram of the structure of a system maintenance device provided in this application;

[0043] Figure 6 This is a structural diagram of an electronic device provided in this application. DETAILED DESCRIPTION

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

[0045] In current hyper-converged systems, operations and maintenance personnel are required to monitor the system at all times. If on-site operations and maintenance personnel are unable to resolve a fault, significant losses may result. Furthermore, current automated operations and maintenance systems repair the system by restarting the fault-related services, resulting in poor repair results. This application can perform repairs based on the manufacturer's maintenance rule package when a system fault is detected, and then update the maintenance rule package after returning the repair process to the manufacturer for confirmation. This allows the system to be automatically repaired when the same fault occurs, building a self-maintaining system that does not require manual intervention, reducing manual monitoring costs and potential losses.

[0046] See also Figure 1 As shown, an embodiment of the present invention discloses a system maintenance method, which is applied to any cluster node, including:

[0047] Step S11: Add its own IP address to the target cluster, so that the target cluster determines the master maintenance node from all cluster nodes according to all received IP addresses.

[0048] In this embodiment, before deploying the hyper-converged system, a target cluster is constructed using the IP addresses of the nodes that need to be added to the target cluster of the hyper-converged system. This adds the cluster nodes to be monitored to the same cluster. The system obtains a login request for its own self-maintenance interface, and after accepting the login request, obtains an address addition request. The system responds to the address addition request, thereby adding its own IP address to the target cluster.

[0049] The specific steps for adding the IP address to the same cluster are as follows: before the hyper-convergence system is deployed, the user or maintenance personnel can directly connect to the self-maintenance network port of each server through a personal computer, and then log in to the self-maintenance interface corresponding to each cluster node according to the pre-set IP address, and configure the IP address pre-assigned by the manufacturer and customer on the self-maintenance interface. After all nodes are configured, use one end of the network cable to connect to the self-maintenance network port on the server, and connect the other end of the network cable to the switch, so that the self-maintenance device corresponding to each cluster node can communicate with each other in the hyper-convergence system network. It can be understood that the self-maintenance function of any cluster node is realized through the self-maintenance device in the node, and after all nodes are configured, the IP address of the self-maintenance device of each cluster node can be set and directly connected to the Internet, so that after the hyper-convergence system is deployed, the preset maintenance rule package can be received more quickly and the rule package can be updated. Through the above operations, the self-maintenance device in the cluster node can play the function of self-learning and self-maintenance when deploying the hyper-convergence cluster. After the above-mentioned self-maintenance system network is built, you can use a browser to log in to the self-maintenance interface of any node. After logging in to the self-maintenance interface for the first time, you will enter the deployment mode of the hyper-converged system. In the deployment mode, add the IP address of the planned cluster node, that is, the self-maintenance management IP address, to the same cluster, so that the self-maintenance device in the cluster node can manage and detect the physical servers in the target cluster through the self-maintenance management IP address.

[0050] In this embodiment, after the cluster nodes in the target cluster are determined, the self-maintenance device of each node in the target cluster will automatically prioritize each node in the target cluster based on the IP address and MAC address of the self-maintenance device and other information through a preset node priority setting algorithm. It can be understood that the algorithm used for the above-mentioned node priority differentiation is not specifically limited in this application. There is only one master maintenance node in a cluster, and the rest are slave maintenance nodes. The master maintenance node will have an IP address with the same network segment as the management IP address of the corresponding self-maintenance device. The IP address needs to be specified by the maintenance personnel in the deployment mode. In this way, it is convenient for the operation and maintenance personnel to access it directly through the virtual IP address. All slave maintenance nodes are required to report system detection data to the master maintenance node in real time. The master maintenance node collects and analyzes the cluster status and displays it. When the cluster nodes in the target cluster need to be configured, they can also be managed uniformly through the self-maintenance interface of the master maintenance node.

[0051] It should be noted that when the master maintenance node fails and goes offline, the target cluster determines a target node from the currently functioning slave maintenance nodes according to a preset algorithm. The target node's IP address is updated to that of the master maintenance node, allowing it to serve as the new master maintenance node. After the master maintenance node is repaired, priority preemption is not performed, maintaining the current self-maintenance management status, and the target cluster adjusts the master maintenance node to a slave maintenance node. This ensures more stable operation of the target cluster.

[0052] Step S12: Receive the deployment command sent by the master maintenance node to deploy the hyper-converged system, and enter the preset daily maintenance mode after the hyper-converged system deployment is completed; the deployment command is generated by the master maintenance node using its own corresponding self-maintenance interface based on the system deployment toolkit and cluster deployment rule package sent by the manufacturer customer received by the master maintenance node.

[0053] In this embodiment, the deployer can select the manufacturer and version of the hyper-converged system to be deployed on the self-maintenance interface, and then upload the system deployment toolkit and cluster deployment rule package of the determined manufacturer on the self-maintenance interface. The system deployment toolkit is the basic system image and customized component package for system deployment, and the cluster deployment rule package specifies some key information of the cluster, such as: hyper-converged platform IP, designated management node, and methods for handling various problems that arise during the installation process. After the relevant files are uploaded, the main maintenance node generates the deployment command using its own corresponding self-maintenance interface, and then issues the deployment command with one click. Each node in the cluster begins to automatically deploy the uploaded system and enters the preset daily maintenance mode after the hyper-converged system deployment is completed.

[0054] Step S13: When a failure occurs in the hyper-converged system, the hyper-converged system is repaired according to a preset maintenance rule package of the manufacturer and customer corresponding to the hyper-converged system.

[0055] In this embodiment, when a hyper-converged system fails, the hyper-converged system can be repaired directly according to the manufacturer's and customer's preset maintenance rule package. It should be noted that if the repair fails according to the preset maintenance rule package, a prompt message is issued to facilitate manual repair. It should be noted that the preset maintenance rule package is a maintenance rule package of a corresponding version provided by the corresponding manufacturer and imported from the maintenance management interface after the hyper-converged system is deployed and the cluster is operating normally.

[0056] Step S14: When the repair is successful, the repair process as the repair plan to be confirmed is sent to the manufacturer customer, and after the manufacturer customer confirms and approves the repair plan to be confirmed, the preset maintenance rule package is updated using the repair plan to be confirmed.

[0057] In this embodiment, after the repair is successful, the repair process can be recorded, and then the repair process can be determined as a repair plan to be confirmed, and the manufacturer can be notified for confirmation. If the manufacturer confirms that the repair process is valid, the preset maintenance rule package can be updated using the repair plan to be confirmed.

[0058] It can be seen that in this embodiment, its own IP address is added to the target cluster, and the main maintenance node is determined, and a new main maintenance node is reconfirmed when the main maintenance node fails; the deployment command sent by the main maintenance node is received to deploy the hyper-converged system, and the preset daily maintenance mode is entered after the hyper-converged system deployment is completed; when the hyper-converged system fails, it is repaired according to the preset maintenance rule package of the manufacturer customer corresponding to the hyper-converged system; when the repair is successful, the repair process as the repair plan to be confirmed is sent to the manufacturer customer, and after the manufacturer customer confirms the repair plan to be confirmed, the preset maintenance rule package is updated using the repair plan to be confirmed. Through the above technical solution, this application can repair the system based on the manufacturer's maintenance rule package when a system failure is detected after the hyper-converged system is deployed, and update the maintenance rule package after the repair process is returned to the manufacturer for confirmation, so as to automatically repair the system when encountering the same failure. In this way, a self-maintenance system that can automatically repair hyper-converged system failures without human intervention can be constructed, reducing the maintenance cost when the system fails and the possible losses caused by the operation and maintenance personnel's failure to repair the system in time.

[0059] Based on the previous embodiment, it can be seen that the present application can automatically perform system maintenance after the hyper-convergence system is deployed. Next, the deployment process of the hyper-convergence system will be described in detail in this embodiment. Figure 2 As shown, the embodiment of the present application discloses a specific system maintenance method, including:

[0060] Step S21: Monitor various working states of the hyper-converged system according to the cluster deployment rule package.

[0061] Step S22: When it is detected that the working status of each item is normal, the deployment of the hyper-converged system is determined to be complete, and a prompt message for manual confirmation of whether the deployment is successful is triggered by using its own self-maintenance interface.

[0062] In this embodiment, during the deployment process of the hyper-converged system, the self-maintenance device on each cluster node will continuously detect the status of various services of the system based on the cluster deployment rule package, using methods such as detecting service ports and checking the service status within the system. When it is monitored that each service is normal, each node will report the completion of the deployment to the self-maintenance device of the main maintenance node, and use its own self-maintenance interface to trigger a prompt message for manual confirmation of whether the deployment is successful to request manual inspection.

[0063] It should be noted that when a system deployment fails due to a fault or the deployment time expires, the self-maintenance device in the cluster node will repair the problem according to the corresponding solution in the cluster deployment rule package until the deployment is complete. If the cluster deployment rule package does not contain a repair solution for the current hyper-converged system deployment failure, the self-maintenance interface will display a message prompting manual repair and recommend manual intervention until the hyper-converged cluster deployment is complete. By continuously monitoring the working status of the hyper-converged system and manually confirming it, the probability of system failure can be reduced after the cluster deployment is completed, improving system stability.

[0064] Step S23: If an instruction indicating successful deployment is received, the system enters the preset daily maintenance mode, imports the preset maintenance rule package sent by the manufacturer customer corresponding to the hyper-converged system through its own self-maintenance interface, and uses the preset maintenance rule package to configure the system alarm function.

[0065] In this embodiment, after the hyper-converged system is deployed and a manual confirmation application is issued, the operation and maintenance personnel need to check whether the access to each service interface of the cluster is normal. After the inspection is completed, the deployment is confirmed to be complete on the self-maintenance interface of the main maintenance node. After the target cluster receives the instruction indicating the successful deployment confirmation, it enters the preset daily maintenance mode and imports the corresponding version of the preset maintenance rule package provided by the corresponding manufacturer into the self-maintenance management interface to configure and apply services such as alarm functions. The alarm functions include but are not limited to email alarms and SMS alarms.

[0066] Step S24: If an instruction indicating that the deployment has failed is received, an updated cluster deployment rule package is received to redeploy the hyper-converged system based on the updated cluster deployment rule package.

[0067] In this embodiment, if the operation and maintenance personnel manually check the cluster status and find a problem, the cluster deployment failure will be confirmed on the self-maintenance interface of the main maintenance node. The main maintenance node will suggest the deployment personnel to re-upload the system deployment toolkit and cluster deployment rule package. If the cluster node receives an instruction indicating that the deployment has failed, it will receive the updated system deployment toolkit and cluster deployment rule package issued by the main maintenance node and redeploy the hyper-converged system. In this way, the problem of system deployment failure caused by file loss or incompleteness when uploading the system deployment toolkit and cluster deployment rule package can be avoided.

[0068] As can be seen, in this embodiment, the various operating states of the hyper-converged system are monitored based on the cluster deployment rule package. When the various operating states are monitored to be normal, the hyper-converged system deployment is determined to be complete, and a prompt message for manual confirmation of the deployment success is triggered using its own self-maintenance interface. If the deployment fails and the cluster deployment rule package does not contain a repair solution for the current hyper-converged system deployment failure, a message prompting manual repair is displayed through its own self-maintenance interface. If a command indicating successful deployment is received, the system enters a preset daily maintenance mode, imports the preset maintenance rule package sent by the manufacturer and customer of the hyper-converged system through its own self-maintenance interface, and configures the system alarm function using the preset maintenance rule package. If a command indicating failed deployment is received, the system receives an updated cluster deployment rule package so that the hyper-converged system can be redeployed based on the updated cluster deployment rule package. By continuously monitoring the operating state of the hyper-converged system and displaying a prompt for manual repair to manually confirm the system deployment, system deployment failures caused by missing or incomplete files when uploading the system deployment toolkit and cluster deployment rule package can be avoided. The probability of system failure after cluster deployment is completed is reduced, thereby improving system stability.

[0069] Based on the above embodiments, it can be seen that the present application can automatically repair the system after deployment is completed. Next, the process of realizing automatic repair of system failures will be described in detail in this embodiment. Figure 3 As shown, the embodiment of the present application discloses a specific system maintenance method, including:

[0070] Step S31: When a failure occurs in the hyper-converged system, the real-time working status of the monitored system is analyzed, and based on the failure problem obtained after analysis, a query is made as to whether there is a corresponding target repair rule in the preset maintenance rule package.

[0071] In this embodiment, when a hyper-converged system fails, real-time monitoring and data obtained by the self-maintenance device in the cluster node are analyzed to obtain the fault problem corresponding to the current system, and then a query is performed according to the preset maintenance rule package.

[0072] Step S32: If yes, repair the hyper-converged system using the target repair rule.

[0073] If the preset maintenance rule package contains a target repair rule corresponding to the current fault problem, the corresponding fault repair plan in the preset maintenance rule package will be executed until the cluster is healthy.

[0074] Step S33: If it does not exist, the corresponding fault alarm information is sent through the system alarm function configured when the hyper-converged system is deployed to remind maintenance personnel to repair it.

[0075] If the preset maintenance rule package does not contain the target repair rule corresponding to the current fault problem, the corresponding fault information will be sent through the email or SMS alarm function configured in the previous embodiment, requesting maintenance personnel to manually intervene and repair the problem. After receiving the fault alarm information, the maintenance personnel can use the system's virtual IP to log in to the self-maintenance interface of the main maintenance node, view the fault information analyzed by the system's real-time working status, and manually execute the manual repair plan through the self-maintenance interface. After the manual repair is completed, the system will record the repair plan of this manual repair as a pending repair plan for manual confirmation.

[0076] Step S34: When the repair is successful, the repair process as the repair plan to be confirmed is sent to the manufacturer customer, and after the manufacturer customer confirms and approves the repair plan to be confirmed, the preset maintenance rule package is updated using the repair plan to be confirmed.

[0077] In this embodiment, the maintenance personnel confirms the repair process corresponding to the repair plan to be confirmed. After confirming that the repair plan is valid, the repair plan is sent to the manufacturer's corresponding maintenance rule library so that the manufacturer can review the repair plan and generate a new maintenance rule package after the review for distribution so that each node can use the preset maintenance rule package to update. It can be understood that the update operation will not affect other running businesses on the platform.

[0078] It should be noted that if the manufacturer customer does not receive a message confirming the pending repair plan within the preset time period, the pending repair plan will be saved in the local preset system maintenance rule database. In this way, if a similar fault occurs in the system when the node has not received the repair plan after review and confirmation by the manufacturer customer, the system can be directly repaired using the maintenance plan in the local preset system maintenance rule database without the need for manual repair, thereby improving the efficiency of hyper-converged system fault repair. It is understandable that the pending repair plan can also be saved in the local preset system maintenance rule database for backup while sending the pending repair plan to the manufacturer customer, so as to further improve the efficiency of repairing system faults.

[0079] As can be seen, in this embodiment, when a hyper-converged system fails, the system analyzes the monitored real-time operating status of the system and, based on the fault problem identified in the analysis, queries the preset maintenance rule package to determine whether a corresponding target repair rule exists. If so, the hyper-converged system is repaired using the target repair rule. If not, a corresponding fault alarm message is sent via the system alarm function configured during the deployment of the hyper-converged system to alert maintenance personnel to perform the repair. If the repair is successful, the repair process, which serves as the pending repair plan, is sent to the manufacturer customer. After the manufacturer customer confirms and approves the pending repair plan, the preset maintenance rule package is updated using the pending repair plan. If no confirmation of the pending repair plan is received from the manufacturer customer within a preset time period, the pending repair plan is saved in a local preset system maintenance rule database. By sending the manually intervened repair plan to the manufacturer customer for confirmation and then updating the preset maintenance rule package, the preset maintenance rule package's scope of repair for system faults is gradually expanded, and the pending repair plan is saved in the local preset system maintenance rule database, the efficiency of hyper-converged system fault repair can also be improved. In this way, through the continuous supplementation and updating of the preset maintenance rule base between users and manufacturers, a virtuous cycle will be formed, and eventually a self-maintaining hyper-converged system that tends to require no manual maintenance will be obtained, reducing the operation and maintenance personnel expenses of manufacturers and users, and reducing business economic losses caused by failures.

[0080] See also Figure 4 As shown, an embodiment of the present application discloses a specific system maintenance method flow chart, which is applied to any cluster node. In this embodiment, before deploying the hyper-converged cluster, the self-maintenance device on each server is connected, and a self-maintenance network is constructed by configuring the IP address of the self-maintenance device. After the self-maintenance network between each cluster node is constructed, the system enters the deployment mode and determines the cluster nodes that need to join the same cluster; and automatically sets the priority based on the IP address and other information of the cluster node to distinguish between the master maintenance node and the slave maintenance node. Then, the system deployment toolkit and cluster deployment rule package of each manufacturer's hyper-converged system are uploaded to the self-maintenance interface of the master maintenance node, and the deployment command is issued.

[0081] During the deployment process, the self-maintenance device of each node continuously detects the system to determine whether the system deployment is normal. When the deployment encounters a problem, the problem is repaired according to the cluster deployment rule package. If the cluster deployment rule package does not contain a repair solution corresponding to the current problem, manual intervention will be recommended for repair. After detecting that all system services are normal, the deployment completion will be reported to the self-maintenance device of the main maintenance node and a manual inspection will be requested. After the operation and maintenance personnel have checked that the access to each service interface of the cluster is normal, they will confirm it on the self-maintenance interface of the main maintenance node, and the cluster will enter daily maintenance mode. However, if the operation and maintenance personnel find that there is a problem with the cluster, they will confirm that the cluster deployment has failed on the self-maintenance interface of the main maintenance node, re-upload the system deployment toolkit and cluster deployment rule package, and redeploy until the deployment is complete.

[0082] After the system is deployed, the maintenance rule package for the corresponding manufacturer and version is imported, and the alarm function is configured. At this point, when a hyper-converged system fails, the self-maintenance device executes the corresponding fault repair plan based on the maintenance rule package. However, if the self-maintenance device cannot find the corresponding repair plan in the maintenance rule package, it will request manual intervention from maintenance personnel to repair the problem. After the repair is completed, the repair process is recorded and the maintenance personnel are requested to confirm the effective repair plan. This effective repair plan will be recorded in the maintenance rule database and uploaded to the corresponding manufacturer's maintenance rule library in real time for updating, ultimately resulting in a hyper-converged system that does not require manual maintenance.

[0083] The above technical solution uses a self-learning system to learn fault handling methods. By continuously monitoring the hyperconverged system, it can identify faults and automatically execute the corresponding fault repair plan without human intervention. When encountering a fault that has not been learned, the system automatically learns the new fault handling plan through human intervention. Ultimately, through the continuous learning and updating of this self-maintaining device, a hyperconverged system that requires no manual maintenance is achieved, reducing the pressure and overhead on both operators and users.

[0084] See also Figure 5 As shown, the embodiment of the present application further discloses a system maintenance device, which is applied to any cluster node, including:

[0085] The node determination module 11 is configured to add its own IP address to the target cluster so that the target cluster can determine the master maintenance node from all cluster nodes based on all received IP addresses;

[0086] The system deployment module 12 is configured to receive a deployment command sent by the master maintenance node to perform hyper-converged system deployment and enter a preset daily maintenance mode after the hyper-converged system deployment is completed; the deployment command is generated by the master maintenance node using its own corresponding self-maintenance interface based on the system deployment toolkit and cluster deployment rule package sent by the manufacturer and customer received by the master maintenance node;

[0087] A system repair module 13 is configured to repair the hyper-converged system according to a preset maintenance rule package of a manufacturer and customer corresponding to the hyper-converged system when a failure occurs in the hyper-converged system;

[0088] The rule package updating module 14 is used to send the current repair process as the repair plan to be confirmed to the manufacturer customer when the repair is successful, and update the preset maintenance rule package using the repair plan to be confirmed after the manufacturer customer confirms and approves the repair plan to be confirmed.

[0089] In this embodiment, after adding its own IP address to the target cluster, the target cluster determines the master maintenance node from all cluster nodes based on all the received IP addresses; deploys the hyper-converged system by receiving the deployment command sent by the master maintenance node, and enters the preset daily maintenance mode after the hyper-converged system is deployed; when a failure occurs in the hyper-converged system, the hyper-converged system is repaired according to the preset maintenance rule package of the manufacturer customer corresponding to the hyper-converged system; when the repair is successful, the repair process as the repair plan to be confirmed is sent to the manufacturer customer, and after the manufacturer customer confirms and approves the repair plan to be confirmed, the preset maintenance rule package is updated using the repair plan to be confirmed. It can be seen from this that this embodiment can perform repairs based on the manufacturer's maintenance rule package when a system failure is detected after the hyper-converged system is deployed, and update the maintenance rule package after the repair process is returned to the manufacturer for confirmation, so as to automatically perform system repairs when encountering the same failure, thereby building a self-maintenance system that automatically repairs failures without human intervention, thereby reducing system maintenance costs.

[0090] In some specific embodiments, the node determination module 11 specifically includes:

[0091] A request acquisition unit, configured to acquire a login request for its own self-maintenance interface and acquire an address addition request after agreeing to the login request;

[0092] The address adding unit is used to respond to the address adding request to add its own IP address to the target cluster.

[0093] In some specific embodiments, the node determination module 11 further includes:

[0094] A node determination unit, configured to determine a target node from the currently normally operating slave maintenance nodes through the target cluster and according to a preset algorithm when the master maintenance node fails and goes offline;

[0095] an address updating unit, configured to update the IP address of the target node to the IP address of the master maintenance node, so as to use the target node as a new master maintenance node;

[0096] The node adjustment unit is configured to adjust the master maintenance node to a slave maintenance node through the target cluster after the master maintenance node is repaired.

[0097] In some specific embodiments, the system deployment module 12 specifically includes:

[0098] a first system repair unit, configured to detect the deployment process of the hyper-converged system and, when the deployment of the hyper-converged system fails, perform deployment repair according to the repair solution in the cluster deployment rule package;

[0099] The information prompting unit is used to display information for prompting manual repair through its own self-maintenance interface if there is no repair solution for the problem corresponding to the current hyper-converged system deployment failure in the cluster deployment rule package.

[0100] In some specific embodiments, the system deployment module 12 specifically includes:

[0101] A status monitoring unit, configured to monitor various working states of the hyper-converged system according to the cluster deployment rule package;

[0102] a prompt triggering unit, configured to determine that the deployment of the hyper-converged system is complete upon detecting that the various working states are normal, and trigger a prompt message for manually confirming whether the deployment is successful using its own self-maintenance interface;

[0103] an alarm configuration unit, configured to, upon receiving an instruction indicating successful deployment confirmation, enter the preset daily maintenance mode, import the preset maintenance rule package sent by the manufacturer customer corresponding to the hyper-converged system through its own self-maintenance interface, and configure the system alarm function using the preset maintenance rule package;

[0104] The rule package receiving unit is configured to receive an updated cluster deployment rule package upon receiving an instruction indicating that the deployment has failed, so as to redeploy the hyper-converged system based on the updated cluster deployment rule package.

[0105] In some specific embodiments, the system repair module 13 specifically includes:

[0106] A status analysis unit is configured to analyze the real-time working status of the monitored system when a failure occurs in the hyper-converged system, and query whether a corresponding target repair rule exists in the preset maintenance rule package based on the failure problem obtained after the analysis;

[0107] The second system repair unit is used to repair the hyper-converged system using the target repair rule if it exists, and if not, send corresponding fault alarm information through the system alarm function to remind maintenance personnel to perform repairs.

[0108] In some specific embodiments, the rule package updating module 14 further includes:

[0109] The solution saving unit is configured to save the repair solution to be confirmed into a local preset system maintenance rule database if no message is received from the manufacturer customer confirming the repair solution to be confirmed within a preset time period.

[0110] Furthermore, the embodiment of the present application also discloses an electronic device, Figure 6 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the diagram should not be considered as any limitation to the scope of application of the present application.

[0111] Figure 6 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps of the system maintenance method disclosed in any of the aforementioned embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0112] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device. The communication protocol it follows is any communication protocol that can be applied to the technical solution of this application and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world. Its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0113] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or CD, etc. The resources stored thereon can include an operating system 221, a computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0114] The operating system 221 is used to manage and control the hardware devices on the electronic device 20 and the computer program 222, which can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program that can be used to implement the system maintenance method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include a computer program that can be used to implement other specific tasks.

[0115] Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the system maintenance method disclosed above is implemented. The specific steps of this method can be referred to the corresponding contents disclosed in the aforementioned embodiments and will not be repeated here.

[0116] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. Reference can be made to the descriptions of the identical or similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and the relevant parts can be referred to the descriptions of the methods.

[0117] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0118] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0119] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0120] The above is a detailed introduction to the technical solution provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the ideas of the present application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A system maintenance method, characterized in that: Applicable to any cluster node, including: Add its own IP address to the target cluster so that the target cluster determines the master maintenance node from all cluster nodes according to all received IP addresses; Receive the deployment command sent by the master maintenance node to deploy the hyper-converged system, and enter the preset daily maintenance mode after the hyper-converged system deployment is completed; the deployment command is generated by the master maintenance node using its own corresponding self-maintenance interface based on the system deployment toolkit and cluster deployment rule package sent by the manufacturer customer received by the master maintenance node; When the hyper-convergence system fails, the hyper-convergence system is repaired according to a preset maintenance rule package of the manufacturer and customer corresponding to the hyper-convergence system; When the repair is successful, the repair process as the repair plan to be confirmed is sent to the manufacturer customer, and after the manufacturer customer confirms and approves the repair plan to be confirmed, the preset maintenance rule package is updated using the repair plan to be confirmed.

2. The system maintenance method according to claim 1, characterized in that: Adding its own IP address to the target cluster includes: Obtain a login request for its own self-maintenance interface, and obtain an address adding request after agreeing to the login request; Respond to the address adding request to add its own IP address to the target cluster.

3. The system maintenance method according to claim 1, characterized in that: After adding the own IP address to the target cluster so that the target cluster determines the main maintenance node from all cluster nodes according to all received IP addresses, the method further includes: When the master maintenance node fails and goes offline, the target node is determined from the slave maintenance nodes that are currently operating normally through the target cluster and according to a preset algorithm, and the IP address of the target node is updated to the IP address of the master maintenance node, so that the target node is used as the new master maintenance node; After the repair of the master maintenance node is completed, the master maintenance node is adjusted to a slave maintenance node through the target cluster.

4. The system maintenance method according to claim 1, characterized in that: The receiving a deployment command sent by the master maintenance node to perform hyper-converged system deployment includes: Detecting the deployment process of the hyper-converged system, and when the deployment of the hyper-converged system fails, performing deployment and repair according to the repair solution in the cluster deployment rule package; If the cluster deployment rule package does not contain a repair solution for the problem corresponding to the current hyper-converged system deployment failure, information for prompting manual repair is displayed through its own self-maintenance interface.

5. The system maintenance method according to claim 4, characterized in that: The receiving of the deployment command sent by the master maintenance node to perform hyper-convergence system deployment, and entering a preset daily maintenance mode after the hyper-convergence system deployment is completed, includes: Monitoring various working states of the hyper-converged system according to the cluster deployment rule package; When the working status of each item is normal, the deployment of the hyper-converged system is determined to be completed, and a prompt message for manual confirmation of whether the deployment is successful is triggered by using its own self-maintenance interface; If an instruction indicating successful deployment is received, the preset daily maintenance mode is entered, and the preset maintenance rule package sent by the manufacturer customer corresponding to the hyper-converged system is imported through its own self-maintenance interface, and the system alarm function is configured using the preset maintenance rule package; If an instruction indicating that the deployment has failed is received, an updated cluster deployment rule package is received so as to redeploy the hyper-converged system based on the updated cluster deployment rule package.

6. The system maintenance method according to claim 5, characterized in that: When a failure occurs in the hyper-converged system, repairing the hyper-converged system according to a preset maintenance rule package of a manufacturer and customer corresponding to the hyper-converged system includes: When a failure occurs in the hyper-converged system, the real-time working status of the monitored system is analyzed, and based on the failure problem obtained after the analysis, it is inquired whether there is a corresponding target repair rule in the preset maintenance rule package; If it exists, the target repair rule is used to repair the hyper-converged system. If it does not exist, the corresponding fault alarm information is sent through the system alarm function to remind maintenance personnel to repair it.

7. The system maintenance method according to any one of claims 1 to 6, characterized in that: When the repair is successful, after sending the repair process as the repair solution to be confirmed to the manufacturer customer, it also includes: If no message is received from the manufacturer customer confirming the pending repair plan within a preset time period, the pending repair plan is saved in a local preset system maintenance rule database.

8. A system maintenance device, characterized in that: Applicable to any cluster node, including: A node determination module, used to add its own IP address to the target cluster, so that the target cluster determines the main maintenance node from all cluster nodes according to all received IP addresses; A system deployment module is used to receive a deployment command sent by the master maintenance node to perform hyper-converged system deployment, and enter a preset daily maintenance mode after the hyper-converged system deployment is completed; the deployment command is generated by the master maintenance node using its corresponding self-maintenance interface based on the system deployment toolkit and cluster deployment rule package sent by the manufacturer customer and received by the master maintenance node; A system repair module, used to repair the hyper-converged system according to a preset maintenance rule package of a manufacturer and customer corresponding to the hyper-converged system when a failure occurs in the hyper-converged system; The rule package updating module is used to send the current repair process as the repair plan to be confirmed to the manufacturer customer when the repair is successful, and to update the preset maintenance rule package using the repair plan to be confirmed after the manufacturer customer confirms and approves the repair plan to be confirmed.

9. An electronic device, characterized in that: The electronic device comprises a processor and a memory; wherein the memory is used to store a computer program, and the computer program is loaded and executed by the processor to implement the system maintenance method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Used to store a computer program, which, when executed by a processor, implements the system maintenance method according to any one of claims 1 to 7.

Images