CN116319354B

CN116319354B - Network topology updating method based on cloud instance migration

Info

Publication number: CN116319354B
Application number: CN202310111525.1A
Authority: CN
Inventors: 朱丽品; 杨其
Original assignee: Hangzhou Youyun Technology Co ltd
Current assignee: Hangzhou Youyun Technology Co ltd
Priority date: 2023-01-30
Filing date: 2023-01-30
Publication date: 2023-11-28
Anticipated expiration: 2043-01-30
Also published as: CN116319354A

Abstract

The specification provides a network topology updating method based on cloud instance migration. The cloud computing network comprises a plurality of available areas which support mutual communication; the method comprises the following steps: the method comprises the steps that a summary node corresponding to any one of a plurality of available areas receives a first migration notification message sent by a source host and used for notifying each summary node that a target cloud instance migrates from the source host to a target host; according to the identification information of the target cloud instance included in the first migration notification message, cloud instance information of the target cloud instance maintained by the summary node is found, and the IP address of the host where the target cloud instance is located included in the cloud instance information of the target cloud instance is updated from the IP address of the source host to the IP address of the target host; and sending a second migration notification message for notifying each host machine that the target cloud instance is migrated to each host machine located in the available area, so that each host machine updates the instance information of the target cloud instance maintained by each host machine.

Description

Network topology updating method based on cloud instance migration

Technical Field

One or more embodiments of the present disclosure relate to the field of cloud computing technologies, and in particular, to a network topology updating method based on cloud instance migration.

Background

In a cloud computing network, cloud instances running on one host may be migrated to another host. For example, if there are fewer cloud instances running on two hosts, then the cloud instance running on one host may be migrated to the other host to perform resource integration on the cloud computing resources; further, the host machine which does not run the cloud instance can be powered down, so that resources are saved. For another example, if one host fails, resulting in that the cloud instance running on that host is also unable to provide service normally, the cloud instance running on that host may be migrated to other non-failed hosts.

After migrating a cloud instance running on one host to another host, a change in the network topology of the virtualized network may result. In such a scenario, in order to reduce the service interruption time of the cloud instance where migration occurs, it is necessary to improve the network topology update efficiency of the virtualized network, that is, it is necessary for the virtualized network to accelerate convergence.

However, in the related art, in the process of cloud instance migration, the security inside the network cannot be ensured while the network convergence is quickened.

Disclosure of Invention

The application provides a network topology updating method based on cloud instance migration, wherein a cloud computing network comprises a plurality of available areas supporting mutual communication; each of the plurality of available areas is respectively configured with a corresponding summary node; each summary node maintains instance information of cloud instances running on hosts located in the plurality of available areas; each host maintains instance information of cloud instances running on the host and instance information of other cloud instances communicable with the cloud instances running on the host; the cloud instance information comprises identification information of the cloud instance and an IP address of a host machine where the cloud instance is located;

the method is applied to any summarizing node in the cloud computing network; the method comprises the following steps:

receiving a first migration notification message sent by a source host machine and used for notifying each summarized node of migration of a target cloud instance from the source host machine to a target host machine, and acquiring identification information of the target cloud instance and an IP address of the target host machine, wherein the identification information is included in the first migration notification message;

according to the identification information of the target cloud instance, cloud instance information of the target cloud instance maintained by the summary node is found, and the IP address of the host where the target cloud instance is located, which is included in the cloud instance information of the target cloud instance, is updated from the IP address of the source host to the IP address of the target host;

And sending a second migration notification message for notifying that the target cloud instance is migrated to each host located in the available area, so that each host updates the instance information of the target cloud instance maintained by each host.

The application also provides another network topology updating method based on cloud instance migration, 6, a network topology updating method based on cloud instance migration, wherein the cloud computing network comprises a plurality of available areas supporting mutual communication; each of the plurality of available areas is respectively configured with a corresponding summary node; each summary node maintains instance information of cloud instances running on hosts located in the plurality of available areas; each host maintains instance information of cloud instances running on the host and instance information of other cloud instances communicable with the cloud instances running on the host; the cloud instance information comprises identification information of the cloud instance and an IP address of a host machine where the cloud instance is located;

the method is applied to any host in the cloud computing network; the method comprises the following steps:

receiving a second migration notification message sent by a summary node in the available area, wherein the second migration notification message is used for notifying each host that the target cloud instance is migrated; the second migration notification message is sent after the summary node responds to a first migration notification message sent by a source host, and according to the identification information of the target cloud instance included in the first migration notification message, cloud instance information of the target cloud instance maintained by the summary node is found, and an IP address of a host where the target cloud instance is located and included in the cloud instance information of the target cloud instance is updated from the IP address of the source host to the IP address of a destination host included in the first migration notification message; the first migration notification message is used for notifying each summary node that the target cloud instance migrates from the source host to the target host;

And updating the instance information of the target cloud instance maintained by the host machine in response to the second migration notification message.

The application also provides a network topology updating device based on cloud instance migration, wherein the cloud computing network comprises a plurality of available areas supporting mutual communication; each of the plurality of available areas is respectively configured with a corresponding summary node; each summary node maintains instance information of cloud instances running on hosts located in the plurality of available areas; each host maintains instance information of cloud instances running on the host and instance information of other cloud instances communicable with the cloud instances running on the host; the cloud instance information comprises identification information of the cloud instance and an IP address of a host machine where the cloud instance is located;

the device is applied to any summarizing node in the cloud computing network; the device comprises:

the first receiving unit is used for receiving a first migration notification message sent by a source host machine and used for notifying each summarizing node of migration of a target cloud instance from the source host machine to a target host machine, and acquiring identification information of the target cloud instance and an IP address of the target host machine, wherein the identification information is included in the first migration notification message;

The first searching unit is used for searching cloud instance information of the target cloud instance maintained by the summarizing node according to the identification information of the target cloud instance;

a first updating unit, configured to update an IP address of a host where the target cloud instance is located, which is included in the cloud instance information of the target cloud instance, from an IP address of the source host to an IP address of the destination host;

and the second sending unit is used for sending a second migration notification message for notifying that the target cloud instance is migrated to each host machine in the available area so as to enable each host machine to update the instance information of the target cloud instance maintained by the host machine.

The application also provides another network topology updating device based on cloud instance migration, wherein the cloud computing network comprises a plurality of available areas supporting mutual communication; each of the plurality of available areas is respectively configured with a corresponding summary node; each summary node maintains instance information of cloud instances running on hosts located in the plurality of available areas; each host maintains instance information of cloud instances running on the host and instance information of other cloud instances communicable with the cloud instances running on the host; the cloud instance information comprises identification information of the cloud instance and an IP address of a host machine where the cloud instance is located;

The device is applied to any host in the cloud computing network; the device comprises:

a fourth receiving unit, configured to receive a second migration notification message sent by a summary node located in the present available area, where the second migration notification message is used to notify each host that the target cloud instance has been migrated; the second migration notification message is sent after the summary node responds to a first migration notification message sent by a source host, and according to the identification information of the target cloud instance included in the first migration notification message, cloud instance information of the target cloud instance maintained by the summary node is found, and an IP address of a host where the target cloud instance is located and included in the cloud instance information of the target cloud instance is updated from the IP address of the source host to the IP address of a destination host included in the first migration notification message; the first migration notification message is used for notifying each summary node that the target cloud instance migrates from the source host to the target host;

and the second updating unit is used for responding to the second migration notification message and updating the instance information of the target cloud instance maintained by the host.

The application also provides electronic equipment, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are mutually connected through the bus;

the memory stores machine-readable instructions and the processor performs any of the methods described above by invoking the machine-readable instructions.

The present application also provides a machine-readable storage medium storing machine-readable instructions that, when invoked and executed by a processor, implement any of the methods described above.

Through the above embodiment, on the one hand, after the target cloud instance is migrated from the source host to the destination host, since the source host may send the first migration notification message to each summary node corresponding to each communicable available area, so that each summary node updates the instance information of the target cloud instance maintained by each summary node, and each host located in the available area may send the second migration notification message to each host, so that each host updates the instance information of the target cloud instance maintained by each host, without waiting for ARP table entry to age automatically, the virtualized network may converge rapidly after migration of the target cloud instance occurs, thereby improving the network topology updating efficiency of the virtualized network.

On the other hand, the source host machine can actively inform each summarizing node corresponding to each communicable available area to update the instance information of the target cloud instance maintained by the summarizing node, so that each summarizing node is triggered to actively inform the host machine positioned in each available area to update the instance information of the target cloud instance maintained by the summarizing node, a free ARP protocol is not required to be adopted to send broadcast messages, and control authority of the switching equipment is not required to be provided, so that the network topology updating efficiency across the available areas is improved, and meanwhile, the safety inside the network is ensured.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic architecture diagram of a cloud computing network, as shown in an exemplary embodiment;

FIG. 2 is a flow chart illustrating a method of network topology upgrade based on cloud instance migration in accordance with an exemplary embodiment;

FIG. 3 is a flow chart illustrating another method of network topology upgrade based on cloud instance migration, according to an exemplary embodiment;

FIG. 4 is a schematic diagram of an electronic device in which a network topology updating apparatus based on cloud instance migration is located, according to an exemplary embodiment;

FIG. 5 is a block diagram of a network topology upgrade apparatus based on cloud instance migration, as shown in an exemplary embodiment;

fig. 6 is a block diagram of another network topology upgrade apparatus based on cloud instance migration, as shown in an exemplary embodiment.

Detailed Description

In order to make the technical solutions in the present specification better understood by those skilled in the art, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.

With the continuous development of cloud computing technology, the performance requirements on the virtualized network are also higher and higher, and the rapid development of various network virtualization technologies is promoted. For example, demands are made on the flexibility (scalability), security (security), reliability (reliability), privacy (privacy), interconnectivity (performance), and the like of the virtualized network.

In network virtualization technology, yun Shili (closed instance) may refer to various virtual devices in a cloud computing network, which may include, but are not limited to, virtual hosts, virtual network cards, routers, gateways, load balancers, and the like. A host (host) may refer to a container for running cloud instances.

In practical applications, a cloud instance running on one host may be migrated to another host. For example, if there are fewer cloud instances running on two hosts, then the cloud instance running on one host may be migrated to the other host to perform resource integration on the cloud computing resources; further, the host machine which does not run the cloud instance can be powered down, so that resources are saved. For another example, if one host fails, resulting in that the cloud instance running on that host is also unable to provide service normally, the cloud instance running on that host may be migrated to other non-failed hosts.

Further, migrating a cloud instance running on one host to another host may result in a change in the network topology of the virtualized network. In such a scenario, in order to reduce the service interruption time of the cloud instance where migration occurs, it is necessary to improve the network topology update efficiency of the virtualized network, that is, it is necessary for the virtualized network to accelerate convergence.

In addition, in the cloud computing network, since the available areas (availability zone) located in different areas (regions) are isolated from each other, and the available areas located in the same area can communicate with each other, if a cloud instance located in a certain available area migrates, in addition to updating network topology information maintained by network devices located in the available area, updating network topology information maintained by network devices located in other available areas that can communicate with the available area is also required.

In one related art embodiment, after a cloud instance migrates from a source host to a destination host, the destination host may send a gratuitous ARP broadcast message based on gratuitous ARP (Address Resolution Protocol ) to enable other hosts and switching devices in a virtualized network to update a routing table maintained by the host after receiving the gratuitous ARP broadcast message.

In the embodiment shown above, if the network topology of the virtualized network is updated based on the gratuitous ARP after the cloud instance migrates, the virtualized network may be attacked by the gratuitous ARP initiated by the malicious cloud instance, which causes a security problem.

In another related art embodiment, in order to avoid the gratuitous ARP attack, gratuitous ARP may be disabled internally on the network, and the MAC (Media Access Control ) address and port mapping table of each cloud instance may be recorded based on the switching device in the two-layer communication; if the source host and the destination host are connected to different switching device ports, after the cloud instance is migrated from the source host to the destination host, because the ARP entry corresponding to the switching device port connected to the source host is not aged, the situation of traffic failure and service interruption may occur in the migrated cloud instance until the aging time of the old ARP entry is overtime, and an ARP entry corresponding to the switching device port connected to the destination host is created.

In the embodiment shown above, the control authority of the switching device needs to be provided to accelerate the update of the network topology, so that the cloud instance after migration is available as soon as possible, but a new security problem is caused.

In view of this, the present disclosure aims to propose a network topology updating scheme that combines efficiency and security in the cloud instance migration process.

In this specification, a cloud computing network may include a plurality of available areas supporting intercommunication; each of the plurality of available regions may be configured with a corresponding aggregation node, respectively. Wherein each summary node may maintain instance information for cloud instances running on hosts located in the plurality of availability zones; each host may maintain instance information of cloud instances running on the host, as well as instance information of other cloud instances communicable with the cloud instance running on the host.

When the cloud computing network is realized, any summary node in the cloud computing network can receive a first migration notification message sent by a source host machine and used for notifying each summary node of migration of a target cloud instance from the source host machine to a target host machine, and acquire identification information of the target cloud instance and an IP address (Internet Protocol Address ) of the target host machine, which are included in the first migration notification message; further, the summary node may find cloud instance information of the target cloud instance maintained by the summary node according to the identification information of the target cloud instance, and may update an IP address of a host where the target cloud instance is located, which is included in the cloud instance information of the target cloud instance, from an IP address of the source host to an IP address of the destination host; further, the summary node may send a second migration notification message to each host located in the present available area, where the second migration notification message is used to notify that the target cloud instance has migrated, so that each host responds to the second migration notification message, and updates the instance information of the target cloud instance maintained by each host.

Therefore, in the technical solution in the present specification, on one hand, after the target cloud instance is migrated from the source host to the destination host, since the source host may send a first migration notification message to each summary node corresponding to each communicable available area, so that each summary node updates the instance information of the target cloud instance maintained by each summary node, and each host located in the available area may send a second migration notification message to each host, so that each host updates the instance information of the target cloud instance maintained by each host, without waiting for automatic ageing of ARP table entries, the virtualized network may quickly converge after migration of the target cloud instance, thereby improving the network topology updating efficiency of the virtualized network.

The present application is described below by way of specific embodiments and in connection with specific application scenarios.

For example, referring to fig. 1, fig. 1 is a schematic architecture diagram of a cloud computing network according to an exemplary embodiment. As shown in fig. 1, the available area a and the available area B are two available areas located in the same area "eastern china", and communication is supported between the available area a and the available area B; the available area a may be configured with a corresponding summary node a, and the available area B may be configured with a corresponding summary node B.

Host1, host2, and host3 are hosts located in available region a, and host4 and host5 are hosts located in available region B; wherein, the host1 can be operated with the cloud instance VM1, the host2 can be operated with the cloud instance VM2, the host3 may have a cloud instance VM3 running thereon, the host4 may have a cloud instance VM4 running thereon, and the host5 may have a cloud instance VM5 running thereon. In addition, each host machine can also be operated with a virtual switch; the virtual switch may be configured to forward a message sent by a cloud instance running on a host to other hosts, and may be configured to forward a received message sent by other hosts to a cloud instance running on the host.

The summary node a corresponding to the available area a may maintain instance information of the cloud instance VM1, the cloud instance VM2, the cloud instance VM3, the cloud instance VM4 and the cloud instance VM 5; the summary node B corresponding to the available area B may also maintain instance information of the cloud instance VM1, the cloud instance VM2, the cloud instance VM3, the cloud instance VM4, and the cloud instance VM 5. Assuming that communication may be made between Yun Shili VM1, cloud instance VM2, cloud instance VM3, and cloud instance VM4, host1 may maintain instance information for cloud instance VM1 running on the host, and may maintain instance information for cloud instance VM2, cloud instance VM3, and cloud instance VM4 that may be in communication with cloud instance VM 1.

It should be noted that, in the embodiment shown in fig. 1, a cloud instance is running on a host, which is merely an exemplary description, and is not meant to limit the present disclosure specifically; in practice, one or more cloud instances may be running on each host.

In this specification, the summary node may include one summary device, or may include a summary device cluster formed by a plurality of summary devices.

For example, as shown in fig. 1, the summary node a may specifically include a summary cluster composed of a master summary device a1 and a standby summary device a2, so as to ensure high availability of the summary node a and avoid performance bottlenecks of the summary node.

In this specification, the instance information of the cloud instance may specifically include, but is not limited to: the method comprises the steps of identifying information of a cloud instance, an IP address of a host machine where the cloud instance is located, identifying information of an available area where the cloud instance is located, identifying information of a network card bound by the cloud instance, LAN identification of a LAN where the cloud instance is located, VLAN identification of the VLAN where the cloud instance is located, final active time of the cloud instance, link type and the like.

For example, as shown in fig. 1, the identification information of the cloud instance VM1 may be "VM1", the identification information of the host where the cloud instance VM1 is located may be "host1", the IP address of the host where the cloud instance VM1 is located may be "IP1", the identification information of the available area where the cloud instance VM1 is located may be "available area a", the identification information of the network card to which the cloud instance VM1 is bound may be "card id1", the LAN identification of the LAN where the cloud instance VM1 is located may be "LAN id1", the VLAN identification of the VLAN where the cloud instance VM1 is located may be "VLAN id1", and the last active time of the cloud instance VM1 may be time "t1".

In one embodiment shown, the respective summary nodes may maintain instance information of cloud instances running on hosts located in the plurality of available zones through a flow table; the respective hosts may maintain instance information of cloud instances running on the local host, as well as instance information of other cloud instances communicable with the cloud instance running on the local host, through a neighbor table.

For example, for a cloud computing network as shown in fig. 1, please refer to table 1, table 1 is a flow table maintained by summary node a shown in an exemplary embodiment,

TABLE 1

Referring to table 2, table 2 shows a neighbor table maintained by host1 in an exemplary embodiment,

TABLE 2

It follows that the neighbor table may be a sub-table of the flow table; thus, if the summary node updates the flow table it maintains, the host should also update the neighbor table it maintains.

In this specification, the target cloud instance may be a cloud instance in which migration occurs in the cloud computing network.

In this specification, in response to migration of the target cloud instance from a source host to a destination host, the source host may send a first migration notification message to each summary node for notifying that the target cloud instance is migrated from the source host to the destination host, respectively.

For example, as shown in fig. 1, the target cloud instance may be cloud instance VM3; in response to Yun Shili migration of VM3 from source host3 to destination host2, source host3 may send first migration notification messages (1) to summary node a and summary node b, respectively, and first migration notification messages (1) may be used to notify the summary nodes corresponding to the respective available regions that cloud instance VM3 has migrated from source host3 to destination host2.

Specifically, because the available areas located in the same area can be communicated through a dedicated line, the source host can respectively send a first migration notification message for notifying that the target cloud instance is migrated from the source host to the destination host to each summary node through the dedicated line between the source host and each summary node.

For example, as shown in fig. 1, a source host3 located in the available area a may send a first migration notification message (1) to the summary node b through a dedicated line between the source host3 and the summary node b.

Wherein other available areas that are communicable may be preconfigured for the respective available areas, and a plurality of aggregation nodes that support communication across the available areas may be configured.

For example, in the available region configuration information for the available region a, other available regions that can be communicated may be preconfigured as "available region B"; as shown in fig. 1, the summary node a may specifically include a summary cluster composed of a primary summary device a1 and a standby summary device a2, and the summary node b may specifically include a summary cluster composed of a primary summary device a1 and a standby summary device a2, and in the available area configuration information for the available area a, a summary device list supporting communication across the available area may be preconfigured as "summary device a1 x summary device a2 x summary device b1 x summary device b2"; in response to Yun Shili VM3 migrating from source host3 to destination host2, source host3 may send first migration notification messages (1) to aggregators a1 and b1, respectively, according to configuration information for available region a.

In addition, the available area configuration information may be preconfigured with IP addresses of a plurality of summary nodes supporting cross-available area communication, which are not described in detail herein.

Referring to fig. 2, fig. 2 is a flowchart illustrating a network topology updating method based on cloud instance migration according to an exemplary embodiment. The network topology updating method based on cloud instance migration can be applied to any summarizing node in the cloud computing network. The following describes a technical solution in this specification by taking an example that the method is applied to the summary node a shown in fig. 1.

The network topology updating method based on cloud instance migration can execute the following steps:

step 202: and receiving a first migration notification message sent by a source host machine and used for notifying each summarized node of migration of a target cloud instance from the source host machine to a target host machine, and acquiring identification information of the target cloud instance and an IP address of the target host machine, wherein the identification information is included in the first migration notification message.

For example, as shown in fig. 1, the target cloud instance may be cloud instance VM3; the summary node a may receive a first migration notification message (1) sent by the source host3, where the first migration notification message (1) may be used to notify the summary node a that the cloud instance VM3 has migrated from the source host3 to the destination host2; further, the summary node a may acquire the identification information "VM3" of the target cloud instance included in the first migration notification message (1), and the IP address "IP2" of the destination host 2.

Step 204: and according to the identification information of the target cloud instance, searching the cloud instance information of the target cloud instance maintained by the summarizing node, and updating the IP address of the host where the target cloud instance is located, which is included in the cloud instance information of the target cloud instance, from the IP address of the source host to the IP address of the target host.

For example, after the identification information "VM3" of the target cloud instance and the IP address "IP2" of the destination host2 included in the first migration notification message (1) are acquired, according to the identification information "VM3" of the target cloud instance, the summary node a may find out the cloud instance information of the cloud instance VM3 maintained by the summary node, and update the IP address of the host where the cloud instance included in the cloud instance information of the cloud instance VM3 is located from the IP address "IP3" of the source host3 to the IP address "IP2" of the destination host 2.

In one embodiment shown, the respective summary node may update its maintained flow table in response to the first migration notification message. When the method is implemented, according to the identification information of the target cloud instance, cloud instance information of the target cloud instance maintained by the summary node is found, and an IP address of a host where the target cloud instance is located, which is included in the cloud instance information of the target cloud instance, is updated from an IP address of the source host to an IP address of the destination host, which specifically may include: and searching a flow table item, in which the identification information of the included cloud instance is the same as the identification information of the target cloud instance, in a flow table maintained by the summarizing node, and updating the IP address of the host machine where the searched flow table item includes the cloud instance from the IP address of the source host machine to the IP address of the target host machine.

For example, after the identification information "VM3" of the target cloud instance and the IP address "IP2" of the destination host2 included in the first migration notification message (1) are acquired, the aggregation node a may find out, from the flow table as shown in table 1 maintained by itself, the 3 rd flow table entry including the identification information of the cloud instance that is the same as the identification information of the target cloud instance, and may update the IP address of the host where the found cloud instance included in the flow table entry from the IP address "IP3" of the source host3 to the IP address "IP2" of the destination host 2. Referring to table 3, table 3 shows an updated flow table maintained by summary node a,

TABLE 3 Table 3

Step 206: and sending a second migration notification message for notifying that the target cloud instance is migrated to each host located in the available area, so that each host updates the instance information of the target cloud instance maintained by each host.

For example, as shown in fig. 1, after updating the IP address of the host machine where the cloud instance included in the cloud instance information of the cloud instance VM3 is located from the IP address "IP3" of the source host machine host3 to the IP address "IP2" of the destination host machine host2, the summary node a may send second migration notification messages (2) to the host machine host1, host machine host2, and host machine host3 located in the available area a, respectively, and the second migration notification messages (2) may be used to notify each host machine that the cloud instance VM3 has been migrated; further, host1, in response to receiving the second migration notification message (2) sent by summary node a, cloud instance information of the cloud instance VM3 maintained by the cloud instance VM3 can be updated; similarly, in response to receiving the second migration notification message (2) sent by the summary node a, the host2 and the host3 may also update the cloud instance information of the cloud instance VM3 that they maintain.

In the embodiment shown above, the second migration notification message may carry updated instance information of the target cloud instance, so that after receiving the second migration notification message, each host may directly update the instance information of the target cloud instance maintained by the host according to the updated instance information of the target cloud instance carried in the second migration notification message. The second migration notification message may not carry the updated instance information of the target cloud instance, but only notify each host that the target cloud instance has been migrated, so that each host updates the instance information of the target cloud instance maintained by itself as required.

In one embodiment shown, each host may update its maintained neighbor table in response to the second migration notification message. When implementing, the sending, by the respective hosts located in the present available area, a second migration notification message for notifying that the target cloud instance has been migrated, so that the respective hosts update the instance information of the target cloud instance maintained by the respective hosts, may specifically include: and sending a second migration notification message for notifying that the target cloud instance is migrated to each host located in the available area, so that each host obtains the LAN identifier of the LAN where the target cloud instance is located and the VLAN identifier of the VLAN where the target cloud instance is located, and after the host obtains the LAN identifier of the LAN where the target cloud instance is located, if the LAN identifier of the LAN where the cloud instance is located and the LAN identifier of the LAN where the target cloud instance is located are found in the neighbor table maintained by the host, and the VLAN identifier of the VLAN where the cloud instance is located and the VLAN identifier of the VLAN where the target cloud instance is located are the same as neighbor table entries maintained by the host, updating the neighbor table entries corresponding to the target cloud instance.

For example, as shown in FIG. 1, after updating the IP address of the host in which the cloud instance included in the cloud instance information of the cloud instance VM3 is located from the IP address "IP3" of the source host3 to the IP address "IP2" of the destination host2, the summary node a may send second migration notification messages (2) to the hosts host1, host2 and host3 located in the available area a, respectively; further, in response to receiving the second migration notification message (2) sent by the summary node a, the host1 may acquire a LAN identifier "LAN id1" of the LAN where the target cloud instance VM3 is located and a VLAN identifier "VLAN id1" of the VLAN where the target cloud instance VM3 is located, which are included in the second migration notification message (2); further, the host1 may find out, in a neighbor table maintained by itself and shown in table 2, a 1 st to 4 th neighbor table entry, where the LAN identifier of the LAN where the cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, and the VLAN identifier of the VLAN where the cloud instance is located is the same as the VLAN identifier of the VLAN where the target cloud instance is located, and may update the 3 rd neighbor table entry corresponding to the target cloud instance VM3, which is maintained by the host. Referring to table 4, table 4 shows an updated neighbor table maintained by host1 in accordance with an exemplary embodiment,

TABLE 4 Table 4

By a similar procedure to the host1 shown above updating the neighbor table maintained by itself, the host2 and host3 can also update the neighbor table maintained by themselves, and the host can be realized by a person skilled in the art without performing creative labor, and the details are not repeated here.

For another example, as shown in fig. 1, after updating the IP address of the host machine where the cloud instance included in the cloud instance information of the cloud instance VM3 is located from the IP address "IP3" of the source host machine host3 to the IP address "IP2" of the destination host machine host2, the aggregation node B may send the second migration notification message (2) to the host machine host4 and the host machine host5 located in the available area B, respectively; the host4 may obtain, in response to receiving the second migration notification message (2) sent by the summary node b, a LAN identifier "LAN id1" of a LAN where the target cloud instance VM3 is located and a VLAN identifier "VLAN id1" of a VLAN where the target cloud instance VM3 is located, where the second migration notification message (2) is included; further, since there are only neighbor table entries corresponding to "LAN id1+ VLAN id2" in the neighbor table maintained by the host4, the host4 maintains, among its own neighbor tables, the neighbor table entry that the LAN identifier of the LAN where the included cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located and the VLAN identifier of the VLAN where the included cloud instance is located is the same as the VLAN identifier of the VLAN where the target cloud instance is located cannot be found, which indicates that the host4 does not need to update the example information of the target cloud instance, and may directly discard the second migration notification message (2).

It should be noted that, in the above illustrated embodiment, since each cloud instance in the cloud computing network may be divided into different LANs, each cloud instance in the same LAN may be divided into different VLANs, and only cloud instances in the same LAN and having the same VLAN identifier may communicate with each other; therefore, the second migration notification message may include the LAN identifier of the LAN where the target cloud instance is located and the VLAN identifier of the VLAN where the target cloud instance is located, so that each host determines whether to update the maintained neighbor table thereof; if a host finds a neighbor table entry corresponding to the LAN identifier+VLAN identifier of the target cloud instance in a neighbor table maintained by the host, the host indicates that the target cloud instance is operated on the host or other cloud instances which can communicate with the target cloud instance are operated on the host, so that after the target cloud instance is migrated, the host needs to update the neighbor table maintained by the host in time so as to ensure the normal communication of the target cloud instance after the migration; if a host cannot find the neighbor table entry corresponding to the LAN identifier+vlan identifier of the target cloud instance in the neighbor table maintained by the host, it is indicated that the host does not operate the target cloud instance or other cloud instances communicable with the target cloud instance, so that after the target cloud instance is migrated, the host does not need to update the neighbor table maintained by the host.

In the embodiment shown above, when a host determines that the neighbor table maintained by the host needs to be updated, the host may acquire updated instance information of the target cloud instance from the summary node corresponding to the available area, and update the neighbor table maintained by the host according to the acquired updated instance information of the target cloud instance.

In a possible case, the host can request the summary node to accurately query the updated instance information of the target cloud instance, and update the neighbor table maintained by the host according to the accurate query result returned by the summary node. In this case, after the step 206, the method may further include:

step 208-a: receiving a first migration information request message sent by any host located in the available area; the first migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located and a VLAN identifier of the VLAN where the target cloud instance is located;

step 210-a: responding to the first migration information request message, and searching a flow table entry, in which the LAN identifier of the included cloud instance is identical to the LAN identifier of the LAN of the target cloud instance and the VLAN identifier of the VLAN of the included cloud instance is identical to the VLAN identifier of the VLAN of the target cloud instance, in the flow table maintained by the summary node;

Step 212-a: and returning the query result to a host machine which sends the first migration information request message as a first migration information response message corresponding to the first migration information request message.

For example, as shown in fig. 1, in response to receiving the second migration notification message (2) sent by the summary node a, the host1 may acquire the LAN identifier "LAN id1" of the LAN where the target cloud instance VM3 is located and the VLAN identifier "VLAN id1" of the VLAN where the target cloud instance VM3 is located, which are included in the second migration notification message (2); further, the host1 may find a neighbor table entry corresponding to "lan id1+vlan id1" in the neighbor table maintained by itself as shown in table 2, so the host1 may send a first migration information request message (3) to the summary node a, where the first migration information request message (3) may include "lan id1+vlan id1"; further, in response to the first migration information request message (3), the summary node a may find out the flow table entry corresponding to "lan id1+vlan id1", that is, the 1 st, 2 nd, 3 rd and 5 th flow table entries in table 3, in the flow table maintained by itself and shown in table 3; further, the summary node a may return the 1 st, 2 nd, 3 rd, and 5 th flow table entries in table 3 to the host1 as the first migration information response message (4) corresponding to the first migration information request message (3), so that the host1 may update the neighbor table shown in table 4 according to the 1 st, 2 nd, 3 rd, and 5 th flow table entries in table 3 in response to the first migration information response message (4).

In another possible case, the host may request the summary node to roughly query all information related to the updated instance information of the target cloud instance, then further screen the updated instance information of the target cloud instance according to the rough query result returned by the summary node, and update the neighbor table maintained by the host according to the screening result, thereby reducing the performance pressure of the summary node. In this case, after the step 206, the method may further include:

step 208-b: receiving a second migration information request message sent by any host located in the available area; the second migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located;

step 210-b: responding to the second migration information request message, and searching out a flow table entry, in which the LAN identifier of the LAN where the included cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, in the flow table maintained by the summary node;

step 212-b: and returning the query result to the host machine which sends the second migration information request message as a second migration information response message corresponding to the second migration information request message.

For example, as shown in fig. 1, in response to receiving the second migration notification message (2) sent by the summary node a, the host1 may acquire the LAN identifier "LAN id1" of the LAN where the target cloud instance VM3 is located and the VLAN identifier "VLAN id1" of the VLAN where the target cloud instance VM3 is located, which are included in the second migration notification message (2); further, the host1 may find a neighbor table entry corresponding to "lan id1+vlan id1" in the neighbor table maintained by itself as shown in table 2, so the host1 may send a second migration information request message (3) to the summary node a, where the second migration information request message (3) may include "lan id1"; further, the summary node a responds to the second migration information request message (3), and can find out the flow table entry corresponding to the lan id1, namely the 1 st to 5 th flow table entry in the table 3, in the self-maintained flow table shown in the table 3; further, the summary node a may return the 1 st to 5 th flow table entries in table 3 as a second migration information response message (4) corresponding to the second migration information request message (3), so that the host1 responds to the second migration information response message (4), and may search the 1 st to 5 th flow table entries in table 3 included in the second migration information response message (4) for a flow table entry corresponding to "lan id1+vlan id1", and update the neighbor table shown in table 4 according to the flow table entry corresponding to "lan id1+vlan id1" included in the second migration information response message (4) that is screened.

In step 210-b, the aggregation node may convert the LAN identifier into a bitmap, and then query the LAN identifier by using a bitmap comparison method, so as to increase the response speed of the second migration information request message, and further increase the network convergence speed after the cloud instance is migrated.

When the method is realized, according to the flow table maintained by the summarizing node, the LAN identification of the LAN where the cloud instance is located in each flow table entry can be converted into a bitmap value to form a bitmap corresponding to the flow table; that is, each bit in the bitmap may correspond to a LAN identification included in one of the flow table entries, and a bitmap value of each bit in the bitmap may be used to indicate whether the corresponding LAN identification is set. For specific implementation of bitmap comparison, reference may be made to related art, which is not described herein.

In the embodiment shown above, the specific implementation manner of updating the neighbor table maintained by the host according to the query result returned by the summary node may include:

for the flow table entry included in the first migration information response message or the second migration information response message, if the LAN identifier included in the flow table entry is the same as the LAN identifier of the LAN where the target cloud instance is located and the VLAN identifier included in the flow table entry is the same as the VLAN identifier of the VLAN where the target cloud instance is located, the neighbor table entry corresponding to the identifier information of the target cloud instance may be searched in a neighbor table maintained by the host;

If the neighbor table entry corresponding to the identification information of the target cloud instance is found in the neighbor table maintained by the host, the neighbor table entry corresponding to the flow table entry can be added in the neighbor table maintained by the host;

if a neighbor table entry corresponding to the identification information of the target cloud instance is found in a neighbor table maintained by the host, whether the flow table entry is identical to the neighbor table entry or not can be compared;

if the flow table entry is different from the neighbor table entry, the neighbor table entry may be updated based on the flow table entry;

if the flow table entry is the same as the neighbor table entry, the neighbor table entry does not need to be updated.

Referring to fig. 3, fig. 3 is a flowchart illustrating another network topology updating method based on cloud instance migration according to an exemplary embodiment. The network topology updating method based on cloud instance migration can be applied to any host in the cloud computing network; in particular, the method may be applied to virtual switches running on any host.

Step 302: receiving a second migration notification message sent by a summary node in the available area, wherein the second migration notification message is used for notifying each host that the target cloud instance is migrated; the second migration notification message is sent after the summary node responds to a first migration notification message sent by a source host, and according to the identification information of the target cloud instance included in the first migration notification message, cloud instance information of the target cloud instance maintained by the summary node is found, and an IP address of a host where the target cloud instance is located and included in the cloud instance information of the target cloud instance is updated from the IP address of the source host to the IP address of a destination host included in the first migration notification message; the first migration notification message is used for notifying each summary node that the target cloud instance migrates from the source host to the target host;

step 304: and updating the instance information of the target cloud instance maintained by the host machine in response to the second migration notification message.

In one embodiment shown, the respective hosts maintain instance information of cloud instances running on the host through neighbor tables, and instance information of other cloud instances communicable with the cloud instances running on the host; the instance information of the cloud instance further comprises a LAN identifier of a LAN where the cloud instance is located and a VLAN identifier of the VLAN where the cloud instance is located.

In this case, the updating, in response to the second migration notification message, instance information of the target cloud instance maintained by the host may specifically include: responding to the second migration notification message, and acquiring a LAN identifier of the LAN where the target cloud instance is located and a VLAN identifier of the VLAN where the target cloud instance is located, wherein the LAN identifier is included in the second migration notification message; in a neighbor table maintained by a host, searching a neighbor table entry, wherein the LAN identifier of the LAN where the included cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, and the VLAN identifier of the VLAN where the included cloud instance is located is the same as the VLAN identifier of the VLAN where the target cloud instance is located; if the neighbor table entry, which is maintained by the host and corresponds to the target cloud instance, of which the LAN identifier of the included cloud instance is the same as the LAN identifier of the LAN of the target cloud instance and the VLAN identifier of the VLAN of the included cloud instance is the same as the VLAN identifier of the VLAN of the target cloud instance, is found in the neighbor table maintained by the host, the neighbor table entry, which is maintained by the host and corresponds to the target cloud instance, is updated.

In one embodiment shown, before updating the neighbor table entry corresponding to the target cloud instance maintained by the host, the method may further include: sending a first migration information request message to the summarizing node; the first migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located and a VLAN identifier of the VLAN where the target cloud instance is located; receiving a first migration information response message corresponding to the first migration information request message returned by the summarizing node; the first migration information response message includes a flow table entry, in which the flow table maintained by the summary node, the found LAN identifier of the LAN where the cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, and the VLAN identifier of the VLAN where the cloud instance is located is the same as the VLAN identifier of the VLAN where the target cloud instance is located.

In another embodiment shown, before updating the neighbor table entry corresponding to the target cloud instance maintained by the host, the method may further include: sending a second migration information request message to the summarizing node; the second migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located; receiving a second migration information response message corresponding to the second migration information request message returned by the summarizing node; the second migration information response message includes a flow table entry, in which the LAN identifier of the LAN where the cloud instance is located and the LAN identifier of the LAN where the target cloud instance is located are the same, in the flow table maintained by the summary node; and searching a neighbor table entry, in which the LAN identifier of the included cloud instance is the same as the LAN identifier of the LAN of the cloud instance included in the received flow table entry, and the VLAN identifier of the included cloud instance is the same as the VLAN identifier of the VLAN of the cloud instance included in the received flow table entry, in the neighbor table maintained by the host.

In one embodiment shown, the method may further comprise: and responding to the migration of the target cloud instance from the host machine serving as a source host machine to other host machines serving as destination host machines, and respectively sending first migration notification messages for notifying the migration of the target cloud instance from the host machine to the other host machines to the summarization nodes through special lines between the host machine and the summarization nodes.

In this specification, the specific implementation manners of step 302 to step 304 are similar to those of step 202 to step 206, and are not repeated here.

According to the technical scheme, on one hand, after the target cloud instance is migrated from the source host to the target host, the source host can send the first migration notification message to each summarized node corresponding to each communicable available area so that each summarized node can update the instance information of the target cloud instance maintained by the summarized node, and each host located in the available area can send the second migration notification message so that each host can update the instance information of the target cloud instance maintained by the summarized node without waiting for automatic ageing of ARP (Address resolution protocol) table entries, so that the virtualized network can quickly converge after the migration of the target cloud instance, and the network topology updating efficiency of the virtualized network is improved.

Corresponding to the embodiment of the network topology updating method based on cloud instance migration, the specification also provides an embodiment of a network topology updating device based on cloud instance migration.

Referring to fig. 4, fig. 4 is a hardware structure diagram of an electronic device where a network topology updating device based on cloud instance migration is shown in an exemplary embodiment. At the hardware level, the device includes a processor 402, an internal bus 404, a network interface 406, a memory 408, and a non-volatile storage 410, although other hardware required for the service is possible. One or more embodiments of the present description may be implemented in a software-based manner, such as by the processor 402 reading a corresponding computer program from the non-volatile memory 410 into the memory 408 and then running. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.

Referring to fig. 5, fig. 5 is a block diagram illustrating a network topology upgrade apparatus based on cloud instance migration according to an exemplary embodiment. The network topology updating device based on cloud instance migration can be applied to the electronic equipment shown in fig. 4 to realize the technical scheme of the specification. The cloud computing network comprises a plurality of available areas which support mutual communication; each of the plurality of available areas is respectively configured with a corresponding summary node; each summary node maintains instance information of cloud instances running on hosts located in the plurality of available areas; each host maintains instance information of cloud instances running on the host and instance information of other cloud instances communicable with the cloud instances running on the host; the instance information of the cloud instance comprises identification information of the cloud instance and an IP address of a host where the cloud instance is located. The apparatus may be applied to any aggregation node in the cloud computing network.

The network topology updating device based on cloud instance migration may include:

a first receiving unit 502, configured to receive a first migration notification message sent by a source host and used to notify each summary node that a target cloud instance migrates from the source host to a destination host, and obtain identification information of the target cloud instance and an IP address of the destination host included in the first migration notification message;

the first searching unit 504 is configured to find cloud instance information of the target cloud instance maintained by the summary node according to the identification information of the target cloud instance;

a first updating unit 506, configured to update, from an IP address of the source host to an IP address of the destination host, an IP address of a host where the target cloud instance is located, which is included in the cloud instance information of the target cloud instance;

and the first sending unit 508 is configured to send a second migration notification message to each host located in the present available area, where the second migration notification message is used to notify that the target cloud instance has been migrated, so that each host updates the instance information of the target cloud instance maintained by the host.

In this embodiment, the summary nodes maintain instance information of cloud instances running on hosts located in the multiple available areas through a flow table;

The first search unit 504 is specifically configured to:

searching a flow table item, in which the identification information of the included cloud instance is the same as the identification information of the target cloud instance, in a flow table maintained by the summarizing node;

the first updating unit 506 is specifically configured to:

and updating the IP address of the host machine where the cloud instance included in the searched flow table entry is located from the IP address of the source host machine to the IP address of the destination host machine.

In this embodiment, the respective hosts maintain, through a neighbor table, instance information of a cloud instance running on the host, and instance information of other cloud instances communicable with the cloud instance running on the host; the instance information of the cloud instance further comprises a LAN identifier of a LAN where the cloud instance is located and a VLAN identifier of the VLAN where the cloud instance is located;

the first sending unit 508 is specifically configured to:

and sending a second migration notification message for notifying that the target cloud instance is migrated to each host located in the available area, so that each host obtains the LAN identifier of the LAN where the target cloud instance is located and the VLAN identifier of the VLAN where the target cloud instance is located, and after the host obtains the LAN identifier of the LAN where the target cloud instance is located, if the LAN identifier of the LAN where the cloud instance is located and the LAN identifier of the LAN where the target cloud instance is located are found in the neighbor table maintained by the host, and the VLAN identifier of the VLAN where the cloud instance is located and the VLAN identifier of the VLAN where the target cloud instance is located are the same as neighbor table entries maintained by the host, updating the neighbor table entries corresponding to the target cloud instance.

In this embodiment, the apparatus further includes:

the second receiving unit is used for receiving a first migration information request message sent by any host machine in the available area; the first migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located and a VLAN identifier of the VLAN where the target cloud instance is located;

the second searching unit is used for responding to the first migration information request message, and searching out a flow table item, in which the LAN identifier of the LAN where the included cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, and the VLAN identifier of the VLAN where the included cloud instance is located is the same as the VLAN identifier of the VLAN where the target cloud instance is located, from the flow table maintained by the summarizing node;

and the second sending unit is used for returning the query result to the host machine which sends the first migration information request message as a first migration information response message corresponding to the first migration information request message.

In this embodiment, the apparatus further includes:

the third receiving unit is used for receiving a second migration information request message sent by any host machine in the available area; the second migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located;

The third searching unit is used for responding to the second migration information request message and searching out a flow table item, in which the LAN identifier of the LAN where the included cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, in the flow table maintained by the summarizing node;

and the third sending unit is used for returning the query result to the host machine which sends the second migration information request message as a second migration information response message corresponding to the second migration information request message.

Referring to fig. 6, fig. 6 is a block diagram illustrating another network topology upgrade apparatus based on cloud instance migration according to an exemplary embodiment. The network topology updating device based on cloud instance migration can be applied to the electronic equipment shown in fig. 4 to realize the technical scheme of the specification. The cloud computing network comprises a plurality of available areas which support mutual communication; each of the plurality of available areas is respectively configured with a corresponding summary node; each summary node maintains instance information of cloud instances running on hosts located in the plurality of available areas; each host maintains instance information of cloud instances running on the host and instance information of other cloud instances communicable with the cloud instances running on the host; the instance information of the cloud instance comprises identification information of the cloud instance and an IP address of a host where the cloud instance is located. The apparatus may be applied to any host in the cloud computing network.

a fourth receiving unit 602, configured to receive a second migration notification message sent by a summary node located in the present available area, where the second migration notification message is used to notify each host that the target cloud instance has been migrated; the second migration notification message is sent after the summary node responds to a first migration notification message sent by a source host, and according to the identification information of the target cloud instance included in the first migration notification message, cloud instance information of the target cloud instance maintained by the summary node is found, and an IP address of a host where the target cloud instance is located and included in the cloud instance information of the target cloud instance is updated from the IP address of the source host to the IP address of a destination host included in the first migration notification message; the first migration notification message is used for notifying each summary node that the target cloud instance migrates from the source host to the target host;

and the second updating unit 604 is configured to update instance information of the target cloud instance maintained by the host in response to the second migration notification message.

In this embodiment, the respective hosts maintain, through a neighbor table, instance information of a cloud instance running on the host, and instance information of other cloud instances communicable with the cloud instance running on the host;

the instance information of the cloud instance further comprises a LAN identifier of a LAN where the cloud instance is located and a VLAN identifier of the VLAN where the cloud instance is located;

the second updating unit 604 is specifically configured to:

responding to the second migration notification message, and acquiring a LAN identifier of the LAN where the target cloud instance is located and a VLAN identifier of the VLAN where the target cloud instance is located, wherein the LAN identifier is included in the second migration notification message;

in a neighbor table maintained by a host, searching a neighbor table entry, wherein the LAN identifier of the LAN where the included cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, and the VLAN identifier of the VLAN where the included cloud instance is located is the same as the VLAN identifier of the VLAN where the target cloud instance is located;

if the neighbor table entry, which is maintained by the host and corresponds to the target cloud instance, of which the LAN identifier of the included cloud instance is the same as the LAN identifier of the LAN of the target cloud instance and the VLAN identifier of the VLAN of the included cloud instance is the same as the VLAN identifier of the VLAN of the target cloud instance, is found in the neighbor table maintained by the host, the neighbor table entry, which is maintained by the host and corresponds to the target cloud instance, is updated.

In this embodiment, before updating the neighbor table entry corresponding to the target cloud instance maintained by the host, the second updating unit 604 is specifically further configured to:

sending a first migration information request message to the summarizing node; the first migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located and a VLAN identifier of the VLAN where the target cloud instance is located;

receiving a first migration information response message corresponding to the first migration information request message returned by the summarizing node; the first migration information response message includes a flow table entry, in which the flow table maintained by the summary node, the found LAN identifier of the LAN where the cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, and the VLAN identifier of the VLAN where the cloud instance is located is the same as the VLAN identifier of the VLAN where the target cloud instance is located.

sending a second migration information request message to the summarizing node; the second migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located;

Receiving a second migration information response message corresponding to the second migration information request message returned by the summarizing node; the second migration information response message includes a flow table entry, in which the LAN identifier of the LAN where the cloud instance is located and the LAN identifier of the LAN where the target cloud instance is located are the same, in the flow table maintained by the summary node;

and searching a neighbor table entry, in which the LAN identifier of the included cloud instance is the same as the LAN identifier of the LAN of the cloud instance included in the received flow table entry, and the VLAN identifier of the included cloud instance is the same as the VLAN identifier of the VLAN of the cloud instance included in the received flow table entry, in the neighbor table maintained by the host.

In this embodiment, the apparatus further includes:

and the fourth sending unit is used for responding to the migration of the target cloud instance from the host machine serving as the source host machine to other host machines serving as the destination host machines, and respectively sending first migration notification messages for notifying the migration of the target cloud instance from the host machine to the other host machines to the summarizing nodes through special lines between the host machine and the summarizing nodes.

The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are illustrative only, in that the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer 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, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of related data is required to comply with the relevant laws and regulations and standards of the relevant country and region, and is provided with corresponding operation entries for the user to select authorization or rejection.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.

Claims

1. A network topology updating method based on cloud instance migration includes a plurality of available areas supporting mutual communication in a cloud computing network; each of the plurality of available areas is respectively configured with a corresponding summarized node, and each available area is also configured with other available areas which can communicate, wherein in the available area configuration information for each available area, a summarized node list which can communicate with the summarized node in the available area and is positioned in other available areas is configured; each summary node maintains instance information of cloud instances running on hosts located in the plurality of available areas; each host maintains instance information of cloud instances running on the host and instance information of other cloud instances communicable with the cloud instances running on the host; the cloud instance information comprises identification information of the cloud instance and an IP address of a host machine where the cloud instance is located;

receiving a first migration notification message sent by a source host machine through a dedicated line and used for notifying each summarizing node of migration of a target cloud instance from the source host machine to a target host machine, and acquiring identification information of the target cloud instance and an IP address of the target host machine, wherein the identification information is included in the first migration notification message;

2. The method of claim 1, the respective summary nodes maintaining instance information of cloud instances running on hosts located in the plurality of availability zones through a flow table;

According to the identification information of the target cloud instance, cloud instance information of the target cloud instance maintained by the summary node is found, and an IP address of a host where the target cloud instance is located, which is included in the cloud instance information of the target cloud instance, is updated from an IP address of the source host to an IP address of the target host, including:

and searching a flow table item, in which the identification information of the included cloud instance is the same as the identification information of the target cloud instance, in a flow table maintained by the summarizing node, and updating the IP address of the host machine where the searched flow table item includes the cloud instance from the IP address of the source host machine to the IP address of the target host machine.

3. The method of claim 2, the respective hosts maintaining instance information of cloud instances running on the host through neighbor tables, and instance information of other cloud instances communicable with the cloud instance running on the host;

the sending, by each host located in the present available area, a second migration notification message for notifying that the target cloud instance has migrated, so that each host updates instance information of the target cloud instance maintained by the host, including:

4. A method according to claim 3, the method further comprising:

receiving a first migration information request message sent by any host located in the available area; the first migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located and a VLAN identifier of the VLAN where the target cloud instance is located;

responding to the first migration information request message, and searching a flow table entry, in which the LAN identifier of the included cloud instance is identical to the LAN identifier of the LAN of the target cloud instance and the VLAN identifier of the VLAN of the included cloud instance is identical to the VLAN identifier of the VLAN of the target cloud instance, in the flow table maintained by the summary node;

And returning the query result to a host machine which sends the first migration information request message as a first migration information response message corresponding to the first migration information request message.

5. A method according to claim 3, the method further comprising:

receiving a second migration information request message sent by any host located in the available area; the second migration information request message comprises a LAN identifier of a LAN where the target cloud instance is located;

responding to the second migration information request message, and searching out a flow table entry, in which the LAN identifier of the LAN where the included cloud instance is located is the same as the LAN identifier of the LAN where the target cloud instance is located, in the flow table maintained by the summary node;

and returning the query result to the host machine which sends the second migration information request message as a second migration information response message corresponding to the second migration information request message.

6. A network topology updating method based on cloud instance migration includes a plurality of available areas supporting mutual communication in a cloud computing network; each of the plurality of available areas is respectively configured with a corresponding summarized node, and each available area is also configured with other available areas which can communicate, wherein in the available area configuration information for each available area, a summarized node list which can communicate with the summarized node in the available area and is positioned in other available areas is configured; each summary node maintains instance information of cloud instances running on hosts located in the plurality of available areas; each host maintains instance information of cloud instances running on the host and instance information of other cloud instances communicable with the cloud instances running on the host; the cloud instance information comprises identification information of the cloud instance and an IP address of a host machine where the cloud instance is located;

receiving a second migration notification message sent by a summary node in the available area, wherein the second migration notification message is used for notifying each host that the target cloud instance is migrated; the second migration notification message is a first migration notification message sent by the summary node in response to a source host through a dedicated line, and is sent after searching cloud instance information of the target cloud instance maintained by the summary node according to identification information of the target cloud instance included in the first migration notification message, and updating an IP address of a host where the target cloud instance is located and included in the cloud instance information of the target cloud instance from an IP address of the source host to an IP address of a destination host included in the first migration notification message; the first migration notification message is used for notifying each summary node that the target cloud instance migrates from the source host to the target host;

7. The method of claim 6, the respective hosts maintaining instance information of cloud instances running on the host through neighbor tables, and instance information of other cloud instances communicable with the cloud instance running on the host;

the updating, in response to the second migration notification message, instance information of the target cloud instance maintained by the host includes:

8. The method of claim 7, prior to updating the neighbor table entry maintained by the host machine that corresponds to the target cloud instance, the method further comprising:

9. The method of claim 7, prior to updating the neighbor table entry maintained by the host machine that corresponds to the target cloud instance, the method further comprising:

10. The method of claim 6, the method further comprising:

and responding to the migration of the target cloud instance from the host machine serving as a source host machine to other host machines serving as destination host machines, and respectively sending first migration notification messages for notifying the migration of the target cloud instance from the host machine to the other host machines to the summarization nodes through special lines between the host machine and the summarization nodes.

11. An electronic device comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;

the memory stores machine readable instructions, and the processor performs the method of any of claims 1-5 or 6-10 by invoking the machine readable instructions.

12. A machine-readable storage medium storing machine-readable instructions which, when invoked and executed by a processor, implement the method of any one of claims 1-5 or 6-10.