A method, device, medium and product for inspecting a server cluster

Abstract

This invention relates to the field of distributed technology and discloses a method, device, medium, and product for inspecting server clusters. The method includes: acquiring the server cluster to be inspected and generating an inspection script corresponding to the server cluster using batch operation and maintenance software; based on the inspection script, performing a basic status check on the container network components of the server cluster to be inspected, obtaining a first inspection result, and if the first inspection result is a pass, acquiring the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server; performing a connectivity check on the container network components based on the container network component subnet segments, obtaining a second inspection result, and generating an inspection log based on the first and second inspection results. This method can improve the inspection efficiency and accuracy of server clusters and reduce the probability of missed or false detections.

Description

Technical Field

[0001] This invention relates to the field of distributed technology, and in particular to a method, device, medium and product for inspecting server clusters. Background Technology

[0002] In the context of financial private cloud, pre-inspection and daily inspection of the container network environment of server clusters are of great significance to ensuring cluster health and business stability.

[0003] Currently, existing server cluster inspection methods typically employ manual inspection, checking each server in the cluster one by one. However, this manual inspection method is inefficient, difficult to adapt to large-scale clusters and ever-increasing expansion needs, and has low accuracy, easily leading to missed detections and false positives. Summary of the Invention

[0004] This invention provides a method, device, medium, and product for inspecting server clusters, which can improve the inspection efficiency and accuracy of server clusters and reduce the probability of missed and false detections.

[0005] According to one aspect of the present invention, a method for inspecting a server cluster is provided, comprising: Obtain the server cluster to be inspected, and use batch operation and maintenance software to generate the inspection script corresponding to the server cluster to be inspected. Based on the inspection script, a basic status check of the container network components of the server cluster to be inspected is performed to obtain a first inspection result. When the first inspection result is that the inspection is passed, the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server are obtained. A connectivity check of the container network component is performed between the container network component subnet segment and the container network subnet segment to obtain a second check result. An inspection log is then generated based on the first check result and the second check result.

[0006] According to another aspect of the present invention, a server cluster inspection device is provided, comprising: The script generation module is used to obtain the server cluster to be inspected and to generate the inspection script corresponding to the server cluster to be inspected using batch operation and maintenance software. The network segment acquisition module is used to perform a basic status check on the container network components of the server cluster to be inspected based on the inspection script, obtain a first inspection result, and when the first inspection result is that the inspection is passed, obtain the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server. The log generation module is used to perform a connectivity check on the container network component based on the container network component subnet segment and the container network subnet segment, obtain a second check result, and generate an inspection log based on the first check result and the second check result.

[0007] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the server cluster inspection method according to any embodiment of the present invention.

[0008] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program, the computer program being executed by a processor to implement the server cluster inspection method according to any embodiment of the present invention.

[0009] According to another aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the server cluster inspection method described in any embodiment of the present invention.

[0010] The technical solution of this invention involves acquiring a server cluster to be inspected and using batch operation and maintenance software to generate an inspection script corresponding to the server cluster. Based on the inspection script, a basic status check of the container network components of the server cluster to be inspected is performed to obtain a first check result. If the first check result is a pass, the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server are acquired. A connectivity check of the container network components is performed based on the container network component subnet segments to obtain a second check result. An inspection log is generated based on the first and second check results. By generating an inspection script and performing a connectivity check of the container network components based on the corresponding subnet segments after the server cluster to be inspected passes the basic status check, the final inspection result can be obtained. This improves the inspection efficiency and accuracy of the server cluster and reduces the probability of missed or false detections.

[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This is a flowchart of a server cluster inspection method according to Embodiment 1 of the present invention; Figure 2 This is a flowchart of a server cluster inspection method according to Embodiment 2 of the present invention; Figure 3 This is a schematic diagram of the structure of a server cluster inspection device according to Embodiment 3 of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device that implements the server cluster inspection method of this invention. Detailed Implementation

[0014] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0015] It should be noted that the terms "first," "second," "modification," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] Example 1 Figure 1This is a flowchart of a server cluster inspection method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations involving pre-inspection or inspection of server clusters. The method can be executed by a server cluster inspection device, which can be implemented in hardware and / or software. Typically, the server cluster inspection device can be configured in electronic devices, such as computer equipment, servers, etc. Figure 1 As shown, the method includes: S110. Obtain the server cluster to be inspected, and use batch operation and maintenance software to generate the inspection script corresponding to the server cluster to be inspected.

[0017] It should be noted that, in this embodiment, the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with the relevant laws, regulations and standards of the relevant countries and regions, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0018] The server cluster can consist of control node servers, business node servers, and database node servers. The control node servers are responsible for managing container orchestration, deployment, and scheduling, while the business node servers are the carriers on which the containers run, also known as container hosts. In this embodiment, a user-configured inspection cluster form can be obtained, and its content can be extracted to acquire each server cluster to be inspected. The inspection cluster form may include information such as the name and identifier of the server clusters to be inspected. Alternatively, the server clusters to be inspected can be acquired based on the user's selection of existing server clusters on the system page.

[0019] The batch operation and maintenance software can perform functions such as batch system configuration, batch program deployment, and batch command execution. It does not require client installation on the remote host; instead, it communicates directly with the remote host based on the Secure Shell protocol. In this embodiment, a pre-configured inspection process can be obtained from the user, and the batch operation and maintenance software can automatically generate inspection scripts corresponding to the server cluster to be inspected based on this process. The inspection scripts can use a data / configuration declarative language, rather than a markup language. The inspection process can consist of multiple inspection items and their corresponding inspection order.

[0020] Optionally, batch operation and maintenance software can be used to generate inspection scripts corresponding to the server cluster to be inspected, which may include: If the server cluster to be inspected is detected to exist, and each node server in the server cluster is accessible, then batch operation and maintenance software is used to generate the inspection script corresponding to the server cluster to be inspected.

[0021] In an optional example, an initial check is performed on the server cluster to be inspected before generating the inspection script. Specifically, based on the obtained name of the server cluster to be inspected, it is determined whether the cluster exists. If it exists, it is further determined whether each node server in the cluster is accessible. For example, a detection signal is sent to each node server, and it is determined whether there is a corresponding response signal. If it is determined that each node server is accessible, the corresponding inspection script is generated using batch operation and maintenance software.

[0022] The inspection script includes a node definition configuration file, which contains information such as the Internet Protocol (IP) address, group, and connection method of each node server in the server cluster to be inspected.

[0023] In this embodiment, by performing an initial check on the server cluster to be inspected in advance, the generation of inspection scripts for invalid server clusters can be avoided, thereby improving the efficiency of cluster inspection.

[0024] S120. Based on the inspection script, perform a basic status check on the container network components of the server cluster to be inspected, obtain a first inspection result, and when the first inspection result is that the inspection is passed, obtain the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server.

[0025] The basic status checks can include basic network reachability checks, service process checks, and configuration checks. In this embodiment, an inspection script can be run to first perform basic status checks on the container network components of the server cluster to be inspected, obtaining the corresponding first check results. Then, if the first check result is a failure, the exception information is recorded, and subsequent checks on the current server cluster to be inspected are skipped, proceeding to the next server cluster to be inspected. If the first check result is a success, the connectivity checks on the container network components of the current server cluster to be inspected continue. Specifically, first, it checks whether a container component exists on the business node server of the server cluster to be inspected. If it does, it checks whether the container component's configuration file contains container network segment and container network subnet segment configurations. If so, it extracts the container network subnet segment corresponding to the container component from the configuration file. Simultaneously, it reads the corresponding container network component subnet segment from the business node server. The container network component subnet segment is the subnet segment configured for the container network component.

[0026] In this embodiment, a container network component can be used to assign a unique IP address to each basic unit in the cluster, ensuring that these basic units can communicate directly with each other regardless of which physical node they are located on, thereby enabling cross-node network communication between containers. This embodiment does not specifically limit the type of container network component.

[0027] S130. Perform a connectivity check on the container network component based on the container network component subnet segment and the container network subnet segment, obtain a second check result, and generate an inspection log based on the first check result and the second check result.

[0028] Specifically, if the container network component subnet segment is the same as the container network subnet segment, it indicates that the containers are naturally connected to the container network, and the second check result can be determined as a pass. If the container network component subnet segment is different from the container network subnet segment, the second check result can be determined as a fail. Finally, the first and second check results can be output according to a preset log format to obtain the inspection log corresponding to the current server cluster under inspection.

[0029] Optionally, after determining that the container network component subnet segment is different from the container network subnet segment, an anomaly repair suggestion can be generated based on the container network component subnet segment. For example, if the container network component subnet segment is A, the anomaly repair suggestion could be "Container network subnet segment setting is incorrect, please change it to A". Alternatively, the current business node server can be directly controlled to change the container network subnet segment to the current container network component subnet segment.

[0030] Optionally, performing a connectivity check on the container network component based on the container network component subnet segment and obtaining a second check result may include: When it is determined that the container network component subnet segment is the same as the container network subnet segment, a test signal is sent through the business node server to the core domain name system resolution component of the control node server in the server cluster to be tested. If the business node server successfully receives the response signal sent by the core domain name system resolution component, then the second check result is obtained as a pass.

[0031] In this embodiment, when the container network component subnet segment is detected to be the same as the container network subnet segment, it is further possible to check whether the core domain name system (DNS) resolution components of the business node server and the control node server are connected. Specifically, first, it is determined whether the control node server has a core DNS resolution component. If so, a test signal is sent to the core DNS resolution component through the business node server. If a response signal sent by the core DNS resolution component is successfully received within a set time period, it indicates that the business node server and the core DNS resolution component are successfully connected, and the second check result can be set as check passed. If no response signal is received, the second check result is set as check failed.

[0032] Among them, the core domain name system resolution component is used to provide domain name resolution services for all components within the cluster. In addition to container network interconnection, business connectivity also includes domain name resolution capabilities.

[0033] In this embodiment, by setting a connectivity check that includes checking whether the business node server and the core domain name system resolution component are connected, the accuracy of the connectivity check can be improved.

[0034] Optionally, generating an inspection log based on the first inspection result and the second inspection result may include: When the second check result is that the check fails, the container network registry is read from the database node server in the server cluster to be checked; Based on the container network registry and the container network subnet segment, the anomaly range is obtained, and an inspection log is generated based on the anomaly range, the first inspection result, and the second inspection result.

[0035] The container network registry is used to record various related data of the container network, including container network identity information, network interface and connection information, subnet and routing rule information, service discovery and load balancing information, network policy and access control information, etc.

[0036] In this embodiment, when the second check result is a failure, the operation and maintenance script can read the IP address of the database node server from the node definition configuration file, and based on that IP address, read the container network registry from the database node server. Next, based on the current container network subnet segment, it can perform a matching search in the subnet and routing rule information of the container network registry to obtain the business node server or container component associated with that container network subnet segment. Then, based on the current business node server and container component, as well as the associated business node server and container component, the anomaly range is jointly determined. Finally, the anomaly range, the first check result, and the second check result can be output according to a preset log format to obtain the final inspection log.

[0037] In this embodiment, by determining the corresponding anomaly range based on the container network registry when the check fails, the efficiency of locating the anomaly location can be improved, and the efficiency of anomaly repair can be improved.

[0038] The technical solution of this invention involves acquiring a server cluster to be inspected and using batch operation and maintenance software to generate an inspection script corresponding to the server cluster. Based on the inspection script, a basic status check of the container network components of the server cluster to be inspected is performed to obtain a first check result. If the first check result is a pass, the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server are acquired. A connectivity check of the container network components is performed based on the container network component subnet segments to obtain a second check result. An inspection log is generated based on the first and second check results. By generating an inspection script and performing a connectivity check of the container network components based on the corresponding subnet segments after the server cluster to be inspected passes the basic status check, the final inspection result can be obtained. This improves the inspection efficiency and accuracy of the server cluster and reduces the probability of missed or false detections.

[0039] Example 2 Figure 2 This is a flowchart of a server cluster inspection method provided in Embodiment 2 of the present invention. This embodiment is a further refinement of the above technical solution, and the technical solution in this embodiment can be combined with one or more of the above implementation methods. Figure 2 As shown, the method includes: S210. Obtain the server cluster to be inspected, and use batch operation and maintenance software to generate the inspection script corresponding to the server cluster to be inspected.

[0040] S220. Based on the inspection script, obtain the address information corresponding to each node server in the server cluster to be inspected, and perform a service process check of the container network component of the server cluster to be inspected according to the address information, and obtain a third inspection result.

[0041] In this embodiment, the basic status check of the container network component may include service process check and configuration check; wherein, the service process check is to check whether the processes related to the container network component are running normally; and the configuration check is to check whether the configuration related to the container network component is correct.

[0042] Specifically, the inspection script reads the address information corresponding to each node server from the node definition configuration file, and based on this address information, accesses the control node server and the business node server to check whether the container network component processes of each node server are running normally, and obtains the corresponding third-party inspection results. The third-party inspection results can include whether the inspection passed or failed.

[0043] Optionally, performing a service process check on the container network components of the server cluster under inspection based on the address information to obtain a third check result may include: Based on the address information, obtain the process status of the first container network component and the core domain name system resolution component corresponding to the control node server in the server cluster to be inspected; If the process status of the first container network component and the status of the core domain name system resolution component are both detected to be normal, then the process status of the second container network component corresponding to the business node server is obtained. If the process status of the second container network component is detected to be normal, then the third check result is obtained as "check passed".

[0044] In this embodiment, the inspection script can access the control node server based on the IP address corresponding to the control node server. Next, it checks whether a container networking component process exists on the control node server. If it exists, it further checks whether the process's status is normal. If the process does not exist or its status is abnormal, the first container networking component process status is set to abnormal; if the process exists and its status is normal, the first container networking component process status is set to normal. Then, it checks whether a core domain name system (DNS) resolution component exists on the control node server. If it exists, it checks whether the component's status is normal. If the component exists and its status is normal, the core DNS resolution component status is set to normal; otherwise, if the component does not exist or its status is abnormal, the core DNS resolution component status is set to abnormal.

[0045] Furthermore, after completing the check of the control node server, if it is determined that the status of the first container network component process and the core domain name system resolution component are both normal, then the presence of the container network component process on the business node server is checked. If it is found to exist, the status of the process is further checked. If the process exists and is in a normal state, the status of the second container network component process is determined to be normal, and the third check result is then obtained as a pass.

[0046] In this embodiment, by setting the service process check of the container network component to include the process status check of the container network component on the control node server and the status check of the core domain name system resolution component, as well as the process status check of the container network component on the business node server, the accuracy of the service process check can be improved.

[0047] S230. If the third check result is a pass, then the configuration check of the container network component of the server cluster to be checked is performed according to the address information to obtain the fourth check result, and the first check result is obtained according to the third check result and the fourth check result.

[0048] In this embodiment, when the third check result is determined to be a pass, i.e., the service process check passes, the inspection script further performs a configuration check. Specifically, the inspection script accesses the control node server and the business node server based on the address information of each node server, and checks whether the version and mode of the container network components of the control node server and the business node server meet the preset configuration conditions, thereby obtaining the fourth check result. Finally, the third check result and the fourth check result can be combined to obtain the final first check result.

[0049] Optionally, performing a configuration check on the container network components of the server cluster under inspection based on the address information to obtain a fourth check result may include: Based on the address information, obtain the first container network component version corresponding to the control node server in the server cluster to be inspected, and the second container network component version corresponding to the business node server. If the version of the first container network component is detected to be the same as the version of the second container network component, then the first container network component mode corresponding to the control node server and the second container network component mode corresponding to the business node server are obtained. If the first container network component mode is detected to be the same as the second container network component mode, then the fourth check result is obtained as a pass.

[0050] In this embodiment, during configuration checks, the inspection script first obtains the container network component versions corresponding to the control node server and the business node server, and then compares whether they are the same. If they are the same, it further obtains the container network component modes corresponding to the control node server and the business node server, and compares whether they are the same. If they are still the same, the fourth check result is "check passed". If a version or mode difference is detected, the fourth check result is "check failed", and the IP address of the current business node server is recorded. The container network component modes include User Datagram Protocol (UDP) mode and Virtual Extended LAN (VLAN) mode.

[0051] In this embodiment, by setting the configuration check to include checks on the container network component version and container network component mode, the accuracy of the configuration check can be improved.

[0052] S240. When the first inspection result is that the inspection is passed, obtain the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server.

[0053] S250. Perform a connectivity check on the container network component based on the container network component subnet segment and the container network subnet segment, obtain a second check result, and generate an inspection log based on the first check result and the second check result.

[0054] The technical solution of this invention, based on an inspection script, obtains the address information corresponding to each node server in the server cluster to be inspected, and performs a service process check on the container network component of the server cluster to be inspected according to the address information to obtain a third check result; if the third check result is a pass, then performs a configuration check on the container network component of the server cluster to be inspected according to the address information to obtain a fourth check result, and obtains a first check result based on the third check result and the fourth check result; by setting the basic status check of the container network component to include service process check and configuration check, the accuracy of the basic status check can be improved.

[0055] In the context of multi-cluster operation and maintenance of financial private clouds, facing the problem of complex container network structure, this invention provides a container network inspection solution that can be used for both cluster building pre-inspection and daily inspection. It covers key configuration and connectivity checks of container networks, avoids network connectivity problems after daily equipment supply, and avoids affecting business launch. At the same time, it provides basic diagnostic information for container network service issues.

[0056] The technical solution of this invention is simple to deploy and easy to use. It can be integrated into the existing orchestration of batch operation and maintenance software for pre-inspection, or inherited into scheduled inspection tasks for daily inspection and location. It also supports repeated execution, which can reduce the workload of manual inspection. In addition, it can reduce security risks, reduce hidden cluster failures caused by server environment network problems, and reduce the risk of subsequent business container deployment.

[0057] Example 3 Figure 3 This is a schematic diagram of the structure of a server cluster inspection device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes: a script generation module 310, a network segment acquisition module 320, and a log generation module 330; wherein, The script generation module 310 is used to obtain the server cluster to be inspected and to generate the inspection script corresponding to the server cluster to be inspected using batch operation and maintenance software. The network segment acquisition module 320 is used to perform a basic status check on the container network components of the server cluster to be inspected based on the inspection script, obtain a first inspection result, and when the first inspection result is that the inspection is passed, obtain the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server. The log generation module 330 is used to perform a connectivity check on the container network component based on the container network component subnet segment and the container network subnet segment, obtain a second check result, and generate an inspection log based on the first check result and the second check result.

[0058] The technical solution of this invention involves acquiring a server cluster to be inspected and using batch operation and maintenance software to generate an inspection script corresponding to the server cluster. Based on the inspection script, a basic status check of the container network components of the server cluster to be inspected is performed to obtain a first check result. If the first check result is a pass, the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server are acquired. A connectivity check of the container network components is performed based on the container network component subnet segments to obtain a second check result. An inspection log is generated based on the first and second check results. By generating an inspection script and performing a connectivity check of the container network components based on the corresponding subnet segments after the server cluster to be inspected passes the basic status check, the final inspection result can be obtained. This improves the inspection efficiency and accuracy of the server cluster and reduces the probability of missed or false detections.

[0059] Optionally, the script generation module 310 is specifically used to generate an inspection script corresponding to the server cluster under inspection if the existence of the server cluster under inspection is detected and each node server in the server cluster under inspection is accessible, using batch operation and maintenance software.

[0060] Optionally, the network segment acquisition module 320 includes: The service process inspection unit is used to obtain the address information corresponding to each node server in the server cluster to be inspected based on the inspection script, and to perform service process inspection of the container network component of the server cluster to be inspected based on the address information, and obtain a third inspection result. A configuration check unit is configured to perform a configuration check on the container network components of the server cluster to be checked based on the address information if the third check result is a pass, obtain a fourth check result, and obtain the first check result based on the third check result and the fourth check result.

[0061] Optionally, the service process checking unit is specifically used to obtain the process status of the first container network component and the core domain name system resolution component corresponding to the control node server in the server cluster to be checked, based on the address information. If the process status of the first container network component and the status of the core domain name system resolution component are both detected to be normal, then the process status of the second container network component corresponding to the business node server is obtained. If the process status of the second container network component is detected to be normal, then the third check result is obtained as "check passed".

[0062] Optionally, a check unit is configured to obtain, based on the address information, the first container network component version corresponding to the control node server in the server cluster to be checked, and the second container network component version corresponding to the business node server. If the version of the first container network component is detected to be the same as the version of the second container network component, then the first container network component mode corresponding to the control node server and the second container network component mode corresponding to the business node server are obtained. If the first container network component mode is detected to be the same as the second container network component mode, then the fourth check result is obtained as a pass.

[0063] Optionally, the log generation module 330 is specifically used to send a test signal to the core domain name system resolution component of the control node server in the server cluster under test through the business node server when it is determined that the container network component subnet segment is the same as the container network subnet segment. If the business node server successfully receives the response signal sent by the core domain name system resolution component, then the second check result is obtained as a pass.

[0064] Optionally, the log generation module 330 is further configured to read the container network registry from the database node server in the server cluster to be inspected when the second check result is that the check fails. Based on the container network registry and the container network subnet segment, the anomaly range is obtained, and an inspection log is generated based on the anomaly range, the first inspection result, and the second inspection result.

[0065] The server cluster inspection device provided in this embodiment of the invention can execute the server cluster inspection method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method.

[0066] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0067] Example 4 Figure 4 A schematic diagram of an electronic device 40 that can be used to implement embodiments of the present invention is shown. The electronic device 40 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device 40 can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0068] like Figure 4 As shown, the electronic device 40 includes at least one processor 41 and a memory, such as a read-only memory (ROM) 42 or a random access memory (RAM) 43, communicatively connected to the at least one processor 41. The memory stores computer programs executable by the at least one processor. The processor 41 can perform various appropriate actions and processes based on the computer program stored in the read-only memory 42 or loaded from the storage unit 48 into the random access memory 43. The RAM 43 can also store various programs and data required for the operation of the electronic device 40. The processor 41, ROM 42, and RAM 43 are interconnected via a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0069] Multiple components in electronic device 40 are connected to I / O interface 45, including: input unit 46, such as keyboard, mouse, etc.; output unit 47, such as various types of monitors, speakers, etc.; storage unit 48, such as disk, optical disk, etc.; and communication unit 49, such as network card, modem, wireless transceiver, etc. Communication unit 49 allows electronic device 40 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0070] Processor 41 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 41 include, but are not limited to, central processing units, graphics processing units, various special-purpose artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any suitable processor, controller, microcontroller, etc. Processor 41 performs the various methods and processes described above, such as the inspection methods of a server cluster.

[0071] In some embodiments, the server cluster inspection method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 48. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 40 via ROM 42 and / or communication unit 49. When the computer program is loaded into RAM 43 and executed by processor 41, one or more steps of the server cluster inspection method described above may be performed. Alternatively, in other embodiments, processor 41 may be configured to perform the server cluster inspection method by any other suitable means (e.g., by means of firmware).

[0072] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays, application-specific integrated circuits (ASICs), application-specific standard products (ASICs), system-on-a-chip (SoCs), complex programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0073] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0074] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory, optical fibers, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0075] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device 40, which includes: a display device (e.g., a cathode ray tube or liquid crystal display) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device 40. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0076] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0077] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact via a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server.

[0078] This embodiment may also include a computer program product, which includes a computer program that, when executed by a processor, implements the server cluster inspection method provided in any embodiment of the present invention.

[0079] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0080] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for inspecting a server cluster, characterized in that, include: Obtain the server cluster to be inspected, and use batch operation and maintenance software to generate the inspection script corresponding to the server cluster to be inspected. Based on the inspection script, a basic status check of the container network components of the server cluster to be inspected is performed to obtain a first inspection result. When the first inspection result is that the inspection is passed, the container network component subnet segment corresponding to the business node server in the server cluster to be inspected, and the container network subnet segment corresponding to the container component in the business node server are obtained. A connectivity check of the container network component is performed between the container network component subnet segment and the container network subnet segment to obtain a second check result. An inspection log is then generated based on the first check result and the second check result.

2. The method according to claim 1, characterized in that, Using batch operation and maintenance software, an inspection script corresponding to the server cluster to be inspected is generated, including: If the server cluster to be inspected is detected to exist, and each node server in the server cluster is accessible, then batch operation and maintenance software is used to generate the inspection script corresponding to the server cluster to be inspected.

3. The method according to claim 1, characterized in that, Based on the inspection script, a basic status check of the container network components of the server cluster to be inspected is performed to obtain a first inspection result, including: Based on the inspection script, the address information corresponding to each node server in the server cluster to be inspected is obtained, and the service process of the container network component of the server cluster to be inspected is checked according to the address information to obtain the third inspection result. If the third check result is a pass, then the configuration check of the container network component of the server cluster to be checked is performed according to the address information to obtain the fourth check result, and the first check result is obtained according to the third check result and the fourth check result.

4. The method according to claim 3, characterized in that, Based on the address information, the service processes of the container network components of the server cluster under inspection are checked to obtain a third inspection result, including: Based on the address information, obtain the process status of the first container network component and the core domain name system resolution component corresponding to the control node server in the server cluster to be inspected; If the process status of the first container network component and the status of the core domain name system resolution component are both detected to be normal, then the process status of the second container network component corresponding to the business node server is obtained. If the process status of the second container network component is detected to be normal, then the third check result is obtained as "check passed".

5. The method according to claim 3, characterized in that, Based on the address information, the configuration of the container network components of the server cluster under inspection is checked to obtain a fourth inspection result, including: Based on the address information, obtain the first container network component version corresponding to the control node server in the server cluster to be inspected, and the second container network component version corresponding to the business node server. If the version of the first container network component is detected to be the same as the version of the second container network component, then the first container network component mode corresponding to the control node server and the second container network component mode corresponding to the business node server are obtained. If the first container network component mode is detected to be the same as the second container network component mode, then the fourth check result is obtained as a pass.

6. The method according to claim 1, characterized in that, Based on the connectivity check between the container network component subnet segment and the container network subnet segment, a second check result is obtained, including: When it is determined that the container network component subnet segment is the same as the container network subnet segment, a test signal is sent through the business node server to the core domain name system resolution component of the control node server in the server cluster to be tested. If the business node server successfully receives the response signal sent by the core domain name system resolution component, then the second check result is obtained as a pass.

7. The method according to claim 1, characterized in that, Based on the first inspection result and the second inspection result, an inspection log is generated, including: When the second check result is that the check fails, the container network registry is read from the database node server in the server cluster to be checked. Based on the container network registry and the container network subnet segment, the anomaly range is obtained, and an inspection log is generated based on the anomaly range, the first inspection result, and the second inspection result.

8. An electronic device, characterized in that, The electronic device includes: At least one processor, and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the inspection method of the server cluster according to any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the inspection method for the server cluster according to any one of claims 1-7.

10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the inspection method for the server cluster according to any one of claims 1-7.

Images