Registration information migration method and device, electronic equipment and storage medium

Abstract

The invention discloses a registration information migration method and device, electronic equipment and a storage medium. The method comprises the following steps: deploying a new node cluster of a target service tool; sending an information acquisition request to the target service tool to obtain existing registration information in the service; screening out registration information to be migrated from existing registration information in the service; constructing a plurality of registration information migration requests by using the to-be-migrated registration information; and sending the registration information migration request to a plurality of client nodes in a new node cluster of the target service tool, and migrating the to-be-migrated registration information to the new node cluster of the target service tool through each client node.

Description

Technical Field

[0001] The present application relates to the technical field of information migration, and in particular to a registration information migration method and device, electronic device, and storage medium. Background Art

[0002] The service tool Consul is an open source service discovery and configuration management tool designed for building and maintaining distributed systems. Its functions include service registration and discovery, health check, etc. In an enterprise production environment, Consul will be expanded or upgraded in scale as the number of microservice registration information increases. Among them, the successful migration of registration information is a necessary means to ensure the stability of Consul services.

[0003] Currently, the migration of Consul registration information is mainly implemented by snapshot. Specifically, the internal CLI command is used to create a snapshot of the registration information from the original Consul cluster, that is, the registration information is exported internally in the form of a snapshot, and then the snapshot of the registration information is imported into the server node Server of the migration target through communication with the migration target, that is, imported into the new Consul cluster to achieve the migration of registration information.

[0004] However, this method is very limited because it relies on internal CLI commands, the storage path of the exported snapshot can only be inside the container, and the communication with the migration target must be considered. If there is a difference in the version, the snapshot import will fail. In addition, from creating a snapshot to importing data, all operations are performed on the server node Server, which puts too much pressure on the server node Server. Summary of the invention

[0005] Based on the above-mentioned deficiencies of the prior art, the present application provides a registration information migration method and device, electronic device, and storage medium to solve the problem that the prior art is more limited and causes excessive pressure on the server.

[0006] In order to achieve the above objectives, this application provides the following technical solutions:

[0007] The first aspect of the present application provides a registration information migration method, comprising:

[0008] Deploy a new node cluster of the target service tool;

[0009] Obtaining existing registration information in the service by sending an information acquisition request to the target service tool;

[0010] Filtering the registration information to be migrated from the existing registration information in the service;

[0011] Constructing multiple registration information migration requests using the registration information to be migrated;

[0012] The registration information migration request is sent to multiple client nodes in the new node cluster of the target service tool, and the registration information to be migrated is migrated to the new node cluster of the target service tool through each of the client nodes.

[0013] Optionally, in the above registration information migration method, the new node cluster of the deployment target service tool includes:

[0014] Deploy a new node cluster of the target service tool of the client and server architecture including a plurality of server nodes and a plurality of client nodes in a container cluster management system;

[0015] Selecting a main service node from each of the service end nodes; wherein the number of the service end nodes is odd;

[0016] The persistence of each of the server nodes is turned on, and the persistence of each of the server nodes is turned off.

[0017] Optionally, in the above registration information migration method, the step of obtaining the existing registration information in the service by sending an information acquisition request to the target service tool includes:

[0018] Obtaining a service list by sending an information acquisition request in a hypertext transfer protocol format to an application program interface of the target service tool;

[0019] Traverse each server request in the service list to obtain the existing registration information in the service.

[0020] Optionally, in the above registration information migration method, after constructing multiple registration information migration requests using the registration information to be migrated, the method further includes:

[0021] The registration information to be migrated is stored and backed up via data files in a variety of preset formats.

[0022] Optionally, in the above registration information migration method, sending the registration information migration request to multiple client nodes in the new node cluster of the target service tool, and migrating the registration information to be migrated to the new node cluster of the target service tool through each of the client nodes, includes:

[0023] For each registration information migration request, determining the category of the registration information to be migrated requested by the registration information migration request;

[0024] The registration information migration request is sent to one of the client nodes in the load balancing server corresponding to the category of the registration information to be migrated that is requested to be migrated, and the registration information to be migrated requested to be migrated is registered in the new node cluster of the target service tool through the client node.

[0025] A second aspect of the present application provides a registration information migration device, including:

[0026] A deployment unit is used to deploy a new node cluster of the target service tool;

[0027] An information acquisition unit, configured to obtain existing registration information in the service by sending an information acquisition request to the target service tool;

[0028] A screening unit, used to screen the registration information to be migrated from the existing registration information in the service;

[0029] A construction unit, configured to construct a plurality of registration information migration requests using the registration information to be migrated;

[0030] The migration unit is used to send the registration information migration request to multiple client nodes in the new node cluster of the target service tool, and migrate the registration information to be migrated to the new node cluster of the target service tool through each of the client nodes.

[0031] Optionally, in the above-mentioned registration information migration device, the deployment unit includes:

[0032] A cluster deployment unit, configured to deploy a new node cluster of the target service tool of a client and server architecture including a plurality of server nodes and a plurality of client nodes in a container cluster management system;

[0033] A selection unit, configured to select a main service node from each of the service end nodes; wherein the number of the service end nodes is odd;

[0034] The configuration unit is used to enable persistence of each of the server nodes and disable persistence of each of the server nodes.

[0035] Optionally, in the above-mentioned registration information migration device, the information acquisition unit includes:

[0036] A list acquisition unit, configured to obtain a service list by sending an information acquisition request in a hypertext transfer protocol format to an application program interface of the target service tool;

[0037] The traversal unit is used to traverse each server request in the service list to obtain the existing registration information in the service.

[0038] Optionally, the above-mentioned registration information migration device further includes:

[0039] The backup unit is used to store and back up the registration information to be migrated through data files in multiple preset formats.

[0040] Optionally, in the above-mentioned registration information migration device, the migration unit includes:

[0041] a category determination unit, configured to determine, for each of the registration information migration requests, the category of the registration information to be migrated requested to be migrated by the registration information migration request;

[0042] A registration unit is used to send the registration information migration request to one of the client nodes in the load balancing server corresponding to the category of the registration information to be migrated that is requested to be migrated, and register the registration information to be migrated requested to be migrated by the registration information migration request in the new node cluster of the target service tool through the client node.

[0043] A third aspect of the present application provides an electronic device, including:

[0044] Memory and processor;

[0045] Wherein, the memory is used to store programs;

[0046] The processor is used to execute the program, and when the program is executed, it is specifically used to implement the registration information migration method as described in any one of the above.

[0047] A fourth aspect of the present application provides a computer storage medium for storing a computer program, which, when executed, is used to implement a registration information migration method as described in any one of the above.

[0048] The embodiment of the present application provides a method for migrating registration information, which first deploys a new node cluster of a target service tool. Then, by sending an information acquisition request to the target service tool, the existing registration information in the service is obtained, so that the registration information of the service of the target service tool is obtained by sending an information acquisition request to the target service tool externally, thereby replacing the method of obtaining the registration information by creating a snapshot through an internal CLI instruction, so that the acquisition method is no longer limited. Then, the registration information to be migrated is screened out from the existing registration information in the service, and multiple registration information migration requests are constructed using the registration information to be migrated, so that the registration information obtained externally can be sent to the server node in the target service tool for registration, without the need for the original service tool to communicate with the migration target, and there is no need to worry about the failure of migration when the versions of the two are inconsistent, so that the migration of registration information is no longer restricted in these aspects. Therefore, the registration information migration request is finally sent to multiple client nodes in the new node cluster of the target service tool, and the registration information to be migrated is migrated to the new node cluster of the target service tool through each client node, so that the migration of registration information is realized through the client node, so that the pressure on the server node will not be too large. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0050] Figure 1 A flowchart of a registration information migration method provided in an embodiment of the present application;

[0051] Figure 2 A flowchart of a method for deploying a new node cluster of a target service tool provided in an embodiment of the present application;

[0052] Figure 3 A flowchart of a method for obtaining existing registration information in a service provided in an embodiment of the present application;

[0053] Figure 4 A flowchart of a method for migrating registration information to be migrated to a new node cluster of a target service tool provided in an embodiment of the present application;

[0054] Figure 5 A schematic diagram of the architecture of a registration information migration device provided in an embodiment of the present application;

[0055] Figure 6A schematic diagram of the architecture of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0056] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0057] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0058] The present application embodiment provides a method for migrating registration information, such as Figure 1 As shown, the following steps are included:

[0059] S101. Deploy a new node cluster of the target service tool.

[0060] The target service tool is a service tool that currently needs to perform registration information migration. Specifically, it may be Consul, an open source service discovery and configuration management tool that currently needs to perform registration information migration. The new node cluster is a cluster composed of new nodes.

[0061] Therefore, in the embodiment of the present application, a new node cluster is first created for the target service tool that needs to migrate the registration information to facilitate the subsequent migration of the registration information.

[0062] It should be noted that in the embodiment of the present application, the migration work is performed through the client node, i.e., the Client node, and the service node, i.e., the Server node is the node for realizing the main functions of the target service tool, so the new node cluster of the target service tool created in the embodiment of the present application needs to include Client nodes and Server nodes.

[0063] Optionally, in another embodiment of the present application, a specific implementation of step S101 is as follows: Figure 2 As shown, the following steps are included:

[0064] S201. Deploy a new node cluster of a target service tool of a client and server architecture including multiple server nodes and multiple client nodes in a container cluster management system.

[0065] It should be noted that in the embodiment of the present application, the client and server architecture, namely the C / S architecture, is adopted. The architecture is composed of multiple Client nodes and Server nodes, which can well meet the requirements of this solution. The container cluster management system can adopt Kubernetes.

[0066] Therefore, specifically, in the embodiment of the present application, step S201 can specifically be a new node cluster of the target service tool of the C / S architecture including the Server role and the Client role in the container cluster management system Kubernetes.

[0067] S202: Select a main service node from each service end node.

[0068] Among them, the number of server nodes is odd.

[0069] It should be noted that in order to implement the Raft server node, it is necessary to deploy the server node based on an odd number of nodes to ensure that the main service node, that is, the Leader, can be selected from them.

[0070] S203: Enable persistence for each server node, and disable persistence for each server node.

[0071] In the embodiment of the present application, the Server node only assumes the master role of electing and persisting cluster node information, so it is necessary to enable persistence for each server node. The Client node assumes the target role of service registration, responsible for health detection and distributing the load of Server requests. Therefore, in the process of registering information to the migration target, it can be specified that the registration information needs to be imported into the Client node, so each server node does not need to enable persistence.

[0072] It should be noted that in another embodiment of the present application, a new node cluster of the target service tool created may also include a load balancing gateway. Specifically, Nginx may be used for load balancing in front of multiple Client nodes. Specifically, multiple Nginx may be deployed and registered to the Client group according to business divisions. Of course, Nginx may also be deployed in front of the Server node for load balancing of read requests for obtaining service information.

[0073] S102: Obtain existing registration information in the service by sending an information acquisition request to the target service tool.

[0074] It should be noted that in order to obtain information without relying on the CLI command inside the target service tool, so that the method of obtaining information is no longer limited, in the embodiment of the present application, an external application sends an information acquisition request to the target service tool to request to obtain the existing registration information in the service. Specifically, the information acquisition request can be sent to the API provided by the target service tool to obtain the existing registration information in the service fed back by the target service tool.

[0075] Optionally, in another embodiment of the present application, the specific implementation of step S102 is as follows: Figure 3 As shown, the following steps are included:

[0076] S301: Obtain a service list by sending an information acquisition request in a hypertext transfer protocol format to an application program interface of a target service tool.

[0077] That is to say, in the embodiment of the present application, an HTTP request is sent to the application program interface of the target service tool to obtain a service list, thereby replacing the method of creating a snapshot by using the command line CLI inside the service.

[0078] S302: Traverse each server request in the service list to obtain existing registration information in the service.

[0079] Specifically, after obtaining the service list, each server request in the service list is traversed to obtain the registration information in each service. Among them, the Key / Value is also obtained in the same way, so the complete and backup registration information can be obtained.

[0080] S103: Filter out the registration information to be migrated from the existing registration information in the service.

[0081] Optionally, the acquired registration information may be screened as the registration information to be migrated, that is, all the registration information needs to be migrated, or some registration information to be migrated may be screened from the existing registration information in the service as the registration information to be migrated.

[0082] Optionally, the registration information meeting the requirements may be filtered out as the information to be migrated according to the set service range and health level.

[0083] It should be noted that, considering the version of the migration target, that is, in order to realize the construction of sending requests to migration targets of different versions, after the above screening, secondary filtering and screening can be performed according to the version of the migration target.

[0084] S104: Construct multiple registration information migration requests using the registration information to be migrated.

[0085] It should be noted that, in the embodiment of the present application, the registration information is obtained by sending an information acquisition request to the target service tool from the outside, that is, the registration information is obtained from the outside, and its snapshot is not created through internal CLI instructions and cached internally, so it is necessary to construct a corresponding registration information migration request to achieve the migration of the obtained registration information to the new node cluster of the target service tool.

[0086] Optionally, the request body of the request needs to include fields such as service ID, service name, IP address, label, health check related information (check path, interval time), etc. In addition, when constructing the request, the registration information can be re-edited according to business needs to meet current business needs.

[0087] Optionally, in another embodiment of the present application, after executing step S104, the following may be further performed:

[0088] The registration information to be migrated is stored and backed up through data files in a variety of preset formats.

[0089] It should be noted that, considering the possibility of failure in the migration of registration information, the registration information to be migrated needs to be stored and backed up through data files in a variety of preset formats.

[0090] Optionally, you can further increase the audit of registration actions, set the flow of data exports, and achieve diversified information processing.

[0091] S105 , sending a registration information migration request to multiple client nodes in the new node cluster of the target service tool, and migrating the registration information to be migrated to the new node cluster of the target service tool through each client node.

[0092] Specifically, since a registration information migration request is constructed, it can be sent to the corresponding node as needed. Therefore, in an embodiment of the present application, the registration information migration request is sent to the client node for information migration, so that there is no need to migrate through the server node.

[0093] Therefore, in an embodiment of the present application, a registration information migration request is sent to each client node in the new node cluster of the target service tool, and each client node responds to the received registration information migration request and migrates the requested registration information to be migrated to the new node cluster of the target service tool, thereby realizing the migration of registration information.

[0094] Optionally, in another embodiment of the present application, a specific implementation of step S105 is as follows: Figure 4 As shown, the following steps are included:

[0095] S401. Determine, for each registration information migration request, the category of the registration information to be migrated requested by the registration information migration request.

[0096] In the embodiment of the present application, load balancing is performed according to the category of the registration information to be migrated, so it is necessary to first determine the category of the registration information to be migrated requested to be migrated by the registration information migration request.

[0097] S402, sending the registration information migration request to a client node in the load balancing server corresponding to the category of the registration information to be migrated requested to be migrated, and registering the registration information to be migrated requested to be migrated in the new node cluster of the target service tool through the client node.

[0098] It should be noted that different Client nodes are pre-composed into load balancing servers Nginx corresponding to different categories. Therefore, after determining the category of the registration information to be migrated, the corresponding request can be sent to the Client node in the load balancing server Nginx of the corresponding category, and the registration information to be migrated is registered to the new node cluster of the target service tool through the Client node.

[0099] It should also be noted that since the Client node does not need to be persistent, it can be expanded infinitely and there is no single point of failure. Therefore, combined with the backup storage of registration information files, the registration action can be called after the Client node is reset or a new node is added, ensuring the integrity and consistency of the data.

[0100] The embodiment of the present application provides a method for migrating registration information, which first deploys a new node cluster of a target service tool. Then, by sending an information acquisition request to the target service tool, the existing registration information in the service is obtained, so that the registration information of the service of the target service tool is obtained by sending an information acquisition request to the target service tool externally, thereby replacing the method of obtaining the registration information by creating a snapshot through an internal CLI instruction, so that the acquisition method is no longer limited. Then, the registration information to be migrated is screened out from the existing registration information in the service, and multiple registration information migration requests are constructed using the registration information to be migrated, so that the registration information obtained externally can be sent to the server node in the target service tool for registration, without the need for the original service tool to communicate with the migration target, and there is no need to worry about the failure of migration when the versions of the two are inconsistent, so that the migration of registration information is no longer restricted in these aspects. Therefore, the registration information migration request is finally sent to multiple client nodes in the new node cluster of the target service tool, and the registration information to be migrated is migrated to the new node cluster of the target service tool through each client node, so that the migration of registration information is realized through the client node, so that the pressure on the server node will not be too large.

[0101] Another embodiment of the present application provides a registration information migration device, such as Figure 5 As shown, it includes the following units:

[0102] The deployment unit 501 is used to deploy a new node cluster of the target service tool.

[0103] The information acquisition unit 502 is used to obtain the existing registration information in the service by sending an information acquisition request to the target service tool.

[0104] The screening unit 503 is used to screen the registration information to be migrated from the existing registration information in the service.

[0105] The constructing unit 504 is configured to construct multiple registration information migration requests using the registration information to be migrated.

[0106] The migration unit 505 is used to send a registration information migration request to multiple client nodes in the new node cluster of the target service tool, and migrate the registration information to be migrated to the new node cluster of the target service tool through each client node.

[0107] Optionally, in the registration information migration device provided in another embodiment of the present application, the deployment unit includes:

[0108] The cluster deployment unit is used to deploy a new node cluster of a target service tool of a client and server architecture including multiple server nodes and multiple client nodes in a container cluster management system.

[0109] The selection unit is used to select a main service node from each service end node. The number of the service end nodes is odd.

[0110] The configuration unit is used to enable persistence for each server node and disable persistence for each server node.

[0111] Optionally, in the registration information migration device provided in another embodiment of the present application, the information acquisition unit includes:

[0112] The list acquisition unit is used to obtain the service list by sending an information acquisition request in a hypertext transfer protocol format to an application program interface of a target service tool.

[0113] The traversal unit is used to traverse each server request in the service list and obtain the existing registration information in the service.

[0114] Optionally, in the registration information migration device provided in another embodiment of the present application, the following may be further included:

[0115] The backup unit is used to store and back up the registration information to be migrated through data files in a variety of preset formats.

[0116] Optionally, in the registration information migration device provided in another embodiment of the present application, the migration unit includes:

[0117] The category determination unit is used to determine, for each registration information migration request, the category of the registration information to be migrated requested by the registration information migration request.

[0118] The registration unit is used to send a registration information migration request to a client node in a load balancing server corresponding to the category of the registration information to be migrated requested to be migrated, and register the registration information to be migrated requested to be migrated in the new node cluster of the target service tool through the client node.

[0119] It should be noted that the specific working process of each unit provided in the above embodiments of the present application can refer to the implementation process of the corresponding steps in the above method embodiments, and will not be repeated here.

[0120] Another embodiment of the present application provides an electronic device, such as Figure 6 As shown, including:

[0121] Memory 601 and processor 602 .

[0122] The memory 601 is used to store programs.

[0123] The processor 602 is used to execute the program stored in the memory 601. When the program is executed, it is specifically used to implement the registration information migration method provided in any one of the above embodiments.

[0124] Another embodiment of the present application provides a computer storage medium for storing a computer program. When the computer program is executed, it is used to implement the registration information migration method provided in any one of the above embodiments.

[0125] Computer storage media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

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

[0127] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A registration information migration method, characterized in that: include: Deploy a new node cluster of the target service tool; Obtaining existing registration information in the service by sending an information acquisition request to the target service tool; Filtering the registration information to be migrated from the existing registration information in the service; Constructing multiple registration information migration requests using the registration information to be migrated; The registration information migration request is sent to multiple client nodes in the new node cluster of the target service tool, and the registration information to be migrated is migrated to the new node cluster of the target service tool through each of the client nodes.

2. The method according to claim 1, characterized in that The new node cluster of the deployment target service tool includes: Deploy a new node cluster of the target service tool of the client and server architecture including a plurality of server nodes and a plurality of client nodes in a container cluster management system; Selecting a main service node from each of the service end nodes; wherein the number of the service end nodes is odd; The persistence of each of the server nodes is turned on, and the persistence of each of the server nodes is turned off.

3. The method according to claim 1, characterized in that The step of obtaining the existing registration information in the service by sending an information acquisition request to the target service tool includes: Obtaining a service list by sending an information acquisition request in a hypertext transfer protocol format to an application program interface of the target service tool; Traverse each server request in the service list to obtain the existing registration information in the service.

4. The method according to claim 1, characterized in that: After constructing a plurality of registration information migration requests using the registration information to be migrated, the method further includes: The registration information to be migrated is stored and backed up via data files in a variety of preset formats.

5. The method according to claim 1, characterized in that The step of sending the registration information migration request to multiple client nodes in the new node cluster of the target service tool, and migrating the registration information to be migrated to the new node cluster of the target service tool through each of the client nodes, includes: For each registration information migration request, determining the category of the registration information to be migrated requested by the registration information migration request; The registration information migration request is sent to one of the client nodes in the load balancing server corresponding to the category of the registration information to be migrated that is requested to be migrated, and the registration information to be migrated requested to be migrated is registered in the new node cluster of the target service tool through the client node.

6. A registration information migration device, characterized in that: include: A deployment unit is used to deploy a new node cluster of the target service tool; An information acquisition unit, configured to obtain existing registration information in the service by sending an information acquisition request to the target service tool; A screening unit, used to screen the registration information to be migrated from the existing registration information in the service; A construction unit, configured to construct a plurality of registration information migration requests using the registration information to be migrated; The migration unit is used to send the registration information migration request to multiple client nodes in the new node cluster of the target service tool, and migrate the registration information to be migrated to the new node cluster of the target service tool through each of the client nodes.

7. The device according to claim 6, characterized in that The deployment unit includes: A cluster deployment unit, configured to deploy a new node cluster of the target service tool of a client and server architecture including a plurality of server nodes and a plurality of client nodes in a container cluster management system; A selection unit, configured to select a main service node from each of the service end nodes; wherein the number of the service end nodes is odd; The configuration unit is used to enable persistence of each of the server nodes and disable persistence of each of the server nodes.

8. The device according to claim 6, characterized in that The information acquisition unit comprises: A list acquisition unit, configured to obtain a service list by sending an information acquisition request in a hypertext transfer protocol format to an application program interface of the target service tool; The traversal unit is used to traverse each server request in the service list to obtain the existing registration information in the service.

9. An electronic device, characterized in that: include: Memory and processor; Wherein, the memory is used to store programs; The processor is used to execute the program, and when the program is executed, it is specifically used to implement the registration information migration method as described in any one of claims 1 to 5.

10. A computer storage medium, characterized in that: Used to store a computer program, which, when executed, is used to implement the registration information migration method as described in any one of claims 1 to 5.

Images