CN117560282A - Cluster equipment rapid deployment method and system and terminal equipment - Google Patents
Cluster equipment rapid deployment method and system and terminal equipment Download PDFInfo
- Publication number
- CN117560282A CN117560282A CN202311505422.XA CN202311505422A CN117560282A CN 117560282 A CN117560282 A CN 117560282A CN 202311505422 A CN202311505422 A CN 202311505422A CN 117560282 A CN117560282 A CN 117560282A
- Authority
- CN
- China
- Prior art keywords
- configuration
- cluster
- data
- abnormal
- abnormality
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 230000005856 abnormality Effects 0.000 claims abstract description 67
- 230000002159 abnormal effect Effects 0.000 claims abstract description 53
- 238000012545 processing Methods 0.000 claims abstract description 22
- 238000011084 recovery Methods 0.000 claims abstract description 6
- 230000003993 interaction Effects 0.000 claims description 20
- 238000004891 communication Methods 0.000 claims description 18
- 238000009434 installation Methods 0.000 claims description 13
- 230000008569 process Effects 0.000 claims description 9
- 238000007689 inspection Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 5
- 238000012360 testing method Methods 0.000 claims description 4
- 238000011900 installation process Methods 0.000 claims description 3
- 238000005259 measurement Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 3
- 238000003672 processing method Methods 0.000 description 3
- 238000011835 investigation Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0889—Techniques to speed-up the configuration process
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Abstract
The application discloses a cluster equipment rapid deployment method and system and terminal equipment. Responding to a one-key deployment instruction of a user by receiving cluster information of user input equipment and service data to be configured of each node, and sequentially executing corresponding configuration according to the input content type; when the configuration execution of each step has problems, the abnormal type is identified, the corresponding abnormal processing algorithm is called to clear the problems, and the configuration is continued to be executed after the recovery; after the configuration is completed, globally checking whether the configured service data is normal or not; if an abnormality is detected, identifying an abnormality type, and calling a corresponding abnormality processing algorithm to clear the problem; and finally, one-key deployment is completed. After the user inputs the cluster information and the service data, the system does not need manual operation, the intelligent cluster information is directly issued after being identified, the problem is automatically cleared after the intelligent cluster information is identified, the operation is simple, and the possible error of manual operation is avoided.
Description
Technical Field
The application relates to the technical field of distributed system networks, in particular to a cluster equipment rapid deployment method and system.
Background
In the process of on-site deployment of various devices, the processes of version installation, cluster deployment and service data configuration are complicated, and some subtle problems often occur, some are caused by improper operation, and some are hidden in the BUG, so that the devices cannot be normally used. At this time, the equipment is inspected by the technical staff of the equipment provider, so that many rare problems are difficult to solve on the spot or take a long time for the technical staff.
The complex or problematic deployment at the customer site can create a poor impression to the customer, so a rapid and correct deployment approach is critical.
At present, the clusters are deployed and configured with data one by one according to requirements, and then the cluster communication and the data correctness are checked one by one. Specifically, for cluster deployment, the prior art mainly comprises one installation version, one cluster is assembled one by one, one data is assembled one by one, and for a large cluster system, deployment is very complex and time-consuming. In addition, due to complex deployment, errors are easy to occur, and the time of the investigation process is prolonged.
The existing deployment method and system have the following defects:
1. the data can be deployed and configured respectively only one by one, the deployment is troublesome and the time is very long.
2. The configuration data needs to be manually judged, and then the configuration is carried out one by one, so that the deployment is troublesome and the time is very long.
3. When the deployment is not carried out according to the normal requirements, problems can occur, and the investigation can take a long time.
4. The whole cluster is inspected by configuring each node one by one, which is time-consuming.
Disclosure of Invention
The application provides a rapid deployment method and system for cluster equipment and terminal equipment, and aims to solve the problems of trouble deployment, time consumption and the like of the conventional cluster system.
In a first aspect, a method for rapidly deploying cluster devices includes:
step S1: receiving equipment cluster information input by a user; the equipment cluster information comprises the IP, roles and software versions for online at the time of each node in the cluster;
step S2: receiving business data which are input by a user and need to be configured by each node; the service data comprises authoritative domain name configuration and recursive domain name configuration of DNS equipment;
step S3: responding to a one-key deployment instruction of a user, and sequentially executing corresponding configuration according to content types by utilizing the content input by the user; when the configuration execution of each step has problems, identifying the abnormal type, calling a corresponding abnormal processing algorithm to clear the problems, and continuing to execute the configuration after the recovery;
step S4: after the configuration is completed, globally checking whether the configured service data is normal or not; if an abnormality is detected, identifying an abnormality type, and calling a corresponding abnormality processing algorithm to clear the problem;
step S5: and finally, if no abnormality exists, notifying that the deployment is successfully displayed on the human-computer interaction interface, and if the abnormality does not exist, displaying an abnormal result on the human-computer interaction interface.
Optionally, when receiving service data to be configured of each node input by a user in step S2, providing a service data filling template through a man-machine interaction interface, and providing an option of checking the correctness of the configuration data after the completion of the configuration; if the user chooses not to check the correctness of the configuration data, the following step S4 skips the checking of the correctness of the configuration data in the execution process.
Optionally, the executing the corresponding configuration sequentially according to the content type by using the content input by the user specifically includes:
s301: setting roles and installing versions of each node in the cluster according to the roles and software versions of each node input by a user;
s302: performing cluster communication configuration according to the IP and roles of each node input by a user;
s303: and distributing service configuration to service data input by the user.
Optionally, the roles are divided into a network management node, a service node, an HA node and a standby management node.
Optionally, the exception types of the version installation include: the installation package is abnormal in inspection, the installation process is abnormal, and the service is started abnormally; and judging which abnormality is through keyword matching in the log, and selecting a corresponding abnormality processing algorithm.
Optionally, the exception type of the cluster connectivity configuration includes: abnormal nodes, abnormal cluster communication and abnormal data synchronization; judging whether the node is abnormal or not through keyword matching in the log; judging whether the cluster is abnormal in communication and data synchronization and the type of the abnormality by matching keywords of a communication test result and matching keywords of a database query; then a corresponding exception handling algorithm is selected.
Optionally, the exception type of the service configuration includes: issuing data loss and data inspection abnormality; judging whether the transmitted data is lost or not by inquiring keyword matching through a database; for data inspection abnormality, key word matching is returned through an interface to judge whether the data inspection abnormality exists; and selecting a corresponding exception handling algorithm.
Optionally, in step S4, the global checking is performed to determine whether the configured service data is normal, where the types of anomalies include: configuration data errors and abnormal business logic; for configuration data errors, key word matching is returned through an interface to judge whether the configuration data errors are abnormal; for abnormal business logic, judging whether the business logic is abnormal or not through keyword matching of a domain name dialing measurement result; and selecting a corresponding exception handling algorithm.
In a second aspect, a cluster device rapid deployment system includes:
the receiving configuration module is used for receiving equipment cluster information input by a user and service data to be configured by each node; the equipment cluster information comprises the IP, roles and software versions for online at the time of each node in the cluster; the service data comprises authoritative domain name configuration and recursive domain name configuration of DNS equipment;
the configuration issuing module is used for responding to a one-key deployment instruction of a user, and sequentially executing corresponding configuration according to the content type by utilizing the content input by the user;
the checking data module is used for globally checking whether the configured service data is normal or not after the configuration is completed;
the exception handling module is used for identifying the exception type and calling a corresponding exception handling algorithm to clear the problem when the configuration execution of each step has the problem in the execution process of the configuration issuing module and the checking data module;
and the deployment result feedback module is used for informing that the deployment is successfully displayed on the man-machine interaction interface if no abnormality exists, and displaying the abnormal result on the man-machine interaction interface if no abnormality exists.
The third aspect is that the terminal device includes a memory, a processor, and a man-machine interaction interface, where the memory stores a computer program, and the method is characterized in that the processor implements the steps of the cluster device rapid deployment method when executing the computer program.
Compared with the prior art, the method and the device have the advantages that cluster information (IP, roles and software versions for online at this time) of the user input equipment and service data (authority domain name configuration and recursive domain name configuration of DNS equipment) required to be configured by each node are received, the service data files in a set format are supported to be directly imported, and corresponding configuration is sequentially executed according to content types by utilizing the content input by a user in response to a one-key deployment instruction of the user; fully considering the occurrence characteristics of various abnormal conditions and the overall deployment logic, identifying the abnormal type when the configuration execution of each step has problems, calling a corresponding abnormal processing algorithm to clear the problems, and continuing to execute the configuration after the recovery; after the configuration is completed, globally checking whether the configured service data is normal or not; if an abnormality is detected, identifying an abnormality type, and calling a corresponding abnormality processing algorithm to clear the problem; and finally, if no abnormality exists, notifying that the deployment is successfully displayed on the human-computer interaction interface, and if the abnormality does not exist, displaying an abnormal result on the human-computer interaction interface.
The application has at least the following beneficial effects:
1. the time of node-by-node deployment is saved, and the system can directly deploy and start the whole cluster by one key.
2. The manual judgment of the service data logic is omitted, the service data file is directly imported, and the service data is generated by one key.
3. The step and logic of learning to correctly configure the cluster and the service data are omitted, and the system can directly generate the cluster system and the service data according to the correct step.
4. The time waste for checking the problem is saved, the system can directly process the abnormal situation, and the reconfiguration is changed into the normal situation.
Drawings
Fig. 1 is a flow chart of a method for rapidly deploying cluster devices according to an embodiment of the present application;
fig. 2 is a logic schematic diagram of a cluster device rapid deployment system according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a system operation provided in one embodiment of the present application;
FIG. 4 is a schematic diagram of various abnormal condition checking and corresponding processing algorithms according to one embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
In the description of the present application: unless otherwise indicated, the terms "comprise," "include," "have" and the like are also intended to be "non-limiting" (certain units, components, materials, steps, etc.).
The embodiment provides a set of guide type deployment method for cluster deployment, which is convenient for a user to rapidly deploy a cluster system, can enable equipment suppliers to finish cluster deployment by one key to achieve the online standard, and improves deployment timeliness.
In one embodiment, as shown in fig. 1, a cluster device rapid deployment method includes:
step S1: receiving equipment cluster information input by a user; the device cluster information includes the IP, roles, and software versions (actually used) of each node in the cluster for this time on-line use.
The roles of each node are divided into a network management node, a service node, an HA node (hot standby, which can replace the network management node and also can replace the service node) and a standby management node (cold standby, which can replace the network management node).
Step S2: receiving business data which are input by a user and need to be configured by each node; the service data comprises authoritative domain name configuration and recursive domain name configuration of DNS equipment;
when receiving the business data which is input by the user and needs to be configured by each node, the step can provide a business data filling template through a man-machine interaction interface and can provide an option of checking the correctness of the configuration data after the configuration is completed; if the user chooses not to check the correctness of the configuration data, the following step S4 is performed while skipping checking the correctness of the configuration data (but only checking whether the business logic is normal).
Step S3: responding to a one-key deployment instruction of a user, and sequentially executing corresponding configuration according to content types by utilizing the content input by the user; when the configuration execution of each step has problems, the abnormal type is identified, the corresponding abnormal processing algorithm is called to clear the problems, and the configuration is continued to be executed after the recovery.
The method comprises the steps of sequentially executing corresponding configuration according to content types by utilizing content input by a user, wherein the specific steps include:
s301: setting roles and installing versions of each node in the cluster according to the roles and software versions of each node input by a user;
s302: performing cluster communication configuration according to the IP and roles of each node input by a user;
s303: and distributing service configuration to service data input by the user.
Step S4: after the configuration is completed, globally checking whether the configured service data is normal or not; if an abnormality is detected, identifying an abnormality type, and calling a corresponding abnormality processing algorithm to clear the problem;
because the operation of this step is relatively long, and besides the problem of service logic, the same problem will not occur at this time as long as the exception identification and processing configured in each step of the previous step S3 is performed, so the user may choose not to check the correctness of the configuration data in step S2, thereby further saving time.
Step S5: and finally, if no abnormality exists, notifying that the deployment is successfully displayed on the human-computer interaction interface, and if the abnormality does not exist, displaying an abnormal result on the human-computer interaction interface.
Accordingly, in one embodiment, as shown in fig. 2, a cluster device rapid deployment system includes:
the receiving configuration module is used for receiving equipment cluster information input by a user and service data to be configured by each node; the equipment cluster information comprises the IP, roles and software versions for online at the time of each node in the cluster; the service data comprises authoritative domain name configuration and recursive domain name configuration of DNS equipment;
the configuration issuing module is used for responding to a one-key deployment instruction of a user, and sequentially executing corresponding configuration according to the content type by utilizing the content input by the user; the configuration issuing module specifically comprises an installation version module, a cluster communication configuration module and a service data issuing module;
the checking data module is used for globally checking whether the configured service data is normal or not after the configuration is completed;
the exception handling module is used for identifying the exception type and calling a corresponding exception handling algorithm to clear the problem when the configuration execution of each step has the problem in the execution process of the configuration issuing module and the checking data module; the exception handling module specifically comprises an installation version exception handling module, a cluster configuration exception handling module, a business issuing exception handling module and a checking data exception handling module, and corresponding exception handling flows are automatically triggered when problems occur in each configuration issuing module;
and the deployment result feedback module is used for informing that the deployment is successfully displayed on the man-machine interaction interface if no abnormality exists, and displaying the abnormal result on the man-machine interaction interface if no abnormality exists.
After receiving the input configuration and executing deployment, a normal one-key deployment flow is started.
The exception handling modules are, as shown in fig. 2 and 4, specifically divided into:
the installation version exception handling module is used for handling the exception condition of the installation version module and classifying the installation exception: whether the installation package is abnormal, the installation process is abnormal or the service is started abnormally. And judging which abnormality is by the key words, and selecting a corresponding abnormality processing algorithm.
The cluster configuration exception handling module is used for handling the exception condition of the cluster configuration module and classifying the cluster configuration exception: whether the node is abnormal, the cluster communication is abnormal or the data synchronization is abnormal. And judging which abnormality is by the key words, and selecting a corresponding abnormality processing algorithm.
The issuing service exception handling module is used for handling the exception condition of the issuing service configuration module and classifying the issuing service configuration exception: and issuing data loss and checking abnormality of the data. And judging which abnormality is by the key words, and selecting a corresponding abnormality processing algorithm.
And the checking data abnormality module is used for classifying checking data abnormality, namely, configuration data error and business logic abnormality, corresponding to the business data which is configured in a global checking mode. And judging which abnormality is by the key words, and selecting a corresponding abnormality processing algorithm.
The abnormal processing modules can automatically start an intelligent algorithm to match abnormal information after detecting the abnormal information. And after matching, determining the type of the abnormality and the abnormality processing method. After the treatment is completed, the next step is carried out according to the flow.
And the unprocessed error report log and the interface return error information which are matched are transmitted back to the foreground and printed out to the user for manual maintenance.
The workflow of intelligent one-key deployment adopting the system is shown in fig. 3, and comprises the following steps:
step one: starting an intelligent one-key deployment cluster system (the system is installed and started before deployment is carried out to a client);
step two: first fill in cluster information: each node role (is one of a network management node, a service node, an HA node and a standby management node) and version;
step three: and then filling in business data: the service data that each node needs to be configured (the service data can be input through the provided template, and then the whole template is added for importing), and then whether the correctness of the configuration data needs to be checked is selected; the service data is the service actually deployed by the client, such as authority domain name configuration and recursion domain name configuration of DNS equipment, and the service data needs to be configured in advance;
step four: starting a one-key deployment button;
step five: the system starts intelligent identification of the content type and carries out corresponding configuration according to the content type; the content types comprise an installation version, a role configuration, a cluster connectivity configuration, an authoritative data configuration and a recursive data configuration;
the system firstly identifies the version numbers and roles of all nodes in the cluster, then starts to set the roles and install the versions of the nodes according to preset standard steps, performs cluster connection configuration according to the standard steps after the node is installed, and performs distribution configuration on each node according to the identified service configuration content according to the standard steps after the cluster connection is successful.
Step six: after the configuration is completed, starting to check data; checking whether the configured service data is normal or not;
after the cluster communication and data configuration are completed, a checking data module is started, and whether all nodes in the cluster can normally communicate or not is checked through test operation, and whether service data can be normally issued to each node or not is checked; after the cluster is communicated, checking whether the service data of each node is normally issued to the database, and performing full data dial testing on all the nodes to verify that no abnormality exists.
Step seven: if the abnormal type occurs, the abnormal type is intelligently identified, and corresponding processing is carried out according to the abnormal type; if the abnormality occurs, the type of the abnormality is judged intelligently, then the type of the abnormality is processed according to an abnormality processing algorithm, and the data is reprocessed for normal issuing after recovery. If the abnormality cannot be solved, an abnormality log and an abnormality description are popped up; the types of anomalies are classified as: installation version abnormality, cluster configuration abnormality, issuing data abnormality and checking data abnormality;
step eight: and finishing one-key deployment.
After the exception handling is completed and the recheck data is completed, if no exception exists, the deployment is notified to be successfully displayed on the page, and if the exception does not exist, the exception result is displayed on the page.
The system is a system for deploying and starting the cluster by pressing one key of input information, when the system is used, after the cluster information and service data are input, manual operation is not needed, the cluster information is intelligently identified and then is directly issued, problems can be automatically cleared after the problems are intelligently identified, the operation is simple, and the problem that the manual operation is easy to make mistakes is avoided.
Fig. 4 illustrates the principle of anomaly detection and handling, including anomaly type, matching algorithm, and processing method (mechanism). Different exception types can find different processing methods through different matching algorithms to solve the current exception. The exception type, matching algorithm, and processing mechanism are not limited to the ones illustrated in fig. 4.
In one embodiment, a computer device, which may be a terminal, is also provided. The computer device comprises a processor, a memory, a communication interface and a man-machine interaction interface (a combination of a display screen and a keyboard can be adopted, a touch screen can also be adopted, etc.) which are connected through a system bus. The processor of the computer device is used for providing computing and control capabilities, and the communication interface is used for conducting wired or wireless communication with an external terminal, wherein the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer equipment loads and runs the computer program to realize the cluster equipment rapid deployment method.
Those skilled in the art will appreciate that a particular computer device may include more or fewer components than the architecture exemplified above, or may combine certain components, or have a different arrangement of components.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
Claims (10)
1. The cluster equipment rapid deployment method is characterized by comprising the following steps of:
step S1: receiving equipment cluster information input by a user; the equipment cluster information comprises the IP, roles and software versions for online at the time of each node in the cluster;
step S2: receiving business data which are input by a user and need to be configured by each node; the service data comprises authoritative domain name configuration and recursive domain name configuration of DNS equipment;
step S3: responding to a one-key deployment instruction of a user, and sequentially executing corresponding configuration according to content types by utilizing the content input by the user; when the configuration execution of each step has problems, identifying the abnormal type, calling a corresponding abnormal processing algorithm to clear the problems, and continuing to execute the configuration after the recovery;
step S4: after the configuration is completed, globally checking whether the configured service data is normal or not; if an abnormality is detected, identifying an abnormality type, and calling a corresponding abnormality processing algorithm to clear the problem;
step S5: and finally, if no abnormality exists, notifying that the deployment is successfully displayed on the human-computer interaction interface, and if the abnormality does not exist, displaying an abnormal result on the human-computer interaction interface.
2. The rapid deployment method of cluster equipment according to claim 1, wherein when receiving service data to be configured of each node inputted by a user in step S2, providing a service data filling template through a man-machine interaction interface, and providing an option of checking correctness of configuration data after completion of configuration; if the user chooses not to check the correctness of the configuration data, the following step S4 skips the checking of the correctness of the configuration data in the execution process.
3. The rapid deployment method of cluster equipment according to claim 1, wherein in step S3, the corresponding configuration is sequentially performed according to content types by using content input by a user, and specifically includes:
s301: setting roles and installing versions of each node in the cluster according to the roles and software versions of each node input by a user;
s302: performing cluster communication configuration according to the IP and roles of each node input by a user;
s303: and distributing service configuration to service data input by the user.
4. The rapid deployment method of cluster equipment according to claim 1, wherein the roles are divided into a network management node, a service node, an HA node and a standby management node.
5. The cluster-device rapid deployment method of claim 3, wherein the version-installed exception type comprises: the installation package is abnormal in inspection, the installation process is abnormal, and the service is started abnormally; and judging which abnormality is through keyword matching in the log, and selecting a corresponding abnormality processing algorithm.
6. The method for rapid deployment of cluster equipment according to claim 3, wherein the exception type of the cluster connectivity configuration comprises: abnormal nodes, abnormal cluster communication and abnormal data synchronization; judging whether the node is abnormal or not through keyword matching in the log; judging whether the cluster is abnormal in communication and data synchronization and the type of the abnormality by matching keywords of a communication test result and matching keywords of a database query; then a corresponding exception handling algorithm is selected.
7. The method for rapidly deploying cluster equipment according to claim 3, wherein the exception type of the service configuration comprises: issuing data loss and data inspection abnormality; judging whether the transmitted data is lost or not by inquiring keyword matching through a database; for data inspection abnormality, key word matching is returned through an interface to judge whether the data inspection abnormality exists; and selecting a corresponding exception handling algorithm.
8. The rapid deployment method of cluster equipment according to claim 1, wherein in step S4, the global checking whether the configured service data is normal or not, and the related exception types include: configuration data errors and abnormal business logic; for configuration data errors, key word matching is returned through an interface to judge whether the configuration data errors are abnormal; for abnormal business logic, judging whether the business logic is abnormal or not through keyword matching of a domain name dialing measurement result; and selecting a corresponding exception handling algorithm.
9. A cluster-device rapid deployment system, comprising:
the receiving configuration module is used for receiving equipment cluster information input by a user and service data to be configured by each node; the equipment cluster information comprises the IP, roles and software versions for online at the time of each node in the cluster; the service data comprises authoritative domain name configuration and recursive domain name configuration of DNS equipment;
the configuration issuing module is used for responding to a one-key deployment instruction of a user, and sequentially executing corresponding configuration according to the content type by utilizing the content input by the user;
the checking data module is used for globally checking whether the configured service data is normal or not after the configuration is completed;
the exception handling module is used for identifying the exception type and calling a corresponding exception handling algorithm to clear the problem when the configuration execution of each step has the problem in the execution process of the configuration issuing module and the checking data module;
and the deployment result feedback module is used for informing that the deployment is successfully displayed on the man-machine interaction interface if no abnormality exists, and displaying the abnormal result on the man-machine interaction interface if no abnormality exists.
10. A terminal device comprising a memory, a processor and a human-computer interaction interface, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the cluster device rapid deployment method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311505422.XA CN117560282A (en) | 2023-11-13 | 2023-11-13 | Cluster equipment rapid deployment method and system and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311505422.XA CN117560282A (en) | 2023-11-13 | 2023-11-13 | Cluster equipment rapid deployment method and system and terminal equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117560282A true CN117560282A (en) | 2024-02-13 |
Family
ID=89819703
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311505422.XA Pending CN117560282A (en) | 2023-11-13 | 2023-11-13 | Cluster equipment rapid deployment method and system and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117560282A (en) |
-
2023
- 2023-11-13 CN CN202311505422.XA patent/CN117560282A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108108297B (en) | Method and device for automatic testing | |
| US8793660B2 (en) | Automated testing of programming code for a web service | |
| CN101135989B (en) | Automatization test method and device for Web applied system | |
| CN113206763A (en) | Simulation test system and method suitable for Internet of things management platform | |
| CN105487859A (en) | Template based WEB deployment method for big data components | |
| JPWO2006117833A1 (en) | Monitoring simulation apparatus, method and program thereof | |
| CN114064208A (en) | Method and device for detecting application service state, electronic equipment and storage medium | |
| CN113645162B (en) | Hardware testing method, system, equipment and medium of switch | |
| CN112540924A (en) | Interface automation test method, device, equipment and storage medium | |
| CN112529223A (en) | Equipment fault repair method and device, server and storage medium | |
| CN110119325A (en) | Server failure processing method, device, equipment and computer readable storage medium | |
| CN110674029A (en) | Method and device for automatically generating test data, electronic equipment and storage medium | |
| CN112612706A (en) | Automated testing method, computer device and storage medium | |
| CN117560282A (en) | Cluster equipment rapid deployment method and system and terminal equipment | |
| CN103684814A (en) | Method and device for comparing data of communication system | |
| US7373623B2 (en) | Method and apparatus for locating circuit deviations | |
| CN113127036B (en) | Software development system, method, apparatus and medium for continuous integration of code | |
| CN115794530A (en) | Hardware connection testing method, device, equipment and readable storage medium | |
| CN115629919A (en) | Method and device for fast switching fault system | |
| CN111008113A (en) | SAS-Expander test method and tool | |
| CN114978923A (en) | Fault drilling method, device and system | |
| CN113703782A (en) | Method and device for automatically deploying copy set, electronic equipment and storage medium | |
| CN115623195A (en) | Television fault diagnosis method, device, equipment and storage medium | |
| CN112667512A (en) | Data drive test method, device, equipment and computer readable storage medium | |
| CN114785673B (en) | Method and device for acquiring abnormal information during active-standby switching |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |