CN113691436B

CN113691436B - Virtual machine migration method and virtual machine migration device

Info

Publication number: CN113691436B
Application number: CN202111043242.5A
Authority: CN
Inventors: 张余
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2021-09-07
Filing date: 2021-09-07
Publication date: 2023-04-18
Anticipated expiration: 2041-09-07
Also published as: CN113691436A

Abstract

The invention discloses a virtual machine migration method and a virtual machine migration device, and relates to the technical field of communication. The method comprises the following steps: receiving a second migration request sent by the cloud management platform in response to the first migration request triggered by the virtual machine; acquiring a virtual extended local area network (VLAN) tunnel endpoint (VTEP) stored in an ARP (Address resolution protocol) list item warning information table, and acquiring each physical host identifier corresponding to the VTEP, wherein the VTEP in the ARP list item warning information table is the VTEP of which the number of ARP list items reaches a preset threshold value; and sending migration response information carrying the physical host identifier to the cloud management platform, so that the cloud management platform deletes the physical host corresponding to the physical host identifier from the virtual machine migration target host option table. The method can avoid the problem that the data message cannot be normally forwarded due to the fact that the virtual machine is migrated to the physical host corresponding to the VTEP with insufficient ARP table entry allowance.

Description

Virtual machine migration method and virtual machine migration device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a virtual machine migration method and a virtual machine migration apparatus.

Background

When an EVPN (Ethernet Virtual Private Network) adopts a distributed gateway architecture, each VTEP (VXLAN Tunnel End Point) device can be used as an EVPN gateway to forward the traffic of a local site in three layers. However, the number of access users of different distributed gateways is different, and the processing capability of each distributed gateway is different, so that the difference of the processing capability of an Address Resolution Protocol (ARP) between different distributed gateways is large. When the number of the ARP table entries of one of the distributed gateways reaches the maximum value, the ARP table entries cannot be learned and responded, so that a user of the EVPN network cannot normally forward data messages.

Disclosure of Invention

Therefore, the invention provides a virtual machine migration method and a virtual machine migration device, which are used for solving the problem that in the prior art, a user of an EVPN network cannot normally forward data messages because the virtual machine is migrated to a physical host under VTEP (virtual machine virtualization technology) of which the ARP table entry number reaches the maximum value, so that the ARP table entries cannot be learned and responded.

In order to achieve the above object, in a first aspect, the present invention provides a virtual machine migration method, including:

receiving a second migration request sent by the cloud management platform in response to the first migration request triggered by the virtual machine;

acquiring a virtual extended local area network (VLAN) tunnel endpoint (VTEP) stored in an ARP (Address resolution protocol) list item warning information table, and acquiring each physical host identifier corresponding to the VTEP, wherein the VTEP in the ARP list item warning information table is the VTEP of which the number of ARP list items reaches a preset threshold value;

and sending migration response information carrying the physical host identifier to the cloud management platform, so that the cloud management platform deletes the physical host corresponding to the physical host identifier from the virtual machine migration target host option table.

In some examples, before receiving the second migration request sent by the cloud management platform in response to the first migration request triggered by the virtual machine, the method further includes:

receiving ARP table item warning information sent by the VTEP in response to the ARP table item quantity reaching a preset threshold;

and creating the ARP table item warning information table according to the ARP table item warning information.

In some examples, obtaining a virtual extended local area network tunnel endpoint VTEP stored in an ARP table entry warning information table, and obtaining each physical host identity corresponding to the VTEP includes:

acquiring the VTEP stored in the ARP table item warning information table;

and acquiring each physical host identifier corresponding to the VTEP from a preset mapping table of the VTEP and the physical host.

In some examples, after sending, to the cloud management platform, migration response information carrying the physical host identifier, so that the cloud management platform deletes the physical host corresponding to the physical host identifier from the virtual machine migration target host option table, the method further includes:

receiving migration confirmation information sent by the cloud management platform in response to migration success information triggered by the virtual machine, wherein the migration confirmation information comprises a VTEP identifier corresponding to the migrated virtual machine;

determining a target VTEP according to whether the corresponding VTEP before the virtual machine is migrated is the same as the corresponding VTEP after the virtual machine is migrated;

and sending the flow table corresponding to the virtual machine to the target VTEP.

In some examples, the sending the flow table corresponding to the virtual machine to the target VTEP includes:

sending an original flow table clearing request corresponding to the virtual machine to the target VTEP;

receiving clearing confirmation information returned by the target VTEP in response to the original flow table clearing request, and sending an ARP request corresponding to the virtual machine to the corresponding migrated VTEP, so that the corresponding migrated VTEP forwards the ARP request to the virtual machine;

receiving ARP response information returned by the corresponding VTEP after migration, wherein the ARP response information is sent by the virtual machine in response to the ARP request;

and creating a flow table corresponding to the virtual machine according to the ARP response information and sending the flow table to the target VTEP.

In some examples, the determining a target VTEP according to whether the VTEP corresponding to the virtual machine before migration is the same as the VTEP corresponding to the virtual machine after migration includes:

determining a VTEP corresponding to the migrated virtual machine according to the VTEP identifier;

and comparing whether the VTEP corresponding to the virtual machine before migration is the same as the VTEP corresponding to the virtual machine after migration, if so, determining that the target VTEP is the VTEP corresponding to the virtual machine after migration, and if not, determining that the target VTEP is each VTEP managed by the SDN controller to which the VTEP corresponding to the virtual machine after migration belongs.

In a second aspect, the present invention provides a virtual machine migration method, including:

responding to a first migration request triggered by a virtual machine, sending a second migration request to an SDN controller, enabling the SDN controller to obtain VTEPs stored in an ARP (address resolution protocol) table entry warning information table and obtain physical host identifiers corresponding to the VTEPs, wherein the VTEPs in the ARP table entry warning information table are the VTEPs with the ARP table entry quantity reaching a preset threshold;

receiving migration response information carrying the physical host identifier and sent by the SDN controller, and deleting the physical host corresponding to the physical host identifier from a virtual machine migration target host option list.

In some examples, after receiving migration response information carrying the physical host identifier sent by the SDN controller and deleting a physical host corresponding to the physical host identifier from a virtual machine migration target host option table, the method further includes:

responding to migration success information triggered by a virtual machine, sending migration confirmation information to the SDN controller, enabling the SDN controller to determine a target VTEP according to whether a VTEP corresponding to the virtual machine before migration is the same as a VTEP corresponding to the virtual machine after migration, and sending a flow table corresponding to the virtual machine to the target VTEP, wherein the migration confirmation information comprises a VTEP identifier corresponding to the virtual machine after migration.

In a third aspect, the present invention provides a virtual machine migration apparatus, including:

the first receiving module is used for receiving a second migration request sent by the cloud management platform in response to a first migration request triggered by the virtual machine;

an obtaining module, configured to obtain a virtual extended local area network tunnel endpoint VTEP stored in an ARP table entry warning information table, and obtain each physical host identifier corresponding to the VTEP, where the VTEP in the ARP table entry warning information table is a VTEP whose ARP table entry number reaches a preset threshold;

a first sending module, configured to send migration response information carrying the physical host identifier to the cloud management platform, so that the cloud management platform deletes the physical host corresponding to the physical host identifier from a virtual machine migration target host option table.

In a fourth aspect, the present invention provides a virtual machine migration apparatus, including:

a second sending module, configured to send a second migration request to an SDN controller in response to a first migration request triggered by a virtual machine, so that the SDN controller obtains VTEPs stored in an ARP entry warning information table, and obtains each physical host identifier corresponding to the VTEP, where the VTEPs in the ARP entry warning information table are VTEPs whose ARP entry number reaches a preset threshold;

a second receiving module, configured to receive migration response information carrying the physical host identifier sent by the SDN controller, and delete the physical host corresponding to the physical host identifier from a virtual machine migration target host option table.

In a fifth aspect, the present invention provides an electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method described above.

In a sixth aspect, the present invention provides a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the above-described method.

The invention has the following advantages:

according to the virtual machine migration method provided by the invention, before the virtual machine migration, the SDN (Software Defined Network) controller is used for acquiring each physical host under the VTEP with insufficient ARP table entry allowance, so that the virtual machine can be prevented from being migrated to the physical host corresponding to the VTEP with insufficient ARP table entry allowance, the ARP table entry learning can not be carried out, and the problem that the data message can not be normally forwarded after the migration can be avoided.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention.

Figure 1 is a schematic diagram of a SDN architecture;

fig. 2 is a flowchart illustrating an embodiment of a virtual machine migration method according to the present invention;

fig. 3 is a second flowchart illustrating a virtual machine migration method according to an embodiment of the present invention;

fig. 4 is a third schematic flowchart of an embodiment of a virtual machine migration method according to the present invention;

fig. 5 is a flowchart illustrating another embodiment of a virtual machine migration method according to the present invention;

fig. 6 is a second flowchart illustrating a virtual machine migration method according to another embodiment of the present invention;

fig. 7 is a schematic structural diagram of an embodiment of a virtual machine migration apparatus provided in the present invention;

fig. 8 is a schematic structural diagram of another embodiment of a virtual machine migration apparatus provided in the present invention;

fig. 9 is a schematic structural diagram of an electronic device provided in the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the present invention is further described in detail with reference to the accompanying drawings and the detailed description below.

It is to be understood that the specific embodiments and figures described herein are merely illustrative of the invention and are not to be considered as limiting.

It is to be understood that the embodiments and features of the embodiments can be combined with each other without conflict.

It is to be understood that, for the convenience of description, only parts related to the present invention are shown in the drawings of the present invention, and parts not related to the present invention are not shown in the drawings.

It should be understood that each unit and module related in the embodiments of the present invention may correspond to only one physical structure, may also be composed of multiple physical structures, or multiple units and modules may also be integrated into one physical structure.

It will be understood that, without conflict, the functions, steps, etc. noted in the flowchart and block diagrams of the present invention may occur in an order different from that noted in the figures.

It is to be understood that the flowchart and block diagrams of the present invention illustrate the architecture, functionality, and operation of possible implementations of systems, apparatus, devices and methods according to various embodiments of the present invention. Each block in the flowchart or block diagrams may represent a unit, module, segment, code, which comprises executable instructions for implementing the specified function(s). Furthermore, each block or combination of blocks in the block diagrams and flowchart illustrations can be implemented by a hardware-based system that performs the specified functions or by a combination of hardware and computer instructions.

It is to be understood that the units and modules involved in the embodiments of the present invention may be implemented by software, and may also be implemented by hardware, for example, the units and modules may be located in a processor.

In the related art, VXLAN (Virtual eXtensible Virtual local area Network) is a two-layer VPN (Virtual Private Network) technology based on an IP (Internet Protocol) Network and adopting a MAC-in-UDP (Media Access Control Address-in-User data Protocol, physical Address encapsulation in User data Protocol) encapsulation form. VXLAN can provide two-layer interconnection for dispersed physical sites based on existing service provider or enterprise IP networks and can provide service isolation for different tenants. VXLAN is used primarily in data center networks. VXLAN has many characteristics, for example, a large number of tenants are supported, 24-bit identifiers are used, and at most 24 powers (16777216) of VXLAN can be supported, so that the number of the supported tenants is increased in a large scale, and the problem of insufficient resources of the traditional two-layer network VLAN is solved. For example, the network is easy to maintain, a large two-layer network is constructed based on an IP network, so that the network deployment and maintenance are easier, and the existing IP network technology can be fully utilized, for example, equivalent routing is utilized for load sharing and the like; only the edge device of the IP core network needs to carry out VXLAN processing, and the network intermediate device only needs to forward the message according to the IP header, thereby reducing the difficulty and the cost of network deployment. The VXLAN technology takes an existing three-layer physical network as an Underlay network (i.e., an Underlay network), and a virtual two-layer network, i.e., an Overlay network (i.e., a Overlay network), is constructed on the Underlay network. The Overlay network realizes the transfer of the second-layer message of the tenant between different sites across a three-layer network by using a three-layer forwarding path provided by the Underlay network through a packaging technology. For the tenant, the Underlay network is transparent, and different sites of the same tenant work in a local area network. A typical network model for VXLAN may include the following sections:

VM (Virtual Machine): multiple virtual machines can be created on one server, and different virtual machines can belong to different VXLANs. Virtual machines belonging to the same VXLAN are in the same logic two-layer network and are communicated with each other in two layers; two levels of isolation between virtual machines belonging to different VXLANs. VXLAN is identified by VXLAN ID, also known as VNI (VXLAN Network Identifier), which is 24 bits long.

VTEP (VXLAN Tunnel End Point ): edge device of VXLAN. The VXLAN processing is performed on the VTEP, for example, to identify the VXLAN to which the ethernet data frame belongs, to perform two-layer forwarding on the data frame based on the VXLAN, and to encapsulate/decapsulate the packet. The VTEP may be an independent physical device, or may be a server where the virtual machine is located, and is not limited herein.

VXLAN tunnel: a point-to-point logical tunnel between two VTEPs. After encapsulating a VXLAN header, a UDP (User data Protocol) header, and an IP header for a data frame, the VTEP forwards the encapsulated packet to a remote VTEP through a VXLAN tunnel, and the remote VTEP decapsulates the packet.

Core equipment: devices in an IP core network. The core device does not participate in VXLAN processing, and only needs to forward the message in three layers according to the destination IP address of the encapsulated message.

VSI (Virtual Switch Instance): a virtual switching instance on the VTEP provides a two-layer switching service for VXLAN. The VSI can be viewed as a virtual switch on the VTEP that performs layer two forwarding based on VXLAN, and has all the functions of a conventional ethernet switch, including source MAC address learning, MAC address aging, flooding, and the like. VSIs correspond one-to-one to VXLANs.

AC (Attachment Circuit, access Circuit): the VTEP connects physical or virtual circuits of the local site. On the VTEP, the three-tier interface or ethernet service instance (service instance) associated with the VSI is referred to as the AC. Wherein an ethernet service instance is created on a layer two ethernet interface that defines a set of matching rules for matching data frames received from the layer two ethernet interface. The service instance AC is configured under 1 two-layer physical port.

Furthermore, EVPN (Ethernet Virtual Private Network) is a two-layer VPN technology, where the control plane uses MP-BGP (Border Gateway Protocol) to announce EVPN routing information, and the data plane uses VXLAN encapsulation to forward packets. The EVPN has the advantages of simplifying configuration, realizing VTEP automatic discovery, VXLAN tunnel automatic establishment and VXLAN automatic association through MP-BGP, avoiding manual configuration of a user and reducing network deployment difficulty. And the control plane and the data plane are separated, the control plane is responsible for issuing the routing information, the data plane is responsible for forwarding the message, the division of labor is clear, and the management is easy.

It should be noted that the virtual machine migration method provided by the present invention may be applied in an SDN architecture, such as the SDN architecture shown in fig. 1, where the SDN architecture may include an SDN controller, a cloud management platform, several VTEPs, and VMs. The VTEP device may be a VXLAN-capable hardware device or a device integrated with VXLAN-capable software, and the VM may run an operating system OS and various applications. Each VTEP device can be regarded as a switch of a virtual subnet (shortly: subnet), so that all VMs in the subnet corresponding to each VTEP device can communicate with VMs outside the subnet through the VTEP device, and VTEP devices can establish a VXLAN tunnel, so as to transmit data of the virtual network through the VXLAN tunnel. A plurality of VMs can be mounted under the VTEP, for example, as shown in fig. 1, the SDN architecture includes VTEP devices, such as VTEP1 and VTEP2, and virtual machines, such as VM1, VM2, VM3, and VM4, where VM1, VM2, and VM3 belong to a subnet corresponding to VTEP1 and communicate with VMs outside the subnet through VTEP1, and similarly, VM4 belongs to a subnet corresponding to VTEP2 and communicates with VMs outside the subnet through VTEP 2. It should be noted that the VTEP device includes at least one egress interface, and the VTEP device communicates with the VMs in its corresponding subnet through the egress interface, and each VM corresponds to one VTEP device egress interface. A cloud management platform is connected between each VM and the SDN controller for managing communications between the VM and the SDN controller, and in some examples, the cloud management platform may further connect a VTEP device. The SDN controller is used for maintaining ARP table entries of the VTEP equipment in a unified mode, and the ARP table entries comprise mapping relations between the VTEP equipment output interface information and MAC addresses (physical addresses) and IP addresses of all VMs in a corresponding subnet of the VTEP equipment. The virtual machine migration method includes the steps that VMs are stored in physical hosts, the physical hosts are mounted under VTEPs, ARP table entries of one VTEP comprise MAC addresses and IP addresses of the physical hosts where the VMs under the VTEP are located, and the virtual machine migration is to migrate the VMs from one physical host to another physical host. Generally, when a VM is online, the VM sends a registration request to an SDN controller, and uploads a mapping relationship corresponding to the registration request to the SDN controller, and after the SDN controller obtains the mapping relationship corresponding to the VM from the VM, the SDN controller generates an ARP entry for a VTEP device corresponding to the VM based on the mapping relationship, and then issues the ARP entry corresponding to each VTEP device to all VTEP devices managed by the SDN controller.

The first embodiment,

Referring to fig. 2, the present invention provides a virtual machine migration method applied to an SDN controller side, where the method includes:

s11, receiving a second migration request sent by the cloud management platform in response to the first migration request triggered by the virtual machine.

When a virtual machine (hereinafter referred to as a VM) needs to be migrated, a first migration request is sent to a cloud management platform, and after receiving the first migration request, the cloud management platform generates a second migration request and sends the second migration request to an SDN controller. In some examples, the first migration request and the second migration request may be the same migration request, that is, the cloud management platform forwards the first migration request to the SDN controller after receiving the first migration request. Wherein, the first migration request and/or the second migration request may include an IP address, a MAC address, and a VLAN of the VM.

It should be noted that the VM migration is a transfer of a VM from a physical host where the VM is located to another physical host.

S12, acquiring a virtual extended local area network tunnel endpoint VTEP stored in an ARP table entry warning information table, and acquiring each physical host identity corresponding to the VTEP, wherein the VTEP in the ARP table entry warning information table is the VTEP of which the ARP table entry quantity reaches a preset threshold value.

Specifically, an ARP table entry warning information table is pre-stored in the SDN controller, one or more VTEP identifiers are stored in the ARP table entry warning information table, the VTEPs corresponding to the VTEP identifiers are VTEPs whose ARP table entry number reaches a preset threshold, a physical host identifier corresponding to each VTEP is queried through the VTEP identifiers, and migration response information carrying the physical host identifiers is generated to notify which physical hosts exist under the VTEPs with insufficient ARP table entry margin of the cloud management platform, so that the cloud management platform is prevented from migrating virtual machines into the physical hosts. The preset threshold may be any integer greater than or equal to 1, such as 200, 300, and the like, and is not limited herein.

And S13, sending migration response information carrying the physical host identifier to the cloud management platform, so that the cloud management platform deletes the physical host corresponding to the physical host identifier from the virtual machine migration target host option table.

Specifically, the SDN controller sends migration response information carrying the physical host identifier to the cloud management platform, and the cloud platform manages and receives the migration response information, acquires the physical host identifier carried therein, and deletes the physical host corresponding to the physical host identifier from the virtual machine migration target host option list, that is, eliminates the physical host, so that when a target host for virtual machine migration is selected, a physical host with insufficient ARP table entry margin can be prevented from being selected as the target host for migration.

The ARP entry may be used to query the MAC address of the target device (e.g., VM) via the IP address of the target device to ensure smooth communication. Because the processing capacity of each VTEP is limited, when the ARP table entry of one VTEP reaches the maximum specification, the ARP table entry can not be learned and responded according to the ARP message requesting the gateway MAC address, and the ARP request message can not be sent out according to the target IP address of the three-layer forwarded Ethernet data message to learn the ARP table entry, so that the forwarding failure of the data message of the user of the EVPN network is caused.

In some examples, prior to performing virtual machine migration, the SDN controller and the cloud management platform need to be configured first. Before S11, the method further includes: and the cloud management platform establishes connection with the SDN controller.

Specifically, the SDN controller is interfaced with the cloud management platform through a TCP (Transmission Control Protocol), an undefined port is selected as a port for transmitting a TCP data packet, and the SDN controller is connected with the cloud management platform through heartbeat information storage.

In some examples, after the cloud management platform establishes the connection with the SDN controller, the method further includes: information types communicated between the SDN controller and the cloud management platform are defined.

Specifically, the information types communicated between the SDN controller and the cloud management platform include: migration request information (e.g., first migration request and second migration request), migration response information, migration confirmation information. The migration request information may include an IP address, an MAC address, and a VLAN of the virtual machine, the migration response information may include a physical host identifier corresponding to a VTEP in the warning information table of the IP address, the MAC address, the VLAN, and the ARP entry of the virtual machine, and the migration confirmation information may include the IP address, the MAC address, the VLAN, and the physical host identifier after migration of the virtual machine.

In some examples, after defining the type of information communicated between the SDN controller and the cloud management platform, the method further comprises: the SDN controller creates a mapping table of VTEPs to physical hosts. The mapping table is stored in the SDN controller, the mapping table comprises the identifications of all VTEPs managed by the SDN controller and the identifications of all physical hosts corresponding to all VTEPs, and the physical hosts under all VTEPs can be inquired through the mapping table.

In some examples, after creating the mapping table of VTEPs to physical hosts, the method further comprises: the SDN controller sets each ARP table entry, and the content of the ARP table entry can include the MAC address of a VM under the VTEP, the ARP address, the attributive VTEP identifier and the attributive physical host identifier.

Example II,

Fig. 3 shows a flowchart of a virtual machine migration method according to another embodiment of the present invention. Referring to fig. 3, the method comprises the steps of:

and S01, receiving ARP table item warning information sent by the VTEP in response to the ARP table item quantity reaching a preset threshold value.

Specifically, after the connection between the SDN controller and the cloud management platform is established, when the ARP entry remaining amount of one VTEP is insufficient, that is, when the number of ARP entries reaches a preset threshold, the VTEP sends ARP entry warning information to the SDN controller, where the ARP entry warning information carries an identifier of the VTEP. The VTEP may send ARP entry warning information to the SDN controller through a northbound interface, such as OPENFLOW protocol. The preset threshold may be any integer greater than or equal to 1, such as 200, 300, and the like, and is not limited herein.

And S02, creating an ARP table item warning information table according to the ARP table item warning information.

Specifically, the SDN controller receives the ARP entry warning information, acquires the identifier of the VTEP whose number of ARP entries carried therein reaches a preset threshold, creates an ARP entry warning information table, and records the VTEP identifier in the ARP entry warning information table. It should be noted that the SDN controller creates the ARP entry warning information table only when receiving the first ARP entry warning information, and then records the VTEP identifier in the ARP entry warning information into the created ARP entry warning information table only when receiving an ARP entry warning information.

Step S01 and step S02 are optional steps, and in some embodiments, step S01 and/or step S02 may be omitted.

S121, acquiring VTEP identification stored in the ARP table entry warning information table.

Specifically, the SDN controller obtains, from a pre-stored ARP entry warning information table, an identifier of a VTEP for which the number of stored ARP entries reaches a preset threshold.

S122, acquiring each physical host identifier corresponding to the VTEP identifier from a preset mapping table of the VTEP and the physical host.

Specifically, after acquiring the VTEP identifiers stored in the ARP entry warning information table, the SDN controller acquires physical host identifiers corresponding to all VTEPs of the ARP entry warning information table according to a pre-stored mapping table between VTEPs and physical hosts, and generates migration response information carrying the physical host identifiers.

Step S121 and step S122 are one implementation manner of step S12, and step S12 may also be implemented in other manners, for example, the mapping relationship between the VTEP and the physical host may be directly stored in the ARP entry warning information table, so that the VTEP identifier and the physical host identifier corresponding to the VTEP identifier may be obtained through the ARP entry warning information table.

S14, migration confirmation information sent by the cloud management platform in response to the migration success information triggered by the virtual machine is received, wherein the migration confirmation information comprises a VTEP mark corresponding to the migrated virtual machine.

Specifically, the SDN controller sends migration response information carrying physical host identifiers corresponding to VTEPs with insufficient ARP table entry allowance to a cloud management platform, the cloud platform manages and receives the migration response information, obtains the physical host identifiers carried in the migration response information, deletes the physical hosts corresponding to the physical host identifiers from a virtual machine migration target host option list, selects the remaining physical hosts as target hosts to perform VM migration, sends migration success information to the cloud management platform after the VM migration is successful, sends migration confirmation information to the SDN controller after the cloud management platform receives the migration success information, and the migration confirmation information comprises the VTEP identifiers corresponding to the migrated virtual machines so as to inform the SDN controller of the VTEPs after the virtual machines are migrated.

S15, determining a target VTEP according to whether the corresponding VTEP before the virtual machine is migrated is the same as the corresponding VTEP after the virtual machine is migrated.

Specifically, according to whether the VTEP attributed to the physical host to which the VM belongs after migration is the same as the VTEP attributed to the physical host to which the VM belongs before migration, the object (i.e., the target VTEP) for sending the flow table after update is different from the object for sending the original flow table.

Step S15 is an optional step, and in some embodiments, step S15 may also be omitted.

In some examples, referring to fig. 4, fig. 4 includes a plurality of substeps of S15, and S15 may include:

and S151, determining the corresponding VTEP after the virtual machine is migrated according to the VTEP identifier.

Specifically, the VTEP identifier corresponding to the migrated virtual machine carried in the migration confirmation information is obtained, and the VTEP after the virtual machine migration is determined.

S152, whether the corresponding VTEP before the virtual machine migration is the same as the corresponding VTEP after the virtual machine migration is compared.

Specifically, according to the identification of the VTEP corresponding to the virtual machine before migration in the ARP entry stored in the SDN controller, comparing the identification with the obtained VTEP identification corresponding to the virtual machine after migration, and determining whether the VTEP to which the physical host after migration belongs is the same as the VTEP to which the physical host before migration belongs.

S1531, if the VTEP to which the physical host belongs after the virtual machine migration is the same as the VTEP to which the physical host belongs before the virtual machine migration, determining that the target VTEP is the VTEP after the virtual machine migration.

S1532, if the VTEP to which the physical host after the virtual machine migration belongs is different from the VTEP to which the physical host before the virtual machine migration belongs, determining that the target VTEP is each VTEP managed by the SDN controller to which the corresponding VTEP after the virtual machine migration belongs (including the VTEP to which the physical host after the virtual machine migration belongs).

And S16, sending the flow table corresponding to the virtual machine to the target VTEP.

During the operation of the switch, the basis of data forwarding is the flow table. In the traditional network device, the data forwarding of the switch and the router needs to rely on a two-layer MAC address forwarding table or a three-layer IP address routing table stored in the device, and the flow table is the same, and only the table entries of the flow table integrate the network configuration information of each layer in the network, so that richer rules can be used during data forwarding. The flow table contains the port number of the ethernet switch connected downstream, when the VTEP corresponding to the physical host after the virtual machine migration changes, the flow table corresponding to the VTEP after the migration needs to be updated to each VTEP because the VTEP address of the next hop may change, and if the VTEP corresponding to the physical host after the virtual machine migration does not change, only the flow table of the VTEP where the current virtual machine is located needs to be updated, so in both cases, the sending of the flow table is different from the target VTEP.

Step S16 is an optional step, and in some embodiments, step S16 may also be omitted.

In some examples, with continued reference to fig. 4, fig. 4 includes a plurality of substeps of S16, S16 including:

s161, sending the request of clearing the original flow table of the corresponding virtual machine to the target VTEP.

If the VTEP to which the physical host belongs after the virtual machine migration is the same as the VTEP to which the physical host before the virtual machine migration belongs, sending an original flow table clearing request to the VTEP corresponding to the physical host after the virtual machine migration, enabling the VTEP corresponding to the physical host after the virtual machine migration to clear the currently stored flow table, and feeding back clearing confirmation information to the SDN controller after the VTEP corresponding to the physical host after the virtual machine migration clears the flow table.

If the VTEP to which the physical host belongs after the virtual machine migration is different from the VTEP to which the physical host before the virtual machine migration belongs, sending an original flow table clearing request to all VTEPs (including the VTEP to which the physical host after the virtual machine migration belongs) managed by the SDN controller to which the corresponding VTEP after the virtual machine migration belongs, enabling all VTEPs managed by the SDN controller to which the corresponding VTEP after the migration to clear the currently stored flow tables, and feeding back clearing confirmation information to the SDN controller after all VTEPs managed by the SDN controller to which the corresponding VTEP after the migration belongs clear the flow tables.

And S162, receiving clearing confirmation information returned by the target VTEP responding to the original flow table clearing request, and sending an ARP request corresponding to the virtual machine to the corresponding VTEP after the migration, so that the corresponding VTEP after the migration forwards the ARP request to the virtual machine.

Specifically, after receiving the clearing confirmation information fed back by the target VTEP, the SDN controller sends an ARP request of the corresponding virtual machine to the VTEP corresponding to the migrated VTEP, and performs ARP update. The ARP request carries the identification of the migrated virtual machine and broadcast range indication information, and the broadcast range indication information is used for indicating that the ARP request is only broadcast in a two-layer VNI domain of a VTEP downlink. After receiving the ARP request, the VTEP broadcasts the ARP request in a second-layer VNI domain of a downstream connection, after receiving the ARP request, the VM1 returns ARP response information to the VTEP, and the VTEP sends the ARP response information to the SDN controller to finish ARP updating.

And S163, receiving ARP response information returned by the corresponding VTEP after the migration, wherein the ARP response information is sent by the virtual machine in response to the ARP request.

Specifically, the ARP response information carries the port number of the ethernet switch that the VM is linked up, so as to ensure that the VM can communicate normally.

And S164, creating a flow table corresponding to the virtual machine according to the ARP response information and sending the flow table to the target VTEP.

Specifically, after updating port information according to the ARP response information, the SDN controller creates a new flow table, and if the VTEP to which the physical host after the virtual machine migration belongs is the same as the VTEP to which the physical host before the virtual machine migration belongs, sends the new flow table to the VTEP corresponding to the physical host after the virtual machine migration.

And if the VTEP to which the physical host belongs after the virtual machine migration is different from the VTEP to which the physical host before the virtual machine migration belongs, sending a new flow table to each VTEP (including the VTEP to which the physical host after the virtual machine migration belongs) managed by the SDN controller to which the corresponding VTEP after the virtual machine migration belongs. Through the steps, the migrated virtual machine can normally communicate with the VTEP and SDN controllers.

Example III,

The invention provides a virtual machine migration method, which is applied to a cloud management platform side, and referring to fig. 5, the method comprises the following steps:

s21, responding to a first migration request triggered by the virtual machine, sending a second migration request to the SDN controller, enabling the SDN controller to obtain VTEPs stored in an ARP table entry warning information table, and obtaining physical host identifiers corresponding to the VTEPs, wherein the VTEPs in the ARP table entry warning information table are the VTEPs with the ARP table entry quantity reaching a preset threshold value.

Specifically, when the virtual machine needs to be migrated, a first migration request is sent to the cloud management platform, and after receiving the first migration request, the cloud management platform generates a second migration request and sends the second migration request to the SDN controller. In some examples, the first migration request and the second migration request may be the same migration request, that is, the cloud management platform forwards the first migration request to the SDN controller after receiving the first migration request. Wherein, the first migration request and/or the second migration request may include an IP address, a MAC address, and a VLAN of the VM. After receiving the second migration request, the SDN controller acquires VTEP identifiers stored in a pre-stored ARP entry warning information table, where the VTEP identifiers are VTEP identifiers whose ARP entry number reaches a preset threshold, acquires physical host identifiers corresponding to all VTEP identifiers in the ARP entry warning information table from a pre-stored mapping table of VTEP and physical hosts, and generates migration response information carrying the physical host identifiers.

S22, receiving migration response information carrying the physical host identifier and sent by the SDN controller, and deleting the physical host corresponding to the physical host identifier from the virtual machine migration target host option list.

Specifically, the cloud management platform receives migration response information sent by the SDN controller, acquires physical host identifiers carried therein, and deletes physical hosts corresponding to the physical host identifiers from a virtual machine migration target host option table, that is, eliminates the physical hosts, so that when a target host for virtual machine migration is selected, a physical host with insufficient ARP table entry allowance can be prevented from being selected as the target host for migration.

In some examples, referring to fig. 6, after S22, the method further comprises:

and S23, sending migration confirmation information to the SDN controller in response to the migration success information triggered by the virtual machine, enabling the SDN controller to determine a target VTEP according to whether the VTEP corresponding to the virtual machine before migration is the same as the VTEP corresponding to the virtual machine after migration, and sending a flow table corresponding to the virtual machine to the target VTEP, wherein the migration confirmation information comprises a VTEP identifier corresponding to the virtual machine after migration.

Specifically, the SDN controller sends migration response information carrying physical host identifiers corresponding to VTEPs with insufficient ARP table entry allowance to a cloud management platform, the cloud platform manages and receives the migration response information, obtains the physical host identifiers carried in the migration response information, deletes physical hosts corresponding to the physical host identifiers from a virtual machine migration target host option list, selects the remaining physical hosts as target hosts to perform VM migration, after VM migration is successful, the VM sends migration success information to the cloud management platform, after the cloud management platform receives the migration success information, migration confirmation information is sent to the SDN controller, the migration confirmation information comprises VTEP identifiers corresponding to the migrated virtual machines, and the SDN controller is informed of the VTEPs after the virtual machines are migrated. After receiving the migration confirmation information, the SDN controller obtains a VTEP identifier corresponding to the migrated virtual machine carried in the migration confirmation information, determines a VTEP after the migration of the virtual machine, and then compares the VTEP identifier corresponding to the migrated virtual machine with the VTEP identifier corresponding to the migrated virtual machine, according to an identifier of a VTEP corresponding to the migrated virtual machine before the virtual machine is stored in an ARP entry of the SDN controller, determines whether the VTEP to which the physical host after the migration of the virtual machine belongs is the same as the VTEP to which the physical host before the migration belongs, determines that the target VTEP is the VTEP after the migration if the VTEP to which the physical host after the migration of the virtual machine belongs is the same as the VTEP to which the physical host before the migration belongs, and determines that the target VTEP is each VTEP managed by the SDN controller to which the corresponding VTEP after the migration belongs (including the VTEP to which the physical host after the migration of the virtual machine belongs) if the VTEP after the migration of the virtual machine is different from the VTEP before the migration, and after determining the target VTEP, the SDN corresponding to forward data to the target VTEP corresponding to the target VTEP.

Example four,

Referring to fig. 7, the present invention provides a virtual machine migration apparatus, including:

the first receiving module 101 is configured to receive a second migration request sent by the cloud management platform in response to the first migration request triggered by the virtual machine.

An obtaining module 102, configured to obtain a virtual local area network tunnel endpoint VTEP stored in an ARP table entry warning information table, and obtain each physical host identifier corresponding to the VTEP, where a VTEP in the ARP table entry warning information table is a VTEP whose ARP table entry number reaches a preset threshold.

A first sending module 103, configured to send migration response information carrying the physical host identifier to the cloud management platform, so that the cloud management platform deletes the physical host corresponding to the physical host identifier from the virtual machine migration target host option table.

Example V,

Referring to fig. 8, the present invention provides a virtual machine migration apparatus, including:

a second sending module 201, configured to send a second migration request to the SDN controller in response to the first migration request triggered by the virtual machine, so that the SDN controller obtains VTEPs stored in the ARP entry warning information table, and obtains each physical host identifier corresponding to the VTEP, where the VTEP in the ARP entry warning information table is a VTEP whose ARP entry number reaches a preset threshold.

A second receiving module 202, configured to receive migration response information carrying a physical host identifier sent by the SDN controller, and delete a physical host corresponding to the physical host identifier from the virtual machine migration target host option table.

According to the virtual machine migration device provided by the embodiment of the invention, before the virtual machine migration, the SDN (Software Defined Network) controller is used for acquiring each physical host under the VTEP with insufficient ARP table entry allowance, so that the problem that the virtual machine is migrated to the physical host corresponding to the VTEP with insufficient ARP table entry allowance to cause that ARP table entry learning cannot be carried out can be avoided, and the problem that data messages cannot be normally forwarded after the migration can be avoided.

Examples six,

The present invention provides an electronic device, including:

at least one processor. And

a memory communicatively coupled to the at least one processor. Wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the virtual machine migration method described above.

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.

Referring to fig. 9, fig. 9 shows a schematic block diagram of an example electronic device 800 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not intended to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 9, the apparatus 800 includes a computing unit 801 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 802 or a computer program loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the device 800 can also be stored. The calculation unit 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

A number of components in the device 800 are connected to the I/O interface 805, including: an input unit 806, such as a keyboard, a mouse, etc. An output unit 807 such as various types of displays, speakers, and the like. A storage unit 808 such as a magnetic disk, optical disk, or the like. And a communication unit 809 such as a network card, modem, wireless communication transceiver, etc. The communication unit 809 allows the device 800 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

Computing unit 801 may be a variety of general and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and the like. The computing unit 801 performs the various methods and processes described above, such as the virtual machine migration method. For example, in some embodiments, the virtual machine migration method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of a computer program may be loaded onto and/or installed onto device 800 via ROM 802 and/or communications unit 809. When the computer program is loaded into RAM 803 and executed by computing unit 801, one or more steps of the virtual machine migration method described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the virtual machine migration method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

Example seven,

The present invention provides a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to execute the method according to the above.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user. And a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with the user. For example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback). And input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server combining a blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.

According to the virtual machine migration method provided by the embodiment of the invention, before the virtual machine migration, the SDN (Software Defined Network) controller is used for acquiring each physical host under the VTEP with insufficient ARP table entry allowance, so that the problem that the virtual machine is migrated to the physical host corresponding to the VTEP with insufficient ARP table entry allowance, the ARP table entry learning cannot be carried out, and the problem that the data message cannot be normally forwarded after the migration can be avoided.

It will be understood that the above embodiments are merely exemplary embodiments taken to illustrate the principles of the present invention, which is not limited thereto. It will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the spirit and substance of the invention, and these modifications and improvements are also considered to be within the scope of the invention.

Claims

1. A virtual machine migration method is applied to an SDN controller and comprises the following steps:

sending migration response information carrying the physical host identifier to the cloud management platform, so that the cloud management platform deletes the physical host corresponding to the physical host identifier from a virtual machine migration target host option table;

before receiving a second migration request sent by the cloud management platform in response to the first migration request triggered by the virtual machine, the method further includes:

creating the ARP table entry warning information table according to the ARP table entry warning information;

the acquiring a virtual extended local area network tunnel endpoint VTEP stored in an ARP table entry warning information table, and acquiring each physical host identifier corresponding to the VTEP, includes:

acquiring the VTEP identifier stored in the ARP table item warning information table;

and acquiring each physical host identifier corresponding to the VTEP identifier from a preset mapping table of the VTEP and the physical host.

2. The method of claim 1, wherein after sending migration response information carrying the physical host identifier to the cloud management platform to enable the cloud management platform to delete the physical host corresponding to the physical host identifier from a virtual machine migration target host option table, the method further comprises:

3. The method of claim 2, wherein the sending the flow table corresponding to the virtual machine to the target VTEP comprises:

4. The method according to claim 2 or 3, wherein the determining a target VTEP according to whether the VTEP corresponding to the virtual machine before migration is the same as the VTEP corresponding to the virtual machine after migration comprises:

and comparing whether the VTEP corresponding to the virtual machine before migration is the same as the VTEP corresponding to the virtual machine after migration, if so, determining that the target VTEP is the VTEP corresponding to the virtual machine after migration, and if not, determining that the target VTEP is each VTEP managed by a Software Defined Network (SDN) controller to which the VTEP corresponding to the virtual machine after migration belongs.

5. A virtual machine migration method is applied to a cloud management platform and comprises the following steps:

receiving migration response information carrying the physical host identifier sent by the SDN controller, and deleting the physical host corresponding to the physical host identifier from a virtual machine migration target host option table;

before the SDN controller receives a first migration request triggered by the cloud management platform in response to the virtual machine and sends a second migration request to the SDN controller, the method further includes:

the SDN controller receives ARP table item warning information sent by the VTEP in response to the ARP table item quantity reaching a preset threshold value;

creating the ARP table item warning information table according to the ARP table item warning information;

the enabling the SDN controller to obtain the VTEP stored in an ARP entry warning information table and obtain the physical host identifiers corresponding to the VTEP includes:

the SDN controller acquires the VTEP identifier stored in the ARP table item warning information table;

and the SDN controller acquires each physical host identifier corresponding to the VTEP identifier from a preset mapping table of the VTEP and the physical host.

6. The method of claim 5, wherein after receiving migration response information carrying the physical host identifier sent by the SDN controller and deleting a physical host corresponding to the physical host identifier from a virtual machine migration target host option table, the method further comprises:

responding migration success information triggered by a virtual machine, sending migration confirmation information to the SDN controller, enabling the SDN controller to determine a target VTEP according to whether a VTEP corresponding to the virtual machine before migration is the same as a VTEP corresponding to the virtual machine after migration, and sending a flow table corresponding to the virtual machine to the target VTEP, wherein the migration confirmation information comprises a VTEP identifier corresponding to the virtual machine after migration.

7. A virtual machine migration device applied to an SDN controller comprises the following components:

the first receiving module is used for receiving a second migration request sent by the cloud management platform in response to the first migration request triggered by the virtual machine;

a first sending module, configured to send migration response information carrying the physical host identifier to the cloud management platform, so that the cloud management platform deletes the physical host corresponding to the physical host identifier from a virtual machine migration target host option table;

before the receiving of the second migration request sent by the cloud management platform in response to the first migration request triggered by the virtual machine, the method further includes:

acquiring the VTEP identifier stored in the ARP table entry warning information table;

8. The virtual machine migration device is applied to a cloud management platform and comprises the following components:

a second receiving module, configured to receive migration response information carrying the physical host identifier sent by the SDN controller, and delete the physical host corresponding to the physical host identifier from a virtual machine migration target host option table;

wherein, the enabling the SDN controller to obtain the VTEP stored in the ARP entry warning information table and obtain each physical host identifier corresponding to the VTEP includes:

the SDN controller acquires the VTEP identifier stored in the ARP table entry warning information table;

9. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-4 or to perform the method of any one of claims 5-6.

10. A non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any one of claims 1-4 or to perform the method of any one of claims 5-6.