Cloud service migration information processing method, device, equipment, medium and product

Abstract

The disclosed embodiment discloses a cloud service migration information processing method, device, equipment, medium and product, the method comprising: obtaining a network access information file of a node to be migrated through a secure shell protocol (SSH) jump server; obtaining a target network access record of the node to be migrated according to the network access information file, and obtaining network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship according to the target network access record; generating a topology map corresponding to the system to be migrated according to the network topology information. The solution can obtain a topology map for display to the user without affecting the normal operation of the node, so that the user can more conveniently obtain the corresponding information by viewing the topology map, which helps to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the solution for migration, etc., thereby improving the user experience.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, and in particular to a cloud service migration information processing method, device, equipment, medium and product. Background Art

[0002] With the continuous popularization and development of cloud computing, cloud products developed using cloud computing technology have gained attention, making the types of cloud products more and more diverse. As a basic cloud computing service, cloud server (Elastic Compute Service, ECS) can be used as conveniently and efficiently as using water, electricity, gas and other resources, and is widely used. In recent years, more and more systems have been migrated to the cloud.

[0003] Before migrating the system to the cloud, it is necessary to investigate the resources of the system to be migrated. In related technologies, a corresponding client can be installed on the nodes of the system to be migrated, and the client can extract corresponding information from each node, and based on the acquired information, the resource overview of the system to be migrated can be displayed to the user, so that the user can plan a specific migration plan based on the displayed information.

[0004] In the above scheme, although the corresponding information of each node in the system to be migrated can be obtained, considering that installing the client on the node will increase the burden on the node and also require the node to give the user terminal higher permissions, it may interfere with the normal operation of the node and damage the user experience. Summary of the invention

[0005] In order to solve the problems in the related art, the embodiments of the present disclosure provide a cloud service migration information processing method, apparatus, device, medium and product.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for processing cloud service migration information, the method comprising:

[0007] Obtaining a network access information file of a node to be migrated through a secure shell protocol (SSH) jump server, where the node to be migrated belongs to the system to be migrated;

[0008] Acquire a target network access record of the node to be migrated according to the network access information file, and acquire network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record;

[0009] A topology map corresponding to the system to be migrated is generated according to the network topology information.

[0010] In an implementation of the present disclosure, before acquiring network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record, the method further includes:

[0011] Rewrite the loopback address in the target network access record, the Internet Protocol (IP) address of the container located in the node to be migrated, the intranet IP address of the node to be migrated, and the extranet IP address of the node to be migrated into the target intranet IP address of the node to be migrated;

[0012] The network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship is obtained according to the target network access record, including:

[0013] The network topology information is obtained according to the rewritten target network access record.

[0014] In an implementation of the present disclosure, before acquiring network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record, the method further includes:

[0015] Remove the network access record of the node to be migrated accessing itself and the network access record of the node to be migrated accessing the gateway from the target network access record;

[0016] The network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship is obtained according to the target network access record, including:

[0017] The network topology information is obtained according to the removed target network access records.

[0018] In one implementation of the present disclosure, obtaining network topology information indicating a network access relationship between a node to be migrated and other nodes and a direction of the network access relationship according to a target network access record includes:

[0019] In response to the target network access record including a first network access record in which the source port belongs to the node to be migrated and the target port belongs to the first other node, generating network topology information indicating that there is a network access relationship between the node to be migrated and the first other node in a direction from the node to be migrated to the first other node;

[0020] Or, in response to the target network access record including a second network access record in which the destination port belongs to the node to be migrated and the source port belongs to a second other node, network topology information is generated to indicate that a network access relationship exists between the node to be migrated and the second other node in a direction from the second other node to the node to be migrated.

[0021] In an implementation of the present disclosure, the topology map includes an IP address corresponding to each of the at least one node to be migrated.

[0022] In one implementation of the present disclosure, before generating a topology map according to the network topology information, the method further includes:

[0023] Obtain the process information file of the node to be migrated through the SSH jump server;

[0024] Obtaining the target process type of the process whose resource occupancy rate in the node to be migrated meets the resource occupancy rate requirement according to the process information file;

[0025] Generate a topology map based on network topology information, including:

[0026] A topology map is generated according to the network topology information and the target process type. The topology map includes a target process type identifier corresponding to each of the at least one node to be migrated. The target process type identifier is used to indicate the target process type of the corresponding node to be migrated.

[0027] In one implementation of the present disclosure, before generating a topology map according to the network topology information, the method further includes:

[0028] Obtain the network topology information to be updated;

[0029] Generate a topology map based on network topology information, including:

[0030] The network topology information to be updated is updated according to the network topology information, and a topology map is generated according to the updated network topology information to be updated.

[0031] In one implementation of the present disclosure, the method further includes:

[0032] Obtain the node system specification information file, process information file, and node system load snapshot of the node to be migrated through the SSH jump server;

[0033] Generate a serialization file according to at least one of a network access information file, a node system specification information file, a process information file, and a node system load snapshot;

[0034] Display topology diagram and serialized files;

[0035] Obtain the input review pass information, and upload the serialized file in response to the review pass information;

[0036] Or, obtain the input review and edit information, edit the serialized file according to the review and edit information, and upload the edited serialized file.

[0037] In a second aspect, an embodiment of the present disclosure provides a cloud service migration information processing device, the device comprising:

[0038] A first information acquisition module is configured to acquire a network access information file of a node to be migrated through a secure shell protocol (SSH) jump server, where the node to be migrated belongs to a system to be migrated;

[0039] A second information acquisition module is configured to acquire a target network access record of the node to be migrated according to the network access information file, and acquire network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record;

[0040] The topology map generation module is configured to generate a topology map corresponding to the system to be migrated according to the network topology information.

[0041] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising a memory and at least one processor; the memory is used to store one or more computer instructions, and the one or more computer instructions are executed by at least one processor to implement the method steps of the first aspect or any one of the implementation methods of the first aspect.

[0042] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium on which computer instructions are stored. When the computer instructions are executed by a processor, the method steps of the first aspect or any one of the implementation methods of the first aspect are implemented.

[0043] In a fifth aspect, a computer program product is provided in an embodiment of the present disclosure, comprising a computer program / instruction, which, when executed by a processor, implements the method steps of the first aspect or any one of the implementation methods of the first aspect.

[0044] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0045] In the above implementation, the network access information file of the node to be migrated belonging to the system to be migrated is obtained through the SSH jump server, wherein, since it is not necessary to install any client or other program on the node when obtaining the network access information file of the node to be migrated through the SSH jump server, and the required permissions are relatively low, it will not affect the normal operation of the node; the target network access record of the node to be migrated is obtained according to the network access information file, and the network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship is obtained according to the target network access record, and a topology map corresponding to the system to be migrated is generated according to the network topology information. Among them, when the obtained topology map is displayed, the user can clearly know the network access relationship between the node to be migrated and other nodes in the system to be migrated and the direction of the network access relationship, so that it can be more convenient to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the scheme for migration, etc. Therefore, the above solution can obtain a topology map corresponding to the system to be migrated for display to the user without affecting the normal operation of the node, so that the user can more conveniently obtain the corresponding information by viewing the topology map, which helps to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the plan for migration, etc., thereby improving the user experience.

[0046] In the above embodiment, the loopback address, the Internet Protocol (IP) address of the container in the node to be migrated, the intranet IP address of the node to be migrated, and the external IP address of the node to be migrated in the target network access record are rewritten into the target intranet IP address of the node to be migrated, and the network topology information is obtained according to the rewritten target network access record. Since in the target network access record, the loopback address, the Internet Protocol (IP) address of the container in the node to be migrated, the intranet IP address of the node to be migrated, and the external IP address of the node to be migrated all correspond to the node to be migrated, in order to avoid different node identifiers corresponding to the same node to be migrated appearing in the topology map when the topology map is generated according to the network topology information, by rewriting the above addresses in the target network access record into the target intranet IP address of the node to be migrated, it can be ensured that the same IP address corresponds to the same node in the rewritten target network access record, and it can be ensured that different node identifiers corresponding to the same node will not appear in the topology map when the topology map is generated according to the network topology information, thereby improving the accuracy of the generated topology map.

[0047] In the above embodiment, since the network access records of the node to be migrated accessing itself and the network access records of the node to be migrated accessing the gateway have low correlation with the services provided by the application corresponding to the system to be migrated, and have little impact on the type of cloud services required after migration and the solution used for migration, the network access records of the node to be migrated accessing itself and the network access records of the node to be migrated accessing the gateway are removed from the target network access records, and the network topology information is obtained based on the removed target network access records. The amount of data to be processed can be reduced without affecting the accuracy of the obtained network topology information.

[0048] In the above embodiment, when the target network access record includes a first network access record in which the source port belongs to the node to be migrated and the target port belongs to the first other node, it can be understood that network access to the first other node has been initiated from the node to be migrated, and therefore a network access relationship can be generated to indicate that a network access relationship exists between the node to be migrated and the first other node in a direction from the node to be migrated to the first other node; when the target network access record includes a second network access record in which the destination port belongs to the node to be migrated and the source port belongs to the second other node, it can be understood that network topology information of network access to the node to be migrated has been initiated from the second other node, and therefore network topology information can be generated to indicate that a network access relationship exists between the node to be migrated and the second other node in a direction from the second other node to the node to be migrated, thereby improving the accuracy of the generated network topology information.

[0049] In the above implementation, by making the topology map include the IP address corresponding to each of the at least one node to be migrated, it is convenient for the user to determine the corresponding identity of the node to be migrated according to the IP address, thereby improving the user experience.

[0050] In the above implementation, considering that when different types of processes have high resource occupancy rates on the node to be migrated, there are certain differences in the cloud services used after the node to be migrated is migrated to the cloud, and there are corresponding differences in the migration schemes adopted in the migration process. Therefore, the process information file of the node to be migrated is obtained through the SSH jump server, and the target process type of the process whose resource occupancy rate meets the resource occupancy rate requirements in the node to be migrated is obtained according to the process information file, and a topology map is generated according to the network topology information and the target process type. The topology map includes a target process type identifier corresponding to each node to be migrated in at least one node to be migrated, so that the user can clearly know the type of target process whose resource occupancy rate meets the resource occupancy rate requirements on each node to be migrated by viewing the displayed topology map, so as to select the corresponding cloud service and migration scheme, thereby improving the user experience.

[0051] In the above implementation, by obtaining the network topology information to be updated, updating the network topology information to be updated according to the network topology information, and generating a topology map according to the updated network topology information to be updated, the amount of data required to be processed when generating the topology map can be reduced, thereby improving the efficiency of generating the topology map.

[0052] In the above implementation, the node system specification information file, process information file, and node system load snapshot of the node to be migrated are obtained through an SSH jump server, and a serialized file is generated according to at least one of the network access information file, the node system specification information file, the process information file, and the node system load snapshot, and a topology map and a serialized file are displayed. The input review approval information is obtained, and the serialized file is uploaded in response to the review approval information; or, the input review and editing information is obtained, the serialized file is edited according to the review and editing information, and the edited serialized file is uploaded. This can facilitate the recommendation of corresponding cloud services and at least one of the migration solutions for migrating the node to be migrated to the user based on the serialized file, thereby improving the user experience.

[0053] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Other features, objectives and advantages of the present disclosure will become more apparent through the following detailed description of non-limiting embodiments in conjunction with the accompanying drawings. In the accompanying drawings:

[0055] Figure 1 A flowchart of a method for processing cloud service migration information according to an embodiment of the present disclosure is shown.

[0056] Figure 2 A schematic topological diagram according to an embodiment of the present disclosure is shown.

[0057] Figure 3 A schematic topological diagram according to an embodiment of the present disclosure is shown.

[0058] Figure 4 A structural block diagram of a cloud service migration information processing device according to an embodiment of the present disclosure is shown.

[0059] Figure 5 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0060] Figure 6 It is a schematic diagram of the structure of a computer system suitable for implementing the method according to the embodiment of the present disclosure. DETAILED DESCRIPTION

[0061] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. In addition, for the sake of clarity, parts not related to the description of the exemplary embodiments are omitted in the accompanying drawings.

[0062] In the present disclosure, it should be understood that terms such as "include" or "have" are intended to indicate the presence of labels, numbers, steps, behaviors, components, parts, or combinations thereof disclosed in the present specification, and are not intended to exclude the possibility that one or more other labels, numbers, steps, behaviors, components, parts, or combinations thereof exist or are added.

[0063] It should also be noted that, in the absence of conflict, the embodiments and labels in the embodiments of the present disclosure can be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0064] In order to investigate the resources of the system to be migrated before migrating the system to the cloud, the inventors of the present disclosure considered the following solutions:

[0065] In the related art, a corresponding client can be installed on the nodes of the system to be migrated, and the corresponding information extracted from each node by the client can be displayed to the user based on the acquired information to display the resource profile of the system to be migrated, so that the user can plan a specific migration plan based on the displayed information.

[0066] Disadvantages of this solution: When the client installed on the node is working, it will occupy part of the node's processing resources, thereby increasing the node's burden. In addition, since the node needs to grant the user client higher permissions, and some nodes have strict permission management, conflicts are prone to occur. Therefore, installing the client on the node may interfere with the normal operation of the node and damage the user experience.

[0067] Considering the shortcomings of the above schemes, the inventors of the present disclosure have proposed a new scheme: obtaining the network access information file of the node to be migrated belonging to the system to be migrated through the Secure Shell (SSH) jump server, wherein, since when obtaining the network access information file of the node to be migrated through the SSH jump server, it is not necessary to install any client or other program on the node, and the required permissions are relatively low, which will not affect the normal operation of the node; obtaining the target network access record of the node to be migrated according to the network access information file, and obtaining the network topology information for indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship according to the target network access record, and generating a topology map corresponding to the system to be migrated according to the network topology information. Among them, when the obtained topology map is displayed, the user can clearly know the network access relationship between the node to be migrated and other nodes in the system to be migrated and the direction of the network access relationship, so that it is more convenient to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the scheme for migration, etc. Therefore, the above solution can obtain a topology map corresponding to the system to be migrated for display to the user without affecting the normal operation of the node, so that the user can more conveniently obtain the corresponding information by viewing the topology map, which helps to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the plan for migration, etc., thereby improving the user experience.

[0068] In order to solve the above problems, the present disclosure proposes a cloud service migration information processing method, device, equipment, medium and product.

[0069] Figure 1 FIG. 1 is a flow chart showing a method for processing cloud service migration information according to an embodiment of the present disclosure. Figure 1 As shown, the cloud service migration information processing method includes steps S101-S103.

[0070] In step S101, a network access information file of a node to be migrated is obtained through a secure shell protocol (SSH) jump server.

[0071] Among them, the node to be migrated belongs to the system to be migrated;

[0072] In step S102, a target network access record of the node to be migrated is obtained according to the network access information file, and network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship is obtained according to the target network access record.

[0073] In step S103, a topology map corresponding to the system to be migrated is generated according to the network topology information.

[0074] In an implementation of the present disclosure, the system to be migrated may be understood as a system for carrying applications that need to be migrated, and the system to be migrated may include multiple nodes.

[0075] In one embodiment of the present disclosure, a node can be understood as a device that carries corresponding data and applications and has data processing functions. A node may include, but is not limited to, a personal computer (PC), a tablet computer, a laptop computer, a mobile communication terminal, a wearable device, a voice interaction device, and a server. Among them, a server can be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers.

[0076] In one implementation of the present disclosure, an SSH jump server can be understood as a physical machine or virtual machine that can log in to the node to be migrated through the secure shell protocol, thereby monitoring the node to be migrated. Among them, the virtual machine can be understood as a virtualization layer running on a virtualization platform. Exemplarily, in a cloud computing platform, a virtual machine can be one or more independent hosts (i.e., cloud hosts) or one or more independent servers (i.e., cloud servers) divided out on a cluster server by the virtualization technology; in other virtualization systems or platforms, a virtual machine can be one or more virtual hosts implemented using the virtualization technology on one or more physical hosts, or can be one or more virtual dedicated servers implemented using the virtualization technology on one or more physical servers. A physical machine can be understood as the name of a physical computer relative to a virtual machine. A physical machine can provide a hardware environment for a virtual machine.

[0077] In one implementation of the present disclosure, the network access information file can be understood as a network access record for indicating the node to be migrated, and the network access record may include the destination Internet Protocol Address (IP) address, source IP address, destination port number and source port number of at least one network access of the node to be migrated.

[0078] In one implementation of the present disclosure, obtaining the network access information file of the node to be migrated through the SSH jump server can be to read the network access information file from the target file directory of the node to be migrated through the SSH jump server. Exemplarily, when the node to be migrated runs under the Linux system, the target file directory can be the / proc directory.

[0079] In one implementation of the present disclosure, the network topology information may be understood as being used to indicate the network access relationship between the node to be migrated and other nodes, and the direction of the network access relationship, that is, which node in the network access relationship actively initiates the network access.

[0080] In one implementation of the present disclosure, a topology map corresponding to the system to be migrated is generated based on network topology information. It can be understood that the generated topology map can display the node identifier of at least one node to be migrated, the node identifier of at least one other node, the network access relationship between the node to be migrated and the other nodes, and which node in the network access relationship actively initiates the network access, that is, the direction of the network access relationship.

[0081] For example, Figure 2 Schematic topological diagram according to an embodiment of the present disclosure is shown. Figure 2 As shown, the topology map 100 includes multiple nodes, which may include a node identifier 101 to be migrated corresponding to each node to be migrated belonging to the system to be migrated and other node identifiers 102 corresponding to other nodes; wherein, if it is determined based on the network topology information that the node to be migrated has actively initiated network access to other nodes, then in the topology map 100, the above-mentioned network access relationship is represented by a dotted arrow pointing from the node identifier 101 to the other node identifier 102; if it is determined based on the network topology information that other nodes have actively initiated network access to the node to be migrated, then in the topology map 100, the above-mentioned network access relationship is represented by a dotted arrow pointing from the other node identifier 102 to the node identifier 101 to be migrated.

[0082] In the above implementation, the network access information file of the node to be migrated belonging to the system to be migrated is obtained through the SSH jump server, wherein, since it is not necessary to install any client or other program on the node when obtaining the network access information file of the node to be migrated through the SSH jump server, and the required permissions are relatively low, it will not affect the normal operation of the node; the target network access record of the node to be migrated is obtained according to the network access information file, and the network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship is obtained according to the target network access record, and a topology map corresponding to the system to be migrated is generated according to the network topology information. Among them, when the obtained topology map is displayed, the user can clearly know the network access relationship between the node to be migrated and other nodes in the system to be migrated and the direction of the network access relationship, so that it can be more convenient to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the scheme for migration, etc. Therefore, the above solution can obtain a topology map corresponding to the system to be migrated for display to the user without affecting the normal operation of the node, so that the user can more conveniently obtain the corresponding information by viewing the topology map, which helps to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the plan for migration, etc., thereby improving the user experience.

[0083] In an implementation of the present disclosure, before obtaining network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship according to the target network access record, the method further includes the following steps:

[0084] Rewrite the loopback address in the target network access record, the Internet Protocol (IP) address of the container located in the node to be migrated, the intranet IP address of the node to be migrated, and the extranet IP address of the node to be migrated into the target intranet IP address of the node to be migrated;

[0085] In step S102, obtaining network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship according to the target network access record can be achieved by the following steps:

[0086] The network topology information is obtained according to the rewritten target network access record.

[0087] In an implementation of the present disclosure, the target intranet IP address can be understood as any intranet address of the node to be migrated.

[0088] In the above embodiment, the loopback address, the Internet Protocol (IP) address of the container in the node to be migrated, the intranet IP address of the node to be migrated, and the external IP address of the node to be migrated in the target network access record are rewritten into the target intranet IP address of the node to be migrated, and the network topology information is obtained according to the rewritten target network access record. Since in the target network access record, the loopback address, the Internet Protocol (IP) address of the container in the node to be migrated, the intranet IP address of the node to be migrated, and the external IP address of the node to be migrated all correspond to the node to be migrated, in order to avoid different node identifiers corresponding to the same node to be migrated appearing in the topology map when the topology map is generated according to the network topology information, by rewriting the above addresses in the target network access record into the target intranet IP address of the node to be migrated, it can be ensured that the same IP address corresponds to the same node in the rewritten target network access record, and it can be ensured that different node identifiers corresponding to the same node will not appear in the topology map when the topology map is generated according to the network topology information, thereby improving the accuracy of the generated topology map.

[0089] In an implementation of the present disclosure, before obtaining network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship according to the target network access record, the method further includes the following steps:

[0090] Remove the network access record of the node to be migrated accessing itself and the network access record of the node to be migrated accessing the gateway from the target network access record;

[0091] In step S102, obtaining network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship according to the target network access record can be achieved by the following steps:

[0092] The network topology information is obtained according to the removed target network access records.

[0093] In the above embodiment, since the network access records of the node to be migrated accessing itself and the network access records of the node to be migrated accessing the gateway have low correlation with the services provided by the application corresponding to the system to be migrated, and have little impact on the type of cloud services required after migration and the solution used for migration, the network access records of the node to be migrated accessing itself and the network access records of the node to be migrated accessing the gateway are removed from the target network access records, and the network topology information is obtained based on the removed target network access records. The amount of data to be processed can be reduced without affecting the accuracy of the obtained network topology information.

[0094] In one implementation of the present disclosure, in step S102, obtaining network topology information indicating a network access relationship between a node to be migrated and other nodes and a direction of the network access relationship according to a target network access record can be implemented by the following steps:

[0095] In response to the target network access record including a first network access record in which the source port belongs to the node to be migrated and the target port belongs to the first other node, generating network topology information indicating that there is a network access relationship between the node to be migrated and the first other node in a direction from the node to be migrated to the first other node;

[0096] Or, in response to the target network access record including a second network access record in which the destination port belongs to the node to be migrated and the source port belongs to a second other node, network topology information is generated to indicate that a network access relationship exists between the node to be migrated and the second other node in a direction from the second other node to the node to be migrated.

[0097] In the above embodiment, when the target network access record includes a first network access record in which the source port belongs to the node to be migrated and the target port belongs to the first other node, it can be understood that network access to the first other node has been initiated from the node to be migrated, and therefore a network access relationship can be generated to indicate that a network access relationship exists between the node to be migrated and the first other node in a direction from the node to be migrated to the first other node; when the target network access record includes a second network access record in which the destination port belongs to the node to be migrated and the source port belongs to the second other node, it can be understood that network topology information of network access to the node to be migrated has been initiated from the second other node, and therefore network topology information can be generated to indicate that a network access relationship exists between the node to be migrated and the second other node in a direction from the second other node to the node to be migrated, thereby improving the accuracy of the generated network topology information.

[0098] In an implementation of the present disclosure, the topology map includes an IP address corresponding to each of the at least one node to be migrated.

[0099] Exemplarily, the topology map may include an IP address corresponding to each node to be migrated, and the IP address is located below the node identifier to be migrated corresponding to each node to be migrated.

[0100] In the above implementation, by making the topology map include the IP address corresponding to each of the at least one node to be migrated, it is convenient for the user to determine the corresponding identity of the node to be migrated according to the IP address, thereby improving the user experience.

[0101] In one implementation of the present disclosure, before generating a topology map according to the network topology information, the method further includes the following steps:

[0102] Obtain the process information file of the node to be migrated through the SSH jump server;

[0103] Obtaining the target process type of the process whose resource occupancy rate in the node to be migrated meets the resource occupancy rate requirement according to the process information file;

[0104] Generating a topology map based on network topology information can be achieved through the following steps:

[0105] A topology map is generated according to the network topology information and the target process type. The topology map includes a target process type identifier corresponding to each of the at least one node to be migrated. The target process type identifier is used to indicate the target process type of the corresponding node to be migrated.

[0106] In one implementation of the present disclosure, the process information file can be understood as an identifier used to indicate some or all processes on the node to be migrated, as well as at least one of the commands executed by some or all processes on the node to be migrated, the capacity of the memory occupied, and the CPU occupancy rate.

[0107] In one implementation of the present disclosure, the resource occupancy rate can be understood as the ratio of the memory capacity occupied by the process to the total memory capacity of the node, or can be understood as the CPU occupancy rate of the process, or can be understood as a value calculated based on the above two.

[0108] In one implementation of the present disclosure, process types may include traffic (forwarding) type, service-related type, database-related type, big data-related type, etc., wherein a process with a traffic (forwarding) type can be understood as being used to forward data traffic, a process with a service-related type can be understood as being used to process service data, a process with a database-related type can be understood as being used to read and write data in a database, and a process with a big data-related type can be understood as being used to process data related to big data services.

[0109] In one implementation of the present disclosure, the target process type of the process whose resource occupancy rate meets the resource occupancy rate requirement can be understood as the process type whose resource occupancy rate is greater than or equal to the resource occupancy rate threshold is the target process type, and can also be understood as, among the resource occupancy rates corresponding to multiple process types, the resource occupancy rate corresponding to the target process type is the largest; or it can also be understood as, among the resource occupancy rates corresponding to multiple process types, the resource occupancy rate corresponding to the target process type is the largest, and the resource occupancy rate corresponding to the target process type is greater than or equal to the resource occupancy rate threshold.

[0110] In one implementation of the present disclosure, the process type identifier can be understood as an identifier for distinguishing different process types. In the topology diagram, the process type identifier corresponding to each node to be migrated can be marked in a position corresponding to the node to be migrated, such as in the node identifier of the node to be migrated or around the node identifier.

[0111] For example, Figure 3 Schematic topological diagram according to an embodiment of the present disclosure is shown. Figure 3 As shown, when the process type of the target process type of a node to be migrated is a traffic (forwarding) type, the node to be migrated identifier 110 corresponding to the node to be migrated includes a traffic (forwarding) type identifier 111 corresponding to the traffic (forwarding) type; when the process type of the target process type of a node to be migrated is a database-related type, the node to be migrated identifier 120 corresponding to the node to be migrated includes a database-related type identifier 121 corresponding to the database-related type; when the process type of the target process type of a node to be migrated is a service-related type, the node to be migrated identifier 130 corresponding to the node to be migrated includes a service-related type identifier 131 corresponding to the service-related type.

[0112] In the above implementation, considering that when different types of processes have high resource occupancy rates on the node to be migrated, there are certain differences in the cloud services used after the node to be migrated is migrated to the cloud, and there are corresponding differences in the migration schemes adopted in the migration process. Therefore, the process information file of the node to be migrated is obtained through the SSH jump server, and the target process type of the process whose resource occupancy rate meets the resource occupancy rate requirements in the node to be migrated is obtained according to the process information file, and a topology map is generated according to the network topology information and the target process type. The topology map includes a target process type identifier corresponding to each node to be migrated in at least one node to be migrated, so that the user can clearly know the type of target process whose resource occupancy rate meets the resource occupancy rate requirements on each node to be migrated by viewing the displayed topology map, so as to select the corresponding cloud service and migration scheme, thereby improving the user experience.

[0113] In an implementation of the present disclosure, before generating a topology map according to the network topology information, the method further includes the following steps:

[0114] Obtain the network topology information to be updated;

[0115] Generating a topology map based on network topology information can be achieved through the following steps:

[0116] The network topology information to be updated is updated according to the network topology information, and a topology map is generated according to the updated network topology information to be updated.

[0117] In an implementation of the present disclosure, the network topology information to be updated may be understood as information obtained in advance for indicating a network access relationship between at least one node in the system to be migrated and other nodes and the direction of the network access relationship.

[0118] In the above implementation, by obtaining the network topology information to be updated, updating the network topology information to be updated according to the network topology information, and generating a topology map according to the updated network topology information to be updated, the amount of data required to be processed when generating the topology map can be reduced, thereby improving the efficiency of generating the topology map.

[0119] In one implementation of the present disclosure, the method further includes the following steps:

[0120] Obtain the node system specification information file, process information file, and node system load snapshot of the node to be migrated through the SSH jump server;

[0121] Generate a serialization file according to at least one of a network access information file, a node system specification information file, a process information file, and a node system load snapshot;

[0122] Display topology diagram and serialized files;

[0123] Obtain the input review pass information, and upload the serialized file in response to the review pass information;

[0124] Or, obtain the input review and edit information, edit the serialized file according to the review and edit information, and upload the edited serialized file.

[0125] In one implementation of the present disclosure, the node system specification information file can be understood as a file used to indicate the operating system information, hardware system information, etc. of the corresponding node. Exemplarily, the node system specification information file can be used to indicate at least one of the operating system kernel version, number of processor cores, processor frequency, memory capacity, disk space, and network card bandwidth of the corresponding node.

[0126] In one implementation of the present disclosure, the node system load snapshot can be understood as indicating the load of the operating system and hardware system of the corresponding node at at least one moment. Exemplarily, the node system load snapshot can be used to indicate at least one of the actual occupied capacity of the memory, the actual occupied space of the disk, the read and write speed of the disk, the actual occupancy rate of the CPU, the number of tasks, the actual occupied bandwidth, and the network read and write speed of the corresponding node at at least one moment.

[0127] In one implementation of the present disclosure, a serialized file may be understood as a network access information file, a node system specification information file, a process information file, and a node system load snapshot that indicate part or all of the information that affects the cloud services used by the node to be migrated after it is migrated to the cloud and the migration scheme used for the migration.

[0128] In an implementation of the present disclosure, based on the uploaded serialized file, at least one of a corresponding cloud service and a migration solution for migrating the node to be migrated may be recommended.

[0129] In the above implementation, the node system specification information file, process information file, and node system load snapshot of the node to be migrated are obtained through an SSH jump server, and a serialized file is generated according to at least one of the network access information file, the node system specification information file, the process information file, and the node system load snapshot, and a topology map and a serialized file are displayed. The input review approval information is obtained, and the serialized file is uploaded in response to the review approval information; or, the input review and editing information is obtained, the serialized file is edited according to the review and editing information, and the edited serialized file is uploaded. This can facilitate the recommendation of corresponding cloud services and at least one of the migration solutions for migrating the node to be migrated to the user based on the serialized file, thereby improving the user experience.

[0130] The following reference Figure 4A cloud service migration information processing device according to an embodiment of the present disclosure is described. Figure 4 A structural block diagram of a cloud service migration information processing device according to an embodiment of the present disclosure is shown.

[0131] like Figure 4 As shown, the cloud service migration information processing device 200 includes:

[0132] The first information acquisition module 201 is configured to acquire a network access information file of a node to be migrated through a secure shell protocol (SSH) jump server, where the node to be migrated belongs to a system to be migrated;

[0133] The second information acquisition module 202 is configured to acquire a target network access record of the node to be migrated according to the network access information file, and acquire network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record;

[0134] The topology map generating module 203 is configured to generate a topology map corresponding to the system to be migrated according to the network topology information.

[0135] According to the technical solution provided by the embodiment of the present disclosure, a network access information file of a node to be migrated belonging to a system to be migrated is obtained through a Secure Shell (SSH) jump server, wherein, since it is not necessary to install any client or other program on the node when obtaining the network access information file of the node to be migrated through the SSH jump server, and the required permissions are relatively low, it will not affect the normal operation of the node; the target network access record of the node to be migrated is obtained according to the network access information file, and the network topology information used to indicate the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship is obtained according to the target network access record, and a topology map corresponding to the system to be migrated is generated according to the network topology information. Among them, when the obtained topology map is displayed, the user can clearly know the network access relationship between the node to be migrated and other nodes in the system to be migrated and the direction of the network access relationship, so that it can be more convenient to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the scheme for migration, etc. Therefore, the above solution can obtain a topology map corresponding to the system to be migrated for display to the user without affecting the normal operation of the node, so that the user can more conveniently obtain the corresponding information by viewing the topology map, which helps to determine the nodes that need to be migrated in the system to be migrated, the type of cloud service required after migration, and the plan for migration, etc., thereby improving the user experience.

[0136] Those skilled in the art will understand that referring to Figure 4 The technical solution described can be compared with the above Figure 1The corresponding embodiments are combined to have Figure 1 The technical effects achieved by the corresponding embodiments. For details, please refer to Figure 1 The specific contents of the description of the corresponding embodiments will not be repeated here.

[0137] Figure 5 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0138] The present disclosure also provides an electronic device, such as Figure 5 As shown, the electronic device 300 includes at least one processor 301. And a memory 302 that is communicatively connected to the at least one processor 301. The memory 302 stores instructions that can be executed by the at least one processor 301, and the instructions can be executed by the at least one processor 301 to implement the following steps:

[0139] In a first aspect, an embodiment of the present disclosure provides a method for processing cloud service migration information, the method comprising:

[0140] Obtaining a network access information file of a node to be migrated through a secure shell protocol (SSH) jump server, where the node to be migrated belongs to the system to be migrated;

[0141] Acquire a target network access record of the node to be migrated according to the network access information file, and acquire network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record;

[0142] A topology map corresponding to the system to be migrated is generated according to the network topology information.

[0143] In an implementation of the present disclosure, before acquiring network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record, the method further includes:

[0144] Rewrite the loopback address in the target network access record, the Internet Protocol (IP) address of the container located in the node to be migrated, the intranet IP address of the node to be migrated, and the extranet IP address of the node to be migrated into the target intranet IP address of the node to be migrated;

[0145] The network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship is obtained according to the target network access record, including:

[0146] The network topology information is obtained according to the rewritten target network access record.

[0147] In an implementation of the present disclosure, before acquiring network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record, the method further includes:

[0148] Remove the network access record of the node to be migrated accessing itself and the network access record of the node to be migrated accessing the gateway from the target network access record;

[0149] The network topology information indicating the network access relationship between the node to be migrated and other nodes and the direction of the network access relationship is obtained according to the target network access record, including:

[0150] The network topology information is obtained according to the removed target network access records.

[0151] In one implementation of the present disclosure, obtaining network topology information indicating a network access relationship between a node to be migrated and other nodes and a direction of the network access relationship according to a target network access record includes:

[0152] In response to the target network access record including a first network access record in which the source port belongs to the node to be migrated and the target port belongs to the first other node, generating network topology information indicating that there is a network access relationship between the node to be migrated and the first other node in a direction from the node to be migrated to the first other node;

[0153] Or, in response to the target network access record including a second network access record in which the destination port belongs to the node to be migrated and the source port belongs to a second other node, network topology information is generated to indicate that a network access relationship exists between the node to be migrated and the second other node in a direction from the second other node to the node to be migrated.

[0154] In an implementation of the present disclosure, the topology map includes an IP address corresponding to each of the at least one node to be migrated.

[0155] In one implementation of the present disclosure, before generating a topology map according to the network topology information, the method further includes:

[0156] Obtain the process information file of the node to be migrated through the SSH jump server;

[0157] Obtaining the target process type of the process whose resource occupancy rate in the node to be migrated meets the resource occupancy rate requirement according to the process information file;

[0158] Generate a topology map based on network topology information, including:

[0159] A topology map is generated according to the network topology information and the target process type. The topology map includes a target process type identifier corresponding to each of the at least one node to be migrated. The target process type identifier is used to indicate the target process type of the corresponding node to be migrated.

[0160] In one implementation of the present disclosure, before generating a topology map according to the network topology information, the method further includes:

[0161] Obtain the network topology information to be updated;

[0162] Generate a topology map based on network topology information, including:

[0163] The network topology information to be updated is updated according to the network topology information, and a topology map is generated according to the updated network topology information to be updated.

[0164] In one implementation of the present disclosure, the method further includes:

[0165] Obtain the node system specification information file, process information file, and node system load snapshot of the node to be migrated through the SSH jump server;

[0166] Generate a serialization file according to at least one of a network access information file, a node system specification information file, a process information file, and a node system load snapshot;

[0167] Display topology diagram and serialized files;

[0168] Obtain the input review pass information, and upload the serialized file in response to the review pass information;

[0169] Or, obtain the input review and edit information, edit the serialized file according to the review and edit information, and upload the edited serialized file.

[0170] like Figure 6 As shown, the computer system 400 includes a processing unit 401, which can perform various processes in the embodiments shown in the above figures according to the program stored in the read-only memory (ROM) 402 or the program loaded from the storage part 408 to the random access memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the system 400 are also stored. The CPU 401, the ROM 402, and the RAM 403 are connected to each other through a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0171] The following components are connected to the I / O interface 405: an input section 406 including a keyboard, a mouse, etc. An output section 407 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc. A storage section 408 including a hard disk, etc. And a communication section 409 including a network interface card such as a LAN card, a modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 410 as needed, so that the computer program read therefrom is installed into the storage section 408 as needed. Among them, the processing unit 401 can be implemented as a processing unit such as a CPU, a GPU, a TPU, an FPGA, an NPU, etc.

[0172] In particular, according to an embodiment of the present disclosure, the method described above with reference to the accompanying drawings can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program tangibly contained on a readable medium thereof, and the computer program includes a program code for executing the method in the accompanying drawings. In such an embodiment, the computer program can be downloaded and installed from a network through the communication part 409, and / or installed from a removable medium 411. For example, an embodiment of the present disclosure includes a readable storage medium on which computer instructions are stored, and when the computer instructions are executed by a processor, the program code for executing the method in the accompanying drawings is implemented.

[0173] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the road map or block diagram can represent a part of a module, program segment or code, and the part of the module, program segment or code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a different order from the order marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0174] The units or modules involved in the embodiments described in the present disclosure may be implemented by software or hardware. The units or modules described may also be set in a processor, and the names of these units or modules do not constitute limitations on the units or modules themselves in some cases.

[0175] As another aspect, the present disclosure further provides a computer-readable storage medium, which may be a computer-readable storage medium included in the node in the above-mentioned embodiment. It may also be a computer-readable storage medium that exists independently and is not assembled into a device. The computer-readable storage medium stores one or more programs, and the programs are used by one or more processors to execute the method described in the present disclosure.

[0176] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present disclosure is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other.

Claims

1. A method for processing cloud service migration information, wherein: The method comprises: Reading a network access information file of the node to be migrated from a target file directory of the node to be migrated through a secure shell protocol (SSH) jump server, wherein the node to be migrated belongs to the system to be migrated; Acquire a target network access record of the node to be migrated according to the network access information file, and acquire network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record; A topology map corresponding to the system to be migrated is generated according to the network topology information.

2. The cloud service migration information processing method according to claim 1, wherein: Before acquiring network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record, the method further includes: Rewrite the loopback address in the target network access record, the Internet Protocol (IP) address of the container located in the node to be migrated, the intranet IP address of the node to be migrated, and the extranet IP address of the node to be migrated into the target intranet IP address of the node to be migrated; The acquiring, according to the target network access record, network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship includes: The network topology information is obtained according to the rewritten target network access record.

3. The cloud service migration information processing method according to claim 1, wherein: Before acquiring network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record, the method further includes: Remove the network access record of the node to be migrated accessing itself and the network access record of the node to be migrated accessing the gateway from the target network access record; The acquiring, according to the target network access record, network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship includes: The network topology information is obtained according to the removed target network access record.

4. The cloud service migration information processing method according to claim 1, wherein: The acquiring, according to the target network access record, network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship includes: In response to the target network access record including a first network access record in which a source port belongs to the node to be migrated and a target port belongs to a first other node, generating network topology information indicating that there is a network access relationship between the node to be migrated and the first other node in a direction from the node to be migrated to the first other node; Or, in response to the target network access record including a second network access record in which the destination port belongs to the node to be migrated and the source port belongs to a second other node, network topology information is generated to indicate that there is a network access relationship between the node to be migrated and the second other node in a direction from the second other node to the node to be migrated.

5. The cloud service migration information processing method according to any one of claims 1 to 4, wherein: The topology map includes an IP address corresponding to each of the at least one node to be migrated.

6. The cloud service migration information processing method according to any one of claims 1 to 4, wherein: Before generating a topology map according to the network topology information, the method further includes: Obtaining the process information file of the node to be migrated through the SSH jump server; Acquire, according to the process information file, a target process type of a process whose resource occupancy rate in the node to be migrated meets a resource occupancy rate requirement; The generating a topology map according to the network topology information includes: The topology map is generated according to the network topology information and the target process type, wherein the topology map includes a target process type identifier corresponding to each node to be migrated in at least one node to be migrated, and the target process type identifier is used to indicate the target process type of the corresponding node to be migrated.

7. The cloud service migration information processing method according to any one of claims 1 to 4, wherein: Before generating a topology map according to the network topology information, the method further includes: Obtain the network topology information to be updated; The generating a topology map according to the network topology information includes: The network topology information to be updated is updated according to the network topology information, and the topology map is generated according to the updated network topology information to be updated.

8. The cloud service migration information processing method according to any one of claims 1 to 4, wherein: The method further comprises: Obtaining the node system specification information file, process information file, and node system load snapshot of the node to be migrated through the SSH jump server; Generate a serialization file according to at least one of the network access information file, the node system specification information file, the process information file, and the node system load snapshot; Displaying the topology diagram and the serialized file; Obtaining input review passing information, and uploading the serialized file in response to the review passing information; Or, obtain input review and editing information, edit the serialization file according to the review and editing information, and upload the edited serialization file.

9. A cloud service migration information processing device, wherein: The device comprises: A first information acquisition module is configured to read a network access information file of a node to be migrated from a target file directory of the node to be migrated through a secure shell protocol (SSH) jump server, wherein the node to be migrated belongs to a system to be migrated; A second information acquisition module is configured to acquire a target network access record of the node to be migrated according to the network access information file, and acquire network topology information indicating a network access relationship between the node to be migrated and other nodes and a direction of the network access relationship according to the target network access record; The topology map generating module is configured to generate a topology map corresponding to the system to be migrated according to the network topology information.

10. An electronic device comprising a memory and at least one processor; wherein: The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the at least one processor to implement the method steps described in any one of claims 1-8.

11. A computer-readable storage medium having computer instructions stored thereon, wherein: When the computer instructions are executed by a processor, the method steps described in any one of claims 1 to 8 are implemented.

12. A computer program product comprising a computer program / instructions, wherein: When the computer program / instructions are executed by a processor, the method steps described in any one of claims 1 to 8 are implemented.

Images