Multi-mode cross-domain cluster deployment method and device and computer equipment

Abstract

The invention relates to a multi-mode cross-domain cluster deployment method and device and computer equipment. The method comprises the following steps: performing data verification on to-be-deployed configuration data according to to-be-deployed environment data to obtain a data verification result; generating a to-be-implemented scheme and a corresponding difference configuration file based on the to-be-deployed mode and the to-be-deployed configuration data under the condition that the data verification result is that the to-be-deployed environment meets the deployment requirement; transmitting the to-be-implemented scheme and the difference configuration file corresponding to the to-be-implemented scheme to each cluster host, and receiving a deployment feedback result of each cluster host; and when the deployment feedback result is successful deployment, ending the deployment task and updating the process information. By adopting the method, the feasibility and accuracy of cluster deployment can be improved, and the possibility of secondary deployment is reduced, so that the deployment efficiency and the system stability are improved, multi-mode and cross-domain disaster recovery deployment is realized, and flexible expansion and multi-platform compatibility are supported.

Description

Technical Field

[0001] The present application relates to the technical field of cluster deployment, and in particular to a multi-mode cross-domain cluster deployment method, apparatus and computer equipment. Background Art

[0002] With the growing demand for distributed architecture and large-scale data processing, message queue systems have gradually become one of the core components of enterprise applications. As a high-performance, high-reliability distributed message middleware, RocketMQ is widely used in various business scenarios, such as big data stream processing, event-driven architecture, microservice communication, etc. However, in the actual application process, enterprises face many challenges in deploying and operating RocketMQ. In particular, due to the different business structures and maintenance habits of different product lines, the system deployment and operation standards are not unified, which increases the complexity of management. In addition, due to the differences in requirements of different business scenarios, the traditional single deployment method can no longer meet the flexible and customized needs.

[0003] The related technologies mainly include fault-tolerant mechanisms based on heartbeat monitoring, batch deployment solutions, and automated deployment through scripts and deployment packages. Among them, RocketMQ's standard distributed deployment solution relies on the heartbeat mechanism to detect the health of the Broker and implements system fault detection by modifying the data table.

[0004] However, in related technologies, the fault-tolerance mechanism based on heartbeat monitoring cannot fully realize the automatic switching and self-healing effects of the system, especially in low-fault-tolerance business scenarios, which easily leads to insufficient system reliability. In addition, when facing large-scale, cross-platform, and multi-node deployment requirements, there is a lack of sufficient automation support, resulting in high operation and maintenance costs, long deployment cycles, and difficulty in adapting to the differentiated needs of different business lines. Summary of the invention

[0005] Based on this, it is necessary to provide a multi-mode cross-domain cluster deployment method, device, computer equipment, computer-readable storage medium and computer program product that can flexibly adapt to different needs, improve maintenance efficiency and reduce maintenance difficulty in response to the above technical problems.

[0006] In a first aspect, the present application provides a multi-mode cross-domain cluster deployment method, which is applied to a server. The method comprises:

[0007] Perform data verification on the configuration data to be deployed according to the environment data to be deployed, and obtain the data verification result;

[0008] If the data verification result shows that the environment to be deployed meets the deployment requirements, the implementation plan and its corresponding differential configuration files are generated based on the mode to be deployed and the configuration data to be deployed;

[0009] Transmit the implementation plan and its corresponding differential configuration files to each cluster host, and receive the deployment feedback results of each cluster host;

[0010] If the deployment feedback result is successful deployment, end the deployment task and update the process information.

[0011] In one of the embodiments, after performing data verification on the configuration data to be deployed according to the environment data to be deployed and obtaining the data verification result, the method further includes:

[0012] If the data verification result shows that the environment to be deployed does not meet the deployment requirements, a configuration error prompt message is generated;

[0013] Transmitting error configuration prompt information and error data items to the client terminal;

[0014] receiving the revised configuration data;

[0015] The modified configuration data is verified according to the environment data to be deployed to obtain a secondary verification result.

[0016] In one embodiment, when the data verification result shows that the environment to be deployed meets the deployment requirements, the implementation plan and its corresponding differential configuration file are generated based on the mode to be deployed and the configuration data to be deployed, including:

[0017] If the data verification result shows that the environment to be deployed meets the deployment requirements, a configuration file to be deployed corresponding to the mode to be deployed is generated based on the mode to be deployed and the configuration data to be deployed;

[0018] Allocate and schedule cluster nodes according to the mode to be deployed, and obtain allocated nodes;

[0019] Divide the cluster into regions according to the mode to be deployed, and obtain the divided clusters;

[0020] Based on the configuration file to be deployed corresponding to the mode to be deployed, the allocated nodes and the divided clusters, the implementation plan and its corresponding difference configuration file are generated.

[0021] In a second aspect, the present application provides a multi-mode cross-domain cluster deployment method, which is applied to a cluster. The method includes:

[0022] Configure and deploy the cluster hosts to be deployed according to the implementation plan and its corresponding differential configuration files to obtain the deployed cluster;

[0023] After completing the configuration of the cluster host, monitor the status of the deployed cluster and obtain status detection data;

[0024] Disaster recovery processing is performed according to the status detection data, the preset status threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster.

[0025] In one embodiment, disaster recovery processing is performed according to the state detection data, the preset state threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster, including:

[0026] Compare and analyze the cluster detection data with the preset cluster threshold to obtain the cluster analysis result;

[0027] If the cluster analysis result shows that the cluster detection data is greater than the preset cluster threshold, the disaster recovery domain cluster is promoted to a production domain cluster and status detection data is obtained;

[0028] When the cluster analysis result shows that the cluster detection data is less than or equal to the preset cluster threshold, the in-group detection data is compared and analyzed with the preset in-group threshold to obtain the host analysis result;

[0029] If the host analysis result shows that the detection data within the group is greater than the preset group threshold, the slave node will be promoted to the master node and the faulty master node will be removed;

[0030] When the host analysis result is that the in-group detection data is less than or equal to the preset in-group threshold, the next state detection data is obtained.

[0031] In a third aspect, the present application provides a multi-mode cross-domain cluster deployment method, which is applied to a client terminal. The method includes:

[0032] Generate configuration data to be deployed based on user demand data;

[0033] Transmit the configuration data to be deployed to the server and receive the current feedback results;

[0034] When the current feedback result is that the environment to be deployed does not meet the deployment requirements, the configuration data to be deployed is corrected according to the error configuration prompt information and the error data items to obtain the corrected configuration data;

[0035] The modified configuration data is transmitted to the server, and the next feedback result is received.

[0036] In a fourth aspect, the present application also provides a multi-mode cross-domain cluster deployment device, which is applied to a server. The device includes:

[0037] A data verification module is used to verify the configuration data to be deployed according to the environment data to be deployed, and obtain the data verification result;

[0038] A solution generation module is used to generate a to-be-deployed implementation plan and its corresponding differential configuration file based on the to-be-deployed mode and the to-be-deployed configuration data when the data verification result shows that the to-be-deployed environment meets the deployment requirements;

[0039] The first communication module is used to transmit the implementation plan and its corresponding differential configuration files to each cluster host, and receive the deployment feedback results of each cluster host;

[0040] The information update module is used to end the deployment task and update the process information when the deployment feedback result is a successful deployment.

[0041] In a fifth aspect, the present application also provides a multi-mode cross-domain cluster deployment device, which is applied to a server. The device includes:

[0042] The configuration and deployment module is used to configure and deploy the cluster hosts to be deployed according to the implementation plan and its corresponding differential configuration files to obtain the deployed cluster;

[0043] The status detection module is used to monitor the status of the deployed cluster and obtain status detection data after the configuration of the cluster host is completed;

[0044] The disaster recovery processing module is used to perform disaster recovery processing according to the status detection data, the preset status threshold and the preset disaster recovery plan to obtain the post-disaster recovery cluster.

[0045] In a sixth aspect, the present application also provides a multi-mode cross-domain cluster deployment device, which is applied to a server. The device includes:

[0046] A data processing module, used to generate configuration data to be deployed based on user demand data;

[0047] The second communication module is used to transmit the configuration data to be deployed to the server and receive the current feedback result;

[0048] The data processing module is further used to correct the configuration data to be deployed according to the error configuration prompt information and the error data item to obtain the corrected configuration data when the current feedback result is that the environment to be deployed does not meet the deployment requirements;

[0049] The second communication module is also used to transmit the modified configuration data to the server and receive the next feedback result.

[0050] In a seventh aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0051] Perform data verification on the configuration data to be deployed according to the environment data to be deployed, and obtain the data verification result;

[0052] If the data verification result shows that the environment to be deployed meets the deployment requirements, the implementation plan and its corresponding differential configuration files are generated based on the mode to be deployed and the configuration data to be deployed;

[0053] Transmit the implementation plan and its corresponding differential configuration files to each cluster host, and receive the deployment feedback results of each cluster host;

[0054] If the deployment feedback result is a successful deployment, end the deployment task and update the process information; or

[0055] Configure and deploy the cluster hosts to be deployed according to the implementation plan and its corresponding differential configuration files to obtain the deployed cluster;

[0056] After completing the configuration of the cluster host, monitor the status of the deployed cluster and obtain status detection data;

[0057] Perform disaster recovery processing according to the status detection data, the preset status threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster; or

[0058] Generate configuration data to be deployed based on user demand data;

[0059] Transmit the configuration data to be deployed to the server and receive the current feedback results;

[0060] When the current feedback result is that the environment to be deployed does not meet the deployment requirements, the configuration data to be deployed is corrected according to the error configuration prompt information and the error data items to obtain the corrected configuration data;

[0061] The modified configuration data is transmitted to the server, and the next feedback result is received.

[0062] In an eighth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0063] Perform data verification on the configuration data to be deployed according to the environment data to be deployed, and obtain the data verification result;

[0064] If the data verification result shows that the environment to be deployed meets the deployment requirements, the implementation plan and its corresponding differential configuration files are generated based on the mode to be deployed and the configuration data to be deployed;

[0065] Transmit the implementation plan and its corresponding differential configuration files to each cluster host, and receive the deployment feedback results of each cluster host;

[0066] If the deployment feedback result is a successful deployment, end the deployment task and update the process information; or

[0067] Configure and deploy the cluster hosts to be deployed according to the implementation plan and its corresponding differential configuration files to obtain the deployed cluster;

[0068] After completing the configuration of the cluster host, monitor the status of the deployed cluster and obtain status detection data;

[0069] Perform disaster recovery processing according to the status detection data, the preset status threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster; or

[0070] Generate configuration data to be deployed based on user demand data;

[0071] Transmit the configuration data to be deployed to the server and receive the current feedback results;

[0072] When the current feedback result is that the environment to be deployed does not meet the deployment requirements, the configuration data to be deployed is corrected according to the error configuration prompt information and the error data items to obtain the corrected configuration data;

[0073] The modified configuration data is transmitted to the server, and the next feedback result is received.

[0074] In a ninth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0075] Perform data verification on the configuration data to be deployed according to the environment data to be deployed, and obtain the data verification result;

[0076] If the data verification result shows that the environment to be deployed meets the deployment requirements, the implementation plan and its corresponding differential configuration files are generated based on the mode to be deployed and the configuration data to be deployed;

[0077] Transmit the implementation plan and its corresponding differential configuration files to each cluster host, and receive the deployment feedback results of each cluster host;

[0078] If the deployment feedback result is a successful deployment, end the deployment task and update the process information; or

[0079] Configure and deploy the cluster hosts to be deployed according to the implementation plan and its corresponding differential configuration files to obtain the deployed cluster;

[0080] After completing the configuration of the cluster host, monitor the status of the deployed cluster and obtain status detection data;

[0081] Perform disaster recovery processing according to the status detection data, the preset status threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster; or

[0082] Generate configuration data to be deployed based on user demand data;

[0083] Transmit the configuration data to be deployed to the server and receive the current feedback results;

[0084] When the current feedback result is that the environment to be deployed does not meet the deployment requirements, the configuration data to be deployed is corrected according to the error configuration prompt information and the error data items to obtain the corrected configuration data;

[0085] The modified configuration data is transmitted to the server, and the next feedback result is received.

[0086] The above-mentioned multi-mode cross-domain cluster deployment method, apparatus, computer equipment, storage medium and computer program product, after obtaining the configuration data to be deployed transmitted by the client terminal and the environment data to be deployed transmitted by the cluster, compares the configuration data to be deployed and the environment data to be deployed to determine whether deployment can be performed, and when it is determined that deployment can be performed, determines the implementation plan for deploying the cluster and the differential configuration data corresponding to the cluster based on the environment data to be deployed and the mode to be deployed, and at the same time transmits the implementation plan and the differential configuration file to the cluster, and then waits for the configuration result transmitted after the cluster configuration, and then determines whether secondary deployment is required, which improves the feasibility and accuracy of cluster deployment, reduces the possibility of secondary deployment, thereby improving deployment efficiency and system stability, and realizes multi-mode, cross-domain disaster recovery deployment, supports flexible expansion and multi-platform compatibility, simplifies operation procedures, greatly improves deployment efficiency, reduces manual maintenance costs, and ensures safe and stable business operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] Figure 1 A schematic diagram of a process of applying a multi-mode cross-domain cluster deployment method to a server in one embodiment;

[0088] Figure 2 A detailed flowchart of a multi-mode cross-domain cluster deployment method in one embodiment;

[0089] Figure 3 A schematic diagram of a process of applying a multi-mode cross-domain cluster deployment method to a cluster in one embodiment;

[0090] Figure 4 A schematic diagram of a process of a cross-domain cluster deployment method in a cross-domain disaster recovery mode in one embodiment;

[0091] Figure 5 A schematic diagram of a process of applying a multi-mode cross-domain cluster deployment method to a client terminal in one embodiment;

[0092] Figure 6 It is a structural block diagram of a multi-mode cross-domain cluster deployment device in one embodiment;

[0093] Figure 7 It is a structural block diagram of a multi-mode cross-domain cluster deployment device in one embodiment;

[0094] Figure 8 It is a structural block diagram of a multi-mode cross-domain cluster deployment device in one embodiment;

[0095] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0096] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0097] In one embodiment, Figure 1 As shown, a multi-mode cross-domain cluster deployment method is provided, and the method is applied to a server, including the following steps:

[0098] Step 102: perform data verification on the configuration data to be deployed according to the environment data to be deployed, and obtain a data verification result.

[0099] Exemplarily, the environment data to be deployed includes preset environment information such as host network connectivity in the cluster, host status, whether the deployment port is occupied, standardized deployment directory and data directory, and then each preset environment information is compared with the corresponding data in the configuration data to be deployed to determine whether the preset environment meets the deployment requirements.

[0100] In the case where the deployment requirements are not met, an error configuration prompt message is generated and transmitted to the client terminal together with the error data item, ie, the configuration item that does not meet the requirements.

[0101] If the deployment requirements are met, proceed to the next step.

[0102] Step 104 , when the data verification result shows that the environment to be deployed meets the deployment requirements, a solution to be implemented and its corresponding difference configuration file are generated based on the mode to be deployed and the configuration data to be deployed.

[0103] Among them, the modes to be deployed include cross-domain disaster recovery mode, officially recommended cluster mode, unlimited custom reorganization mode, custom disaster recovery mode and other modes.

[0104] Exemplarily, when the data is verified and it is determined that the environment meets the deployment conditions, different implementation plans and required components, i.e., differential configuration files, are generated according to different deployment modes and the configuration data to be deployed of the cluster to be deployed, specifically:

[0105] If the cross-domain configuration mode is selected, the production domain nodes and disaster recovery domain nodes are determined according to the configuration data to be deployed uploaded by the user terminal, and then the location and path of the disaster recovery node are determined by using the disaster recovery path algorithm combined with the analysis of data relationships. After that, the broker registration group and namesrv group are generated to ensure that each node in the cluster can discover and communicate with each other, and at the same time set a reasonable cluster mapping relationship; in addition, it is necessary to adapt the heartbeat monitoring program for real-time monitoring of the electromechanical status and the automatic switching disaster recovery domain program that can automatically switch in case of failure;

[0106] If you choose the custom master-master / master-slave mode, you need to reasonably divide each business group and configure the corresponding Broker registration group and registration center group. Among them, you can configure multiple groups of single copies, multiple groups of multiple copies asynchronous replication, and multiple groups of multiple copies synchronous dual write according to different business needs and throughput requirements.

[0107] If you choose a custom disaster recovery mode, you can implement cluster management based on business needs and system scale in combination with the Raft algorithm. The cluster is divided into multiple batch registration groups. Each registration group consists of several nodes. Then, a unique node ID is assigned to each node. It is ensured that all nodes can coordinate under the Raft protocol. At the same time, a unique Raft group ID is assigned to each batch registration group to distinguish different clusters and achieve efficient log replication.

[0108] Step 106: transmit the implementation plan and its corresponding differential configuration files to each cluster host, and receive the deployment feedback results of each cluster host.

[0109] Exemplarily, after obtaining the implementation plan and the required components, ie, the difference configuration files, the implementation plan and the required components, ie, the difference configuration files, are transmitted to each cluster host, and waiting is made to receive the configuration status of each cluster host.

[0110] If the configuration fails, the configuration log is analyzed to identify the specific problem and solve it, and then a secondary deployment is performed; the deployment method includes rollback and secondary deployment solutions.

[0111] If the configuration is successful, proceed to the next step.

[0112] Step 108: When the deployment feedback result is successful deployment, the deployment task is ended and the process information is updated.

[0113] For example, when the deployment feedback result is a successful deployment, the system needs to perform persistent storage of the task status to ensure that the task result is not lost, that is, write the final status of the task to the database and update it synchronously to the configuration center to ensure that the data in the configuration center is always kept up to date. At the same time, the deployment task is terminated.

[0114] In the above-mentioned multi-mode cross-domain cluster deployment method, after obtaining the configuration data to be deployed transmitted by the client terminal and the environment data to be deployed transmitted by the cluster, the configuration data to be deployed and the environment data to be deployed are compared to determine whether deployment can be performed. If it is determined that deployment can be performed, the implementation plan for the deployment cluster and the differential configuration data corresponding to the cluster are determined based on the environment data to be deployed and the mode to be deployed. At the same time, the implementation plan and the differential configuration file are transmitted to the cluster, and then the configuration result transmitted after waiting for the cluster configuration is determined to determine whether secondary deployment is required. This improves the feasibility and accuracy of cluster deployment, reduces the possibility of secondary deployment, thereby improving deployment efficiency and system stability, and realizes multi-mode, cross-domain disaster recovery deployment, supports flexible expansion and multi-platform compatibility, simplifies operating procedures, greatly improves deployment efficiency, reduces manual maintenance costs, and ensures safe and stable business operation.

[0115] In an exemplary embodiment, after performing data verification on the configuration data to be deployed according to the environment data to be deployed and obtaining the data verification result, the method further includes:

[0116] When the data verification result shows that the environment to be deployed does not meet the deployment requirements, a configuration error prompt message is generated; the error configuration prompt message and the error data item are transmitted to the client terminal; the corrected configuration data is received; and the corrected configuration data is verified according to the environment to be deployed data to obtain a secondary verification result.

[0117] The data verification result includes error data items.

[0118] For example, if after verification, it is determined that the deployment environment does not meet the deployment requirements, a detailed error configuration prompt message is generated, and the configuration items that do not meet the requirements are clearly marked. The error configuration prompt message and the configuration items that do not meet the requirements are then transmitted to the client terminal to remind the client to make modifications.

[0119] After that, the customer obtains the corrected configuration data based on the error configuration prompt information and the configuration items that do not meet the requirements. The corrected configuration data is then compared with the data of the environment to be deployed to determine whether it meets the deployment requirements, that is, the secondary verification result.

[0120] In an exemplary embodiment, when the data verification result shows that the environment to be deployed meets the deployment requirements, generating the implementation plan and its corresponding differential configuration file based on the mode to be deployed and the configuration data to be deployed includes:

[0121] When the data verification result shows that the environment to be deployed meets the deployment requirements, a configuration file to be deployed corresponding to the mode to be deployed is generated based on the mode to be deployed and the configuration data to be deployed; the cluster nodes are allocated and scheduled according to the mode to be deployed to obtain allocated nodes; the cluster is divided into regions according to the mode to be deployed to obtain divided clusters; based on the configuration file to be deployed corresponding to the mode to be deployed, the allocated nodes and the divided clusters, a plan to be implemented and its corresponding difference configuration files are generated.

[0122] Exemplarily, when it is determined that the environment to be deployed meets the deployment requirements, different solutions are executed according to the selected mode to be deployed, specifically:

[0123] In cross-domain configuration mode, the system determines the production domain nodes and disaster recovery domain nodes based on the configuration data to be deployed uploaded by the user, and uses the disaster recovery path algorithm to analyze the data relationship and determine the location and path of the disaster recovery nodes; then, it generates the Broker registration group and Namesrv group to ensure that the nodes in the cluster can communicate with each other; at the same time, it configures heartbeat monitoring and automatic switching of disaster recovery programs to ensure high availability;

[0124] In the custom master-master / master-slave mode, the system reasonably divides business groups according to business needs and throughput, and configures multiple replicas and synchronous replication modes;

[0125] In the custom disaster recovery mode, the cluster is managed through the Raft algorithm, the cluster is divided into multiple registration groups, and a unique ID is assigned to each node to ensure node coordination and log replication under the Raft protocol.

[0126] According to the above different modes, corresponding implementation plans and their corresponding difference configuration files are generated.

[0127] In an exemplary embodiment, a multi-mode cross-domain cluster deployment method is provided, and the method is applied to a server, comprising the following steps:

[0128] The configuration data to be deployed is verified according to the environment data to be deployed to obtain the data verification result.

[0129] If the data verification result shows that the environment to be deployed does not meet the deployment requirements, a configuration error prompt message is generated.

[0130] Transmit error configuration prompt information and error data items to the client terminal.

[0131] Receive the revised configuration data.

[0132] The modified configuration data is verified according to the environment data to be deployed to obtain a secondary verification result.

[0133] When the data verification result shows that the to-be-deployed environment meets the deployment requirements, a to-be-deployed configuration file corresponding to the to-be-deployed mode is generated based on the to-be-deployed mode and the to-be-deployed configuration data.

[0134] Allocate and schedule cluster nodes according to the mode to be deployed to obtain allocated nodes.

[0135] The cluster is divided into regions according to the mode to be deployed to obtain the divided clusters.

[0136] Based on the configuration file to be deployed corresponding to the mode to be deployed, the allocated nodes and the divided clusters, the implementation plan and its corresponding difference configuration file are generated.

[0137] The implementation plan and its corresponding differential configuration files are transmitted to each cluster host, and the deployment feedback results of each cluster host are received.

[0138] If the deployment feedback result is successful deployment, end the deployment task and update the process information.

[0139] The specific process steps of the above method are as follows Figure 2 shown.

[0140] In one embodiment, Figure 3 As shown, a multi-mode cross-domain cluster deployment method is provided, and the method is applied to the cluster, including the following steps:

[0141] Step 302 , configure and deploy the cluster hosts to be deployed according to the implementation plan and its corresponding differential configuration files to obtain a deployed cluster.

[0142] Exemplarily, after receiving the implementation plans and their corresponding differential configuration files, different configuration deployment operations are performed for different implementation plans, specifically:

[0143] First, determine whether the required dependent software has been installed, such as JDK and Apache components. If not, configure them and ensure that existing resources are reused. Then, deploy Broker and NameSrv components based on cluster data analysis. For resource reuse, optimize the original mqshutdown program in combination with data mapping relationships to prevent multiple instance compatibility issues from causing false shutdowns. Further optimize the traditional cluster service management method, implement service hosting, supervision, and startup and shutdown functions through secondary development, ensure that the service can recover from self-recovery when it fluctuates, and improve the self-healing ability of the service.

[0144] Subsequently, the service functionality test is carried out to verify the validity of the generated configuration and secondary development program, check the service operation status and data transmission, and ensure that fault switching can be smoothly implemented in disaster recovery or disaster tolerance mode.

[0145] Finally, the execution results are fed back to the server to ensure that each link of the deployment meets expectations and that the system runs stably. The system also needs to store the task status persistently to ensure that the task results are not lost. That is, the final status of the task is written to the database and updated synchronously to the configuration center to ensure that the data in the configuration center is always up to date. At the same time, the deployment task is terminated.

[0146] The specific process steps of the above method are as follows Figure 2 shown.

[0147] Step 304: After the configuration of the cluster host is completed, status monitoring is performed on the deployed cluster to obtain status detection data.

[0148] For example, after completing the configuration deployment, taking the cross-domain disaster recovery mode as an example, the production domain data is automatically synchronized to the disaster recovery domain regularly, and the status of the hosts in the deployed cluster is detected to obtain the status data of each host in the cluster and the overall status data of the cluster.

[0149] Step 306 , performing disaster recovery processing according to the status detection data, the preset status threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster.

[0150] The state detection data includes cluster detection data and intra-group detection data, and the preset state threshold includes a preset cluster threshold and a preset intra-group threshold.

[0151] For example, the overall cluster status data is compared with a preset cluster threshold to determine whether the cluster is seriously faulty and then execute a disaster recovery switching solution. At the same time, it is necessary to compare the status data of each host with a preset intra-group threshold to determine whether a node in the host is seriously faulty and then execute a node switching solution. For example:

[0152] Monitor the health database of the Broker group in the production domain. If the healthy nodes exceed 50%, the automatic adjustment mechanism is started. At this time, if the Master node fails, the failed Master will be automatically removed and the Slave node will be promoted to Master to ensure that the cluster continues to run stably and avoid business interruption.

[0153] If the production domain cluster fails more than 50%, the disaster recovery domain automatic switching program will be started. This program will promote the disaster recovery domain cluster to the production domain, take over the load of the production domain, and ensure continuous service of the system.

[0154] In an exemplary embodiment, disaster recovery processing is performed according to state detection data, a preset state threshold, and a preset disaster recovery plan to obtain a post-disaster recovery cluster, including:

[0155] The cluster detection data is compared and analyzed with the preset cluster threshold to obtain the cluster analysis result; when the cluster analysis result is that the cluster detection data is greater than the preset cluster threshold, the disaster recovery domain cluster is promoted to the production domain cluster and the status detection data is obtained; when the cluster analysis result is that the cluster detection data is less than or equal to the preset cluster threshold, the intra-group detection data is compared and analyzed with the preset intra-group threshold to obtain the host analysis result; when the host analysis result is that the intra-group detection data is greater than the preset intra-group threshold, the slave node is promoted to the master node and the faulty master node is eliminated; when the host analysis result is that the intra-group detection data is less than or equal to the preset intra-group threshold, the next status detection data is obtained.

[0156] The state detection data includes cluster detection data and intra-group detection data, and the preset state threshold includes a preset cluster threshold and a preset intra-group threshold.

[0157] Exemplarily, after the cluster and the hosts therein are detected, the cluster detection data is compared with a preset cluster threshold, that is, it is first determined whether a serious fault occurs in the cluster as a whole to determine whether an overall disaster recovery strategy needs to be executed.

[0158] When the cluster detection data exceeds the preset cluster threshold, the overall disaster recovery strategy is executed. Taking the cross-domain disaster recovery mode as an example, the preset cluster threshold is set to 50%. If the cluster detection data shows that the production domain cluster failure exceeds 50%, the automatic switching program is used to promote the disaster recovery domain cluster to the production domain.

[0159] When the cluster detection data does not exceed the preset cluster threshold, the intra-group detection data is compared with the preset intra-group threshold to determine whether a serious fault occurs in the production domain broker group.

[0160] When the detection data within the group exceeds the preset group threshold, the broker role in the production domain is adjusted, the faulty Master is removed, and the Slave is promoted to Master.

[0161] When the detection data within the group does not exceed the preset group threshold, the detection continues.

[0162] In an exemplary embodiment, a multi-mode cross-domain cluster deployment method is provided, and the method is applied to a cluster, comprising the following steps:

[0163] The hosts in the cluster to be deployed are configured and deployed according to the implementation plan and its corresponding differential configuration files to obtain the deployed cluster.

[0164] After completing the configuration of the cluster host, perform status monitoring on the deployed cluster to obtain status detection data.

[0165] The cluster detection data is compared and analyzed with the preset cluster threshold to obtain the cluster analysis results.

[0166] When the cluster analysis result shows that the cluster detection data is greater than the preset cluster threshold, the disaster recovery domain cluster is promoted to a production domain cluster and status detection data is obtained.

[0167] When the cluster analysis result shows that the cluster detection data is less than or equal to the preset cluster threshold, the intra-group detection data is compared and analyzed with the preset intra-group threshold to obtain the host analysis result.

[0168] When the host analysis result shows that the detection data within the group is greater than the preset threshold within the group, the slave node is promoted to the master node and the faulty master node is removed.

[0169] When the host analysis result is that the in-group detection data is less than or equal to the preset in-group threshold, the next state detection data is obtained.

[0170] The above multi-mode cross-domain cluster deployment method applied to clusters is applicable to the cross-domain disaster recovery mode. The specific process is as follows: Figure 4 shown.

[0171] In one embodiment, Figure 5 As shown, a multi-mode cross-domain cluster deployment method is provided, and the method is applied to a client terminal, including the following steps:

[0172] Step 502: Generate configuration data to be deployed based on user demand data.

[0173] For example, the operator customizes different scenario modes according to their own business needs through the UI interaction page of the client terminal, for example:

[0174] ① Select the release version. Support the official mainstream release version. The version library of this solution will synchronize the official versions regularly, store them in the local product library, and update the differential compatibility on time;

[0175] ②Choose a deployment method. Different modes are supported. Integrated cross-domain disaster recovery mode, officially recommended cluster mode, unlimited custom reorganization mode, and custom disaster recovery mode. Each mode can be infinitely and dynamically expanded as long as it meets the official minimum combination, which is extremely flexible.

[0176] ③ Select the deployment room and host. Synchronize the configuration center data and present the asset configuration in the filter box to reduce the probability of manual input errors by users and improve the user's good UI experience;

[0177] ④Customization of important configuration data. Customize configurations such as listening ports and storage size according to different business needs to achieve optimal resource utilization, and dynamic templates support strong compatibility;

[0178] ⑤ Batch deployment. Supports batch replication of single cluster templates, adjusts differential data as needed, completes batch deployment customization, improves maintenance efficiency, and reduces labor maintenance costs. After confirming the first submission, the UI will prompt for a second confirmation, and submit with one click after it is correct.

[0179] If we take the cross-domain disaster recovery mode as an example, then:

[0180] ① Select the release version. Support the official mainstream release version. The version library of this solution synchronizes the official versions regularly, stores them in the local product library, and updates the differential compatibility on time; ② Select the cross-domain disaster recovery deployment method. Under the conditions of the official minimum group, select the group, generate the broker-master and broker-slave roles in the group, and create superimposed groups as needed, such as two masters and two slaves, four masters and four slaves, etc., customized dynamic expansion, and strong flexibility; ③ Select the target host of the production domain and disaster recovery domain. Synchronize the configuration center data, present the asset configuration with a filter box, reduce the risk of manual input errors by users, and enhance the user experience; ④ Customize the listening port and store key configuration data. Adapt data according to resource conditions to allow users to customize and be compatible with different usage scenarios; ⑤ Batch deployment. If you need a multi-cluster batch deployment scenario, you can copy it infinitely according to the previous cluster template, and change the template data if you need to adjust it. Confirm that the data is correct and submit it with one click; ④⑤ items are selected according to the actual business scenario.

[0181] If we take the multi-master and multi-slave asynchronous replication mode as an example, then:

[0182] ① Select the release version. Support the official mainstream release version. The version library of this solution synchronizes the official versions regularly, stores them in the local product library, and updates the differential compatibility on time; ② Select the multi-master and multi-slave asynchronous deployment method. Under the conditions of the official minimum group, select the group, generate the broker-master and broker-slave roles in the group, and create superimposed groups as needed, for example: four groups, four masters and four slaves asynchronous deployment or eight groups, eight masters and eight slaves, supporting unlimited dynamic expansion. It is extremely flexible; ③ Dynamic capture of view data. The user's dependent data is synchronized with the configuration center data, and the data is accurate to reduce human error filling, which is more convenient and increases the user experience; ④ Customize key configuration data such as listening ports and storage. Ports, storage and other data can be customized by users according to resource conditions to adapt to different usage scenarios; ⑤ Batch deployment. If there are multiple clusters in the batch deployment scenario, you can copy it infinitely according to the generated previous cluster template, and change the template data if you need to adjust it. Confirm that the data is correct and submit it with one click; ④⑤ items are selected according to the actual business scenario.

[0183] Generate configuration data to be deployed based on selected demand data

[0184] Step 504: transmit the configuration data to be deployed to the server, and receive the current feedback result.

[0185] Exemplarily, after the configuration data to be deployed is transmitted to the server, the configuration data to be deployed is verified in the server to determine whether the environment to be deployed meets the requirements. After verification, the client terminal receives the current feedback result transmitted by the server.

[0186] If the current feedback result is that the environment to be deployed meets the requirements, wait for the deployment result.

[0187] If the current feedback result is that the environment to be deployed does not meet the requirements, you need to modify the environment to be deployed.

[0188] Step 506: When the current feedback result is that the to-be-deployed environment does not meet the deployment requirements, the to-be-deployed configuration data is corrected according to the error configuration prompt information and the error data items to obtain corrected configuration data.

[0189] Exemplarily, when the current feedback result is that the environment to be deployed does not meet the deployment requirements, the client terminal receives error configuration prompt information and error data items, i.e., configuration items that do not meet the requirements, and corrects the data according to the received information and configuration items to obtain corrected configuration data.

[0190] Step 508: Transmit the modified configuration data to the server and receive the next feedback result.

[0191] Exemplarily, the client terminal transmits the modified configuration data to the server via the network to ensure that the server receives the latest configuration update. After the data transmission is completed, the server processes and verifies the configuration and generates feedback information based on the processing results.

[0192] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0193] Based on the same inventive concept, the embodiment of the present application also provides a multi-mode cross-domain cluster deployment device for implementing the multi-mode cross-domain cluster deployment method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more multi-mode cross-domain cluster deployment device embodiments provided below can refer to the limitations of the multi-mode cross-domain cluster deployment method above, and will not be repeated here.

[0194] In one embodiment, Figure 6 As shown, a multi-mode cross-domain cluster deployment device is provided, which is applied to a server, including: a data verification module 602, a solution generation module 604, a first communication module 606 and an information update module 608, wherein:

[0195] The data verification module 602 is used to perform data verification on the configuration data to be deployed according to the environment data to be deployed, and obtain a data verification result.

[0196] The solution generation module 604 is used to generate a solution to be implemented and its corresponding difference configuration file based on the to-be-deployed mode and the to-be-deployed configuration data when the data verification result shows that the to-be-deployed environment meets the deployment requirements.

[0197] The first communication module 606 is used to transmit the implementation plan and its corresponding differential configuration files to each cluster host, and receive the deployment feedback results of each cluster host.

[0198] The information updating module 608 is used to end the deployment task and update the process information when the deployment feedback result is successful deployment.

[0199] In an exemplary embodiment, the multi-mode cross-domain cluster deployment device is used to generate a configuration error prompt message when the data verification result shows that the environment to be deployed does not meet the deployment requirements; transmit the error configuration prompt message and the error data item to the client terminal; receive the corrected configuration data; perform data verification on the corrected configuration data according to the environment to be deployed data to obtain a secondary verification result.

[0200] In an exemplary embodiment, the solution generation module 604 is also used to generate a configuration file to be deployed corresponding to the mode to be deployed based on the mode to be deployed and the configuration data to be deployed when the data verification result shows that the environment to be deployed meets the deployment requirements; allocate and schedule cluster nodes according to the mode to be deployed to obtain allocated nodes; divide the cluster into regions according to the mode to be deployed to obtain divided clusters; generate a plan to be implemented and its corresponding difference configuration file based on the configuration file to be deployed corresponding to the mode to be deployed, the allocated nodes and the divided clusters.

[0201] In one embodiment, Figure 7As shown, a multi-mode cross-domain cluster deployment device is provided, which is applied to a cluster, including: a configuration deployment module 702, a state detection module 704 and a disaster recovery processing module 706, wherein:

[0202] The configuration and deployment module 702 is used to configure and deploy the hosts of the cluster to be deployed according to the implementation plan and its corresponding differential configuration files to obtain a deployed cluster.

[0203] The status detection module 704 is used to monitor the status of the deployed cluster and obtain status detection data when the configuration of the cluster host is completed.

[0204] The disaster recovery processing module 706 is used to perform disaster recovery processing according to the status detection data, the preset status threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster.

[0205] In an exemplary embodiment, the disaster recovery processing module 706 is further used to compare and analyze the cluster detection data with a preset cluster threshold to obtain a cluster analysis result;

[0206] When the cluster analysis result shows that the cluster detection data is greater than the preset cluster threshold, the disaster recovery domain cluster is promoted to a production domain cluster and the status detection data is obtained; when the cluster analysis result shows that the cluster detection data is less than or equal to the preset cluster threshold, the intra-group detection data is compared and analyzed with the preset intra-group threshold to obtain the host analysis result; when the host analysis result shows that the intra-group detection data is greater than the preset intra-group threshold, the slave node is promoted to the master node and the faulty master node is eliminated; when the host analysis result shows that the intra-group detection data is less than or equal to the preset intra-group threshold, the next status detection data is obtained.

[0207] In one embodiment, Figure 8 As shown, a multi-mode cross-domain cluster deployment device is provided, which is applied to a server and includes: a data processing module 802 and a second communication module 804, wherein:

[0208] The data processing module 802 is used to generate configuration data to be deployed based on user demand data.

[0209] The second communication module 804 is used to transmit the configuration data to be deployed to the server and receive the current feedback result.

[0210] The data processing module 802 is further used to correct the configuration data to be deployed according to the error configuration prompt information and the error data items to obtain the corrected configuration data when the current feedback result is that the environment to be deployed does not meet the deployment requirements.

[0211] The second communication module 804 is further used to transmit the modified configuration data to the server and receive the next feedback result.

[0212] Each module in the above multi-mode cross-domain cluster device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module above.

[0213] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig. 9 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data to be deployed and data of the environment to be deployed. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a multi-mode cross-domain clustering method is implemented.

[0214] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0215] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0216] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0217] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0218] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0219] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0220] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0221] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A multi-mode cross-domain cluster deployment method, characterized in that: Applied to a server, the method comprises: Perform data verification on the configuration data to be deployed according to the environment data to be deployed, and obtain the data verification result; If the data verification result shows that the environment to be deployed meets the deployment requirements, generating a to-be-implemented solution and its corresponding differential configuration file based on the to-be-deployed mode and the to-be-deployed configuration data; Transmitting the implementation plan and its corresponding differential configuration files to each cluster host, and receiving deployment feedback results from each cluster host; When the deployment feedback result is successful deployment, the deployment task is ended and the process information is updated.

2. The multi-mode cross-domain cluster deployment method according to claim 1, characterized in that: The data verification result includes an error data item; after performing data verification on the configuration data to be deployed according to the environment data to be deployed and obtaining the data verification result, the method further includes: If the data verification result is that the to-be-deployed environment does not meet the deployment requirements, a configuration error prompt message is generated; Transmitting the error configuration prompt information and the error data item to the client terminal; receiving the revised configuration data; The modified configuration data is verified according to the to-be-deployed environment data to obtain a secondary verification result.

3. The multi-mode cross-domain cluster deployment method according to claim 1, characterized in that: When the data verification result shows that the environment to be deployed meets the deployment requirements, generating the implementation plan and its corresponding difference configuration file based on the mode to be deployed and the configuration data to be deployed, including: If the data verification result shows that the to-be-deployed environment meets the deployment requirements, generating a to-be-deployed configuration file corresponding to the to-be-deployed mode based on the to-be-deployed mode and the to-be-deployed configuration data; Allocate and schedule the cluster nodes according to the to-be-deployed mode to obtain allocated nodes; Divide the cluster into regions according to the to-be-deployed mode to obtain divided clusters; A to-be-implemented solution and its corresponding difference configuration file are generated based on the to-be-deployed configuration file corresponding to the to-be-deployed mode, the allocated nodes and the divided clusters.

4. A multi-mode cross-domain cluster deployment method, characterized in that: Applied to a cluster, the method comprises: Configure and deploy the cluster hosts to be deployed according to the implementation plan and its corresponding differential configuration files to obtain the deployed cluster; When the configuration of the cluster host is completed, status monitoring is performed on the deployed cluster to obtain status detection data; Disaster recovery processing is performed according to the state detection data, the preset state threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster.

5. The multi-mode cross-domain cluster deployment method according to claim 4, characterized in that: The state detection data includes cluster detection data and intra-group detection data; the preset state threshold includes a preset cluster threshold and a preset intra-group threshold; The performing disaster recovery processing according to the state detection data, the preset state threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster includes: Compare and analyze the cluster detection data with the preset cluster threshold to obtain the cluster analysis result; When the cluster analysis result shows that the cluster detection data is greater than a preset cluster threshold, the disaster recovery domain cluster is promoted to a production domain cluster and status detection data is obtained; When the cluster analysis result is that the cluster detection data is less than or equal to the preset cluster threshold, the intra-group detection data is compared and analyzed with the preset intra-group threshold to obtain the host analysis result; When the host analysis result shows that the detection data within the group is greater than the preset threshold within the group, the slave node is promoted to the master node and the faulty master node is removed; When the host analysis result is that the in-group detection data is less than or equal to a preset in-group threshold, the next state detection data is obtained.

6. A multi-mode cross-domain cluster deployment method, characterized in that: Applied to a client terminal, the method comprises: Generate configuration data to be deployed based on user demand data; Transmitting the configuration data to be deployed to the server and receiving the current feedback result; When the current feedback result is that the environment to be deployed does not meet the deployment requirements, the configuration data to be deployed is corrected according to the error configuration prompt information and the error data item to obtain the corrected configuration data; The modified configuration data is transmitted to the server, and the next feedback result is received.

7. A multi-mode cross-domain cluster deployment device, characterized in that: Applied to a server, the device comprises: A data verification module is used to verify the configuration data to be deployed according to the environment data to be deployed, and obtain the data verification result; A solution generation module, configured to generate a solution to be implemented and its corresponding difference configuration file based on the to-be-deployed mode and the to-be-deployed configuration data when the data verification result shows that the to-be-deployed environment meets the deployment requirements; A first communication module is used to transmit the to-be-implemented plan and its corresponding differential configuration files to each cluster host, and receive deployment feedback results from each cluster host; The information updating module is used to end the deployment task and update the process information when the deployment feedback result is a successful deployment.

8. A multi-mode cross-domain cluster deployment device, characterized in that: Applied to a cluster, the device comprises: The configuration and deployment module is used to configure and deploy the cluster hosts to be deployed according to the implementation plan and its corresponding differential configuration files to obtain the deployed cluster; A status detection module is used to monitor the status of the deployed cluster and obtain status detection data when the configuration of the cluster host is completed; The disaster recovery processing module is used to perform disaster recovery processing according to the state detection data, the preset state threshold and the preset disaster recovery plan to obtain a post-disaster recovery cluster.

9. A multi-mode cross-domain cluster deployment device, characterized in that: Applied to a client terminal, the device comprises: A data processing module, used to generate configuration data to be deployed based on user demand data; A second communication module is used to transmit the configuration data to be deployed to the server and receive the current feedback result; The data processing module is further used to correct the configuration data to be deployed according to the error configuration prompt information and the error data item to obtain the corrected configuration data when the current feedback result is that the environment to be deployed does not meet the deployment requirements; The second communication module is further used to transmit the modified configuration data to the server and receive the next feedback result.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

Images