WO2018028594A1 - 一种混合云平台的组网方法及混合云平台系统 - Google Patents

一种混合云平台的组网方法及混合云平台系统 Download PDF

Info

Publication number
WO2018028594A1
WO2018028594A1 PCT/CN2017/096608 CN2017096608W WO2018028594A1 WO 2018028594 A1 WO2018028594 A1 WO 2018028594A1 CN 2017096608 W CN2017096608 W CN 2017096608W WO 2018028594 A1 WO2018028594 A1 WO 2018028594A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
virtual machine
switch
network
virtual
Prior art date
Application number
PCT/CN2017/096608
Other languages
English (en)
French (fr)
Inventor
翁建钢
张雷
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018028594A1 publication Critical patent/WO2018028594A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2863—Arrangements for combining access network resources elements, e.g. channel bonding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Definitions

  • This paper refers to, but is not limited to, network virtualization technology under the cloud platform, especially relates to a networking method of a hybrid cloud platform and a hybrid cloud platform system.
  • OpenStack is a commonly used open source cloud computing platform management software, which provides an infrastructure as a service (IaaS, Infrastructure as a Service) solution for public and private cloud deployment and management, and gradually becomes a cloud computing platform. The mainstream choice.
  • IaaS infrastructure as a service
  • IaaS Infrastructure as a Service
  • SDN Software Defined Network
  • OpenFlow OpenFlow Protocol
  • the embodiment of the present invention is to provide a hybrid cloud platform networking method and a hybrid cloud platform system, which can implement a virtual switch of a VMware system to access an SDN network, so that the VMware virtual switch can support the OpenFlow protocol.
  • an embodiment of the present invention provides a networking method of a hybrid cloud platform, where the method is applied to a group consisting of an OpenStack computing platform, a VMware vCenter, at least one ESXi host, a switch supporting an OpenFlow protocol, and an SDN controller.
  • the method includes:
  • the ESXi host When the virtual machine is deployed, the ESXi host discovers the network port of the newly deployed virtual machine, and encapsulates the port information of the newly deployed virtual machine into a first virtual station interface VSI discovery protocol VDP message and reports the WLAN controller to the SDN controller.
  • the first VDP packet is used to associate a port of the newly deployed virtual machine with a port of the switch supporting the OpenFlow protocol;
  • the ESXi host When the virtual machine is revoked, the ESXi host discovers that the network port of the virtual machine is revoked, and the port information of the revoked virtual machine is encapsulated into a second VDP message and reported to the SDN controller; The second VDP message is used to release the port of the disconnected virtual machine that is associated with the port of the switch that supports the OpenFlow protocol.
  • the networking structure includes: two virtual switches are deployed on each ESXi host; wherein the first virtual switch is configured to connect to the control plane network, and the second virtual switch is configured to connect to the OpenFlow protocol. switch;
  • a port scanning module is also deployed on each ESXi host, and the port scanning module is configured to discover a network port created or deleted on the second virtual switch, and then construct a corresponding VSI discovery protocol (VDP, VSI Discovery). Protocol) the message to the SDN controller to notify the newly added network port;
  • VDP VSI Discovery Protocol
  • each port network of the VMware virtual machine created by the OpenStack computing platform is separately deployed.
  • the deploying the virtual machine includes: loading, by the Openstack computing platform, a preset driver, where the virtual machine is deployed on the ESXi host by using the VMware vCenter.
  • the Openstack computing platform loads a preset driver, and deploys the virtual machine on the ESXi host by using the VMware vCenter, including:
  • the port information includes: an ESXi host identifier of the port, and a VLAN of the port The tag, the UUID of the port, and the port scan module ID.
  • the method further includes:
  • the service packet to be sent is encapsulated by the VLAN tag corresponding to the virtual machine port, and the encapsulated packet is sent to the switch supporting the OpenFlow protocol.
  • the switch supporting the OpenFlow protocol After receiving the encapsulated packet, the switch supporting the OpenFlow protocol encapsulates the VLAN tag corresponding to the virtual machine port in the packet, encapsulates it with the VLAN tag of the destination port, and forwards the packet from the physical port associated with the destination port. .
  • the revoking the virtual machine includes: loading, by the Openstack computing platform, a preset driver, and canceling the deployed virtual machine on the ESXi host by using the VMware vCenter.
  • the Openstack computing platform loads a preset driver, and the deployed virtual machine is revoked on the ESXi host by using the VMware vCenter, including:
  • an embodiment of the present invention provides a hybrid cloud platform system, where the cloud platform system includes: an OpenStack computing platform, a VMware vCenter, at least one ESXi host, a switch supporting an OpenFlow protocol, and an SDN controller;
  • the ESXi hosts are respectively connected to the VMware vCenter and the switch supporting the OpenFlow protocol;
  • the OpenStack computing platform is configured to deploy the virtual machine; and revoke the virtual machine;
  • the ESXi host is configured to: when the virtual machine is deployed, discover a network port of the newly deployed virtual machine, and package the port information of the newly deployed virtual machine into a first VDP message and report the message to the SDN controller;
  • the first VDP packet is used to associate a port of the newly deployed virtual machine with a port of the switch supporting the OpenFlow protocol; when the virtual machine is revoked, the network port of the virtual machine is revoked.
  • the port information of the revoked virtual machine is encapsulated into a second VDP message and reported to the SDN controller; wherein the second VDP message is used to release the port of the revoked virtual machine that is associated with The end of the switch supporting the OpenFlow protocol mouth.
  • two virtual switches are deployed on each of the ESXi hosts; wherein the first virtual switch is configured to connect to the control plane network, and the second virtual switch is configured to connect to the switch that supports the OpenFlow protocol;
  • a port scanning module is also deployed on each ESXi host, and the port scanning module is configured to discover a network port created or deleted on the second virtual switch, and then construct a corresponding VSI discovery protocol (VDP, VSI Discovery). Protocol) the message to the SDN controller to notify the newly added network port;
  • VDP VSI Discovery Protocol
  • each port network of the VMware virtual machine created by the OpenStack computing platform is separately deployed.
  • the Openstack computing platform is configured to load a preset driver, and the virtual machine is deployed on the ESXi host by using the VMware vCenter.
  • the Openstack computing platform is configured to create an exclusive port network for each port of the virtual machine on the ESXi host where the virtual machine is located;
  • the port information includes: an ESXi host identifier of the port, a VLAN label of the port, and a UUID of the port And the port scan module ID.
  • the ESXi host is further configured to: when the virtual machine sends a service packet, encapsulate the service packet to be sent by using a VLAN tag corresponding to the virtual machine port, and send the encapsulated packet To the switch supporting the OpenFlow protocol;
  • the switch that supports the OpenFlow protocol is further configured to receive the encapsulated packet, and after parsing and removing the VLAN tag corresponding to the virtual machine port in the packet, the packet is encapsulated by the VLAN tag of the destination port, and is associated with the destination port. Physical port forwarding.
  • the Openstack computing platform is configured to load a preset driver, and the deployed virtual machine is revoked on the ESXi host by using the VMware vCenter.
  • the Openstack computing platform is configured to delete the virtual machine to be revoked
  • the port network corresponding to the port to be deleted in the port information table of the ESXi host; and the port information corresponding to the port to be deleted in the port information table of the ESXi host.
  • the embodiment of the invention provides a hybrid cloud platform networking method and a hybrid cloud platform system; each ESXi host is connected with a physical switch supporting the OpenFlow protocol, and the SDN controller manages each ESXi by issuing an instruction to the physical switch. Network traffic of virtual machines in the host. Therefore, a hybrid network platform based on OpenStack+VMware vSphere cluster + SDN controller is proposed, which realizes the virtual switch of VMware system to access the SDN network, enabling the VMware virtual switch to support the OpenFlow protocol.
  • FIG. 1 is a schematic diagram of a networking structure of an integrated VMware product of the OpenStack cloud platform
  • FIG. 2 is a schematic flowchart of a networking method of a hybrid cloud platform system according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of networking of an OpenStack+VMware vSphere cluster+SDN controller according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a virtual machine deployed according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a port for associating a newly deployed virtual machine according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of a service packet forwarding according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart of deleting a virtual machine according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic flowchart of de-association of a port of a deleted virtual machine according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of a hybrid cloud platform system according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another hybrid cloud platform system according to an embodiment of the present invention.
  • VMware vSphere is a virtualized cloud management platform product from VMware that is now widely used in public and private clouds in a variety of industries.
  • the advantage is that the product technology is mature and stable, but the disadvantage is that the technology is completely closed and the user is easily tied.
  • VMware products have added a set of compute virtualization drivers to the OpenStack platform to integrate VMware products into the OpenStack product framework.
  • VMware's virtualization driver only stops at the simplest flat network networking scenario. It cannot support the virtual local area network (VLAN) networking scenario, and cannot support more complex OpenStack+. SDN hybrid cloud networking.
  • FIG. 1 the open network community OpenStack cloud platform integrated VMware product solution network structure shown in Figure 1.
  • Virtual machines created by OpenStack are deployed by VMware vCenter to specific ESXi hosts.
  • the virtual machines on each ESXi host are deployed in a port network of the VMware virtual machine switch.
  • VMware vCenter and VMware ESXi hosts are components of VMware vSphere.
  • the ESXi host is a virtualization management software that allows multiple virtual machines to share the hardware resources of the physical host.
  • VMware vCenter provides centralized management and performance monitoring for all virtual machines and ESXi hosts.
  • the networking structure shown in Figure 1 cannot separate different VLANs for different tenant networks.
  • the VMware virtual switch does not support the OpenFlow protocol.
  • the VMware virtual switch cannot be directly managed through the SDN controller.
  • each host is connected to a virtual switch that supports the OpenFlow protocol, and the SDN controller sends a forwarding rule to the switch through the OpenFlow protocol to control packet flow and network traffic of each host.
  • the SDN controller can provide network services for the KVM VM by controlling the forwarding rules of the OpenVSwitch; however, the virtual switch of the VMware system cannot access the SDN.
  • the internet The internet.
  • each ESXi host is connected to a physical switch supporting the OpenFlow protocol, and the SDN controller manages the network traffic of the virtual machine in each ESXi host by issuing an instruction to the physical switch. That is to say, a networking method based on OpenStack+VMware vSphere cluster + SDN controller is proposed as a solution.
  • FIG. 2 a networking method of a hybrid cloud platform system according to an embodiment of the present invention is shown, which can be applied to an OpenStack computing platform, a VMware vCenter, at least one ESXi host, a switch supporting an OpenFlow protocol, and an SDN controller.
  • the network structure is formed; wherein each ESXi host is connected to a VMware vCenter and a switch supporting the OpenFlow protocol respectively; the method includes:
  • the ESXi host When the virtual machine is deployed, the ESXi host discovers the network port of the newly deployed virtual machine, and encapsulates the port information of the newly deployed virtual machine into the first VDP packet and reports it to the SDN controller.
  • the first VDP packet is used to associate a port of the newly deployed virtual machine with a port of the switch that supports the OpenFlow protocol.
  • the second VDP packet is used to release the port of the associated revoked virtual machine port and the switch supporting the OpenFlow protocol.
  • the ESXi host exports the outgoing traffic of each virtual machine to a switch that supports the OpenFlow protocol.
  • the virtual machine is an OpenStack computing platform that is allocated to the ESXi host through the VMware vCenter.
  • FIG. 2 The technical solution shown in FIG. 2 is applied to the networking structure shown in FIG. 3.
  • two virtual switches are deployed on each ESXi host; wherein, the first virtual switch is configured to be connected to the control plane network, and the second The virtual switch is set up to connect to a switch that supports the OpenFlow protocol.
  • a port scanning module is also deployed on each ESXi host, and the port scanning module is set to send The network port that is created or deleted on the second virtual switch, and then the corresponding VSI (VSI Discovery Protocol) packet of the virtual station interface (VSI) is configured to notify the SDN controller of the newly added network port. information.
  • VSI VSI Discovery Protocol
  • the network ports of each VMware virtual machine created by the OpenStack computing platform are deployed in a single port network.
  • the VLAN tags of each port network are not duplicated.
  • the VLAN tags can be in the range of 1 and 4095. between. Due to the limitations of virtual switch and ESXi host configuration, the network ports deployed on the second virtual switch can't exceed 1024. Therefore, the virtual machine network ports on each EXSi host can occupy a separate VLAN tag.
  • the deploying a virtual machine includes: an Openstack computing platform loading a preset driver to deploy a virtual machine on an ESXi host through VMware vCenter.
  • the OpenStack computing platform can load the pre-configured or modified vmwareapi virtual machine manager driver and communicate with VMware vCenter to deploy the virtual machine on the ESXi host through VMware vCenter.
  • VMware vCenter allocates which ESXi host the OpenStack deployed VMs are. Referring to FIG. 4, the deployment manner includes:
  • S401 Create an exclusive port network for each port of the virtual machine on the ESXi host where the virtual machine is located.
  • S402 Select a corresponding VLAN tag for the port network from the unused VLAN tags on the ESXi host.
  • S403 Generate port information, and write port information to a port information table in the ESXi host.
  • the port information includes: the ESXi host ID of the port, the VLAN tag of the port, the Universally Unique IDentifier (UUID) of the port, and the port scan module ID.
  • UUID Universally Unique IDentifier
  • the ESXi host discovers the network port of the newly deployed virtual machine, and encapsulates the port information of the newly deployed virtual machine into the first VDP packet and reports it to the SDN controller.
  • the port scanning module in the ESXi host discovers the newly deployed port by periodically scanning the port information table.
  • the port scanning module generates a first VDP packet for the port information corresponding to the newly deployed port.
  • the port scanning module sends the first VDP packet to the switch that supports the OpenFlow protocol by using a port that is connected to the switch that supports the OpenFlow protocol.
  • S504 The switch that supports the OpenFlow protocol sends the first VDP packet sent by the port scanning module to the SDN controller.
  • the SDN controller parses the first VDP packet and performs related configuration, the service packet of the virtual machine can be forwarded normally.
  • the method may further include:
  • S602 The switch that supports the OpenFlow protocol receives the encapsulated packet, and removes the VLAN tag corresponding to the virtual machine port in the packet, and then encapsulates it with the VLAN tag of the destination port and forwards the packet from the physical port associated with the destination port.
  • the above example process completes the packet forwarding process of the hybrid cloud platform based on OpenStack+VMware vSphere cluster + SDN controller, and realizes the virtual switch of the VMware system to access the SDN network, so that the VMware virtual switch can support the OpenFlow protocol.
  • the undoing the virtual machine includes: the Openstack computing platform loading the preset driver, and undoing the deployed virtual machine on the ESXi host through the VMware vCenter.
  • the OpenStack computing platform can load the pre-configured or modified vmwareapi virtual machine manager driver and communicate with VMware vCenter to remove the deployed virtual machine from the ESXi host via VMware vCenter.
  • the deletion manner includes:
  • the ESXi host discovers that the network port of the virtual machine is revoked, and encapsulates the port information of the revoked virtual machine into a second VDP message and reports it to the SDN controller.
  • the port scanning module in the ESXi host discovers the deleted port by periodically scanning the port information table.
  • the port scanning module constructs a second VDP packet for the port information corresponding to each deleted port.
  • the port scanning module sends a second VDP packet to the switch that supports the OpenFlow protocol by using a port that is connected to the switch that supports the OpenFlow protocol.
  • S804 The switch supporting the OpenFlow protocol sends the second VDP packet sent by the port scanning module to the SDN controller.
  • the SDN controller can delete the association information between the virtual machine port and the switch port after parsing the second VDP packet and performing related configuration.
  • the interval of the timing scan of the port scanning module may be set to 3 seconds.
  • This embodiment provides a networking method for a hybrid cloud platform system.
  • Each ESXi host is connected to a physical switch supporting the OpenFlow protocol, and the SDN controller manages the virtual machine in each ESXi host by issuing an instruction to the physical switch. Network traffic. Therefore, a hybrid network platform based on OpenStack+VMware vSphere cluster + SDN controller is proposed, which realizes the virtual switch of VMware system to access the SDN network, enabling the VMware virtual switch to support the OpenFlow protocol.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented by the processor to implement the method described in the embodiments.
  • the cloud platform system 90 includes: an OpenStack computing platform 901, a VMware vCenter 902, at least one ESXi host 903, and an OpenFlow protocol-enabled switch 904. And an SDN controller 905; wherein each ESXi host 903 is respectively connected to the VMware vCenter 902 and the switch 904 supporting the OpenFlow protocol;
  • the ESXi host 903 is configured to direct outgoing traffic of each virtual machine to the support a switch 904 of the OpenFlow protocol; wherein the virtual machine is allocated by the VMware vCenter 902 to the ESXi host 903 by the OpenStack computing platform;
  • the OpenStack computing platform 901 is configured to deploy the virtual machine
  • the ESXi host 903 is further configured to: when the virtual machine is deployed, discover a network port of the newly deployed virtual machine, and encapsulate the port information of the newly deployed virtual machine into a first VDP message and report the WLAN control to the SDN control.
  • the first VDP message is used to associate a port of the newly deployed virtual machine with a port of the switch 904 supporting the OpenFlow protocol;
  • the OpenStack computing platform 901 is further configured to revoke the virtual machine
  • the ESXi host 903 is further configured to: when the virtual machine is revoked, discover the network port of the virtual machine, and encapsulate the port information of the revoked virtual machine into a second VDP message and report the SDN control to the SDN control.
  • the second VDP message is used to release the port of the associated revoked virtual machine and the switch of the OpenFlow protocol-enabled switch 904.
  • the first virtual switch 9031 is configured to connect to the control plane network, and the second virtual switch 9032 is configured to connect to the supported OpenFlow. Protocol switch 904;
  • a port scanning module 9033 is also disposed on each ESXi host 903.
  • the port scanning module 9033 is configured to discover a network port created or deleted on the second virtual switch 9032, and then construct a corresponding VSI discovery protocol ( VDP (VSI Discovery Protocol) packet, notifying the SDN controller 905 of the information of the newly added network port;
  • VDP VSI Discovery Protocol
  • each port network of the VMware virtual machine created by the OpenStack computing platform 901 is deployed separately.
  • the Openstack computing platform 901 is configured to load a preset driver, and deploy the virtual machine on the ESXi host 903 through the VMware vCenter 902.
  • the Openstack computing platform 901 is configured to create an exclusive port network for each port of the virtual machine on the ESXi host 903 where the virtual machine is located; and, from the ESXi host 903 Selecting a corresponding VLAN tag for the port network in an unused VLAN tag; and generating port information, and writing the port information to the ESXi The port information table in the host 903; wherein the port information includes: an ESXi host 903 identifier of the port, a VLAN tag of the port, a UUID of the port, and the port scanning module 9033ID.
  • the port scanning module 9033 in the ESXi host 903 is configured to discover the newly deployed port by periodically scanning the port information table; and generating a port information corresponding to the newly deployed port. Transmitting the first VDP message; and transmitting, by the port connected to the switch 904 supporting the OpenFlow protocol, the first VDP message to the switch 904 supporting the OpenFlow protocol;
  • the switch 904 supporting the OpenFlow protocol is configured to send the first VDP message sent by the port scanning module 9033 to the SDN controller 905.
  • the ESXi host 903 is further configured to: when the virtual machine sends a service packet, encapsulate the service packet to be sent by using the VLAN tag of the virtual machine port, and encapsulate the packet after the package is completed.
  • the text is sent to the switch 904 supporting the OpenFlow protocol;
  • the switch 904 supporting the OpenFlow protocol is further configured to receive the encapsulated packet, and after parsing the VLAN tag corresponding to the virtual machine port in the packet, the VLAN tag of the destination port is encapsulated, and the destination port is encapsulated. Associated physical port forwarding.
  • the Openstack computing platform 901 is configured to load a preset driver, and the deployed virtual machine is revoked on the ESXi host 903 by the VMware vCenter 902.
  • the Openstack computing platform 901 is configured to delete an exclusive port network corresponding to each port of the virtual machine to be revoked; and delete the port to be deleted in the port information table in the ESXi host 903. Port information.
  • the port scanning module 9033 in the ESXi host 903 is configured to discover the deleted port by periodically scanning the port information table
  • the port scanning module 9033 is configured to construct a second VDP message for the port information corresponding to each deleted port;
  • the port scanning module 9033 is configured to send a second VDP message to the switch 904 supporting the OpenFlow protocol by using a port connected to the switch 904 supporting the OpenFlow protocol;
  • the switch 904 supporting the OpenFlow protocol is configured to receive the second VDP message sent by the port scanning module 9033 and then send it to the SDN controller 905.
  • the hybrid cloud platform system 90 shown in FIG. 9 or FIG. 10 can be implemented by using the networking structure shown in FIG. 2 , and details are not described in detail in this embodiment.
  • Computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules, or other data. , removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer.
  • communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media.
  • a modulated data signal such as a carrier wave or other transport mechanism
  • the virtual switch of the VMware system is connected to the SDN network, so that the VMware virtual switch can support the OpenFlow protocol.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种混合云平台的组网方法及混合云平台系统；该方法应用于OpenStack计算平台、VMware vCenter、至少一个ESXi主机、支持OpenFlow协议的交换机以及SDN控制器所组成的组网结构中；其中，每个ESXi主机均分别与所述VMware vCenter和所述支持OpenFlow协议的交换机相连；所述方法包括：当部署所述虚拟机时，所述ESXi主机发现新部署虚拟机的网络端口，并将所述新部署虚拟机的端口信息封装成第一VDP报文上报至所述SDN控制器(S201)；当撤销所述虚拟机时，所述ESXi主机发现被撤销虚拟机的网络端口，并将所述被撤销虚拟机的端口信息封装成第二VDP报文上报至所述SDN控制器(S202)。

Description

一种混合云平台的组网方法及混合云平台系统 技术领域
本文涉及但不限于云平台下的网络虚拟技术，尤其涉及一种混合云平台的组网方法及混合云平台系统。
背景技术
OpenStack是当前常用的一种开源云计算平台管理软件，旨在为公有云和私有云部署与管理提供一种基础设施即服务(IaaS，Infrastructure as a Service)的解决方案，并逐渐成为云计算平台的主流选择。
软件定义网络(SDN，Software Defined Network)，是一种新型的网络架构，其将整个网络的控制平面和数据转发平面分离，由集中的控制点即SDN控制器，通过标准的OpenFlow协议，控制整个网络内所有网络硬件设备对业务流的转发规则，实现对全网络流量的灵活控制。相对于OpenStack自身的网络功能服务，SDN的网络功能更加丰富多样，因此各大运营商目前将OpenStack+SDN作为虚拟化云系统的解决方案。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例期望提供一种混合云平台的组网方法及混合云平台系统，能够实现VMware系统的虚拟交换机接入SDN网络，使得VMware虚拟交换机能够支持OpenFlow协议。
第一方面，本发明实施例提供了一种混合云平台的组网方法，所述方法应用于OpenStack计算平台、VMware vCenter、至少一个ESXi主机、支持OpenFlow协议的交换机以及SDN控制器所组成的组网结构中；其中，每个ESXi主机均分别与所述VMware vCenter和所述支持OpenFlow协议的交换 机相连；所述方法包括：
当部署虚拟机时，所述ESXi主机发现新部署虚拟机的网络端口，并将所述新部署虚拟机的端口信息封装成第一虚拟站接口VSI发现协议VDP报文上报至所述SDN控制器；其中，所述第一VDP报文用于将所述新部署虚拟机的端口与所述支持OpenFlow协议的交换机的端口进行关联；
当撤销虚拟机时，所述ESXi主机发现被撤销虚拟机的网络端口，并将所述被撤销虚拟机的端口信息封装成第二VDP报文上报至所述SDN控制器；其中，所述第二VDP报文用于解除已关联的所述被撤销虚拟机的端口与所述支持OpenFlow协议的交换机的端口。
可选的，所述组网结构，包括：每台ESXi主机上均部署两台虚拟交换机；其中，第一虚拟交换机设置为连接控制面网络，第二虚拟交换机设置为连接所述支持OpenFlow协议的交换机；
每台ESXi主机上还部署了一个端口扫描模块，所述端口扫描模块设置为，发现在所述第二虚拟交换机上创建或者删除的网络端口，然后构造相应的VSI的发现协议(VDP，VSI Discovery Protocol)报文，向SDN控制器通告新增网络端口的信息；
在所述第二虚拟交换机上，每个由OpenStack计算平台创建的VMware虚拟机的网络端口单独部署一个端口网络。
可选的，所述部署虚拟机，包括：所述Openstack计算平台加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上部署所述虚拟机。
可选的，所述Openstack计算平台加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上部署所述虚拟机，包括：
在所述虚拟机所在的ESXi主机上为所述虚拟机的每个端口对应创建独占的端口网络；
从所述ESXi主机上未使用的VLAN标签中为所述端口网络选择对应的VLAN标签；
生成端口信息，并将所述端口信息写入所述ESXi主机中的端口信息表；其中，所述端口信息包括：所述端口的ESXi主机标识，所述端口的VLAN 标签，所述端口的UUID以及所述端口扫描模块ID。
可选的，在部署完成虚拟机后，所述方法还包括：
当所述虚拟机发送业务报文时，通过所述虚拟机端口对应的VLAN标签封装待发送的业务报文，并将封装完成后的报文发送至所述支持OpenFlow协议的交换机；
所述支持OpenFlow协议的交换机接收封装完成后的报文，通过解析去除报文中所述虚拟机端口对应的VLAN标签之后，用目的端口的VLAN标签封装，并从与目的端口关联的物理端口转发。
可选的，所述撤销虚拟机，包括：所述Openstack计算平台加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上撤销已部署的虚拟机。
可选的，所述Openstack计算平台加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上撤销已部署的虚拟机，包括：
删除所述待撤销虚拟机的每个端口所对应独占的端口网络；
删除所述ESXi主机中的端口信息表内待删除端口对应的端口信息。
第二方面，本发明实施例提供了一种混合云平台系统，所述云平台系统包括：OpenStack计算平台、VMware vCenter、至少一个ESXi主机、支持OpenFlow协议的交换机以及SDN控制器；其中，每个ESXi主机均分别与所述VMware vCenter和所述支持OpenFlow协议的交换机相连；
所述OpenStack计算平台，设置为部署所述虚拟机；以及撤销所述虚拟机；
所述ESXi主机，设置为当部署所述虚拟机时，发现新部署虚拟机的网络端口，并将所述新部署虚拟机的端口信息封装成第一VDP报文上报至所述SDN控制器；其中，所述第一VDP报文用于将所述新部署虚拟机的端口与所述支持OpenFlow协议的交换机的端口进行关联；当撤销所述虚拟机时，发现被撤销虚拟机的网络端口，并将所述被撤销虚拟机的端口信息封装成第二VDP报文上报至所述SDN控制器；其中，所述第二VDP报文用于解除已关联的所述被撤销虚拟机的端口与所述支持OpenFlow协议的交换机的端 口。
在上述方案中，所述每台ESXi主机上均部署两台虚拟交换机；其中，第一虚拟交换机设置为连接控制面网络，第二虚拟交换机设置为连接所述支持OpenFlow协议的交换机；
每台ESXi主机上还部署了一个端口扫描模块，所述端口扫描模块设置为，发现在所述第二虚拟交换机上创建或者删除的网络端口，然后构造相应的VSI的发现协议(VDP，VSI Discovery Protocol)报文，向SDN控制器通告新增网络端口的信息；
在所述第二虚拟交换机上，每个由所述OpenStack计算平台创建的VMware虚拟机的网络端口单独部署一个端口网络。
可选的，所述Openstack计算平台，是设置为加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上部署所述虚拟机。
可选的中，所述Openstack计算平台是设置为，在所述虚拟机所在的ESXi主机上为所述虚拟机的每个端口对应创建独占的端口网络；
从所述ESXi主机上未使用的VLAN标签中为所述端口网络选择对应的VLAN标签；
生成端口信息，并将所述端口信息写入所述ESXi主机中的端口信息表；其中，所述端口信息包括：所述端口的ESXi主机标识，所述端口的VLAN标签，所述端口的UUID以及所述端口扫描模块ID。
可选的，所述ESXi主机，还设置为当所述虚拟机发送业务报文时，通过所述虚拟机端口对应的VLAN标签封装待发送的业务报文，并将封装完成后的报文发送至所述支持OpenFlow协议的交换机；
所述支持OpenFlow协议的交换机，还设置为接收封装完成后的报文，通过解析去除报文中所述虚拟机端口对应的VLAN标签之后，用目的端口的VLAN标签封装，并从与目的端口关联的物理端口转发。
可选的，所述Openstack计算平台，是设置为加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上撤销已部署的虚拟机。
可选的，所述Openstack计算平台，是设置为删除所述待撤销虚拟机的 每个端口所对应独占的端口网络；以及，删除所述ESXi主机中的端口信息表内待删除端口对应的端口信息。
本发明实施例提供了一种混合云平台的组网方法及混合云平台系统；把每台ESXi主机和支持OpenFlow协议的物理交换机连接，SDN控制器通过对物理交换机下达指令，来管理每台ESXi主机中虚拟机的网络流量。从而提出一种基于OpenStack+VMware vSphere集群+SDN控制器的混合云平台的组网方式，实现了VMware系统的虚拟交换机接入SDN网络，使得VMware虚拟交换机能够支持OpenFlow协议。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为OpenStack云平台集成VMware产品的组网结构示意图；
图2为本发明实施例提供的一种混合云平台系统的组网方法流程示意图；
图3为本发明实施例提供的一种基于OpenStack+VMware vSphere集群+SDN控制器的组网结构示意图；
图4为本发明实施例提供的一种部署虚拟机的流程示意图；
图5为本发明实施例提供的一种新部署虚拟机的端口进行关联的流程示意图；
图6为本发明实施例提供的一种业务报文转发的流程示意图；
图7为本发明实施例提供的一种删除虚拟机的流程示意图；
图8为本发明实施例提供的一种已删除虚拟机的端口进行解关联的流程示意图；
图9为本发明实施例提供的一种混合云平台系统结构示意图；
图10为本发明实施例提供的另一种混合云平台系统结构示意图。
本发明的实施方式
下面将结合本发明实施例中的附图，对本发明实施例进行清楚、完整地描述。
VMware vSphere是VMware公司的一款虚拟化云管理平台产品，目前也广泛应用于各行各业现存的公有云和私有云当中。其优点是产品技术成熟、稳定，但缺点是技术完全封闭，用户容易被捆绑。
在OpenStack+SDN的解决方案下，现存的云系统大部分都是基于VMware产品，希望能够利用现存的VMware云系统，并与新建的OpenStack组成混合云进行统一管理。
为此，VMware产品在OpenStack的平台内加入了一套计算虚拟化驱动，可将VMware产品集成在OpenStack产品框架之下。但是，VMware的这套虚拟化驱动仅仅止步于实现了最简单的扁平网络组网场景，对虚拟局域网(VLAN，Virtual Local Area Network)的组网场景无法支持，更无法支持更为复杂的OpenStack+SDN混合云组网了。
目前，开源社区OpenStack云平台集成VMware产品的解决方案组网结构如图1所示。通过OpenStack创建的虚拟机，由VMware vCenter选择部署到具体的ESXi主机上，每台ESXi主机上的虚拟机都部署在VMware虚拟机交换机的一个端口网络中。
对于上述组网结构，VMware vCenter和VMware ESXi主机属于VMware vSphere的组件。其中，ESXi主机是虚拟化管理软件，允许多个虚拟机共享物理主机的硬件资源。VMware vCenter为所有的虚拟机和ESXi主机提供集中化管理和性能监控。
图1所示的组网结构，一是无法为不同租户网络提供不同的VLAN进行隔离；二是VMware虚拟交换机不支持OpenFlow协议，不能通过SDN控制器直接管理VMware虚拟交换机。
需要说明的是，在基于SDN的网络架构中，每台主机和支持OpenFlow协议的虚拟交换机连接，SDN控制器通过OpenFlow协议向交换机下达转发规则，控制每台主机的报文流向和网络流量。
因此，如果OpenStack云平台中同时部署KVM主机集群和VMware主 机集群，由于KVM主机内的虚拟机部署在支持OpenFlow协议的OpenVSwitch虚拟交换机上，因此SDN控制器可以通过控制OpenVSwitch的转发规则为KVM虚拟机提供网络服务；但VMware系统的虚拟交换机无法接入SDN网络。
本发明实施例把每台ESXi主机和支持OpenFlow协议的物理交换机连接，SDN控制器通过对物理交换机下达指令，来管理每台ESXi主机中虚拟机的网络流量。也就是通过提出一种基于OpenStack+VMware vSphere集群+SDN控制器的混合云平台的组网方式来作为解决方案。
参见图2，其示出了本发明实施例提供的一种混合云平台系统的组网方法，该可以应用于OpenStack计算平台、VMware vCenter、至少一个ESXi主机、支持OpenFlow协议的交换机以及SDN控制器所组成的组网结构中；其中，每个ESXi主机均分别与VMware vCenter和支持OpenFlow协议的交换机相连；所述方法包括：
S201：当部署虚拟机时，ESXi主机发现新部署虚拟机的网络端口，并将新部署虚拟机的端口信息封装成第一VDP报文上报至SDN控制器；
其中，第一VDP报文用于将新部署虚拟机的端口与支持OpenFlow协议的交换机的端口进行关联；
S202：当撤销虚拟机时，ESXi主机发现被撤销虚拟机的网络端口，并将被撤销虚拟机的端口信息封装成第二VDP报文上报至SDN控制器；
其中，第二VDP报文用于解除已关联的被撤销虚拟机的端口与支持OpenFlow协议的交换机的端口。
需要说明的是，上述ESXi主机将每个虚拟机的出向流量引出至支持OpenFlow协议的交换机；其中，虚拟机是OpenStack计算平台通过VMware vCenter分配至ESXi主机的。
图2所示的技术方案应用于图3所示的组网结构中，在图3中，每台ESXi主机上部署两台虚拟交换机；其中，第一虚拟交换机设置为连接控制面网络，第二虚拟交换机设置为连接支持OpenFlow协议的交换机。
每台ESXi主机上还部署了一个端口扫描模块，端口扫描模块设置为发 现在第二虚拟交换机上创建或者删除的网络端口，然后构造相应的虚拟站接口(VSI，Virtual Station Interface)的发现协议(VDP，VSI Discovery Protocol)报文，向SDN控制器通告新增网络端口的信息。在第二虚拟交换机上，每个由OpenStack计算平台创建的VMware虚拟机的网络端口单独部署在一个端口网络中，每个端口网络的VLAN标签均不重复，VLAN标签的范围可以在1和4095之间。由于虚拟交换机和ESXi主机配置的限制，第二虚拟交换机上部署的网络端口一般不能超过1024个，因此每个EXSi主机上的虚拟机网络端口均可占用一个独立的VLAN标签。
示例性地，所述部署虚拟机，包括：Openstack计算平台加载预设的驱动程序，通过VMware vCenter在ESXi主机上部署虚拟机。
可选地，OpenStack计算平台可以加载预先设置或修改完成的vmwareapi虚拟机管理器驱动程序后与VMware vCenter通信，通过VMware vCenter将虚拟机部署在ESXi主机上。例如，vSphere集群中有3台ESXi主机，由VMware vCenter分配OpenStack部署的虚拟机具体在哪台ESXi主机上。参见图4，所述部署方式包括：
S401：在虚拟机所在的ESXi主机上为虚拟机的每个端口对应创建独占的端口网络；
S402：从该ESXi主机上未使用的VLAN标签中为端口网络选择对应的VLAN标签；
S403：生成端口信息，并将端口信息写入ESXi主机中的端口信息表；
其中，端口信息包括：端口的ESXi主机标识，端口的VLAN标签，端口的全局唯一标识符(Universally Unique IDentifier,UUID)以及端口扫描模块ID。
对应于图4所示的详细部署方式，对应地，参见图5，ESXi主机发现新部署虚拟机的网络端口，并将新部署虚拟机的端口信息封装成第一VDP报文上报至SDN控制器，可以包括：
S501：ESXi主机中的端口扫描模块通过定时扫描端口信息表发现新部署的端口；
S502：端口扫描模块为新部署的端口对应的端口信息生成第一VDP报文；
S503：端口扫描模块通过与支持OpenFlow协议的交换机连接的端口，向所述支持OpenFlow协议的交换机发送第一VDP报文；
S504：所述支持OpenFlow协议的交换机收到端口扫描模块发送的第一VDP报文后，上送给SDN控制器；
可以理解地，SDN控制器可以通过解析第一VDP报文，进行相关配置后，虚拟机的业务报文则可以被正常转发。
需要说明的是，在部署完成虚拟机后，参见图6，本方法还可以包括：
S601：当虚拟机发送业务报文时，通过虚拟机端口对应的VLAN标签封装待发送的业务报文，并将封装完成后的报文发送至支持OpenFlow协议的交换机；
S602：支持OpenFlow协议的交换机接收封装完成后的报文，通过解析去除报文中虚拟机端口对应的VLAN标签之后，用目的端口的VLAN标签封装，并从与目的端口关联的物理端口转发。
上述示例过程就完成了基于OpenStack+VMware vSphere集群+SDN控制器的混合云平台的报文转发过程，实现了VMware系统的虚拟交换机接入SDN网络，使得VMware虚拟交换机能够支持OpenFlow协议。
示例性地，所述撤销虚拟机，包括：Openstack计算平台加载预设的驱动程序，通过VMware vCenter在ESXi主机上撤销已部署的虚拟机。
可选地，OpenStack计算平台可以加载预先设置或修改完成的vmwareapi虚拟机管理器驱动程序后与VMware vCenter通信，通过VMware vCenter将已部署的虚拟机从ESXi主机上删除。参见图7，所述删除方式包括：
S701：删除待撤销虚拟机的每个端口所对应独占的端口网络；
S702：删除ESXi主机中的端口信息表内待删除端口对应的端口信息。
对应于图7所示的删除方式，对应地，参见图8，ESXi主机发现被撤销虚拟机的网络端口，并将被撤销虚拟机的端口信息封装成第二VDP报文上报至SDN控制器，可以包括：
S801：ESXi主机中的端口扫描模块通过定时扫描端口信息表发现已删除的端口；
S802：端口扫描模块为每一条已删除的端口对应的端口信息构造第二VDP报文；
S803：端口扫描模块通过与支持OpenFlow协议的交换机连接的端口，向所述支持OpenFlow协议的交换机发送第二VDP报文；
S804：所述支持OpenFlow协议的交换机收到端口扫描模块发送的第二VDP报文后，上送给SDN控制器；
可以理解地，SDN控制器可以通过解析第二VDP报文，进行相关配置后，删除虚拟机端口与交换机端口的关联信息。
需要说明的是，上述实施例中，端口扫描模块的定时扫描的间隔可以设置为3秒。
本实施例提供了一种混合云平台系统的组网方法，把每台ESXi主机和支持OpenFlow协议的物理交换机连接，SDN控制器通过对物理交换机下达指令，来管理每台ESXi主机中虚拟机的网络流量。从而提出一种基于OpenStack+VMware vSphere集群+SDN控制器的混合云平台的组网方式，实现了VMware系统的虚拟交换机接入SDN网络，使得VMware虚拟交换机能够支持OpenFlow协议。
本发明实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现实施例所述的方法。
参见图9，其示出了本发明实施例提供的一种混合云平台系统90，所述云平台系统90包括：OpenStack计算平台901、VMware vCenter902、至少一个ESXi主机903、支持OpenFlow协议的交换机904以及SDN控制器905；其中，每个ESXi主机903均分别与所述VMware vCenter902和所述支持OpenFlow协议的交换机904相连；
所述ESXi主机903，设置为将每个虚拟机的出向流量引出至所述支持 OpenFlow协议的交换机904；其中，所述虚拟机是所述OpenStack计算平台通过所述VMware vCenter902分配至所述ESXi主机903的；
所述OpenStack计算平台901，设置为部署所述虚拟机；
所述ESXi主机903，还设置为当部署所述虚拟机时，发现新部署虚拟机的网络端口，并将所述新部署虚拟机的端口信息封装成第一VDP报文上报至所述SDN控制器905；其中，所述第一VDP报文用于将所述新部署虚拟机的端口与所述支持OpenFlow协议的交换机904的端口进行关联；
所述OpenStack计算平台901，还设置为撤销所述虚拟机；
所述ESXi主机903，还设置为当撤销所述虚拟机时，发现被撤销虚拟机的网络端口，并将所述被撤销虚拟机的端口信息封装成第二VDP报文上报至所述SDN控制器905；其中，所述第二VDP报文用于解除已关联的所述被撤销虚拟机的端口与所述支持OpenFlow协议的交换机904的端口。
在上述方案中，参见图10，所述每台ESXi主机903上均部署两台虚拟交换机；其中，第一虚拟交换机9031设置为连接控制面网络，第二虚拟交换机9032设置为连接所述支持OpenFlow协议的交换机904；
每台ESXi主机903上还部署了一个端口扫描模块9033，所述端口扫描模块9033设置为，发现在所述第二虚拟交换机9032上创建或者删除的网络端口，然后构造相应的VSI的发现协议(VDP，VSI Discovery Protocol)报文，向SDN控制器905通告新增网络端口的信息；
在所述第二虚拟交换机9032上，每个由所述OpenStack计算平台901创建的VMware虚拟机的网络端口单独部署一个端口网络。
在上述方案中，所述Openstack计算平台901，设置为加载预设的驱动程序，通过所述VMware vCenter902在所述ESXi主机903上部署所述虚拟机。
在上述方案中，所述Openstack计算平台901设置为，在所述虚拟机所在的ESXi主机903上为所述虚拟机的每个端口对应创建独占的端口网络；以及，从所述ESXi主机903上未使用的VLAN标签中为所述端口网络选择对应的VLAN标签；以及，生成端口信息，并将所述端口信息写入所述ESXi 主机903中的端口信息表；其中，所述端口信息包括：所述端口的ESXi主机903标识，所述端口的VLAN标签，所述端口的UUID以及所述端口扫描模块9033ID。
在上述方案中，所述ESXi主机903中的端口扫描模块9033，设置为通过定时扫描所述端口信息表发现所述新部署的端口；以及，为所述新部署的端口对应的端口信息生成所述第一VDP报文；以及，通过与所述支持OpenFlow协议的交换机904连接的端口，向所述支持OpenFlow协议的交换机904发送所述第一VDP报文；
所述支持OpenFlow协议的交换机904，设置为收到所述端口扫描模块9033发送的所述第一VDP报文后，上送给所述SDN控制器905。
在上述方案中，所述ESXi主机903，还设置为当所述虚拟机发送业务报文时，通过所述虚拟机端口对应的VLAN标签封装待发送的业务报文，并将封装完成后的报文发送至所述支持OpenFlow协议的交换机904；
所述支持OpenFlow协议的交换机904，还设置为接收封装完成后的报文，通过解析去除报文中所述虚拟机端口对应的VLAN标签之后，用目的端口的VLAN标签封装，并从与目的端口关联的物理端口转发。
在上述方案中，所述Openstack计算平台901，设置为加载预设的驱动程序，通过所述VMware vCenter902在所述ESXi主机903上撤销已部署的虚拟机。
在上述方案中，所述Openstack计算平台901，设置为删除所述待撤销虚拟机的每个端口所对应独占的端口网络；以及，删除所述ESXi主机903中的端口信息表内待删除端口对应的端口信息。
在上述方案中，所述ESXi主机903中的端口扫描模块9033，设置为通过定时扫描端口信息表发现已删除的端口；
所述端口扫描模块9033设置为为每一条已删除的端口对应的端口信息构造第二VDP报文；
所述端口扫描模块9033设置为通过与支持OpenFlow协议的交换机904连接的端口，向所述支持OpenFlow协议的交换机904发送第二VDP报文；
所述支持OpenFlow协议的交换机904，设置为收到端口扫描模块9033发送的第二VDP报文后，上送给SDN控制器905。
可以理解地，在具体实现过程中，图9或图10所示的混合云平台系统90，可以通过图2所示的组网结构来实现，具体描述本实施例不再赘述。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理单元的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。以上所述，仅为本发明的可选实施例而已，并非用于限定本发明的保护范围。
工业实用性
通过上述实施例实现了VMware系统的虚拟交换机接入SDN网络，使得VMware虚拟交换机能够支持OpenFlow协议。

Claims (15)

  1. 一种混合云平台的组网方法，其特征在于，所述方法应用于OpenStack计算平台、VMware vCenter、至少一个ESXi主机、支持OpenFlow协议的交换机以及软件定义网络SDN控制器所组成的组网结构中；其中，每个ESXi主机均分别与所述VMware vCenter和所述支持OpenFlow协议的交换机相连；所述方法包括：
    当部署虚拟机时，所述ESXi主机发现新部署虚拟机的网络端口，并将所述新部署虚拟机的端口信息封装成第一虚拟站接口VSI发现协议VDP报文上报至所述SDN控制器(S201)；其中，所述第一VDP报文用于将所述新部署虚拟机的端口与所述支持OpenFlow协议的交换机的端口进行关联；
    当撤销虚拟机时，所述ESXi主机发现被撤销虚拟机的网络端口，并将所述被撤销虚拟机的端口信息封装成第二VDP报文上报至所述SDN控制器(S202)；其中，所述第二VDP报文用于解除已关联的所述被撤销虚拟机的端口与所述支持OpenFlow协议的交换机的端口。
  2. 根据权利要求1所述的方法，其中，所述组网结构，包括：每台ESXi主机上均部署两台虚拟交换机；其中，第一虚拟交换机设置为连接控制面网络，第二虚拟交换机设置为连接所述支持OpenFlow协议的交换机；
    每台ESXi主机上还部署了一个端口扫描模块，所述端口扫描模块设置为，发现在所述第二虚拟交换机上创建或者删除的网络端口，然后构造相应的VDP报文，向SDN控制器通告新增网络端口的信息；
    在所述第二虚拟交换机上，每个由OpenStack计算平台创建的VMware虚拟机的网络端口单独部署一个端口网络。
  3. 根据权利要求2所述的方法，其中，所述部署虚拟机，包括：所述Openstack计算平台加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上部署所述虚拟机。
  4. 根据权利要求3所述的方法，其中，所述Openstack计算平台加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上部署所述虚拟机，包括：
    在所述虚拟机所在的ESXi主机上为所述虚拟机的每个端口对应创建独占的端口网络(S401)；
    从所述ESXi主机上未使用的虚拟局域网VLAN标签中为所述端口网络选择对应的VLAN标签(S402)；
    生成端口信息，并将所述端口信息写入所述ESXi主机中的端口信息表；其中，所述端口信息包括：所述端口的ESXi主机标识，所述端口的VLAN标签，所述端口的全局唯一标识符UUID以及所述端口扫描模块ID(S403)。
  5. 根据权利要求1所述的方法，所述方法还包括：
    在部署完成虚拟机后，当所述虚拟机发送业务报文时，通过所述虚拟机端口对应的VLAN标签封装待发送的业务报文，并将封装完成后的报文发送至所述支持OpenFlow协议的交换机(S601)；
    所述支持OpenFlow协议的交换机接收封装完成后的报文，通过解析去除报文中所述虚拟机端口对应的VLAN标签之后，用目的端口的VLAN标签封装，并从与目的端口关联的物理端口转发(S602)。
  6. 根据权利要求2所述的方法，其中，所述撤销虚拟机，包括：所述Openstack计算平台加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上撤销已部署的虚拟机。
  7. 根据权利要求6所述的方法，其中，所述Openstack计算平台加载预设的驱动程序，通过所述VMware vCenter在所述ESXi主机上撤销已部署的虚拟机，包括：
    删除所述待撤销虚拟机的每个端口所对应独占的端口网络(S701)；
    删除所述ESXi主机中的端口信息表内待删除端口对应的端口信息(S702)。
  8. 一种混合云平台系统(90)，其中，所述云平台系统(90)包括：OpenStack计算平台(901)、VMware vCenter(902)、至少一个ESXi主机(903)、支持OpenFlow协议的交换机(904)以及软件定义网络SDN控制器(905)；其中，每个ESXi主机(903)均分别与所述VMware vCenter(902)和所述支持OpenFlow协议的交换机(904)相连；
    所述OpenStack计算平台(901)，设置为部署虚拟机；以及撤销所述虚拟机；
    所述ESXi主机(903)，设置为当部署所述虚拟机时，发现新部署虚拟机的网络端口，并将所述新部署虚拟机的端口信息封装成第一虚拟站接口VSI发现协议VDP报文上报至所述SDN控制器(905)；其中，所述第一VDP报文用于将所述新部署虚拟机的端口与所述支持OpenFlow协议的交换机(904)的端口进行关联；以及当撤销所述虚拟机时，发现被撤销虚拟机的网络端口，并将所述被撤销虚拟机的端口信息封装成第二VDP报文上报至所述SDN控制器(905)；其中，所述第二VDP报文用于解除已关联的所述被撤销虚拟机的端口与所述支持OpenFlow协议的交换机(904)的端口。
  9. 根据权利要求8所述的系统(90)，其中，所述每台ESXi主机(903)上均部署两台虚拟交换机；其中，第一虚拟交换机(9031)设置为连接控制面网络，第二虚拟交换机(9032)设置为连接所述支持OpenFlow协议的交换机(904)；
    每台ESXi主机(903)上还部署了一个端口扫描模块(9033)，所述端口扫描模块(9033)设置为，发现在所述第二虚拟交换机(9032)上创建或者删除的网络端口，然后构造相应的VDP报文，向SDN控制器(905)通告新增网络端口的信息；
    在所述第二虚拟交换机(9032)上，每个由所述OpenStack计算平台(901)创建的VMware虚拟机的网络端口单独部署一个端口网络。
  10. 根据权利要求8所述的系统(90)，其中，所述Openstack计算平台(901)，是设置为加载预设的驱动程序，通过所述VMware vCenter(902)在所述ESXi主机(903)上部署所述虚拟机。
  11. 根据权利要求10所述的系统(90)，其中，
    所述Openstack计算平台(901)是设置为在所述虚拟机所在的ESXi主机(903)上为所述虚拟机的每个端口对应创建独占的端口网络；
    从所述ESXi主机(903)上未使用的VLAN标签中为所述端口网络选择对应的VLAN标签；
    生成端口信息，并将所述端口信息写入所述ESXi主机(903)中的端口信息表；其中，所述端口信息包括：所述端口的ESXi主机标识，所述端口的虚拟局域网VLAN标签，所述端口的全局唯一标识符UUID以及所述端口扫描模块ID。
  12. 根据权利要求8所述的系统(90)，所述ESXi主机(903)，还设置为当所述虚拟机发送业务报文时，通过所述虚拟机端口对应的虚拟局域网VLAN标签封装待发送的业务报文，并将封装完成后的报文发送至所述支持OpenFlow协议的交换机(904)；
    所述支持OpenFlow协议的交换机(904)，还设置为接收封装完成后的报文，通过解析去除报文中所述虚拟机端口对应的VLAN标签之后，用目的端口的VLAN标签封装，并从与目的端口关联的物理端口转发。
  13. 根据权利要求8所述的系统(90)，其中，所述Openstack计算平台(901)，是设置为加载预设的驱动程序，通过所述VMware vCenter(902)在所述ESXi主机(903)上撤销已部署的虚拟机。
  14. 根据权利要求13所述的系统(90)，其中，所述Openstack计算平台(901)，是设置为删除所述待撤销虚拟机的每个端口所对应独占的端口网络；
    以及，删除所述ESXi主机(903)中的端口信息表内待删除端口对应的端口信息。
  15. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现权利要求1至7中任一项所述的方法。
PCT/CN2017/096608 2016-08-11 2017-08-09 一种混合云平台的组网方法及混合云平台系统 WO2018028594A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610657363.1A CN107733746B (zh) 2016-08-11 2016-08-11 一种混合云平台的组网方法及混合云平台系统
CN201610657363.1 2016-08-11

Publications (1)

Publication Number Publication Date
WO2018028594A1 true WO2018028594A1 (zh) 2018-02-15

Family

ID=61161737

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/096608 WO2018028594A1 (zh) 2016-08-11 2017-08-09 一种混合云平台的组网方法及混合云平台系统

Country Status (2)

Country Link
CN (1) CN107733746B (zh)
WO (1) WO2018028594A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108809715A (zh) * 2018-06-11 2018-11-13 郑州云海信息技术有限公司 一种部署管理平台的方法及装置
CN109379239A (zh) * 2018-12-25 2019-02-22 杭州迪普科技股份有限公司 一种OpenStack环境中配置接入交换机的方法及装置
CN110308997A (zh) * 2019-07-11 2019-10-08 厦门厦科云海信息技术有限公司 基于OpenStack平台管理GPU设备的方法
CN111541566A (zh) * 2020-04-20 2020-08-14 深圳市三旺通信股份有限公司 交换机设备组网方法、支持profinet协议交换机设备及存储介质
CN112217902A (zh) * 2020-10-22 2021-01-12 新华三信息安全技术有限公司 一种防火墙数据同步方法及装置
CN113132200A (zh) * 2019-12-30 2021-07-16 中兴通讯股份有限公司 数据转发方法、转发器、系统、服务器和存储介质
CN114726715A (zh) * 2021-01-05 2022-07-08 中国移动通信有限公司研究院 一种数据帧传输方法、虚拟化平台及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111771190B (zh) * 2018-04-12 2024-04-09 华为云计算技术有限公司 探测虚拟机状态的方法和设备
CN109246200B (zh) * 2018-08-17 2021-07-06 下一代互联网重大应用技术（北京）工程研究中心有限公司 一种基于虚拟cdn的服务系统和方法
CN109756413B (zh) * 2019-03-05 2021-01-12 浪潮云信息技术股份公司 一种云数据中心异构网络互联系统及方法
CN110795209B (zh) * 2019-10-12 2022-07-12 苏州浪潮智能科技有限公司 一种控制方法和装置
CN110730133B (zh) * 2019-10-21 2021-11-12 北京百度网讯科技有限公司 路由通告方法和系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104205757A (zh) * 2012-04-24 2014-12-10 思科技术公司 用于混合云的分布式虚拟交换机架构
CN104486299A (zh) * 2014-11-28 2015-04-01 杭州华三通信技术有限公司 一种acl下发的方法和设备
US20150263979A1 (en) * 2014-03-14 2015-09-17 Avni Networks Inc. Method and apparatus for a highly scalable, multi-cloud service deployment, orchestration and delivery
CN105207873A (zh) * 2015-08-31 2015-12-30 华为技术有限公司 一种报文处理方法和装置
CN105515933A (zh) * 2015-11-30 2016-04-20 中电科华云信息技术有限公司 基于OpenStack实现VMware网络功能的管理方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9344401B2 (en) * 2009-02-04 2016-05-17 Citrix Systems, Inc. Methods and systems for providing translations of data retrieved from a storage system in a cloud computing environment
CN102546351B (zh) * 2012-03-15 2014-05-14 北京邮电大学 openflow网络和现有IP网络互联的系统和方法
CN104135379B (zh) * 2013-05-03 2017-05-10 新华三技术有限公司 基于OpenFlow协议的端口控制方法及装置
CN103685250A (zh) * 2013-12-04 2014-03-26 蓝盾信息安全技术股份有限公司 一种基于sdn的虚拟机安全策略迁移的系统及方法
CN103825954B (zh) * 2014-03-10 2017-12-01 中国联合网络通信集团有限公司 一种OpenFlow控制方法及相应插件、平台和网络
US20150341377A1 (en) * 2014-03-14 2015-11-26 Avni Networks Inc. Method and apparatus to provide real-time cloud security
CN105391568B (zh) * 2014-09-05 2019-07-23 华为技术有限公司 一种软件定义网络sdn的实现方法、装置和系统
CN104301391B (zh) * 2014-09-19 2019-02-22 北京邮电大学 多域光网络数据中心资源虚拟化映射方法
EP3046028B1 (en) * 2015-01-15 2020-02-19 Alcatel Lucent Load-balancing and scaling of cloud resources by migrating a data session

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104205757A (zh) * 2012-04-24 2014-12-10 思科技术公司 用于混合云的分布式虚拟交换机架构
US20150263979A1 (en) * 2014-03-14 2015-09-17 Avni Networks Inc. Method and apparatus for a highly scalable, multi-cloud service deployment, orchestration and delivery
CN104486299A (zh) * 2014-11-28 2015-04-01 杭州华三通信技术有限公司 一种acl下发的方法和设备
CN105207873A (zh) * 2015-08-31 2015-12-30 华为技术有限公司 一种报文处理方法和装置
CN105515933A (zh) * 2015-11-30 2016-04-20 中电科华云信息技术有限公司 基于OpenStack实现VMware网络功能的管理方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHEN, TIAN ET AL.: "OpenStack-Based Heterogeneous Hybrid Cloud Solution", TELECOMMUNICATIONS SCIENCE, 31 July 2015 (2015-07-31) *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108809715A (zh) * 2018-06-11 2018-11-13 郑州云海信息技术有限公司 一种部署管理平台的方法及装置
CN109379239A (zh) * 2018-12-25 2019-02-22 杭州迪普科技股份有限公司 一种OpenStack环境中配置接入交换机的方法及装置
CN110308997A (zh) * 2019-07-11 2019-10-08 厦门厦科云海信息技术有限公司 基于OpenStack平台管理GPU设备的方法
CN113132200A (zh) * 2019-12-30 2021-07-16 中兴通讯股份有限公司 数据转发方法、转发器、系统、服务器和存储介质
CN113132200B (zh) * 2019-12-30 2024-01-19 中兴通讯股份有限公司 数据转发方法、转发器、系统、服务器和存储介质
CN111541566A (zh) * 2020-04-20 2020-08-14 深圳市三旺通信股份有限公司 交换机设备组网方法、支持profinet协议交换机设备及存储介质
CN111541566B (zh) * 2020-04-20 2023-08-11 深圳市三旺通信股份有限公司 交换机设备组网方法、支持profinet协议交换机设备及存储介质
CN112217902A (zh) * 2020-10-22 2021-01-12 新华三信息安全技术有限公司 一种防火墙数据同步方法及装置
CN112217902B (zh) * 2020-10-22 2022-03-22 新华三信息安全技术有限公司 一种防火墙数据同步方法及装置
CN114726715A (zh) * 2021-01-05 2022-07-08 中国移动通信有限公司研究院 一种数据帧传输方法、虚拟化平台及存储介质

Also Published As

Publication number Publication date
CN107733746A (zh) 2018-02-23
CN107733746B (zh) 2021-06-15

Similar Documents

Publication Publication Date Title
WO2018028594A1 (zh) 一种混合云平台的组网方法及混合云平台系统
US11563669B2 (en) Method for implementing network virtualization and related apparatus and communications system
CN105323136B (zh) 信息的处理方法及装置
US11005752B2 (en) Packet transmission
US20190081921A1 (en) Management of domain name systems in a large-scale processing environment
EP3327994B1 (en) Virtual network management
WO2016107418A1 (zh) 云化网络通信路径的分配方法、装置及系统
WO2016034074A1 (zh) 一种软件定义网络sdn的实现方法、装置和系统
CN112398688B (zh) 容器网络配置方法、容器网络系统以及存储介质
US11641308B2 (en) Software defined networking orchestration method and SDN controller
US20180349033A1 (en) Orchestrator agnostic application container visibility
CN104518963A (zh) 用于经由交换结构在边缘设备之间实施连接的方法和装置
EP3125504B1 (en) Resource allocation method, packet communication method and device
CN112398687B (zh) 云计算网络的配置方法、云计算网络系统以及存储介质
EP3488583B1 (en) System and method for transport-layer level identification and isolation of container traffic
CN109587286A (zh) 一种设备接入控制方法及装置
WO2016150139A1 (zh) 一种建立网络业务实例的方法和装置
US20150301847A1 (en) Environment Virtualization
US20200228440A1 (en) Information processing method and related device
WO2016183832A1 (zh) 一种网络业务实例化的方法及设备
KR101644678B1 (ko) 네크워크 입출력 가상화 환경에서 가상 머신의 이동성 지원 방법 및 이를 수행하는 장치
EP4236270A2 (en) Software defined access fabric without subnet restriction to a virtual network
US11570097B1 (en) Overlay broadcast network for management traffic
CN116888940A (zh) 利用虚拟联网的容器化路由器
CN109104372B (zh) 一种网络对接方法、装置及系统、存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17838724

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17838724

Country of ref document: EP

Kind code of ref document: A1