CN107276783A - A kind of methods, devices and systems for realizing virtual machine unified management and intercommunication - Google Patents

Abstract

The method, device and system for realizing the unified management and intercommunication of virtual machines provided by the present invention construct the first flow table and send the first flow table to the first switch for forwarding the information sent and received by the first virtual machine. The first flow table contains the first flow table Mapping information between a virtual machine and a virtual network; construct a second flow table, and send the second flow table to a second switch for forwarding information sent and received by the second virtual machine, the second flow table includes the second virtual machine and the virtual network Mapping information between networks. It realizes unified management of different types of virtual machines, enhances service capabilities, and reduces operating costs. In addition, the forwarding process between the first virtual machine and the first switch is performed through the first flow table; the forwarding process between the second virtual machine and the second switch is performed through the second flow table. The intercommunication between different types of virtual machines is realized, the network scale in the virtual data center is expanded, and the network scale and range that the virtual data center system can manage are larger.

Description

A method, device and system for realizing unified management and intercommunication of virtual machines

technical field

The invention relates to a communication network, in particular to a method, device and system for realizing unified management and intercommunication of virtual machines.

Background technique

A virtualized data center (Virtual Data Center, VDC) is a new data center form that applies the concept of cloud computing to an IDC (Internet Data Center, Internet Data Center). Through the combination of traditional IDC business and cloud computing technology, build a unified and innovative VDC operation management system, apply technologies such as virtualization and automatic deployment, build a scalable virtual infrastructure, adopt centralized management and distributed service mode, and provide users with one-point Basic IT infrastructure solutions and services for acceptance and network-wide services. The main difference between VDC and traditional IDC is that infrastructure is provided as a service through technical means; physical resources are abstracted and integrated through virtualization technology to enhance service capabilities; resource utilization capabilities and service reliability are improved through dynamic resource allocation and scheduling; Automated service provisioning capabilities, lower operation and maintenance costs, and provide a convenient user experience; provide more security mechanisms and reliability mechanisms to meet the security standards of enterprise-level applications.

Software Defined Network (Software Defined Network, SDN), its core technology, OpenFlow, realizes flexible control of network traffic by separating the control plane of network equipment from the data plane, and provides a good platform for core network and application innovation. Currently, in terms of relatively pure SDN in carrier networks, it is possible to start with scenarios such as data centers with relatively closed networks to build a new type of SDN-enhanced VDC. By introducing an SDN controller on the network control side, the vSwitch built on the computing resources and the ToR (Top of Rack switch) hardware switch enhanced by the OF protocol are centrally controlled to change the traditional data center. The network topology is a large two-layer network architecture.

In the existing technology, the virtual data center involves many network elements, including Openstack virtual platform, VMware ESXi virtual platform, SDN, DVS, ToR switch and other network elements, but the management portal of the virtual data center cannot manage different types of resource pools at the same time For example, VMware and KVM resource pools cannot be managed at the same time. If the management portal can manage both VMware and KVM resource pools at the same time, then these two computing resources can meet the needs of flexible networking, that is, the original VMware ESXi virtual platform can be retained. It can be integrated and interoperated with the Openstack virtual platform. While enhancing service capabilities and reducing operating costs, the SDN-based virtual data center system can manage a larger network scale and scope.

Openstack virtual platform: OpenStack is an open source cloud computing management platform project, which is composed of several main components to complete specific work. OpenStack supports almost all types of cloud environments. The goal of the project is to provide a cloud computing management platform that is simple to implement, scalable, rich, and standardized.

VMware ESXI virtual platform: VMware virtual machine software, providing server and desktop virtualization solutions, is an enterprise-level virtual platform that can run directly on hardware.

SDN controller: What SDN does is to separate the control rights on the network devices and manage them by a centralized controller without relying on the underlying network devices (routers, switches, firewalls), shielding the differences from the underlying network devices.

VDC management system management portal sub-module: resource management system, which mainly provides centralized, elastic, and highly reliable computing, storage, and network resources for VDC, unified management, on-demand allocation, and rental services.

TOR switch: A top-of-rack switch, usually used for physical server access, needs to provide stacking/clustering capabilities. The switch behind the stacking/clustering supports the OpenFlow protocol, and supports port aggregation (same device or cross-device) and hairpin forwarding.

DVS: A virtual switch that can be used to form a virtual network. At the same time, it is necessary to provide a Hypervisoragent (a proxy virtual machine located in ESXI) to register or log out of the VMware virtual machine vlan.

Contents of the invention

The main technical problem to be solved by the present invention is to provide a method, device and system for realizing the unified management and intercommunication of virtual machines, so as to solve the problem that the management interface in the prior art cannot simultaneously manage virtual machines of different types and between virtual machines of different types. Inability to interoperate, resulting in insufficient service capabilities, high operation and maintenance costs, and limitations in the network scale and scope that the virtual data center system can manage.

In order to solve the above-mentioned technical problems, the present invention provides a method for realizing unified management of virtual machines, including: constructing a first flow table, and sending the first flow table to a first switch for forwarding information sent and received by the first virtual machine, so The first flow table includes mapping information between the first virtual machine and the virtual network; construct a second flow table, and send the second flow table to the second switch for forwarding the information sent and received by the second virtual machine, so The second flow table includes mapping information between the second virtual machine and the virtual network.

In an embodiment of the present invention, the constructing the first flow table includes: sending a message containing the identification information of the first virtual machine to the controller for learning; The information of the mapping relationship between the physical address of the machine and the virtual network is encapsulated into the first flow table.

In an embodiment of the present invention, the constructing the second flow table includes: receiving an association message forwarded by the second switch, and setting the port of the second virtual machine and the virtual flow table according to the association message. Mapping between networks: encapsulating information including the mapping relationship between the port and the virtual network into the second flow table.

In an embodiment of the present invention, before constructing the second flow table, it further includes: registering the second virtual machine with the second switch and the controller, and performing the connection between the second virtual machine and the virtual Mapping between LAN and port IDs.

The present invention provides a method for realizing virtual machine intercommunication, comprising: sending a first message to a first switch or a second switch, the first message includes network protocol data packets and virtual local area network information; according to the first message The document determines to perform forwarding processing; perform forwarding processing between the first virtual machine and the first switch through the first flow table, and the first flow table contains mapping information between the first virtual machine and the virtual network; through the second flow table The table performs forwarding processing between the second virtual machine and the second switch, and the second flow table includes mapping information between the second virtual machine and the virtual network.

In an embodiment of the present invention, implementing the intercommunication between the first virtual machine and the second virtual machine includes: when the first virtual machine and the second virtual machine are on the same network segment, implementing Layer 2 intercommunication between the first virtual machine and the second virtual machine; when the first virtual machine and the second virtual machine are on different network segments, the first virtual machine and the second virtual machine are implemented Layer 2 and Layer 3 communication between two virtual machines.

The present invention provides a device for realizing unified management of virtual machines, including: a first processing unit and a second processing unit, the first processing unit is used to construct a first flow table, and send the first flow table to a The first switch for the first virtual machine to send and receive information, the first flow table includes mapping information between the first virtual machine and the virtual network; the second processing unit is configured to construct a second flow table, and the first flow table includes the mapping information between the first virtual machine and the virtual network; The second flow table is sent to the second switch for forwarding the information sent and received by the second virtual machine, and the second flow table includes mapping information between the second virtual machine and the virtual network.

In an embodiment of the present invention, the first processing unit includes a first processing subunit and a second processing subunit, and the first processing subunit is configured to convert the report containing the identification information of the first virtual machine to The file is sent to the controller for learning; the second processing subunit is configured to encapsulate information including the mapping relationship between the physical address of the first virtual machine and the virtual network into the first flow table after the learning is completed.

In an embodiment of the present invention, the second processing unit includes a third processing subunit and a fourth processing subunit, the third processing subunit is configured to receive the association message forwarded by the second switch, Setting the mapping between the port of the second virtual machine and the virtual network according to the association message; the fourth processing subunit is configured to encapsulate information including the mapping relationship between the port and the virtual network into the Describe the second flow table.

The present invention provides a device for realizing virtual machine intercommunication, including a third processing unit, a fourth processing unit, a fifth processing unit and a sixth processing unit, and the third processing unit is used to send The first message, the first message includes network protocol data packets and virtual local area network information; the fourth processing unit is used to determine forwarding processing according to the first message; the fifth processing unit is used to pass The first flow table performs forwarding processing between the first virtual machine and the first switch, and the first flow table includes mapping information between the first virtual machine and the virtual network; the sixth processing unit is used to pass the second The flow table performs forwarding processing between the second virtual machine and the second switch, and the first flow table includes mapping information between the first virtual machine and the virtual network.

The present invention provides a system for realizing unified management and intercommunication of virtual machines, including: a controller, a first switch and a second switch, the controller is used to construct a first flow table and a second flow table, and set the first flow table Send to the first switch, and send the second flow table to the second switch; the first flow table includes mapping information between the first virtual machine and the virtual network, and the second flow table includes the second Mapping information between a virtual machine and the virtual network; the first switch is configured to receive the first flow table sent by the controller, and communicate with the first virtual machine and the first flow table through the first flow table Forwarding processing between the second switches; the second switch is used to receive the second flow table sent by the controller, and communicate with the second virtual machine and the first virtual machine through the second flow table Forwarding processing between switches; the first switch and the second switch are further configured to receive a first message, and the first message includes network protocol data packets and virtual local area network information.

The beneficial effects of the present invention are:

The method, device and system for realizing the unified management and intercommunication of virtual machines provided by the present invention construct the first flow table and send the first flow table to the first switch for forwarding the information sent and received by the first virtual machine. The first flow table contains the first flow table Mapping information between a virtual machine and a virtual network; construct a second flow table, and send the second flow table to a second switch for forwarding information sent and received by the second virtual machine, the second flow table includes the second virtual machine and the virtual network Mapping information between networks. It realizes unified management of different types of virtual machines, enhances service capabilities, and reduces operating costs.

In addition, by sending the first message to the first switch or the second switch, the first message includes network protocol data packets and virtual local area network information; according to the first message, it is determined to perform forwarding processing; through the first flow table, the first virtual machine For forwarding processing with the first switch, the first flow table includes mapping information between the first virtual machine and the virtual network; for forwarding processing between the second virtual machine and the second switch through the second flow table, the second The flow table includes mapping information between the second virtual machine and the virtual network. The intercommunication between different types of virtual machines is realized, the network scale in the virtual data center is expanded, and the network scale and range that the virtual data center system can manage are larger.

Description of drawings

FIG. 1 is a flowchart of a method for realizing unified management of virtual machines in Embodiment 1 of the present invention;

FIG. 2 is a flowchart of a method for realizing virtual machine intercommunication in Embodiment 2 of the present invention;

FIG. 3 is a schematic diagram of an apparatus for realizing unified management of virtual machines in Embodiment 3 of the present invention;

Fig. 4 is a schematic diagram of the first processing unit in Fig. 3;

Fig. 5 is a schematic diagram of the second processing unit in Fig. 3;

FIG. 6 is a schematic diagram of an apparatus for implementing virtual machine intercommunication in Embodiment 4 of the present invention;

FIG. 7 is a schematic diagram of a system for realizing unified management and intercommunication of virtual machines in Embodiment 5 of the present invention;

8 is a schematic diagram of a system that realizes unified management and intercommunication of KVM and VMware virtual machines in Embodiment 5 of the present invention;

9 is another schematic diagram of a system for realizing unified management and intercommunication of KVM and VMware virtual machines in Embodiment 5 of the present invention;

FIG. 10 is a flowchart of a method for realizing unified management and intercommunication between KVM and VMware virtual machines in Embodiment 5 of the present invention.

detailed description

In order to enable those skilled in the art to better understand the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the implementation of the present invention Examples, not all embodiments; It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present invention.

Embodiment one:

This embodiment provides a method for realizing unified management of virtual machines, please refer to FIG. 1, including:

Step 101, constructing a first flow table, and sending the first flow table to a first switch for forwarding information sent and received by the first virtual machine, the first flow table includes mapping information between the first virtual machine and a virtual network ;

Step 102, construct a second flow table, and send the second flow table to the second switch for forwarding the information sent and received by the second virtual machine, the second flow table includes the second virtual machine and the virtual machine Mapping information between networks.

For step 101, building the first flow table includes sending a packet containing the identification information of the first virtual machine to the controller for learning; after the learning is completed, encapsulating the information containing the mapping relationship between the physical address of the first virtual machine and the virtual network as First stream table. Specifically, first configure the virtual platforms corresponding to the first virtual machine and the second virtual machine on the management interface, after the configuration is completed, create the first virtual machine on the management interface, and the first switch passes the packets of the first virtual machine through The Packet-in Message is sent to the controller to learn the MAC (physical address) of the virtual machine. After the learning is completed, the controller sends the first flow table to the first switch where the first virtual machine is located. The first flow table includes VNET (virtual network) +SRC MAC (source MAC physical network card information of the source virtual machine), the subsequent traffic sent by the first virtual machine can be normally forwarded according to this first flow table. Furthermore, the first virtual machine here may be a KVM virtual machine, the corresponding first switch is a DVS, and the controller here may specifically be an SDN controller. It should be understood that the above-mentioned first virtual machine refers to a type of virtual machine that is different from the second virtual machine, rather than a single virtual machine; in addition, the first virtual machine is not limited to the KVM virtual machine, and the first switch is not limited to The DVS and the controller are not limited to the SDN controller, any module that can realize the content of the above step 1 is within the scope of protection of this embodiment, and can be selected and replaced according to specific needs.

For step 102, constructing the second flow table includes receiving the association message forwarded by the second switch, setting the mapping between the port of the second virtual machine and the virtual network according to the association message; mapping the port containing the second virtual machine and the virtual network The information of is encapsulated into the second flow table. Before constructing the second flow table, it also includes: registering the second virtual machine with the second switch and the controller, and performing mapping between the second virtual machine and the virtual local area network and port identifier. Specifically, create a second virtual machine on the management interface, including {"port_uuid (port identification)", "virtualnetwork_id (virtual network identification)", "name (name)", "ip_address (address)", "mac (physical Address)", "security_groups (security group)"} and other information. Then send an association message for port_uuid, which contains {port_uuid, vid}. After creating the second virtual machine and port_uuid, register with the second switch and the controller through the associated message, the registration information includes port_uuid, vlan, and perform the mapping of VM and vlan, port_uuid; when deleting the virtual machine, then register with the second switch Disassociate with the controller, and notify the controller that the virtual machine has been deleted. After the registration is completed, the second switch sends the association message to the controller according to the flow table issued by the controller in advance, and the controller first determines the access location of the second virtual machine according to the port and dpid of the packet-in sent; Then according to the port_uuid, confirm the information of the second virtual machine associated with the association message; then configure the vlan sub-interface to the port of the second virtual machine according to the in_port of vlan and OpenFlow, and add the vlan sub-interface to the virtual network, that is, set the port-vnet mapping , according to the above process, generate a second flow table, where the second flow table includes the mapping relationship between the second virtual machine port and the VNET; and then send the second flow table to the second switch. Furthermore, the second virtual machine can be a VMware virtual machine, the corresponding second switch is a ToR switch, the controller can be an SDN controller, and the management interface is the management interface of the VDC. When creating a VMware virtual machine, the management of the VDC The interface invokes the northbound interface of the SDN controller through OpenStack to create a VMware virtual machine; the corresponding associated message may specifically be a VDP (VSI Discovery Protocol VSI Discovery Protocol) associated message, and the second flow table may specifically be a VDP protocol flow table.

It should be understood that when the first virtual machine is a KVM virtual machine and the second virtual machine is a VMware virtual machine, the specific virtual platforms configured on the VDC management interface are Openstack virtual platform and VMware virtual platform, and the pre-delivered stream Table can be (Ethertype: 0x8940). The above-mentioned first virtual machine and second virtual machine refer to two types of virtual machines of different types, rather than just one virtual machine; in addition, it should be understood that any module that can realize the above content is within the scope of protection of this embodiment. It can be selected and replaced as required.

The method for realizing the unified management of virtual machines provided by this embodiment is to construct the first flow table and send the first flow table to the first switch for forwarding the information sent and received by the first virtual machine. The first flow table includes the first virtual machine and the virtual machine. Mapping information between networks; build a second flow table, and send the second flow table to a second switch for forwarding information sent and received by the second virtual machine, the second flow table includes mapping information between the second virtual machine and the virtual network . It realizes the unified management of the virtual machine by the management interface, enhances the service capability of the system, and reduces the operation cost.

Embodiment two:

This embodiment provides a method for realizing virtual machine intercommunication, please refer to Figure 2, including:

Step 201, sending a first message to a first switch, where the first message includes a network protocol data packet and virtual local area network information;

Step 202, determine to perform forwarding processing according to the first message;

Step 203, perform forwarding processing between the first virtual machine and the first switch through a first flow table, where the first flow table includes mapping information between the first virtual machine and a virtual network;

Step 204, perform switch forwarding processing between the second virtual machine and the second switch through a second flow table, where the second flow table includes mapping information between the second virtual machine and the virtual network.

Through the above steps, the intercommunication between the virtual machines is realized. Specifically, when the first virtual machine and the second virtual machine are in the same network segment, the Layer 2 forwarding intercommunication between the first virtual machine and the second virtual machine is realized; When the virtual machine and the second virtual machine are on different network segments, the Layer 2 and Layer 3 forwarding intercommunication between the VMware virtual machine and the KVM virtual machine is realized.

Specifically, the IP packet (network protocol data packet) can be added with vlan (virtual local area network) information, encapsulated into a first message, and forwarded to the second switch, and the second switch performs forwarding processing according to the first flow table issued by the controller , so as to realize the forwarding intercommunication of the second layer and the third layer between the virtual machines. If the first virtual machine and the second virtual machine are on the same network segment, and the first virtual machine is used as the destination end, and the second virtual machine is used as the source end, then the Hypervisor adds a vlan to the IP packet of the second virtual machine and forwards it to the second switch , the second switch performs forwarding processing according to the first flow table sent by the controller, vlanpops the message according to vlan and inport, and converts it into metadata (VNET); determines whether host learning is required according to metadata (VNET) and src MAC ;According to the metadata (VNET) and dst MAC to determine the layer-2 forwarding, the first switch at the destination end forwards the request message to the first virtual machine after receiving the request message, and the response message of the first virtual machine is also according to the first flow on the first switch The table is sent to the second switch, and the second switch forwards it to the second virtual machine, thereby realizing Layer 2 intercommunication between the first virtual machine and the second virtual machine. If the first virtual machine and the second virtual machine are on different network segments, the Hypervisor adds vlan1 to the IP packet of the second virtual machine and forwards it to the second switch. The second switch performs forwarding processing according to the flow table sent by the controller. According to the vlan, Inport, the message vlan pop, and converted to metadata (VNET); according to metadata (VNET) and src MAC, determine whether host learning is required; according to metadata (VNET) and dst MAC, determine the second layer forwarding; according to metadata ( VRF) and dst IP, for three-layer forwarding; the first switch at the destination end forwards the request message to the first virtual machine after receiving the request message, and the response message of the first virtual machine is also sent to the first virtual machine according to the first flow table on the first switch. two switches, and the second switch forwards the data to the second virtual machine, thereby realizing Layer 3 intercommunication between the first virtual machine and the second virtual machine.

Furthermore, the first virtual machine may be a KVM virtual machine, the second virtual machine may be a VMware virtual machine, and the controller may be an SDN controller. Correspondingly, the first switch is a DVS, and the second switch is a ToR switch , the above-mentioned first virtual machine and second virtual machine refer to two types of virtual machines of different types, rather than just one virtual machine; in addition, it should be understood that any module that can realize the content described in the above steps is included in this embodiment Within the scope of protection, specific selections and replacements can be made as required.

In this embodiment, by sending the first message to the first switch or the second switch, the first message includes network protocol data packets and virtual local area network information; it is determined to perform forwarding processing according to the first message; The forwarding process between the virtual machine and the first switch, the first flow table contains the mapping information between the first virtual machine and the virtual network; the forwarding process between the second virtual machine and the second switch is performed through the second flow table, and the second flow table contains the first 2. Mapping information between the virtual machine and the virtual network. The intercommunication between different types of virtual machines is realized, the network scale in the virtual data center is expanded, and the network scale and range that the virtual data center system can manage are larger.

Embodiment three:

This embodiment provides a device for realizing unified management of virtual machines. Please refer to FIG. 3 , which includes a first processing unit 11 and a second processing unit 12. To the first switch for forwarding the first virtual machine to send and receive information, the first flow table includes mapping information between the first virtual machine and the virtual network; the second processing unit 12 is used to construct the second flow table, and the second flow table sent to the second switch for forwarding the information sent and received by the second virtual machine, and the second flow table includes the mapping information between the second virtual machine and the virtual network.

Further, referring to FIG. 4 , the first processing unit 11 includes a first processing subunit 111 and a second processing subunit 112, and the first processing subunit 111 is configured to send a message containing the identification information of the first virtual machine to the control The second processing subunit 112 is configured to encapsulate information including the mapping relationship between the physical address of the first virtual machine and the virtual network into a first flow table after the learning is completed.

Specifically, first configure the virtual platforms corresponding to the first virtual machine and the second virtual machine on the management interface, after the configuration is completed, create the first virtual machine on the management interface, and the first switch passes the packets of the first virtual machine through The Packet-in Message is sent to the controller to learn the MAC (physical address) of the virtual machine. After the learning is completed, the controller sends the first flow table to the first switch where the first virtual machine is located. The first flow table includes VNET (virtual network) +SRC MAC (source MAC physical network card information of the source virtual machine), the subsequent traffic sent by the first virtual machine can be normally forwarded according to this first flow table. Furthermore, the first virtual machine here may be a KVM virtual machine, the corresponding first switch is a DVS, and the controller here may specifically be an SDN controller. It should be understood that the above-mentioned first virtual machine refers to a type of virtual machine that is different from the second virtual machine, rather than a single virtual machine; in addition, the first virtual machine is not limited to the KVM virtual machine, and the first switch is not limited to The DVS and the controller are not limited to the SDN controller, and any module that can realize the above content is within the scope of protection of this embodiment, and can be selected and replaced as required.

Further, referring to FIG. 5 , the second processing unit 12 includes a third processing subunit 121 and a fourth processing subunit 122, the third processing subunit 121 is configured to receive the association message forwarded by the second switch, and set the Mapping between the port of the second virtual machine and the virtual network; the fourth processing subunit 122 is configured to encapsulate information including the mapping relationship between the port of the second virtual machine and the virtual network into a second flow table. It should be understood that before constructing the second flow table, it also includes registering the second virtual machine with the second switch and the controller, and performing mapping between the second virtual machine and the virtual local area network and port identifier.

Specifically, create a second virtual machine on the management interface, including {"port_uuid (port identification)", "virtualnetwork_id (virtual network identification)", "name (name)", "ip_address (address)", "mac (physical Address)", "security_groups (security group)"} and other information. Then send an association message for port_uuid, which contains {port_uuid, vid}. After creating the second virtual machine and port_uuid, register with the second switch and the controller through the associated message, the registration information includes port_uuid, vlan, and perform the mapping of VM and vlan, port_uuid; when deleting the virtual machine, then register with the second switch Disassociate with the controller, and notify the controller that the virtual machine has been deleted. After the registration is completed, the second switch sends the association message to the controller according to the flow table issued by the controller in advance, and the controller first determines the access location of the second virtual machine according to the port and dpid of the packet-in sent; Then according to the port_uuid, confirm the information of the second virtual machine associated with the association message; then configure the vlan sub-interface to the port of the second virtual machine according to the in_port of vlan and OpenFlow, and add the vlan sub-interface to the virtual network, that is, set the port-vnet mapping , according to the above process, generate a second flow table, where the second flow table includes the mapping relationship between the second virtual machine port and the VNET; and then send the second flow table to the second switch. Furthermore, the second virtual machine can be a VMware virtual machine, the corresponding second switch is a ToR switch, the controller can be an SDN controller, and the management interface is the management interface of the VDC. When creating a VMware virtual machine, the management of the VDC The interface invokes the northbound interface of the SDN controller through OpenStack to create a VMware virtual machine; the corresponding associated message may specifically be a VDP associated message, and the second flow table may specifically be a VDP protocol flow table.

It should be understood that when the first virtual machine is a KVM virtual machine and the second virtual machine is a VMware virtual machine, the specific virtual platforms configured on the VDC management interface are Openstack virtual platform and VMware virtual platform, and the pre-delivered stream Table can be (Ethertype: 0x8940). The above-mentioned first virtual machine and second virtual machine refer to two types of virtual machines of different types, rather than just one virtual machine; in addition, it needs to be understood that any module that can implement the content described in the above steps 1 and 2 is in the Within the protection scope of this embodiment, it can be selected and replaced as required.

The method for realizing the unified management of virtual machines provided by this embodiment is to construct the first flow table and send the first flow table to the first switch for forwarding the information sent and received by the first virtual machine. The first flow table includes the first virtual machine and the virtual machine. Mapping information between networks; build a second flow table, and send the second flow table to a second switch for forwarding information sent and received by the second virtual machine, the second flow table includes mapping information between the second virtual machine and the virtual network . It realizes the unified management of the virtual machine by the management interface, enhances the service capability of the system, and reduces the operation cost.

Embodiment four:

This embodiment provides a device for realizing virtual machine intercommunication, please refer to FIG. For sending the first message to the first switch or the second switch, the first message includes network protocol data packets and virtual local area network information; the fourth processing unit 14 is used to determine forwarding processing according to the first message; the fifth processing unit 15 is used to perform forwarding processing between the first virtual machine and the first switch through the first flow table, and the first flow table includes mapping information between the first virtual machine and the virtual network; the sixth processing unit 16 is used to perform forwarding processing between the first virtual machine and the virtual network through the second flow table For forwarding processing between the second virtual machine and the second switch, the second flow table includes mapping information between the second virtual machine and the virtual network.

Through the above steps, the intercommunication between the virtual machines is realized. Specifically, when the first virtual machine and the second virtual machine are in the same network segment, the Layer 2 forwarding intercommunication between the first virtual machine and the second virtual machine is realized; When the virtual machine and the second virtual machine are on different network segments, the Layer 2 and Layer 3 forwarding intercommunication between the first virtual machine and the second virtual machine is realized.

Specifically, the IP packet (network protocol data packet) can be added with vlan (virtual local area network) information, encapsulated into a first message, and forwarded to the second switch, and the second switch performs forwarding processing according to the first flow table issued by the controller , so as to realize the forwarding intercommunication of the second layer and the third layer between the virtual machines. If the first virtual machine and the second virtual machine are on the same network segment, and the first virtual machine is used as the destination end, and the second virtual machine is used as the source end, then the Hypervisor adds a vlan to the IP packet of the second virtual machine and forwards it to the second switch , the second switch performs forwarding processing according to the first flow table sent by the controller, vlanpops the message according to vlan and inport, and converts it into metadata (VNET); determines whether host learning is required according to metadata (VNET) and src MAC ;According to the metadata (VNET) and dst MAC to determine the layer-2 forwarding, the first switch at the destination end forwards the request message to the first virtual machine after receiving the request message, and the response message of the first virtual machine is also according to the first flow on the first switch The table is sent to the second switch, and the second switch forwards it to the second virtual machine, thereby realizing Layer 2 intercommunication between the first virtual machine and the second virtual machine. If the first virtual machine and the second virtual machine are on different network segments, the Hypervisor adds vlan1 to the IP packet of the second virtual machine and forwards it to the second switch. The second switch performs forwarding processing according to the flow table sent by the controller. According to the vlan, Inport, the message vlan pop, and converted to metadata (VNET); according to metadata (VNET) and src MAC, determine whether host learning is required; according to metadata (VNET) and dst MAC, determine the second layer forwarding; according to metadata ( VRF) and dst IP, for three-layer forwarding; the first switch at the destination end forwards the request message to the first virtual machine after receiving the request message, and the response message of the first virtual machine is also sent to the first virtual machine according to the first flow table on the first switch. two switches, and the second switch forwards the data to the second virtual machine, thereby realizing Layer 3 intercommunication between the first virtual machine and the second virtual machine.

Furthermore, the first virtual machine may be a KVM virtual machine, the second virtual machine may be a VMware virtual machine, and the controller may be an SDN controller. Correspondingly, the first switch is a DVS, and the second switch is a ToR switch , the above-mentioned first virtual machine and second virtual machine refer to two types of virtual machines of different types, rather than just one virtual machine; in addition, it should be understood that any module that can realize the content described in the above steps is included in this embodiment Within the scope of protection, it can be selected and replaced as required.

In this embodiment, by sending the first message to the first switch or the second switch, the first message includes network protocol data packets and virtual local area network information; it is determined to perform forwarding processing according to the first message; The forwarding process between the virtual machine and the first switch, the first flow table contains the mapping information between the first virtual machine and the virtual network; the forwarding process between the second virtual machine and the second switch is performed through the second flow table, and the second flow table contains Mapping information between the second virtual machine and the virtual network. The intercommunication between different types of virtual machines is realized, the network scale in the virtual data center is expanded, and the network scale and range that the virtual data center system can manage are larger.

Embodiment five:

This embodiment provides a system for realizing unified management and intercommunication of virtual machines, please refer to FIG. 7 , including: a controller 1, a first switch 2 and a second switch 3, and the controller 1 is used to construct the first flow table and the second flow table, and send the first flow table to the first switch 2, and send the second flow table to the second switch 3; the first flow table includes the mapping information between the first virtual machine and the virtual network, and the second flow table includes the first flow table Mapping information between the second virtual machine and the virtual network; the first switch 2 is used to receive the first flow table sent by the controller, and perform forwarding processing between the first virtual machine and the second switch through the first flow table; the second The switch 3 is used to receive the second flow table sent by the controller, and perform forwarding processing with the second virtual machine and the first switch through the second flow table; the first switch and the second switch are also used to receive the first A message, the first message includes a network protocol data packet and virtual local area network information.

Further, the first virtual machine may be a KVM virtual machine, the second virtual machine may be a VMware virtual machine, and the controller may be an SDN controller. Correspondingly, the first switch is a DVS, and the second switch is a ToR switch. The virtual platforms corresponding to the KVM virtual machine and the VMware virtual machine are the Openstack virtual platform and the VMware ESXI virtual platform.

Specifically, please refer to FIG. 8, the system for realizing the unified management and intercommunication of KVM virtual machine and VMware virtual machine includes Openstack virtual platform 21, VMware ESXI virtual platform 22, SDN controller 23, ToR switch 24 and DVS25, specifically, Openstack virtual Platform 21 and VMware ESXI virtual platform 22 are respectively used for creating KVM virtual machine and creating VMware virtual machine on the management interface; SDN controller 23 is used for constructing the first flow table and the second flow table, and the first flow table is sent to DVS25, The second flow table is sent to the ToR switch 24; the first flow table includes the mapping information between the physical address of the KVM virtual machine and the VNET, and the second flow table includes the mapping information between the port of the VMware virtual machine and the VNET; DVS25 is used to receive the SDN The first flow table sent by the controller performs forwarding processing with the KVM virtual machine and the ToR switch through the first flow table; the ToR switch is used to receive the second flow table sent by the SDN controller 23, through the second flow table The flow table performs forwarding processing with the VMware virtual machine and the DVS25; it is also used to receive messages sent by the Hypervisor.

Please refer to FIG. 9. FIG. 9 is another schematic diagram of a system for realizing the unified management and intercommunication of VMware virtual machines and KVM virtual machines provided by this embodiment. In addition to each module shown in FIG. 8, it also includes Vcenter/VDP26, VM1 and VM2, specifically, DVS25 may be ZXDVS, VM1 is a VMware virtual machine, and VM2 is a KVM virtual machine.

Referring to FIG. 10, the method for realizing the unified management and intercommunication of VMware and KVM virtual machines provided in this embodiment will be described in detail below, specifically including:

Step 301, configure the Openstack virtual platform and the VMware virtual platform on the management interface of the VDC, create a KVM virtual machine on the management interface, and obtain the first flow table;

Specifically, the DVS sends the virtual machine message to the SDN controller through the Packet-in Message to learn the virtual machine MAC. After the learning is completed, the SDN controller sends the entry containing VNET+SRC MAC to the DVS where the KVM virtual machine is located. That is, the first flow table, that is, the controller associates the virtual machine vid (virtual networkid virtual network identifier) with the VLAN sub-interface, and the traffic sent by the subsequent virtual machine can be normally forwarded according to the first flow table;

Step 302, the management interface of the VDC invokes the northbound interface of the SDN controller through OpenStack to create a VMware virtual machine;

Specifically, pass {"port_uuid (port identification)", "virtualnetwork_id (virtual network identification)", "name (name)", "ip_address (address)", "mac (physical address)", "security_groups (security group) "} and other information to the SDN controller, and the SDN controller saves the information of the virtual machine to the local database;

Step 303, the existing agent virtual machine in ESXI sends a VDP association message, including {port_uuid, vid};

Step 304, after the VMware virtual machine and port_uuid are created, the agent registers with the TOR and the SDN controller through the VDP message;

Specifically, the registration information includes port_uuid and vlan, and the mapping between VM and vlan and port_uuid is performed; when the virtual machine is deleted, the agent removes the association between TOR and the SDN controller, and notifies the controller that the virtual machine has been deleted;

Step 305, setting port-vnet mapping to obtain the second flow table;

Specifically, the ToR switch sends the VDP message to the SDN controller according to the VDP flow table (Ethertype: 0x8940) issued in advance by the SDN controller, and the controller determines the access location according to the port and dpid of the packet-in sent; According to the port_uuid, confirm the virtual machine information associated with the VDP message; configure the vlan sub-interface to the port according to the in_port of vlan and OpenFlow, and add the vlan sub-interface to the virtual network, that is, set the port-vnet mapping, and send it to the ToR switch after processing A second flow table, the second flow table may be a VDP protocol flow table;

Step 306, carry out forwarding processing between the KVM virtual machine and the DVS through the first flow table, and carry out forwarding processing between the VMware virtual machine and the ToR through the second flow table;

Specifically, if the VMware virtual machine and the KVM virtual machine are on the same network segment, the Hypervisor adds a vlan to the IP packet of the VMware virtual machine and forwards it to the ToR switch. ToR performs forwarding processing according to the flow table sent by the SDN controller. According to vlan, inport , pop the message vlan and convert it to metadata (VNET); determine whether host learning is required according to metadata (VNET) and src MAC; determine whether to perform Layer 2 forwarding according to metadata (VNET) and dst MAC, and the destination DVS receives After the request message is forwarded to the KVM virtual machine, the response message of the KVM virtual machine is also sent to the ToR switch according to the flow table on the DVS, and the ToR switch forwards it to the VMware virtual machine, thereby realizing the communication between the VMware virtual machine and the KVM virtual machine. Layer 2 interworking;

If the VMware virtual machine and the KVM virtual machine are on different network segments, the Hypervisor adds vlan1 to the IP packet of the VMware virtual machine and forwards it to the ToR switch. The ToR forwards the packet according to the flow table sent by the SDN controller. Vlan pop and convert to metadata (VNET); determine whether host learning is required according to metadata (VNET) and src MAC; determine layer 2 forwarding according to metadata (VNET) and dst MAC; according to metadata (VRF) and dst IP , carry out two-layer forwarding; the destination DVS forwards the request message to the KVM virtual machine after receiving the request message, and the response message of the KVM virtual machine is also sent to the TOR switch according to the flow table on the DVS, and the ToR switch forwards it to the VMware virtual machine, thereby Realize the three-layer communication between the VMware virtual machine and the KVM virtual machine.

The system provided in this embodiment to realize the unified management and intercommunication of VMware and KVM virtual machines is based on the principle of "do not require VMware to open a special interface, and does not need to be deeply bound and authenticated with VMware", and the VTEP point is moved up to the ToR switch. The above system realizes the unified management and intercommunication of VMware virtual machine and KVM virtual machine, enhances the service capability of the system, reduces operating costs, expands the network scale of the virtual data center based on SDN, and enables the virtual data center system to manage The size and scope of the network is larger.

It should be noted that the VTEP is moved up from the vSwitch to the ToR switch. Under the same port of the ToR switch, each VM has a VLAN. VLAN does not distinguish between networks, but only distinguishes hosts (two hosts on the same network have different VLANs). Under different ToR ports, VLANs can be reused, which can not only simplify the Layer 2 and Layer 3 intercommunication processes between VMware virtual machines and KVM virtual machines, but also manage VMware virtual machines and set advanced functions for them, such as: security Group, Meter, flow mirroring, redirection strategy, etc., and at the same time, it can expand the network scale in the virtual data center based on SDN, so that the network scale and scope that the virtual data center system can manage is larger, and it can be connected to the openstack virtual platform and Docking with the VMware virtual platform, it can also manage the two at the same time and integrate and communicate with each other.

Obviously, those skilled in the art should understand that each module or each step of the present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed on a network formed by multiple computing devices , alternatively, they can be implemented with program codes executable by a computing device, thus, they can be stored in a storage medium (ROM/RAM, magnetic disk, optical disk) to be executed by a computing device, and in some cases , the steps shown or described may be performed in a different order than here, or they may be fabricated into individual integrated circuit modules, or multiple modules or steps among them may be fabricated into a single integrated circuit module for implementation. Therefore, the present invention is not limited to any specific combination of hardware and software.

The above content is a further detailed description of the present invention in conjunction with specific embodiments, and it cannot be assumed that the specific implementation of the present invention is limited to these descriptions. For those of ordinary skill in the technical field of the present invention, without departing from the concept of the present invention, some simple deduction or replacement can be made, which should be regarded as belonging to the protection scope of the present invention.

Claims (11)

1. A method for realizing unified management of virtual machines, characterized in that, comprising: constructing a first flow table, and sending the first flow table to a first switch for forwarding information sent and received by the first virtual machine, where the first flow table includes mapping information between the first virtual machine and a virtual network; Constructing a second flow table, and sending the second flow table to a second switch for forwarding information sent and received by the second virtual machine, the second flow table includes information between the second virtual machine and the virtual network Mapping information. 2. The method for realizing unified management of virtual machines as claimed in claim 1, wherein said building the first flow table comprises: sending the message containing the identification information of the first virtual machine to the controller for learning; After the learning is completed, the information including the mapping relationship between the physical address of the first virtual machine and the virtual network is encapsulated into the first flow table. 3. The method for realizing unified management of virtual machines as claimed in claim 1 or 2, wherein said building a second flow table comprises: receiving an association message forwarded by the second switch, and setting a mapping between a port of the second virtual machine and the virtual network according to the association message; Encapsulating information including the mapping relationship between the port and the virtual network into the second flow table. 4. The method for realizing unified management of virtual machines as claimed in claim 3, wherein, before the construction of the second flow table, further comprising: Registering the second virtual machine with the second switch and the controller, and performing mapping between the second virtual machine and virtual local area networks and port identifiers. 5. A method for realizing virtual machine intercommunication, comprising: Send a first message to the first switch or the second switch, the first message includes network protocol data packets and virtual local area network information; determining to perform forwarding processing according to the first message; performing forwarding processing between the first virtual machine and the first switch through a first flow table, where the first flow table includes mapping information between the first virtual machine and a virtual network; The forwarding process between the second virtual machine and the second switch is performed through a second flow table, where the second flow table includes mapping information between the second virtual machine and the virtual network. 6. The method for realizing virtual machine intercommunication according to claim 5, wherein realizing the intercommunication between the first virtual machine and the second virtual machine comprises: When the first virtual machine and the second virtual machine are in the same network segment, realize Layer 2 intercommunication between the first virtual machine and the second virtual machine; When the first virtual machine and the second virtual machine are in different network segments, layer-2 and layer-3 intercommunication between the first virtual machine and the second virtual machine is implemented. 7. A device for unified management of virtual machines, comprising: a first processing unit and a second processing unit, The first processing unit is configured to construct a first flow table, and send the first flow table to a first switch for forwarding information sent and received by the first virtual machine, the first flow table includes the first virtual machine and the virtual Mapping information between networks; The second processing unit is configured to construct a second flow table, and send the second flow table to a second switch for forwarding information sent and received by the second virtual machine, the second flow table includes the second virtual machine The mapping information between the machine and the virtual network. 8. The device for implementing unified management of virtual machines according to claim 7, wherein the first processing unit comprises a first processing subunit and a second processing subunit, The first processing subunit is configured to send a message containing the identification information of the first virtual machine to the controller for learning; The second processing subunit is configured to encapsulate information including a mapping relationship between the physical address of the first virtual machine and the virtual network into the first flow table after learning. 9. The device for implementing unified management of virtual machines according to claim 7 or 8, wherein the second processing unit comprises a third processing subunit and a fourth processing subunit, The third processing subunit is configured to receive the association message forwarded by the second switch, and set the mapping between the port of the second virtual machine and the virtual network according to the association message; The fourth processing subunit is configured to encapsulate information including a mapping relationship between the port and the virtual network into the second flow table. 10. An apparatus for implementing virtual machine intercommunication, comprising a third processing unit, a fourth processing unit, a fifth processing unit, and a sixth processing unit, The third processing unit is configured to send a first message to the first switch or the second switch, and the first message includes network protocol data packets and virtual local area network information; The fourth processing unit is configured to determine to perform forwarding processing according to the first message; The fifth processing unit is configured to perform forwarding processing between the first virtual machine and the first switch through a first flow table, where the first flow table includes mapping information between the first virtual machine and a virtual network; The sixth processing unit is configured to perform forwarding processing between the second virtual machine and the second switch through a second flow table, and the second flow table includes a mapping between the second virtual machine and the virtual network information. 11. A system for realizing unified management and intercommunication of virtual machines, comprising: a controller, a first switch and a second switch, The controller is configured to construct a first flow table and a second flow table, and send the first flow table to the first switch, and send the second flow table to the second switch; the first flow table includes the first virtual Mapping information between the machine and the virtual network, the second flow table includes mapping information between the second virtual machine and the virtual network; The first switch is configured to receive the first flow table sent by the controller, and perform forwarding processing between the first virtual machine and the second switch through the first flow table; The second switch is configured to receive the second flow table sent by the controller, and perform forwarding processing between the second virtual machine and the first switch through the second flow table; The first switch and the second switch are further configured to receive a first message, and the first message includes a network protocol data packet and virtual local area network information.