WO2018137369A1 - 混合云管理方法、装置和计算设备 - Google Patents

混合云管理方法、装置和计算设备 Download PDF

Info

Publication number
WO2018137369A1
WO2018137369A1 PCT/CN2017/108197 CN2017108197W WO2018137369A1 WO 2018137369 A1 WO2018137369 A1 WO 2018137369A1 CN 2017108197 W CN2017108197 W CN 2017108197W WO 2018137369 A1 WO2018137369 A1 WO 2018137369A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual machine
address
cloud
public cloud
deployed
Prior art date
Application number
PCT/CN2017/108197
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 WO2018137369A1 publication Critical patent/WO2018137369A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • 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/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses

Definitions

  • the present disclosure relates to the field of cloud computing technologies, and in particular, to a hybrid cloud management method, apparatus, and computing device.
  • hybrid cloud combines public cloud and private cloud. It is the main mode and development direction of cloud computing in recent years.
  • Hybrid clouds need to be able to deploy and schedule flexible policies between private and public clouds for applications that target the same enterprise tenant.
  • the application of the private cloud generates explosive resource demand.
  • the resources of the private cloud are insufficient, the flexible cloud is flexibly extended to the public cloud temporary leased resource.
  • These application scenarios, such as the public cloud as a disaster recovery backup point for private clouds have also presented new challenges to hybrid clouds. Therefore, data centers need to be able to interconnect at high speeds, and they need to be able to uniformly manage networks on public clouds and private networks to achieve network interoperability.
  • a first virtual machine runs in the private cloud
  • a second virtual machine runs in the public cloud.
  • the first proxy device is deployed on the first virtual machine, and the second virtual machine is deployed.
  • the second proxy device is deployed.
  • the first virtual machine accesses the second virtual machine
  • the first virtual machine sends an access request to the first proxy device, where the access request carries the IP address of the second virtual machine; the first proxy device forwards the access request to the second proxy device
  • the second proxy device forwards the access request to the second virtual machine to enable the first virtual machine to access the second virtual machine.
  • the virtual machine in the hybrid cloud needs to be configured, which results in poor versatility of the above method.
  • an embodiment of the present disclosure provides a hybrid cloud management method, where the method is applied to a HyperNode HyperNode in a hybrid cloud management system, where the method includes:
  • the accessed virtual machine is a virtual machine deployed in the public cloud
  • the virtual machine deployed in the public cloud carried in the access data packet is interconnected between the first network in the public cloud according to the access data packet.
  • An IP address, the access data packet is sent to the accessed virtual machine;
  • the accessing virtual machine is the virtual machine deployed in the public cloud, obtaining the deployment in the public cloud according to the second IP address of the virtual machine deployed in the public cloud carried by the access data packet a first IP address of the virtual machine, modifying a source IP address of the access data packet to a first IP address of the virtual machine deployed in the public cloud, and sending the access data packet to the accessed virtual machine .
  • the source IP address or the destination IP address of the access data packet is modified by the HyperNode, and the modified access data packet is sent to the accessed virtual machine, thereby eliminating the need for virtual in the hybrid cloud.
  • Network configuration can be achieved by configuring the machine.
  • the obtaining, according to the protocol IP address of the virtual network deployed in the public cloud and being interconnected between the first networks in the public cloud, is obtained according to the access data packet.
  • the second IP address of the virtual machine in the public cloud in the private cloud including:
  • the obtaining, according to the second IP address of the virtual machine deployed in the public cloud, the first IP address of the virtual machine deployed in the public cloud includes:
  • the first IP address of the virtual machine deployed in the public cloud is obtained from the correspondence between the first IP address and the second IP address according to the second IP address of the virtual machine deployed in the public cloud.
  • the HyperNode stores the correspondence between the first IP address and the second IP address, and therefore, when acquiring the second IP address of the virtual machine deployed in the public cloud, according to the virtual machine deployed in the public cloud
  • the first IP address, the second IP address of the virtual machine deployed in the public cloud is obtained from the correspondence between the first IP address and the second IP address, and the first IP address of the virtual machine deployed in the public cloud is obtained.
  • the second IP address of the virtual machine deployed in the public cloud is obtained from the correspondence between the first IP address and the second IP address according to the second IP address of the virtual machine deployed in the public cloud, thereby improving the acquisition.
  • the accuracy of the IP address is obtained from the correspondence between the first IP address and the second IP address, and therefore improving the acquisition.
  • the method before the receiving the access data packet sent by the virtual machine, the method further includes:
  • the second cloud gateway Cloud GW in the public cloud, the first IP address and the second IP address of the virtual machine deployed in the public cloud, and the first IP of the virtual machine deployed in the public cloud
  • the second cloud GW is obtained from the virtual machine deployed in the public cloud, and the second IP address of the virtual machine deployed in the public cloud is the second cloud GW from the hybrid cloud. Obtained in the management module in the management system;
  • the HyperNode establishes a correspondence between the first IP address and the second IP address of the virtual machine deployed in the public cloud, so as to facilitate the subsequent first IP address or the first virtual server according to the virtual cloud deployed in the public cloud.
  • the second IP address, the second IP address or the first IP address of the virtual machine deployed in the public cloud is obtained from the correspondence between the first IP address and the second IP address.
  • the method further includes:
  • the IP address masquerading is implemented by the HyperNode
  • the new ARP Proxy is configured in the HyperNode
  • the MAC address masquerading is implemented by the ARP Proxy, so that the IP address and the MAC address of the virtual machine remain unchanged, and no network configuration is required. Changes can be used to achieve virtual machine migration between clouds.
  • the access virtual machine is a virtual machine deployed in a private cloud
  • the accessed virtual machine is a virtual machine deployed in a public cloud
  • the access data packet further carries the deployed
  • the media control accesses the MAC address of the virtual machine in the public cloud
  • the method further includes: before receiving the access data packet sent by the virtual machine, the method further includes:
  • ARP request sent by the virtual machine deployed in the private cloud, where the ARP request carries the second IP address of the virtual machine deployed in the public cloud;
  • the Hypernode stores the correspondence between the MAC address of the virtual machine deployed in the public cloud and the second IP address. Therefore, the Hypernode can obtain the second IP address of the virtual machine deployed in the public cloud. The MAC address of the virtual machine deployed in the public cloud.
  • an embodiment of the present disclosure provides a hybrid cloud management method, where the method is applied to a management module in a hybrid cloud management system, where the method includes:
  • the management module allocates a second IP address to the virtual machine in the hybrid cloud management system, so that network interaction in the hybrid cloud is not required.
  • the protocol allocates a protocol IP address for the virtual machine to be interconnected between the second networks in the private cloud according to the MAC address of the virtual machine, including:
  • an embodiment of the present disclosure provides a hybrid cloud management device, where the device is applied in a HyperNode HyperNode in a hybrid cloud management system, and the device includes the hybrid cloud management provided by the first aspect. At least one module of the method.
  • an embodiment of the present disclosure provides a hybrid cloud management apparatus, where the apparatus is applied in a management module in a hybrid cloud management system, and the apparatus includes a hybrid cloud management method provided for performing the second aspect. At least one module.
  • an embodiment of the present disclosure provides a computing device, where the computing device includes a first communication interface, a first processor, and a first memory, where the first communication interface and the first processor and the The first memory establishes a communication connection, the first processor establishes a communication connection with the first memory, the first memory is configured to store program code, and the first communication interface and the first processor are configured to execute The hybrid cloud management method provided by the first aspect.
  • an embodiment of the present disclosure provides a computing device, where the computing device includes a second communication interface, a second processor, and a second memory, where the second communication interface and the second processor and the Said second memory establishes a communication connection, said second processor establishes a communication connection with said second memory, said second memory is for storing program code; said second communication interface and said second processor are for performing
  • the second aspect provides a hybrid cloud management method.
  • the source IP address or the destination IP address of the access packet is accessed through the HyperNode.
  • the modification is performed to send the modified access data packet to the accessed virtual machine, so that the virtual machine in the hybrid cloud does not need to be configured, so that network interworking can be realized.
  • 1-1 is a schematic diagram of a hybrid cloud management system according to an embodiment of the present disclosure
  • 1-2 is a schematic diagram of a hybrid cloud management system according to an embodiment of the present disclosure
  • FIG. 1-3 are schematic diagrams of a hybrid cloud management system according to an embodiment of the present disclosure.
  • FIG. 1-4 are schematic diagrams of a hybrid cloud management system according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic structural diagram of a computing device according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a hybrid cloud management method according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart of a hybrid cloud management method according to an embodiment of the present disclosure.
  • FIG. 6 is a flowchart of a hybrid cloud management method according to an embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a hybrid cloud management method according to an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of a hybrid cloud management method according to an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of a hybrid cloud management method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a hybrid cloud management apparatus according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a hybrid cloud management apparatus according to an embodiment of the present disclosure.
  • a flow table is used to control a data flow in a software-defined network.
  • a flow table conforming to a software-defined network (English full name: openflow) protocol is used as an example, and in actual use, other protocols may also be adopted.
  • Flow table conforming to a software-defined network (English full name: openflow) protocol is used as an example, and in actual use, other protocols may also be adopted.
  • the data packet is used in the process of transmission between the public cloud and the private cloud.
  • the overlay encapsulation technology is used, and any of the following may be used: virtual extensible local area network (English name: virtual extensible local area network, abbreviation: VXLAN) Technology, using network virtualization using generic routing encapsulation (English name: NVGRE) technology and stateless transport tunneling (English name: stateless transport tunneling, abbreviation: STT) technology.
  • VXLAN technology is employed.
  • a mixed cloud management system is provided in this specification.
  • the system includes: a management module, a first cloud gateway (English full name: Cloud Gateway, abbreviation: Cloud GW), a second cloud GW, and a first virtual Scalable LAN (English full name: Virtual Extensible LAN, abbreviation: VXLAN) GW, second VXLAN GW and SuperNode (English full name: HyperNode).
  • the management module includes a resource management module and a network service module, and the network service module includes a first dynamic host configuration protocol (English name: Dynamic Host Configuration Protocol, abbreviation: DHCP) server.
  • DHCP Dynamic Host Configuration Protocol
  • the management module, the first Cloud GW, the second Cloud GW, the first VXLAN GW, the second VXLAN GW, the HyperNode, and the virtual machines deployed in the public cloud and deployed in the private cloud all run on the computing device.
  • the structure of each computing device is shown in Figure 2.
  • Each computing device can actually be a server.
  • Each computing device can include a communication interface 110, a processor 120, and a memory 130 that establishes a communication connection with the processor 120 and the memory 130, respectively, and the processor 120 and the memory 130 establish a communication connection.
  • the memory 130 may include a volatile memory (English name: volatile memory), such as a random access memory (English name: random-access memory, abbreviation: RAM); the memory may also include a non-volatile memory (English full name: non- Volatile memory), such as read-only memory (English full name: read-only memory, abbreviation: ROM), flash memory (English full name: flash memory), hard disk (English full name: hard disk drive, abbreviation: HDD) or solid state drive ( The full name of English: solid state drive, abbreviation: SSD); the memory 130 may also include a combination of the above types of memory.
  • program code for implementing the hybrid cloud management method provided by the present disclosure is stored in the memory 130 and executed by the processor 120.
  • Each computing device communicates with each module in the hybrid cloud management system via communication interface 110.
  • the processor 120 can be a central processing unit (English name: central processing unit, abbreviation: CPU).
  • the management module, the first Cloud GW, the second Cloud GW, the first VXLAN GW, the second VXLAN GW, and the HyperNode can be implemented by software running on the virtual machine, the deployment of the virtual machine is flexible. Therefore, the management module, the first Cloud GW, the second Cloud GW, the first VXLAN GW, the second VXLAN GW, the HyperNode, and the virtual machines deployed in the public cloud and deployed in the private cloud may also be merged in actual deployment. deploy.
  • the first VXLAN GW may also be deployed on a computing device of a private cloud in which the virtual machine has been deployed
  • the second VXLAN GW may also be deployed on a computing device of a public cloud in which the virtual machine has been deployed, HyperNode and the second VXLAN GW.
  • the first Cloud GW and the first VXLAN GW are respectively a Cloud GW and a VXLAN GW corresponding to the private cloud
  • the second Cloud GW and the second VXLAN GW are respectively a Cloud GW and a VXLAN GW corresponding to the public cloud.
  • the management module is respectively connected to the first Cloud GW, the second Cloud GW, the first VXLAN GW, and the second VXLAN GW.
  • the first Cloud GW is respectively connected to the host where the virtual machine deployed in the private cloud is located and the first VXLAN GW, and the second Cloud GW is connected to the second VXLAN GW and the HyperNode, respectively.
  • the first VXLAN GW is connected to the second VXLAN GW by the host where the virtual machine deployed in the private cloud is located, and the second VXLAN GW is connected to the HyperNode.
  • a resource management module for providing a hybrid cloud service for a user, such as computing resource management (eg, creating a virtual machine), storage resource management (eg, creating a volume), and network resource management (eg, creating a subnet) .
  • computing resource management eg, creating a virtual machine
  • storage resource management eg, creating a volume
  • network resource management eg, creating a subnet
  • a network service module is configured to create a required network service, such as a DHCP service, according to the requirements of the resource management module.
  • the first Cloud GW is used to provide a service access interface to operate resources in the cloud to provide a set of rules for the private cloud.
  • An interface is used by the hybrid cloud system; and the private cloud is configured according to the requirements of the hybrid cloud management system, for example, network configuration is performed on the first VXLAN GW (for example, the generated flow table is sent to the first VXLAN GW).
  • the second Cloud GW is configured to provide a service access interface to operate resources in the cloud, provide a unified interface for the public cloud to be used by the hybrid cloud system, and perform network configuration on the public cloud according to the requirements of the hybrid cloud management system, for example,
  • the VXLAN GW performs network configuration (for example, the generated flow table is sent to the second VXLAN GW).
  • the HyperNode is configured to intercept the data packet of the virtual machine deployed in the public cloud, and allocate the first IP address of the virtual machine deployed in the public cloud to the first DHCP server through the second DHCP server in the public cloud.
  • the second IP addresses assigned by the virtual machines in the public cloud are mutually converted, so that the virtual machines deployed in the public cloud access each other with the second IP address.
  • the first VXLAN GW is configured to communicate with the second VXLAN GW to implement interworking between the public cloud and the private cloud.
  • the second VXLAN GW is configured to communicate with the first VXLAN GW to implement interworking between the public cloud and the private cloud.
  • the host where the virtual machine is deployed in the private cloud may also include a proxy (English full name: Agent), which is used to complete the configuration of the host with the hybrid cloud management system.
  • Agent English full name: Agent
  • the public cloud also includes a router (English name: Router), which is used to forward data for HyperNode and virtual machines deployed in the public cloud.
  • Router American name: Router
  • HyperNode can run on a virtual machine in the public cloud.
  • the first Cloud GW can be deployed inside the private cloud or outside the private cloud; the second Cloud GW can be deployed inside the public cloud or outside the public cloud.
  • the deployment locations of the first Cloud GW and the second Cloud GW are not specifically limited, as long as the network interworking can be ensured.
  • the connections described in the embodiments of the present disclosure include a wired connection or a wireless connection.
  • the first Cloud GW is deployed outside the private cloud
  • the second Cloud GW is deployed outside the public cloud as an example.
  • the first Cloud GW is deployed inside the private cloud
  • the second Cloud GW is deployed inside the public cloud.
  • the first Cloud GW is deployed outside the private cloud
  • the second Cloud GW is deployed inside the public cloud.
  • the first Cloud GW is deployed inside the private cloud
  • the second Cloud GW is deployed outside the public cloud.
  • the first Cloud GW is deployed on a computing device external to the private cloud
  • the second Cloud GW is deployed on a computing device external to the private cloud.
  • the hybrid cloud management system when the hybrid cloud management system provided by the embodiment of the present disclosure manages the virtual machine deployed in the public cloud and the virtual machine deployed in the private cloud, the first VXLAN GW and the second connection need to be performed according to the above connection relationship.
  • the VXLAN GW, the first Cloud GW, the second Cloud GW, and the HyperNode are deployed, and the network communication between the management plane data and the data plane is configured; and the account information used by the second Cloud GW to create the virtual machine deployed in the public cloud is configured. And network information.
  • the routing rule is configured in the second Cloud GW, so that the network default next hop of the virtual machine deployed in the public cloud created by the second Cloud GW is HyperNode.
  • FIGS. 1-1 to 1-4 indicate the transmission control plane data flow between the two network elements, and the solid line indicates the transmission service plane data flow between the two network elements.
  • Step 201 The network service module acquires subnet information of the network to be created.
  • the user can input subnet information to the network service module; the network service module receives subnet information input by the user.
  • the subnet information may be a protocol for interconnecting networks of subnet segments (English full name: Internet Protocol, abbreviation: IP) address.
  • IP Internet Protocol
  • the IP address of the subnet segment may be 192.168.0.0/24.
  • Step 202 The network service module creates a network according to the subnet information.
  • the network service module creates a VXLAN network according to the subnet information, and the virtual machine in the hybrid cloud management system is connected to the VXLAN network.
  • Step 203 The network service module configures the first DHCP server for the network.
  • the first DHCP server is configured to allocate an IP address for accessing a virtual machine in the VXLAN network.
  • Step 204 The network service module sends the identifier of the first DHCP server to the virtual machine accessing the network.
  • the network service module stores a media access control (English name: Media Access Control, abbreviation: MAC) address for accessing a virtual machine in the network, and accesses the virtual access device according to the MAC address of the virtual machine in the network.
  • the virtual machine in the network sends the identity of the first DHCP server.
  • the virtual machine accessing the network receives the identifier of the first DHCP server sent by the network service module.
  • the server identifier of the first DHCP server may be an IP address or a MAC address of the first DHCP server. In the embodiment of the disclosure, the server identifier of the first DHCP server is not specifically limited.
  • the first DHCP server After the virtual machine deployed in the private cloud and the virtual machine deployed in the public cloud access the network, the first DHCP server allocates an IP address to the virtual machine deployed in the private cloud and the virtual machine deployed in the public cloud. As shown in FIG. 4, the process of assigning an IP address to a virtual machine deployed in a private cloud by the first DHCP server includes:
  • Step 301 The virtual machine deployed in the private cloud in the private cloud sends a first allocation request to the first DHCP server, where the first allocation request carries the MAC address of the virtual machine deployed in the private cloud.
  • the virtual machine deployed in the private cloud in the private cloud has obtained the server identifier of the first DHCP server in step 202, and the virtual machine deployed in the private cloud sends a first allocation request to the first Cloud GW, the first allocation request.
  • the first Cloud GW Carrying the MAC address of the virtual machine deployed in the private cloud and the server identifier of the first DHCP server; the first Cloud GW receives the first allocation request sent by the virtual machine deployed in the private cloud, according to the server identifier of the first DHCP server And forwarding the first allocation request to the first DHCP server.
  • the virtual machine that is deployed in the private cloud is connected to the network service module, and the virtual machine deployed in the private cloud is connected to the first virtual server according to the server identifier of the first DHCP server.
  • the DHCP server sends a first allocation request.
  • Step 302 The first DHCP server receives the first allocation request sent by the virtual machine deployed in the private cloud, and obtains the IP of the virtual machine deployed in the private cloud according to the MAC address of the virtual machine deployed in the private cloud. address.
  • the first DHCP server obtains the IP address of the virtual machine deployed in the private cloud according to the MAC address of the virtual machine deployed in the private cloud.
  • the steps can be:
  • the first DHCP server obtains the IP address of the virtual machine deployed in the private cloud from the correspondence between the MAC address and the IP address according to the MAC address of the virtual machine deployed in the private cloud.
  • the correspondence between the MAC address and the IP address stored in the first DHCP server is as follows:
  • the first DHCP server obtains the IP address of VM1 from Table 1 according to MAC1 to be 192.168.0.3; for example, the virtual machine VM2 deployed in the private cloud.
  • the MAC address is MAC2
  • the first DHCP server obtains the IP address of VM2 from Table 1 according to MAC2 to be 192.168.0.4.
  • Step 303 The first DHCP server sends the IP address to the virtual machine deployed in the private cloud.
  • the first DHCP server sends a first allocation response to the first cloud GW, where the first allocation response carries the MAC address of the virtual machine deployed in the private cloud; the first Cloud GW receives the first allocation response sent by the first DHCP server, according to The MAC address of the virtual machine deployed in the private cloud is forwarded to the virtual machine deployed in the private cloud.
  • Step 304 The virtual machine deployed in the private cloud receives the IP address sent by the first DHCP server.
  • the first DHCP server in the hybrid cloud management system allocates an IP address to the virtual machine deployed in the public cloud
  • the second DHCP server in the public cloud is also the virtual machine deployed in the public cloud.
  • the IP address assigned to the virtual machine deployed in the public cloud is called the first IP address
  • the IP address assigned by the first DHCP server to the virtual machine deployed in the public cloud is as shown in FIG. 5, and includes:
  • Step 401 The virtual machine deployed in the public cloud in the public cloud sends a second allocation request to the second DHCP server in the public cloud, where the second allocation request carries the MAC address of the virtual machine deployed in the public cloud.
  • the server identifier of the second DHCP server in the public cloud is obtained, and the second allocation request is sent to the second cloud GW, and the second allocation request carries the deployment in the public cloud.
  • the management module sends a setup request to the second Cloud GW, where the setup request carries the deployment in the public cloud.
  • the device identifier of the virtual machine is received by the second cloud GW, and the virtual machine deployed in the public cloud is created by calling the interface of the public cloud according to the configuration information.
  • the configuration information includes account information and a network identifier.
  • Step 402 The second DHCP server receives the second allocation request sent by the virtual machine deployed in the public cloud, and obtains the virtual machine deployed in the public cloud according to the MAC address of the virtual machine deployed in the public cloud. One IP address.
  • the second DHCP server obtains the first virtual machine deployed in the public cloud according to the MAC address of the virtual machine deployed in the public cloud.
  • the steps of the IP address can be:
  • the second DHCP server obtains the first IP address of the virtual machine deployed in the public cloud from the correspondence between the MAC address and the IP address according to the MAC address of the virtual machine deployed in the public cloud.
  • the correspondence between the MAC address and the IP address stored in the second DHCP server is as shown in Table 2 below:
  • the second DHCP server obtains the first IP address of the VM3 from Table 2 according to MAC3 as 172.16.0.101; for example, the virtual deployment in the public cloud.
  • the MAC address of the machine VM4 is MAC4
  • the second DHCP server obtains the first IP address of the VM4 from Table 2 according to the MAC4 as 172.16.0.102.
  • Step 403 The second DHCP server sends the first IP address to the virtual machine deployed in the public cloud.
  • the second DHCP server sends a second allocation response to the second Cloud GW, where the second allocation response carries the MAC address of the virtual machine deployed in the public cloud; and the second Cloud GW receives the second allocation response sent by the second DHCP server, according to The public
  • Step 404 The virtual machine deployed in the public cloud receives the first IP address sent by the second DHCP server.
  • Step 405 The second Cloud GW in the public cloud acquires the first IP address of the virtual machine deployed in the public cloud from the virtual machine deployed in the public cloud.
  • Step 406 The second Cloud GW acquires, from the first DHCP server, a second IP address of the virtual machine deployed in the public cloud.
  • the second Cloud GW sends a query request to the first DHCP server, where the query request carries the MAC address of the virtual machine deployed in the public cloud; the first DHCP server receives the query request sent by the second Cloud GW, according to the deployment in the public cloud.
  • the MAC address of the virtual machine acquires the second IP address of the virtual machine deployed in the public cloud, and sends the second IP address of the virtual machine deployed in the public cloud to the second Cloud GW.
  • the step of obtaining, by the first DHCP server, the second IP address of the virtual machine deployed in the public cloud according to the MAC address of the virtual machine deployed in the public cloud may be:
  • the first DHCP server obtains the second IP address of the virtual machine deployed in the public cloud from the correspondence between the MAC address and the IP address according to the MAC address of the virtual machine deployed in the public cloud.
  • the first DHCP server obtains the second IP address of the VM3 from Table 1 according to the MAC3 to be 192.168.0.5; for example, the virtuality deployed in the public cloud.
  • the MAC address of the machine VM4 is MAC4, and the first DHCP server obtains the second IP address of the VM4 from Table 1 according to the MAC4 to be 192.168.0.6.
  • Step 407 The second Cloud GW sends the first IP address and the second IP address of the virtual machine deployed in the public cloud to the HyperNode.
  • Step 408 The HyperNode receives the first IP address and the second IP address of the virtual machine deployed in the public cloud sent by the second Cloud GW, and establishes a first IP address and a second IP of the virtual machine deployed in the public cloud. The correspondence of addresses.
  • the flow table is added to the HyperNode.
  • the HyperNode configures the correspondence between the first IP address and the second IP address of the virtual machine deployed in the public cloud to the flow table.
  • Add an address resolution protocol (English name: Address Resolution Protocol, ARP) proxy server (English name: Proxy) in HyperNode; ARP Proxy is used to modify the IP address of the packet sent by the virtual machine deployed in the public cloud and Modify the IP address of the packet sent to the virtual machine deployed in the public cloud.
  • ARP Address Resolution Protocol
  • the HyperNode receives the data packet sent by the second VXLAN GW, and the destination IP address of the data packet is the second IP address, the HyperNode obtains the deployment according to the second IP address of the virtual machine deployed in the public cloud.
  • the first IP address of the virtual machine in the public cloud, the destination address of the data packet is modified to the first IP address of the virtual machine deployed in the public cloud.
  • the HyperNode modifies the source IP address of the data packet to the virtual machine deployed in the public cloud. The first IP address.
  • the source IP address or the destination IP address of the access data packet is modified by the HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that the virtual machine in the hybrid cloud does not need to be configured. Network interoperability can be achieved.
  • virtual machines can access each other, that is, virtual machines deployed in a private cloud can access virtual machines deployed in the public cloud, and virtual machines deployed in the public cloud can be accessed and deployed in private.
  • Virtual machines in the cloud, virtual machines deployed in the public cloud can also access virtual machines deployed in the public cloud.
  • the process of accessing a virtual machine deployed in a public cloud to a virtual machine deployed in a public cloud is as shown in FIG. 6, and includes:
  • Step 501 The virtual machine deployed in the private cloud sends an ARP request to the HyperNode, where the ARP request carries the second IP address of the virtual machine deployed in the public cloud to be accessed.
  • the MAC address of the virtual machine deployed in the public cloud needs to be obtained. Therefore, the virtual machine access deployed in the private cloud is deployed in the public cloud.
  • the virtual machine deployed in the private cloud sends an ARP request to the HyperNode, and the ARP request is used to obtain the MAC address of the virtual machine deployed in the public cloud.
  • This step can be implemented by the following steps 5011-5014, including:
  • the virtual machine deployed in the private cloud sends an ARP request to the virtual switch of the host where the virtual machine deployed in the private cloud is located, where the ARP request carries the second IP address of the virtual machine deployed in the public cloud to be accessed.
  • the virtual machine deployed in the private cloud obtains the second IP address of the virtual machine to be accessed in the public cloud, according to the IP address of the virtual machine deployed in the private cloud and the virtual machine deployed in the public cloud
  • the second IP address determines that the virtual machine deployed in the public cloud and the virtual machine deployed in the private cloud are in the same VXLAN network, and sends an ARP request to the virtual switch of the host where the virtual machine deployed in the private cloud is located.
  • the virtual machine deployed in the private cloud has an IP address of 192.168.0.3
  • the virtual machine deployed in the public cloud has a second IP address of 192.168.0.5. Since 192.168.0.3 and 192.168.0.5 belong to the same The network segment, therefore, the virtual machine deployed in the private cloud determines that the virtual machine deployed in the public cloud and the virtual machine deployed in the private cloud are in the same vxlan network.
  • the virtual switch receives an ARP request sent by a virtual machine deployed in the private cloud, and sends the ARP request to the second VXLAN GW.
  • the virtual switch encapsulates the ARP request into a VXLAN packet and sends the VXLAN packet to the second VXLAN GW.
  • the second VXLAN GW receives the ARP request sent by the virtual switch, and sends the ARP request to the first VXLAN GW.
  • the second VXLAN GW acquires the identifier of the first VXLAN GW, and sends the ARP request to the first VXLAN GW according to the identifier of the first VXLAN GW.
  • the corresponding relationship between the identifiers of the vxlan network and the VXLAN GW is configured in the second VXLAN GW; correspondingly, the step of obtaining the identifier of the first VXLAN GW by the second VXLAN GW may be:
  • the second VXLAN GW determines, according to the second IP address of the virtual machine deployed in the public cloud, the vxlan network where the virtual machine deployed in the public cloud is located, according to the vxlan network where the virtual machine deployed in the public cloud is located.
  • the identifier of the first VXLAN GW is obtained from the correspondence between the identifiers of the vxlan network and the VXLAN GW.
  • the second VXLAN GW first re-encapsulates the vxlan data packet, and sends the re-encapsulated vxlan data packet to the first VXLAN GW.
  • the first VXLAN GW receives the ARP request sent by the second VXLAN GW, and sends the ARP request to the HyperNode.
  • Step 502 The HyperNode receives the ARP request sent by the virtual machine deployed in the private cloud, and obtains the MAC address of the virtual machine deployed in the public cloud according to the second IP address of the virtual machine deployed in the public cloud.
  • the ARP proxy in the HyperNode is configured with the mapping between the MAC address of the virtual machine deployed in the public cloud and the second IP address.
  • the HyperNode obtains the second IP address of the virtual machine deployed in the public cloud.
  • the steps of the MAC address of the virtual machine deployed in the public cloud can be:
  • the HyperNode sends the second IP address of the virtual machine deployed in the public cloud to the ARP Proxy; the ARP Proxy receives the second IP address of the virtual machine deployed in the public cloud sent by the HyperNode, according to the virtuality of the deployed in the public cloud.
  • the second IP address of the machine obtains the MAC address of the virtual machine deployed in the public cloud from the correspondence between the MAC address and the second IP address, and sends the MAC address of the virtual machine deployed in the public cloud to the HyperNode; HyperNode Receives the MAC address of the virtual machine deployed in the public cloud sent by the ARP Proxy.
  • Step 503 The HyperNode sends the MAC address of the virtual machine deployed in the public cloud to the virtual machine deployed in the private cloud.
  • the HyperNode sends the MAC address of the virtual machine deployed in the public cloud to the virtual machine deployed in the private cloud along the request path for sending the ARP request.
  • the process can be implemented by the following steps 5031-5034, including:
  • the HyperNode sends the MAC address of the virtual machine deployed in the public cloud to the first VXLAN GW.
  • the first VXLAN GW receives the MAC address of the virtual machine deployed in the public cloud sent by the HyperNode, and sends the MAC address of the virtual machine deployed in the public cloud to the second VXLAN GW.
  • the second VXLAN GW receives the MAC address of the virtual machine deployed in the public cloud sent by the first VXLAN GW, and sends the deployment to the virtual switch of the host where the virtual machine deployed in the private cloud is located in the public cloud.
  • the MAC address of the virtual machine is not limited to the public cloud.
  • the virtual switch receives the MAC address of the virtual machine deployed in the public cloud sent by the second VXLAN GW, and sends the MAC address of the virtual machine deployed in the public cloud to the virtual machine deployed in the private cloud.
  • Step 504 The virtual machine deployed in the private cloud receives the MAC address of the virtual machine deployed in the public cloud sent by the HyperNode.
  • step 505 After the virtual machine deployed in the private cloud obtains the MAC address of the virtual machine deployed in the public cloud, the following step 505 sends an access data packet to the virtual machine deployed in the public cloud to access the deployed in the public cloud. Virtual machine.
  • Step 505 The virtual machine deployed in the private cloud sends an access data packet to the HyperNode, where the source IP address of the access data packet is the IP address of the virtual machine deployed in the private cloud, and the source MAC address is deployed in the private cloud.
  • the MAC address of the virtual machine, the destination IP is the second IP address of the virtual machine deployed in the public cloud, and the destination MAC address is the MAC address of the virtual machine deployed in the public cloud.
  • This step can be implemented by the following steps 5051-5054, including:
  • a virtual machine deployed in a private cloud sends an access packet to a virtual switch of a host where a virtual machine deployed in a private cloud is located.
  • the virtual switch receives the access data packet sent by the virtual machine deployed in the private cloud, and sends the access data packet to the second VXLAN GW.
  • the virtual switch encapsulates the access data packet, encapsulates the access data packet into an access data packet in a VXLAN format, and sends the encapsulated access data packet to the second VXLAN GW.
  • the second VXLAN GW receives the access data packet sent by the virtual switch, and sends the access data packet to the first VXLAN GW.
  • the second VXLAN GW re-encapsulates the access packet and transmits the encapsulated access packet to the first VXLAN GW.
  • the first VXLAN GW receives the access data packet sent by the second VXLAN GW, and sends the access data packet to the HyperNode.
  • Step 506 The HyperNode receives the access data packet sent by the virtual machine deployed in the private cloud, and modifies the destination IP address of the access data packet to the first IP address.
  • the HyperNode decapsulates the access packet to obtain an access packet in an Ethernet format, and obtains a correspondence between the second IP address and the first IP address according to the second IP address of the virtual machine deployed in the public cloud.
  • the first IP address of the virtual machine deployed in the public cloud, and the destination IP address of the access data packet is modified to the first IP address.
  • Step 507 The HyperNode sends the access data packet to the virtual machine deployed in the public cloud according to the first IP address.
  • the HyperNode sends the access data packet to the Router node.
  • the Router node receives the access data packet sent by the HyperNode, and sends the access data packet to the virtual machine deployed in the public cloud according to the destination IP address of the access data packet: the first IP address. .
  • Step 508 The virtual machine deployed in the public cloud receives the access data packet sent by the HyperNode.
  • the source IP address or the destination IP address of the access data packet is modified by the HyperNode, and the modified access data packet is sent to the accessed virtual machine, thereby eliminating the need for virtual in the hybrid cloud.
  • Network configuration can be achieved by configuring the machine.
  • Step 601 The virtual machine deployed in the public cloud sends an access data packet to the HyperNode.
  • the source IP address of the access data packet is the first IP address of the virtual machine deployed in the public cloud, and the source MAC address is deployed in the public cloud.
  • the MAC address of the virtual machine, the destination IP address is the IP address of the virtual machine deployed in the private cloud to be accessed, and the destination MAC address is the MAC address of the virtual machine deployed in the private cloud.
  • This step can be implemented by the following steps 6011-6012, including:
  • a virtual machine deployed in the public cloud sends an access packet to a Router node in the public cloud.
  • the virtual machine deployed in the public cloud obtains the IP address of the virtual machine deployed in the private cloud to be accessed, according to the IP address of the virtual machine deployed in the private cloud and the first virtual machine deployed in the public cloud The IP address is determined.
  • the virtual machine deployed in the public cloud is not in the same vxlan network as the virtual machine deployed in the private cloud.
  • the router in the public cloud is required to forward the virtual machine in the public cloud.
  • the Router node in the public cloud sends access packets.
  • the Router node receives the access data packet sent by the virtual machine deployed in the public cloud, and forwards the access data packet to the HyperNode.
  • the Router node forwards the access packet to the HyperNode according to the routing rule.
  • the routing rule is that the next hop of the router node is a HyperNode.
  • Step 602 The HyperNode receives the access data packet sent by the virtual machine deployed in the public cloud, and modifies the source IP address of the access data packet to the second IP address of the virtual machine deployed in the public cloud.
  • the HyperNode acquires the second IP address of the virtual machine deployed in the public cloud from the first IP address and the second IP address according to the first IP address of the virtual machine deployed in the public cloud.
  • the source IP address of the packet is modified to the second IP address of the virtual machine deployed in the public cloud.
  • Step 603 The HyperNode sends the access data packet to the second VXLAN GW.
  • Step 604 The second VXLAN GW receives the access data packet sent by the HyperNode, and sends the access data packet to the first VXLAN GW.
  • the second VXLAN GW encapsulates the access packet and transmits the encapsulated access packet to the first VXLAN GW.
  • Step 605 The first VXLAN GW receives the access data packet sent by the second VXLAN GW, and sends the access data packet to the virtual machine deployed in the private cloud.
  • the first VXLAN GW encapsulates the access packet and sends the access packet to the virtual machine deployed in the private cloud.
  • the first VXLAN GW sends the access data packet to the virtual switch of the host where the virtual machine deployed in the private cloud is located, and the virtual switch receives the access data packet sent by the first VXLAN GW, and decapsulates the access data packet.
  • the decapsulated access packet is sent to the virtual machine deployed in the private cloud.
  • Step 606 The virtual machine deployed in the private cloud receives the access data packet sent by the first VXLAN GW.
  • the process of deploying a virtual machine deployed in a public cloud to a virtual machine deployed in a public cloud is as shown in Figure 8 below.
  • the virtual machine deployed in the public cloud is referred to as the first virtual machine deployed in the public cloud
  • the accessed virtual machine deployed in the public cloud is referred to as the second virtual deployed in the public cloud.
  • Machine including:
  • Step 701 The first virtual machine deployed in the public cloud sends an access data packet to the HyperNode, where the source IP address of the access data packet is the first IP address of the first virtual machine deployed in the public cloud, and the source MAC address is deployed.
  • the destination IP address is the first IP address of the second virtual machine deployed in the public cloud.
  • the destination MAC address is the MAC address of the second virtual machine deployed in the public cloud. .
  • This step can be implemented by the following steps 7011-7012, including:
  • the first virtual machine deployed in the public cloud sends an access packet to the Router node in the public cloud.
  • the Router node in the public cloud receives the access data packet sent by the first virtual machine deployed in the public cloud, and forwards the access data packet to the HyperNode.
  • Step 702 The HyperNode receives the access data packet sent by the first virtual machine deployed in the public cloud, and modifies the source IP address of the access data packet to the second IP address of the first virtual machine deployed in the public cloud.
  • the destination IP address of the access packet is modified to the second IP address of the second virtual machine deployed in the public cloud.
  • the HyperNode obtains the deployment from the correspondence between the first IP address and the second IP address according to the first IP address of the first virtual machine deployed in the public cloud and the first IP address of the second virtual machine deployed in the public cloud.
  • the second IP address of the first virtual machine in the public cloud and the second IP address of the second virtual machine deployed in the public cloud, the source IP address of the access data packet is modified to be the first deployed in the public cloud.
  • the second IP address of the virtual machine, the destination IP address of the access packet is modified to a second IP address of the second virtual machine deployed in the public cloud.
  • Step 703 The HyperNode sends the access data packet to a second virtual machine deployed in the public cloud.
  • the HyperNode sends the access data packet to the Router node, and the Router node receives the access data packet sent by the HyperNode, and deploys the second virtual machine in the public cloud according to the second IP address of the second virtual machine deployed in the public cloud. Forward the access packet.
  • Step 704 The second virtual machine deployed in the public cloud receives the access data packet sent by the HyperNode.
  • the source IP address or the destination IP address of the access data packet is modified by the HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that the virtual machine in the hybrid cloud does not need to be configured. Network interoperability can be achieved.
  • the migration process includes:
  • Step 801 The private cloud virtual machine sends a third allocation request to the second DHCP server, where the third allocation request carries the MAC address of the virtual machine deployed in the private cloud.
  • the hybrid cloud management system migrates the virtual machine deployed in the private cloud from the private cloud to the private cloud, the private cloud virtual machine needs to request the IP address in the public cloud from the second DHCP server in the public cloud.
  • Step 802 The second DHCP server receives the third allocation request sent by the virtual machine deployed in the private cloud, and obtains the first virtual machine deployed in the private cloud according to the MAC address of the virtual machine deployed in the private cloud. IP address.
  • the IP address assigned by the second DHCP server to the virtual machine deployed in the private cloud is referred to as the first IP address
  • the IP address assigned by the first DHCP server to the virtual machine deployed in the private cloud is called Is the second IP address.
  • Step 803 The second DHCP server sends the first IP address of the virtual machine deployed in the private cloud to the virtual machine deployed in the private cloud.
  • Step 804 The virtual machine deployed in the private cloud receives the first IP address of the virtual machine deployed in the private cloud sent by the second DHCP server.
  • Step 805 The second Cloud GW acquires the first IP address of the virtual machine deployed in the private cloud from the virtual machine deployed in the private cloud.
  • Step 806 The second Cloud GW acquires the second IP address of the virtual machine deployed in the private cloud from the first DHCP server.
  • Step 807 The second Cloud GW sends the first IP address and the second IP address of the virtual machine deployed in the private cloud to the HyperNode.
  • Step 808 The HyperNode receives the first IP address and the second IP address of the virtual machine deployed in the private cloud sent by the second Cloud GW, and establishes a first IP address and a second IP of the virtual machine deployed in the private cloud. The correspondence of addresses.
  • the IP address masquerading is implemented by the HyperNode
  • the new ARP Proxy is configured in the HyperNode
  • the MAC address masquerading is implemented by the ARP Proxy, so that the IP address and the MAC address of the virtual machine remain unchanged, and no network configuration is required. Changes can be used to achieve virtual machine migration between clouds.
  • the embodiment of the present disclosure further provides a hybrid cloud management device, which may be implemented by using the computing device shown in FIG. 2, or may be implemented by an application-specific integrated circuit (abbreviation: ASIC), or Programmable logic device (English full name: programmable logic device, abbreviation: PLD) implementation.
  • the PLD may be a complex programmable logic device (full name: CPLD), an FPGA, a general array logic (general array logic, abbreviation: GAL), or any combination thereof.
  • the hybrid cloud management device is used in the above hybrid cloud management method.
  • the hybrid cloud management device may also be a software module.
  • the schematic diagram of the group leader structure of the data clustering apparatus includes: a first receiving module 901, a first management module 902, and a second management module 903.
  • the receiving process in the hybrid cloud management method described above is executed.
  • the apparatus further includes a second receiving module and a first establishing module.
  • the first IP address and the second IP address of the virtual machine deployed in the public cloud sent by the second Cloud GW in the receiving public cloud are executed in the hybrid cloud management method.
  • the correspondence between the first IP address and the second IP address of the virtual machine deployed in the public cloud is implemented in the hybrid cloud management method.
  • the apparatus further includes: a first acquiring module, a determining module, and a second establishing module.
  • the acquisition processing in the hybrid cloud management method described above is performed.
  • the device further includes: a third receiving module, a second acquiring module, and a first sending module.
  • the receiving process in the hybrid cloud management method described above is performed.
  • the acquisition processing in the hybrid cloud management method described above is performed.
  • the transmitting process in the hybrid cloud management method described above is executed.
  • the source IP address or the destination IP address of the access data packet is modified by the HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that the virtual machine in the hybrid cloud does not need to be configured. Network interoperability can be achieved.
  • the embodiment of the present disclosure further provides a hybrid cloud management device, which may be implemented by using the computing device shown in FIG. 2, and may also be implemented by an ASIC or a PLD.
  • the above PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.
  • the hybrid cloud management device is used in the above hybrid cloud management method.
  • the hybrid cloud management device may also be a software module.
  • the schematic diagram of the group length structure of the data clustering apparatus includes a fourth receiving module 1001, an allocating module 1002, and a second sending module 1003.
  • the processing of receiving the allocation request sent by the virtual machine in the hybrid cloud management method described above is performed.
  • the source IP address or the destination IP address of the access data packet is modified by the HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that the virtual machine in the hybrid cloud does not need to be configured. Network interoperability can be achieved.
  • the embodiment of the present disclosure further provides a computing device, which is shown in FIG. 2, and includes a first communication interface, a first processor, and a first memory, where the first communication interface is respectively associated with the first processor and the first
  • the memory establishes a communication connection
  • the first processor establishes a communication connection with the first memory
  • the first memory is configured to store the program code.
  • the first processor executes the program code stored in the first memory to execute the hybrid cloud management method described above.
  • the computing device is also the computing device running the aforementioned HyperNode.
  • the source IP address or the destination IP address of the access data packet is modified by the HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that the virtual machine in the hybrid cloud does not need to be configured. Network interoperability can be achieved.
  • the embodiment of the present disclosure further provides a computing device, which is shown in FIG. 2, and includes a second communication interface, a second processor, and a second memory.
  • the second communication interface is respectively associated with the second processor and the second
  • the memory establishes a communication connection
  • the second processor establishes a communication connection with the second memory
  • the second memory is used to store the program code.
  • the second processor executes the program code stored in the second memory to execute the hybrid cloud management method described above.
  • the computing device is also the computing device running the aforementioned management module.
  • the source IP address or the destination IP address of the access data packet is modified by the HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that the virtual machine in the hybrid cloud does not need to be configured. Network interoperability can be achieved.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

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

本公开提供了一种混合云管理方法、装置和计算设备，属于云计算技术领域。方法包括：接收访问数据包，如果被访问虚拟机为部署在公有云中的虚拟机，根据访问数据包携带的部署在公有云中的虚拟机在公有云中的第一网络之间互连的协议IP地址，获取部署在公有云中的虚拟机在私有云中的第二IP地址，将访问数据包的目的IP地址修改为部署在公有云中的虚拟机的第二IP地址；如果访问虚拟机为部署在公有云中的虚拟机，根据访问数据包携带的部署在公有云中的虚拟机的第二IP地址，获取部署在公有云中的虚拟机的第一IP地址，将访问数据包的源IP地址修改为部署在公有云中的虚拟机的第一IP地址；向被访问虚拟机发送访问数据包。本公开实现网络互通。

Description

混合云管理方法、装置和计算设备 技术领域
本公开涉及云计算技术领域，特别涉及一种混合云管理方法、装置和计算设备。
背景技术
随着云计算技术的发展，混合云的发展得到了越来越多的关注，混合云融合了公有云和私有云，是近年来云计算的主要模式和发展方向。混合云要能够面向同一企业租户的应用在私有云和公有云之间灵活策略部署与调度。私有云的应用产生爆炸性资源需求，私有云的资源不足时，弹性伸缩到公有云临时租借资源。公有云作为私有云的容灾备份点等等这些应用场景也对混合云提出了新的挑战。因此，数据中心要能够高速互联，需要能够统一管理公有云上的网络和私有云上的网络，实现网络互通。
私有云中运行有第一虚拟机，公有云中运行有第二虚拟机；为了实现私有云的网络和公有云的网络互通，在第一虚拟机上部署第一代理设备，在第二虚拟机上部署第二代理设备。在第一虚拟机访问第二虚拟机时，第一虚拟机向第一代理设备发送访问请求，该访问请求携带第二虚拟机的IP地址；第一代理设备向第二代理设备转发该访问请求；第二代理设备向第二虚拟机转发该访问请求，以实现第一虚拟机访问第二虚拟机。
在实现本公开的过程中，发明人发现现有技术至少存在以下问题：
上述方法中，需要对混合云中的虚拟机进行配置，导致上述方法的通用性差。
发明内容
为了解决现有技术的问题，本公开实施例提供了一种混合云管理方法、装置和计算设备。所述技术方案如下：
第一方面，本公开实施例提供了一种混合云管理方法，所述方法应用在混合云管理系统中的超节点HyperNode中，所述方法包括：
接收访问虚拟机发送的访问数据包，所述访问数据包用于访问被访问虚拟机；
如果所述被访问虚拟机为部署在公有云中的虚拟机，根据所述访问数据包携带的所述部署在公有云中的虚拟机在所述公有云中的第一网络之间互连的协议IP地址，获取所述部署在公有云中的虚拟机在私有云中的第二IP地址，将所述访问数据包的目的IP地址修改为所述部署在公有云中的虚拟机的第二IP地址，向所述被访问虚拟机发送所述访问数据包；
如果所述访问虚拟机为所述部署在公有云中的虚拟机，根据所述访问数据包携带的所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的第一IP地址，将所述访问数据包的源IP地址修改为所述部署在公有云中的虚拟机的第一IP地址，向所述被访问虚拟机发送所述访问数据包。
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟 机进行配置，即可实现网络互通。
在一个可能的设计中，所述根据所述访问数据包携带的所述部署在公有云中的虚拟机在所述公有云中的第一网络之间互连的协议IP地址，获取所述部署在公有云中的虚拟机在私有云中的第二IP地址，包括：
根据所述部署在公有云中的虚拟机的第一IP地址，从第一IP地址和第二IP地址的对应关系中获取所述部署在公有云中的虚拟机的第二IP地址；
相应的，所述根据所述访问数据包携带的所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的第一IP地址，包括：
根据所述部署在公有云中的虚拟机的第二IP地址，从第一IP地址和第二IP地址的对应关系中获取所述部署在公有云中的虚拟机的第一IP地址。
在本公开实施例中，HyperNode存储第一IP地址和第二IP地址的对应关系，因此，在获取部署在公有云中的虚拟机的第二IP地址时，根据部署在公有云中的虚拟机的第一IP地址，从第一IP地址和第二IP地址的对应关系中获取部署在公有云中的虚拟机的第二IP地址，获取部署在公有云中的虚拟机的第一IP地址时，根据部署在公有云中的虚拟机的的第二IP地址，从第一IP地址和第二IP地址的对应关系中获取部署在公有云中的虚拟机的第二IP地址，从而提高了获取IP地址的准确性。
在一个可能的设计中，所述接收访问虚拟机发送的访问数据包之前，所述方法还包括：
接收所述公有云中的第二云网关Cloud GW发送的所述部署在公有云中的虚拟机的第一IP地址和第二IP地址，所述部署在公有云中的虚拟机的第一IP地址为所述第二Cloud GW从所述部署在公有云中的虚拟机中获取的，所述部署在公有云中的虚拟机的第二IP地址为所述第二Cloud GW从所述混合云管理系统中的管理模块中获取的；
建立所述部署在公有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
在本公开实施例中，HyperNode建立部署在公有云中的虚拟机的第一IP地址和第二IP地址的对应关系，以便于后续根据部署在公有云中的虚拟机的第一IP地址或第二IP地址，从第一IP地址和第二IP地址的对应关系中获取部署在公有云中的虚拟机的第二IP地址或第一IP地址。
在一个可能的设计中，所述方法还包括：
如果将所述混合云管理系统中的部署在私有云中的虚拟机迁移到所述公有云中，获取所述部署在私有云中的虚拟机在所述公有云中的第一IP地址；
确定所述部署在私有云中的虚拟机在所述私有云中的第二IP地址；
建立所述部署在私有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
在本公开实施例中，通过HyperNode实现IP地址伪装，在HyperNode配置新的ARP Proxy，通过ARP Proxy实现MAC地址伪装，从而实现虚拟机的IP地址和MAC地址保持不变，不需要做任何网络配置改动，即可实现云间虚拟机迁移。
在一个可能的设计中，如果所述访问虚拟机为部署在私有云中的虚拟机，所述被访问虚拟机为部署在公有云中的虚拟机，所述访问数据包还携带所述部署在公有云中的虚拟机的媒体控制访问MAC地址，所述接收访问虚拟机发送的访问数据包之前，所述方法还包括：
接收所述部署在私有云中的虚拟机发送的地址解析协议ARP请求，所述ARP请求携带所述部署在公有云中的虚拟机的第二IP地址；
根据所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的MAC地址；
向所述部署在私有云中的虚拟机发送所述部署在公有云中的虚拟机的MAC地址。
在本公开实施例中，Hypernode中存储部署在公有云中的虚拟机的MAC地址和第二IP地址的对应关系，因此，Hypernode可以根据部署在公有云中的虚拟机的第二IP地址，获取部署在公有云中的虚拟机的MAC地址。
第二方面，本公开实施例提供了一种混合云管理方法，所述方法应用在混合云管理系统中的管理模块，所述方法包括：
接收所述混合云管理系统中的虚拟机发送的分配请求，所述分配请求携带所述虚拟机的媒体访问控制MAC地址；
根据所述虚拟机的MAC地址，为所述虚拟机分配在私有云中的第二网络之间互联的协议IP地址；
向所述虚拟机发送所述虚拟机的第二IP地址。
在本公开实施例中，管理模块为混合云管理系统中的虚拟机分配第二IP地址，从而不需要对混合云中的虚拟机进行配置，即可实现网络互通。
在一个可能的设计中，所述根据所述虚拟机的MAC地址，为所述虚拟机分配在私有云中的第二网络之间互联的协议IP地址，包括：
根据所述虚拟机的MAC地址，从MAC地址和IP地址的对应关系中确定为所述虚拟机分配在所述私有云中的第二IP地址。
第三方面，本公开实施例提供了一种混合云管理装置，所述装置应用在混合云管理系统中的超节点HyperNode中，且所述装置包括了用于执行第一方面提供的混合云管理方法的至少一个模块。
第四方面，本公开实施例提供了一种混合云管理装置，所述装置应用在混合云管理系统中的管理模块中，且所述装置包括了用于执行第二方面提供的混合云管理方法的至少一个模块。
第五方面，本公开实施例提供了一种计算设备，所述计算设备包括第一通信接口、第一处理器和第一存储器，所述第一通信接口分别与所述第一处理器和所述第一存储器建立通信连接，所述第一处理器与所述第一存储器建立通信连接，所述第一存储器用于存储程序代码；所述第一通信接口和所述第一处理器用于执行第一方面提供的混合云管理方法。
第六方面，本公开实施例提供了一种计算设备，所述计算设备包括第二通信接口、第二处理器和第二存储器，所述第二通信接口分别与所述第二处理器和所述第二存储器建立通信连接，所述第二处理器与所述第二存储器建立通信连接，所述第二存储器用于存储程序代码；所述第二通信接口和所述第二处理器用于执行第二方面提供的混合云管理方法。
本公开实施例提供的技术方案带来的有益效果包括：
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址 进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟机进行配置，即可实现网络互通。
附图说明
图1-1是本公开实施例提供的混合云管理系统的示意图；
图1-2是本公开实施例提供的混合云管理系统的示意图；
图1-3是本公开实施例提供的混合云管理系统的示意图；
图1-4是本公开实施例提供的混合云管理系统的示意图；
图2是本公开实施例提供的计算设备的结构示意图；
图3是本公开实施例提供的混合云管理方法流程图；
图4是本公开实施例提供的混合云管理方法流程图；
图5是本公开实施例提供的混合云管理方法流程图；
图6是本公开实施例提供的混合云管理方法流程图；
图7是本公开实施例提供的混合云管理方法流程图；
图8是本公开实施例提供的混合云管理方法流程图；
图9是本公开实施例提供的混合云管理方法流程图；
图10是本公开实施例提供的混合云管理装置的结构示意图；
图11是本公开实施例提供的混合云管理装置的结构示意图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开实施方式作进一步地详细描述。
上述所有可选技术方案，可以采用任意结合形成本公开的可选实施例，在此不再一一赘述。
贯穿本说明书，流表用于在软件定义网络中控制数据流，在本申请实施例中采用符合软件定义网络(英文全称：openflow)协议的流表作为示例，实际使用中也可以采用符合其他协议的流表。
贯穿本说明书，常见的虚拟交换机(英文全称：virtual switch，缩写：VS)包括开放虚拟化软件交换机(英文全称：Open vSwitch，缩写：OVS)，OVS为一个开源项目提供的虚拟交换机。
本说明书中，数据包在公有云和私有云之间传输的过程中采用了overlay封装技术，具体可以采用以下之任一：虚拟可扩展局域网(英文全称：virtual extensible local area network，缩写：VXLAN)技术，使用通用路由的网络虚拟化(英文全称：network virtualization using generic routing encapsulation，缩写：NVGRE)技术和无状态传输隧道(英文全称：stateless transport tunneling，缩写：STT)技术。示例性的说明书中，采用了VXLAN技术。
本说明书中提供了一种混合云管理系统，参见图1-1，该系统包括：管理模块、第一云网关(英文全称：Cloud Gateway，缩写：Cloud GW)、第二Cloud GW、第一虚拟可扩展局域网(英文全称：Virtual Extensible LAN，缩写：VXLAN)GW、第二 VXLAN GW和超节点(英文全称：HyperNode)。其中，管理模块包括资源管理模块和网络服务模块，网络服务模块包括第一动态主机配置协议(英文全称：Dynamic Host Configuration Protocol，缩写：DHCP)服务器。
本说明书中的管理模块、第一Cloud GW、第二Cloud GW、第一VXLAN GW、第二VXLAN GW、HyperNode，以及部署于公有云和部署于私有云的各个虚拟机均运行于计算设备上。每个计算设备的结构示意图如图2。每个计算设备实际可以为服务器。
每个计算设备可以包括通信接口110、处理器120和存储器130，通信接口110分别与处理器120和存储器130建立通信连接，处理器120和存储器130建立通信连接。
存储器130可以包括易失性存储器(英文全称：volatile memory)，例如随机存取存储器(英文全称：random-access memory，缩写：RAM)；存储器也可以包括非易失性存储器(英文全称：non-volatile memory)，例如只读存储器(英文全称：read-only memory，缩写：ROM)，快闪存储器(英文全称：flash memory)，硬盘(英文全称：hard disk drive，缩写：HDD)或固态硬盘(英文全称：solid state drive，缩写：SSD)；存储器130还可以包括上述种类的存储器的组合。在通过软件来实现本申请提供的技术方案时，用于实现本公开提供的混合云管理方法的程序代码保存在存储器130中，并由处理器120来执行。
每个计算设备通过通信接口110与混合云管理系统中的各模块通信。
处理器120可以为中央处理器(英文全称：central processing unit，缩写：CPU)。
由于无论是管理模块、第一Cloud GW、第二Cloud GW、第一VXLAN GW、第二VXLAN GW、HyperNode实际都可以由运行于虚拟机上的软件实现，而虚拟机的部署较为灵活。因此，管理模块、第一Cloud GW、第二Cloud GW、第一VXLAN GW、第二VXLAN GW、HyperNode，以及部署于公有云和部署于私有云的各个虚拟机在实际的部署中，也可以合并部署。例如，第一VXLAN GW也可以部署在已经部署了虚拟机的私有云的计算设备上，第二VXLAN GW也可以部署在已经部署了虚拟机的公有云的计算设备上，HyperNode和第二VXLAN GW可以部署于同一公有云的计算设备上等。第一Cloud GW和第一VXLAN GW分别为私有云对应的Cloud GW和VXLAN GW，第二Cloud GW和第二VXLAN GW分别为公有云对应的Cloud GW和VXLAN GW。
管理模块分别与第一Cloud GW、第二Cloud GW、第一VXLAN GW和第二VXLAN GW连接。第一Cloud GW分别与部署在私有云中的虚拟机所在的主机和第一VXLAN GW相连，第二Cloud GW分别与第二VXLAN GW和HyperNode相连。第一VXLAN GW分别与部署在私有云中的虚拟机所在的主机与第二VXLAN GW连接，第二VXLAN GW与HyperNode相连。
资源管理模块，用于为用户提供混合云服务，该混合云服务可以为计算资源管理(例如，创建虚拟机)、存储资源管理(例如，创建卷)、网络资源管理(例如，创建子网)。
网络服务模块，用于根据资源管理模块的需求，创建需要的网络服务，例如DHCP服务等。
第一Cloud GW，用于为提供服务访问接口操作云中的资源，为私有云提供一套统 一接口供混合云系统使用；并根据混合云管理系统需求对私有云进行网络配置，例如，对第一VXLAN GW进行网络配置(如生成流表下发给第一VXLAN GW)。
第二Cloud GW，用于为提供服务访问接口操作云中的资源，为公有云提供一套统一接口供混合云系统使用；并根据混合云管理系统需求对公有云进行网络配置，例如，对第二VXLAN GW进行网络配置(如生成流表下发给第二VXLAN GW)。
该HyperNode，用于截获部署在公有云中的虚拟机的数据包，通过公有云中的第二DHCP服务器为部署在公有云中的虚拟机分配的第一IP地址同第一DHCP服务器为该部署在公有云中的虚拟机分配的第二IP地址进行互相转换，从而实现部署在公有云中的虚拟机以第二IP地址互相访问。
第一VXLAN GW，用于与第二VXLAN GW进行通信，实现公有云和私有云之间的互通。
第二VXLAN GW，用于与第一VXLAN GW进行通信，实现公有云和私有云之间的互通。
部署在私有云中的虚拟机所在的主机还可以包括代理(英文全称：Agent)，该Agent，用于配合混合云管理系统完成主机的配置。
公有云中还包括路由器(英文全称：Router)，该Router用于为HyperNode和部署在公有云中的虚拟机进行数据转发。
需要说明的是，HyperNode可以运行在公有云中的一台虚拟机上。第一Cloud GW可以部署在私有云内部，也可以部署在私有云外部；第二Cloud GW可以部署在公有云内部，也可以部署在公有云外部。本公开实施例中，对第一Cloud GW和第二Cloud GW的部署位置不作具体限定，只要能保证网络互通即可。本公开实施例所述的连接包括有线连接或者无线连接。
在图1-1中是以第一Cloud GW部署在私有云外部，第二Cloud GW部署在公有云外部为例进行说明。参见图1-2，第一Cloud GW部署在私有云内部，第二Cloud GW部署在公有云内部。参见图1-3，第一Cloud GW部署在私有云外部，第二Cloud GW部署在公有云内部。参见图1-4，第一Cloud GW部署在私有云内部，第二Cloud GW部署在公有云外部。例如，第一Cloud GW部署在私有云外部的计算设备上，第二Cloud GW部署在私有云外部的计算设备上。
需要说明的是，在通过本公开实施例提供的混合云管理系统管理部署在公有云中的虚拟机和部署在私有云中的虚拟机时，需要按照以上连接关系对第一VXLAN GW、第二VXLAN GW、第一Cloud GW、第二Cloud GW、HyperNode进行部署，并配置管理面数据和数据面的网络互通；以及，配置第二Cloud GW创建部署在公有云中的虚拟机时使用的账号信息和网络信息。在第二Cloud GW种配置路由规则，使得第二Cloud GW创建的部署在公有云中的虚拟机的网络默认下一跳为HyperNode。
需要说明的是，图1-1至1-4中的虚线表示两个网元之间传输控制面数据流，实线表示两个网元之间传输业务面数据流。
在对混合云进行管理时，首先需要在混合云管理系统中创建网络，后续私有云中的虚拟机和公有云中的虚拟机都可以挂机到这个网络中。参见图3，创建网络的过程 包括：
步骤201：网络服务模块获取待创建的网络的子网信息。
在创建网络时，用户可以向网络服务模块输入子网信息；网络服务模块接收用户输入的子网信息。其中，子网信息可以为子网段的网络之间互连的协议(英文全称：Internet Protocol，缩写：IP)地址，例如，子网段的IP地址可以为192.168.0.0/24。
步骤202：网络服务模块根据该子网信息创建网络。
网络服务模块根据该子网信息，创建VXLAN网络，混合云管理系统中的虚拟机挂接到该VXLAN网络中。
步骤203：网络服务模块为该网络配置第一DHCP服务器。
第一DHCP服务器用于为接入该VXLAN网络中的虚拟机分配IP地址。
步骤204：网络服务模块向接入该网络中的虚拟机发送第一DHCP服务器的标识。
网络服务模块中存储有接入该网络中的虚拟机的媒体接入控制(英文全称：Media Access Control，缩写：MAC)地址，根据接入该网络中的虚拟机的MAC地址，向接入该网络中的虚拟机发送第一DHCP服务器的标识。接入该网络中的虚拟机接收网络服务模块发送的第一DHCP服务器的标识。其中，第一DHCP服务器的服务器标识可以为第一DHCP服务器的IP地址或者MAC地址等，在本公开实施例中，对第一DHCP服务器的服务器标识不作具体限定。
部署在私有云中的虚拟机和部署在公有云中的虚拟机接入该网络后，第一DHCP服务器为部署在私有云中的虚拟机和部署在公有云中的虚拟机分配IP地址。如图4所示，第一DHCP服务器为部署在私有云中的虚拟机分配IP地址的过程，包括：
步骤301：私有云中的部署在私有云中的虚拟机向第一DHCP服务器发送第一分配请求，第一分配请求携带该部署在私有云中的虚拟机的MAC地址。
私有云中的部署在私有云中的虚拟机在步骤202中已经获取到第一DHCP服务器的服务器标识，部署在私有云中的虚拟机向第一Cloud GW发送第一分配请求，第一分配请求携带该部署在私有云中的虚拟机的MAC地址和第一DHCP服务器的服务器标识；第一Cloud GW接收部署在私有云中的虚拟机发送的第一分配请求，根据第一DHCP服务器的服务器标识，向第一DHCP服务器转发第一分配请求。
其中，该部署在私有云中的虚拟机所在的主机与网络服务模块之间建立网络连接，该部署在私有云中的虚拟机根据第一DHCP服务器的服务器标识，通过该网络连接，向第一DHCP服务器发送第一分配请求。
步骤302：第一DHCP服务器接收该部署在私有云中的虚拟机发送的第一分配请求，根据该部署在私有云中的虚拟机的MAC地址，获取该部署在私有云中的虚拟机的IP地址。
第一DHCP服务器中配置了MAC地址和IP地址的对应关系；相应的，第一DHCP服务器根据该部署在私有云中的虚拟机的MAC地址，获取该部署在私有云中的虚拟机的IP地址的步骤可以为：
第一DHCP服务器根据该部署在私有云中的虚拟机的MAC地址，从MAC地址和IP地址的对应关系中获取该部署在私有云中的虚拟机的IP地址。
例如，第一DHCP服务器中存储的MAC地址和IP地址的对应关系如下表1所示：
表1
MAC地址 IP地址
MAC1 192.168.0.3
MAC2 192.168.0.4
MAC3 192.168.0.5
MAC4 192.168.0.6
例如，部署在私有云中的虚拟机VM1的MAC地址为MAC1，则第一DHCP服务器根据MAC1从表1中获取VM1的IP地址为192.168.0.3；再如，部署在私有云中的虚拟机VM2的MAC地址为MAC2，则第一DHCP服务器根据MAC2从表1中获取VM2的IP地址为192.168.0.4。
步骤303：第一DHCP服务器向该部署在私有云中的虚拟机发送该IP地址。
第一DHCP服务器向第一Cloud GW发送第一分配响应，第一分配响应携带该部署在私有云中的虚拟机的MAC地址；第一Cloud GW接收第一DHCP服务器发送的第一分配响应，根据该部署在私有云中的虚拟机的MAC地址，向该部署在私有云中的虚拟机转发该IP地址。
步骤304：部署在私有云中的虚拟机接收第一DHCP服务器发送的该IP地址。
在本公开实施例中，混合云管理系统中的第一DHCP服务器会为部署在公有云中的虚拟机分配IP地址，公有云中的第二DHCP服务器也会为部署在公有云中的虚拟机分配IP地址；为了便于区分，将第二DHCP服务器为部署在公有云中的虚拟机分配的IP地址称为第一IP地址，将第一DHCP服务器为部署在公有云中的虚拟机分配的IP地址称为第二IP地址，则第一DHCP和第二DHCP服务器为部署在公有云中的虚拟机分配IP地址的过程如图5所示，包括：
步骤401：公有云中的部署在公有云中的虚拟机向公有云中的第二DHCP服务器发送第二分配请求，第二分配请求携带该部署在公有云中的虚拟机的MAC地址。
公有云中的部署在公有云中的虚拟机启动后，获取公有云中的第二DHCP服务器的服务器标识，向第二Cloud GW发送第二分配请求，第二分配请求携带该部署在公有云中的虚拟机的MAC地址和第二DHCP服务器的服务器标识；第二Cloud GW接收部署在公有云中的虚拟机发送的第二分配请求，根据第二DHCP服务器的服务器标识，向第二DHCP服务器转发第二分配请求。
需要说明的是，在本步骤之前，用户在混合云管理系统中创建部署在公有云中的虚拟机时，管理模块向第二Cloud GW发送建立请求，该建立请求携带该部署在公有云中的虚拟机的设备标识；第二Cloud GW接收管理模块发送的建立请求，根据配置信息，调用公有云的接口创建部署在公有云中的虚拟机。其中，该配置信息包括账户信息和网络标识。
步骤402：第二DHCP服务器接收该部署在公有云中的虚拟机发送的第二分配请求，根据该部署在公有云中的虚拟机的MAC地址，获取该部署在公有云中的虚拟机的第一 IP地址。
第二DHCP服务器中配置了MAC地址和IP地址的对应关系；相应的，第二DHCP服务器根据该部署在公有云中的虚拟机的MAC地址，获取该部署在公有云中的虚拟机的第一IP地址的步骤可以为：
第二DHCP服务器根据该部署在公有云中的虚拟机的MAC地址，从MAC地址和IP地址的对应关系中获取该部署在公有云中的虚拟机的第一IP地址。
例如，第二DHCP服务器中存储的MAC地址和IP地址的对应关系如下表2所示：
表2
MAC地址 IP地址
MAC3 172.16.0.101
MAC4 172.16.0.102
例如，部署在公有云中的虚拟机VM3的MAC地址为MAC3，则第二DHCP服务器根据MAC3从表2中获取VM3的第一IP地址为172.16.0.101；再如，部署在公有云中的虚拟机VM4的MAC地址为MAC4，则第二DHCP服务器根据MAC4从表2中获取VM4的第一IP地址为172.16.0.102。
步骤403：第二DHCP服务器向该部署在公有云中的虚拟机发送第一IP地址。
第二DHCP服务器向第二Cloud GW发送第二分配响应，第二分配响应携带该部署在公有云中的虚拟机的MAC地址；第二Cloud GW接收第二DHCP服务器发送的第二分配响应，根据该公有
步骤404：部署在公有云中的虚拟机接收第二DHCP服务器发送的第一IP地址。
步骤405：公有云中的第二Cloud GW从部署在公有云中的虚拟机中获取部署在公有云中的虚拟机的第一IP地址。
步骤406：第二Cloud GW从第一DHCP服务器中获取部署在公有云中的虚拟机的第二IP地址。
第二Cloud GW向第一DHCP服务器发送查询请求，该查询请求携带部署在公有云中的虚拟机的MAC地址；第一DHCP服务器接收第二Cloud GW发送的查询请求，根据该部署在公有云中的虚拟机的MAC地址，获取该部署在公有云中的虚拟机的第二IP地址，向第二Cloud GW发送部署在公有云中的虚拟机的第二IP地址。
第一DHCP服务器根据该部署在公有云中的虚拟机的MAC地址，获取该部署在公有云中的虚拟机的第二IP地址的步骤可以为：
第一DHCP服务器根据该部署在公有云中的虚拟机的MAC地址，从MAC地址和IP地址的对应关系中获取该部署在公有云中的虚拟机的第二IP地址。
例如，部署在公有云中的虚拟机VM3的MAC地址为MAC3，则第一DHCP服务器根据MAC3从表1中获取VM3的第二IP地址为192.168.0.5；再如，部署在公有云中的虚拟机VM4的MAC地址为MAC4，则第一DHCP服务器根据MAC4从表1中获取VM4的第二IP地址为192.168.0.6。
步骤407：第二Cloud GW向HyperNode发送该部署在公有云中的虚拟机的第一IP地址和第二IP地址。
步骤408：HyperNode接收第二Cloud GW发送的该部署在公有云中的虚拟机的第一IP地址和第二IP地址，建立该部署在公有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
在HyperNode中增加流表；HyperNode将该部署在公有云中的虚拟机的第一IP地址和第二IP地址的对应关系配置到该流表。在HyperNode中增加地址解析协议(英文全称：Address Resolution Protocol，缩写：ARP)代理服务器(英文全称：Proxy)；ARP Proxy用于修改该部署在公有云中的虚拟机发送的数据包的IP地址以及修改向该部署在公有云中的虚拟机发送的数据包的IP地址。
例如，如果HyperNode接收到第二VXLAN GW发送的数据包，该数据包的目的IP地址为第二IP地址，则HyperNode根据该部署在公有云中的虚拟机的第二IP地址，获取该部署在公有云中的虚拟机的第一IP地址，将该数据包的目的地址修改为该部署在公有云中的虚拟机的第一IP地址。
再如，如果该部署在公有云中的虚拟机向该混合云管理系统中的其他虚拟机发送数据包时，该HyperNode将该数据包的源IP地址修改为该部署在公有云中的虚拟机的第一IP地址。
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟机进行配置，即可实现网络互通。
在混合云管理系统中，虚拟机之间可以进行互相访问，也即部署在私有云中的虚拟机可以访问部署在公有云中的虚拟机，部署在公有云中的虚拟机可以访问部署在私有云中的虚拟机，部署在公有云中的虚拟机也可以访问部署在公有云中的虚拟机。其中，部署在私有云中的虚拟机访问部署在公有云中的虚拟机的过程如下图6所示，包括：
步骤501：部署在私有云中的虚拟机向HyperNode发送ARP请求，该ARP请求携带待访问的部署在公有云中的虚拟机的第二IP地址。
由于部署在私有云中的虚拟机访问部署在公有云中的虚拟机时，需要获取部署在公有云中的虚拟机的MAC地址，因此，在部署在私有云中的虚拟机访问部署在公有云中的虚拟机之前，部署在私有云中的虚拟机向HyperNode发送ARP请求，该ARP请求用于获取该部署在公有云中的虚拟机的MAC地址。
本步骤可以通过以下步骤5011-5014实现，包括：
5011：部署在私有云中的虚拟机向部署在私有云中的虚拟机所在的主机的虚拟交换机发送ARP请求，该ARP请求携带待访问的部署在公有云中的虚拟机的第二IP地址。
部署在私有云中的虚拟机获取待访问的部署在公有云中的虚拟机的第二IP地址，根据该部署在私有云中的虚拟机的IP地址和该部署在公有云中的虚拟机的第二IP地址，确定该部署在公有云中的虚拟机和该部署在私有云中的虚拟机在同一个VXLAN网络中，向部署在私有云中的虚拟机所在的主机的虚拟交换机发送ARP请求。
例如，该部署在私有云中的虚拟机的IP地址为192.168.0.3，该部署在公有云中的虚拟机的第二IP地址为192.168.0.5。由于192.168.0.3和192.168.0.5属于同一 网段，因此，该部署在私有云中的虚拟机确定该部署在公有云中的虚拟机和该部署在私有云中的虚拟机在同一个vxlan网络中。
5012：虚拟交换机接收部署在私有云中的虚拟机发送的ARP请求，向第二VXLAN GW发送该ARP请求。
虚拟交换机将该ARP请求封装成VXLAN数据包，向第二VXLAN GW发送该VXLAN数据包。
5013：第二VXLAN GW接收虚拟交换机发送的该ARP请求，向第一VXLAN GW发送该ARP请求。
第二VXLAN GW获取第一VXLAN GW的标识，根据第一VXLAN GW的标识向第一VXLAN GW发送该ARP请求。
第二VXLAN GW中配置有vxlan网络和VXLAN GW的标识的对应关系；相应的，第二VXLAN GW获取第一VXLAN GW的标识的步骤可以为：
第二VXLAN GW根据该部署在公有云中的虚拟机的第二IP地址，确定该部署在公有云中的虚拟机所在的vxlan网络，根据该部署在公有云中的虚拟机所在的vxlan网络，从vxlan网络和VXLAN GW的标识的对应关系中获取第一VXLAN GW的标识。
需要说明的是，第二VXLAN GW先对该vxlan数据包进行重封装，向第一VXLAN GW发送重封装后的该vxlan数据包。
5014：第一VXLAN GW接收第二VXLAN GW发送的该ARP请求，向HyperNode发送该ARP请求。
步骤502：HyperNode接收部署在私有云中的虚拟机发送的该ARP请求，根据该部署在公有云中的虚拟机的第二IP地址，获取该部署在公有云中的虚拟机的MAC地址。
HyperNode中的ARP Proxy中配置有部署在公有云中的虚拟机的MAC地址和第二IP地址的对应关系；相应的，HyperNode根据该部署在公有云中的虚拟机的第二IP地址，获取该部署在公有云中的虚拟机的MAC地址的步骤可以为：
HyperNode向ARP Proxy发送该部署在公有云中的虚拟机的第二IP地址；ARP Proxy接收HyperNode发送的该部署在公有云中的虚拟机的第二IP地址，根据该部署在公有云中的虚拟机的第二IP地址，从MAC地址和第二IP地址的对应关系中获取该部署在公有云中的虚拟机的MAC地址，向HyperNode发送该部署在公有云中的虚拟机的MAC地址；HyperNode接收ARP Proxy发送的该部署在公有云中的虚拟机的MAC地址。
步骤503：HyperNode向部署在私有云中的虚拟机发送该部署在公有云中的虚拟机的MAC地址。
HyperNode会沿着发送ARP请求的请求路径向该部署在私有云中的虚拟机发送该部署在公有云中的虚拟机的MAC地址，过程可以通过以下步骤5031-5034实现，包括：
5031：HyperNode向第一VXLAN GW发送该部署在公有云中的虚拟机的MAC地址。
5032：第一VXLAN GW接收HyperNode发送的该部署在公有云中的虚拟机的MAC地址，向第二VXLAN GW发送该部署在公有云中的虚拟机的MAC地址。
5033：第二VXLAN GW接收第一VXLAN GW发送的该部署在公有云中的虚拟机的MAC地址，向该部署在私有云中的虚拟机所在的主机的虚拟交换机发送该部署在公有云中 的虚拟机的MAC地址。
5034：虚拟交换机接收第二VXLAN GW发送的该部署在公有云中的虚拟机的MAC地址，向该部署在私有云中的虚拟机发送该部署在公有云中的虚拟机的MAC地址。
步骤504：部署在私有云中的虚拟机接收HyperNode发送的该部署在公有云中的虚拟机的MAC地址。
部署在私有云中的虚拟机获取到该部署在公有云中的虚拟机的MAC地址之后，通过以下步骤505向该部署在公有云中的虚拟机发送访问数据包来访问该部署在公有云中的虚拟机。
步骤505：部署在私有云中的虚拟机向HyperNode发送访问数据包，该访问数据包的源IP地址为该部署在私有云中的虚拟机的IP地址，源MAC地址为该部署在私有云中的虚拟机的MAC地址，目的IP为该部署在公有云中的虚拟机的第二IP地址，目的MAC地址为该部署在公有云中的虚拟机的MAC地址。
本步骤可以通过以下步骤5051-5054实现，包括：
5051：部署在私有云中的虚拟机向部署在私有云中的虚拟机所在的主机的虚拟交换机发送访问数据包。
5052：虚拟交换机接收部署在私有云中的虚拟机发送的访问数据包，向第二VXLAN GW发送该访问数据包。
虚拟交换机对该访问数据包进行封装，将该访问数据包封装为VXLAN格式的访问数据包，向第二VXLAN GW发送封装后的该访问数据包。
5053：第二VXLAN GW接收虚拟交换机发送的访问数据包，向第一VXLAN GW发送该访问数据包。
第二VXLAN GW对该访问数据包重新进行封装，向第一VXLAN GW发送封装后的该访问数据包。
5054：第一VXLAN GW接收第二VXLAN GW发送的该访问数据包，向HyperNode发送该访问数据包。
步骤506：HyperNode接收部署在私有云中的虚拟机发送的访问数据包，将该访问数据包的目的IP地址修改为第一IP地址。
HyperNode对该访问数据包进行解封装，得到以太网格式的访问数据包，根据该部署在公有云中的虚拟机的第二IP地址，从第二IP地址和第一IP地址的对应关系中获取该部署在公有云中的虚拟机的第一IP地址，将该访问数据包的目的IP地址修改为该第一IP地址。
步骤507：HyperNode根据第一IP地址，向该部署在公有云中的虚拟机发送该访问数据包。
HyperNode向Router节点发送该访问数据包；Router节点接收HyperNode发送的该访问数据包，根据该访问数据包的目的地址：第一IP地址，向该部署在公有云中的虚拟机发送该访问数据包。
步骤508：该部署在公有云中的虚拟机接收HyperNode发送的该访问数据包。
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟 机进行配置，即可实现网络互通。
部署在公有云中的虚拟机访问部署在私有云中的虚拟机的过程如下图7所示，包括：
步骤601：部署在公有云中的虚拟机向HyperNode发送访问数据包，该访问数据包的源IP为部署在公有云中的虚拟机的第一IP地址，源MAC地址为该部署在公有云中的虚拟机的MAC地址，目的IP地址为待访问的部署在私有云中的虚拟机的IP地址，目的MAC地址为该部署在私有云中的虚拟机的MAC地址。
本步骤可以通过以下步骤6011-6012实现，包括：
6011：部署在公有云中的虚拟机向公有云中的Router节点发送访问数据包。
部署在公有云中的虚拟机获取待访问的部署在私有云中的虚拟机的IP地址，根据该部署在私有云中的虚拟机的IP地址和该部署在公有云中的虚拟机的第一IP地址，确定该部署在公有云中的虚拟机和该部署在私有云中的虚拟机不在同一个vxlan网络中，需要公有云中的Router节点进行转发，则部署在公有云中的虚拟机向公有云中的Router节点发送访问数据包。
6012：Router节点接收部署在公有云中的虚拟机发送的该访问数据包，向HyperNode转发该访问数据包。
Router节点根据路由规则，将该访问数据包转发给HyperNode。其中，该路由规则为该Router节点的下一跳为HyperNode。
步骤602：HyperNode接收部署在公有云中的虚拟机发送的访问数据包，将该访问数据包的源IP地址修改为部署在公有云中的虚拟机的第二IP地址。
HyperNode根据该部署在公有云中的虚拟机的第一IP地址，从第一IP地址和第二IP地址的对应关系中获取该部署在公有云中的虚拟机的第二IP地址，将该访问数据包的源IP地址修改为部署在公有云中的虚拟机的第二IP地址。
步骤603：HyperNode向第二VXLAN GW发送该访问数据包。
步骤604：第二VXLAN GW接收HyperNode发送的该访问数据包，向第一VXLAN GW发送该访问数据包。
第二VXLAN GW将该访问数据包进行封装，向第一VXLAN GW发送封装后的该访问数据包。
步骤605：第一VXLAN GW接收第二VXLAN GW发送的该访问数据包，向该部署在私有云中的虚拟机发送该访问数据包。
第一VXLAN GW将该访问数据包进行封装，向该部署在私有云中的虚拟机发送该访问数据包。
第一VXLAN GW向该部署在私有云中的虚拟机所在的主机的虚拟交换机发送该访问数据包，该虚拟交换机接收第一VXLAN GW发送的该访问数据包，对该访问数据包进行解封装，向该部署在私有云中的虚拟机发送解封装后的该访问数据包。
步骤606：该部署在私有云中的虚拟机接收第一VXLAN GW发送的该访问数据包。
部署在公有云中的虚拟机访问部署在公有云中的虚拟机的过程如下图8所示，为 了便于描述，将访问部署在公有云中的虚拟机称为部署在公有云中的第一虚拟机，将被访问的部署在公有云中的虚拟机称为部署在公有云中的第二虚拟机，包括：
步骤701：部署在公有云中的第一虚拟机向HyperNode发送访问数据包，该访问数据包的源IP地址为部署在公有云中的第一虚拟机的第一IP地址，源MAC地址为部署在公有云中的第一虚拟机的MAC地址，目的IP地址为部署在公有云中的第二虚拟机的第一IP地址，目的MAC地址为部署在公有云中的第二虚拟机的MAC地址。
本步骤可以通过以下步骤7011-7012实现，包括：
7011：部署在公有云中的第一虚拟机向公有云中的Router节点发送访问数据包。
7012：公有云中的Router节点接收部署在公有云中的第一虚拟机发送的该访问数据包，向HyperNode转发该访问数据包。
步骤702：HyperNode接收部署在公有云中的第一虚拟机发送的该访问数据包，将该访问数据包的源IP地址修改为部署在公有云中的第一虚拟机的第二IP地址，将该访问数据包的目的IP地址修改为部署在公有云中的第二虚拟机的第二IP地址。
HyperNode根据部署在公有云中的第一虚拟机的第一IP地址和部署在公有云中的第二虚拟机的第一IP地址，从第一IP地址和第二IP地址的对应关系中获取部署在公有云中的第一虚拟机的第二IP地址和部署在公有云中的第二虚拟机的第二IP地址，将该访问数据包的源IP地址修改为部署在公有云中的第一虚拟机的第二IP地址，将该访问数据包的目的IP地址修改为部署在公有云中的第二虚拟机的第二IP地址。
步骤703：HyperNode向部署在公有云中的第二虚拟机发送该访问数据包。
HyperNode向Router节点发送该访问数据包，该Router节点接收HyperNode发送的该访问数据包，根据部署在公有云中的第二虚拟机的第二IP地址，向部署在公有云中的第二虚拟机转发该访问数据包。
步骤704：部署在公有云中的第二虚拟机接收HyperNode发送的该访问数据包。
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟机进行配置，即可实现网络互通。
在混合云管理系统中，虚拟机可以从私有云迁移到公有云上，并且在迁移时，不需要做任何网络配置的改动，即可保证部署在公有云中的虚拟机的MAC地址和第二第三IP地址保持不变。参见图9，迁移的过程包括：
步骤801：私有云虚拟机向第二DHCP服务器发送第三分配请求，第三分配请求携带该部署在私有云中的虚拟机的MAC地址。
混合云管理系统将部署在私有云中的虚拟机从私有云迁移到私有云中时，私有云虚拟机需要向公有云中的第二DHCP服务器请求公有云中的IP地址。
步骤802：第二DHCP服务器接收部署在私有云中的虚拟机发送的第三分配请求，根据该部署在私有云中的虚拟机的MAC地址，获取该部署在私有云中的虚拟机的第一IP地址。
为了便于区分，将第二DHCP服务器为该部署在私有云中的虚拟机分配的IP地址称为第一IP地址，将第一DHCP服务器为该部署在私有云中的虚拟机分配的IP地址称 为第二IP地址。
步骤803：第二DHCP服务器向该部署在私有云中的虚拟机发送该部署在私有云中的虚拟机的第一IP地址。
步骤804：部署在私有云中的虚拟机接收第二DHCP服务器发送的该部署在私有云中的虚拟机的第一IP地址。
步骤805：第二Cloud GW从该部署在私有云中的虚拟机中获取该部署在私有云中的虚拟机的第一IP地址。
步骤806：第二Cloud GW从第一DHCP服务器中获取该部署在私有云中的虚拟机的第二IP地址。
步骤807：第二Cloud GW向HyperNode发送该部署在私有云中的虚拟机的第一IP地址和第二IP地址。
步骤808：HyperNode接收第二Cloud GW发送的该部署在私有云中的虚拟机的第一IP地址和第二IP地址，建立该部署在私有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
在本公开实施例中，通过HyperNode实现IP地址伪装，在HyperNode配置新的ARP Proxy，通过ARP Proxy实现MAC地址伪装，从而实现虚拟机的IP地址和MAC地址保持不变，不需要做任何网络配置改动，即可实现云间虚拟机迁移。
本公开实施例还提供了一种混合云管理装置，该装置可以通过图2所示的计算设备实现，还可以通过专用集成电路(英文全称：application-specific integrated circuit，缩写：ASIC)实现，或可编程逻辑器件(英文全称：programmable logic device，缩写：PLD)实现。上述PLD可以是复杂可编程逻辑器件(英文全称：complex programmable logic device，缩写：CPLD)，FPGA，通用阵列逻辑(英文全称：generic array logic,缩写：GAL)或其任意组合。该混合云管理装置用于上述混合云管理方法。通过软件实现上述混合云管理方法时，混合云管理装置也可以为软件模块。
数据聚类装置的组长结构示意图如图10所示，包括：第一接收模块901、第一管理模块902和第二管理模块903。
第一接收模块901工作时，执行上述混合云管理方法中的接收处理。
第一管理模块902和第二管理模块903工作时，执行上述混合云管理方法中的管理处理。
另外，该装置还包括第二接收模块和第一建立模块。
第二接收模块工作时，执行上述混合云管理方法中的接收公有云中的第二Cloud GW发送的部署在公有云中的虚拟机的第一IP地址和第二IP地址。
第一建立模块工作时，执行上述混合云管理方法中的建立部署在公有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
另外，该装置还包括：第一获取模块、确定模块和第二建立模块。
第一获取模块工作时，执行上述混合云管理方法中的获取处理。
确定模块在工作时，执行上述混合云管理方法中的确定处理。
第二建立模块在工作时，执行上述混合云管理方法中的建立部署在私有云中的虚 拟机的第一IP地址和第二IP地址的对应关系。
另外，该装置还包括：第三接收模块、第二获取模块和第一发送模块。
第三接收模块在工作时，执行上述混合云管理方法中的接收处理。
第二获取模块在工作时，执行上述混合云管理方法中的获取处理。
第一发送模块在工作时，执行上述混合云管理方法中的发送处理。
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟机进行配置，即可实现网络互通。
本公开实施例还提供了一种混合云管理装置，该装置可以通过图2所示的计算设备实现，还可以通过ASIC实现，或PLD实现。上述PLD可以是CPLD，FPGA，GAL或其任意组合。该混合云管理装置用于上述混合云管理方法。通过软件实现上述混合云管理方法时，混合云管理装置也可以为软件模块。
数据聚类装置的组长结构示意图如图11所示，包括：第四接收模块1001、分配模块1002和第二发送模块1003。
第四接收模块1001在工作时，执行上述混合云管理方法中的接收虚拟机发送的分配请求的处理。
分配模块1002在工作时，执行上述混合云管理方法中的分配IP地址的处理。
第二发送模块1003在工作时，执行上述混合云管理方法中的发送IP地址的处理。
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟机进行配置，即可实现网络互通。
本公开实施例还提供了一种计算设备，其组织结构示意图如图2所示，包括第一通信接口、第一处理器和第一存储器，第一通信接口分别与第一处理器和第一存储器建立通信连接，第一处理器与第一存储器建立通信连接，第一存储器用于存储程序代码。
第一处理器执行第一存储器中存储的程序代码以执行上述混合云管理方法。该计算设备也即运行了前述HyperNode的计算设备。
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟机进行配置，即可实现网络互通。
本公开实施例还提供了一种计算设备，其组织结构示意图如图2所示，包括第二通信接口、第二处理器和第二存储器，第二通信接口分别与第二处理器和第二存储器建立通信连接，第二处理器与第二存储器建立通信连接，第二存储器用于存储程序代码。
第二处理器执行第二存储器中存储的程序代码以执行上述混合云管理方法。该计算设备也即运行了前述管理模块的计算设备。
在本公开实施例中，通过HyperNode对访问数据包的源IP地址或者目的IP地址进行修改，向被访问虚拟机发送修改后的访问数据包，从而不需要对混合云中的虚拟机进行配置，即可实现网络互通。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本公开的较佳实施例，并不用以限制本公开，凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (21)

  1. 一种混合云管理方法，其特征在于，所述方法应用在混合云管理系统中的超节点HyperNode中，所述方法包括：
    接收访问虚拟机发送的访问数据包，所述访问数据包用于访问被访问虚拟机；
    如果所述被访问虚拟机为部署在公有云中的虚拟机，根据所述访问数据包携带的所述部署在公有云中的虚拟机在所述公有云中的第一网络之间互连的协议IP地址，获取所述部署在公有云中的虚拟机在私有云中的第二IP地址，将所述访问数据包的目的IP地址修改为所述部署在公有云中的虚拟机的第二IP地址，向所述被访问虚拟机发送所述访问数据包；
    如果所述访问虚拟机为所述部署在公有云中的虚拟机，根据所述访问数据包携带的所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的第一IP地址，将所述访问数据包的源IP地址修改为所述部署在公有云中的虚拟机的第一IP地址，向所述被访问虚拟机发送所述访问数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述根据所述访问数据包携带的所述部署在公有云中的虚拟机在所述公有云中的第一网络之间互连的协议IP地址，获取所述部署在公有云中的虚拟机在私有云中的第二IP地址，包括：
    根据所述部署在公有云中的虚拟机的第一IP地址，从第一IP地址和第二IP地址的对应关系中获取所述部署在公有云中的虚拟机的第二IP地址；
    相应的，所述根据所述访问数据包携带的所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的第一IP地址，包括：
    根据所述部署在公有云中的虚拟机的第二IP地址，从第一IP地址和第二IP地址的对应关系中获取所述部署在公有云中的虚拟机的第一IP地址。
  3. 根据权利要求1或2所述的方法，其特征在于，所述接收访问虚拟机发送的访问数据包之前，所述方法还包括：
    接收所述公有云中的第二云网关Cloud GW发送的所述部署在公有云中的虚拟机的第一IP地址和第二IP地址，所述部署在公有云中的虚拟机的第一IP地址为所述第二Cloud GW从所述部署在公有云中的虚拟机中获取的，所述部署在公有云中的虚拟机的第二IP地址为所述第二Cloud GW从所述混合云管理系统中的管理模块中获取的；
    建立所述部署在公有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    如果将所述混合云管理系统中的部署在私有云中的虚拟机迁移到所述公有云中，获取所述部署在私有云中的虚拟机在所述公有云中的第一IP地址；
    确定所述部署在私有云中的虚拟机在所述私有云中的第二IP地址；
    建立所述部署在私有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
  5. 根据权利要求1所述的方法，其特征在于，如果所述访问虚拟机为部署在私有云中的虚拟机，所述被访问虚拟机为部署在公有云中的虚拟机，所述访问数据包还携带所述部署在公有云中的虚拟机的媒体控制访问MAC地址，所述接收访问虚拟机发送的访问数据包之前，所述方法还包括：
    接收所述部署在私有云中的虚拟机发送的地址解析协议ARP请求，所述ARP请求携带所述部署在公有云中的虚拟机的第二IP地址；
    根据所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的MAC地址；
    向所述部署在私有云中的虚拟机发送所述部署在公有云中的虚拟机的MAC地址。
  6. 一种混合云管理方法，其特征在于，所述方法应用在混合云管理系统中的管理模块，所述方法包括：
    接收所述混合云管理系统中的虚拟机发送的分配请求，所述分配请求携带所述虚拟机的媒体访问控制MAC地址；
    根据所述虚拟机的MAC地址，为所述虚拟机分配在私有云中的第二网络之间互联的协议IP地址；
    向所述虚拟机发送所述虚拟机的第二IP地址。
  7. 根据权利要求6所述的方法，其特征在于，所述根据所述虚拟机的MAC地址，为所述虚拟机分配在私有云中的第二网络之间互联的协议IP地址，包括：
    根据所述虚拟机的MAC地址，从MAC地址和IP地址的对应关系中确定为所述虚拟机分配在所述私有云中的第二IP地址。
  8. 一种混合云管理装置，其特征在于，所述装置应用在混合云管理系统中的超节点HyperNode中，所述装置包括：
    第一接收模块，用于接收访问虚拟机发送的访问数据包，所述访问数据包用于访问被访问虚拟机；
    第一管理模块，用于如果所述被访问虚拟机为部署在公有云中的虚拟机，根据所述访问数据包携带的所述部署在公有云中的虚拟机在所述公有云中的第一网络之间互连的协议IP地址，获取所述部署在公有云中的虚拟机在私有云中的第二IP地址，将所述访问数据包的目的IP地址修改为所述部署在公有云中的虚拟机的第二IP地址，向所述被访问虚拟机发送所述访问数据包；
    第二管理模块，用于如果所述访问虚拟机为所述部署在公有云中的虚拟机，根据所述访问数据包携带的所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的第一IP地址，将所述访问数据包的源IP地址修改为所述部署在公有云中的虚拟机的第一IP地址，向所述被访问虚拟机发送所述访问数据包。
  9. 根据权利要求8所述的装置，其特征在于，
    所述第一管理模块，还用于根据所述部署在公有云中的虚拟机的第一IP地址，从第一IP地址和第二IP地址的对应关系中获取所述部署在公有云中的虚拟机的第二IP地址；
    所述第二管理模块，还用于根据所述部署在公有云中的虚拟机的第二IP地址，从第一IP地址和第二IP地址的对应关系中获取所述部署在公有云中的虚拟机的第一IP地址。
  10. 根据权利要求8或9所述的装置，其特征在于，所述装置还包括：
    第二接收模块，用于接收所述公有云中的第二云网关Cloud GW发送的所述部署在公有云中的虚拟机的第一IP地址和第二IP地址，所述部署在公有云中的虚拟机的第 一IP地址为所述第二Cloud GW从所述部署在公有云中的虚拟机中获取的，所述部署在公有云中的虚拟机的第二IP地址为所述第二Cloud GW从所述混合云管理系统中的管理模块中获取的；
    第一建立模块，用于建立所述部署在公有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
  11. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    第一获取模块，用于如果将所述混合云管理系统中的部署在私有云中的虚拟机迁移到所述公有云中，获取所述部署在私有云中的虚拟机在所述公有云中的第一IP地址；
    确定模块，用于确定所述部署在私有云中的虚拟机在所述私有云中的第二IP地址；
    第二建立模块，用于建立所述部署在私有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
  12. 根据权利要求8所述的装置，其特征在于，如果所述访问虚拟机为部署在私有云中的虚拟机，所述被访问虚拟机为部署在公有云中的虚拟机，所述访问数据包还携带所述部署在公有云中的虚拟机的媒体控制访问MAC地址，所述装置还包括：
    第三接收模块，用于接收所述部署在私有云中的虚拟机发送的地址解析协议ARP请求，所述ARP请求携带所述部署在公有云中的虚拟机的第二IP地址；
    第二获取模块，用于根据所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的MAC地址；
    第一发送模块，用于向所述部署在私有云中的虚拟机发送所述部署在公有云中的虚拟机的MAC地址。
  13. 一种混合云管理装置，其特征在于，所述装置应用在混合云管理系统中的管理模块，所述装置包括：
    第四接收模块，用于接收所述混合云管理系统中的虚拟机发送的分配请求，所述分配请求携带所述虚拟机的媒体访问控制MAC地址；
    分配模块，用于根据所述虚拟机的MAC地址，为所述虚拟机分配在私有云中的第二网络之间互联的协议IP地址；
    第二发送模块，用于向所述虚拟机发送所述虚拟机的第二IP地址。
  14. 根据权利要求13所述的装置，其特征在于，
    所述分配模块，还用于根据所述虚拟机的MAC地址，从MAC地址和IP地址的对应关系中确定为所述虚拟机分配在所述私有云中的第二IP地址。
  15. 一种计算设备，其特征在于，所述计算设备包括第一通信接口、第一处理器和第一存储器，所述第一通信接口分别与所述第一处理器和所述第一存储器建立通信连接，所述第一处理器与所述第一存储器建立通信连接，所述第一存储器用于存储程序代码；
    所述第一通信接口，用于接收访问虚拟机发送的访问数据包，所述访问数据包用于访问被访问虚拟机；
    所述第一处理器，用于如果所述被访问虚拟机为部署在公有云中的虚拟机，根据所述访问数据包携带的所述部署在公有云中的虚拟机在所述公有云中的第一网络之间互连的协议IP地址，获取所述部署在公有云中的虚拟机在私有云中的第二IP地址， 将所述访问数据包的目的IP地址修改为所述部署在公有云中的虚拟机的第二IP地址，向所述被访问虚拟机发送所述访问数据包；
    所述第一处理器，还用于如果所述访问虚拟机为所述部署在公有云中的虚拟机，根据所述访问数据包携带的所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的第一IP地址，将所述访问数据包的源IP地址修改为所述部署在公有云中的虚拟机的第一IP地址，向所述被访问虚拟机发送所述访问数据包。
  16. 根据权利要求15所述的计算设备，其特征在于，
    所述第一处理器，还用于根据所述部署在公有云中的虚拟机的第一IP地址，从第一IP地址和第二IP地址的对应关系中获取所述部署在公有云中的虚拟机的第二IP地址；
    所述第一处理器，还用于根据所述部署在公有云中的虚拟机的第二IP地址，从第一IP地址和第二IP地址的对应关系中获取所述部署在公有云中的虚拟机的第一IP地址。
  17. 根据权利要求15或16所述的计算设备，其特征在于，
    所述第一通信接口，还用于接收所述公有云中的第二云网关Cloud GW发送的所述部署在公有云中的虚拟机的第一IP地址和第二IP地址，所述部署在公有云中的虚拟机的第一IP地址为所述第二Cloud GW从所述部署在公有云中的虚拟机中获取的，所述部署在公有云中的虚拟机的第二IP地址为所述第二Cloud GW从所述混合云管理系统中的管理模块中获取的；
    所述第一处理器，还用于建立所述部署在公有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
  18. 根据权利要求15所述的计算设备，其特征在于，
    所述第一处理器，还用于如果将所述混合云管理系统中的部署在私有云中的虚拟机迁移到所述公有云中，获取所述部署在私有云中的虚拟机在所述公有云中的第一IP地址；
    所述第一处理器，还用于确定所述部署在私有云中的虚拟机在所述私有云中的第二IP地址；
    所述第一处理器，还用于建立所述部署在私有云中的虚拟机的第一IP地址和第二IP地址的对应关系。
  19. 根据权利要求15所述的计算设备，其特征在于，
    所述第一通信接口，还用于接收所述部署在私有云中的虚拟机发送的地址解析协议ARP请求，所述ARP请求携带所述部署在公有云中的虚拟机的第二IP地址；
    所述第一处理器，还用于根据所述部署在公有云中的虚拟机的第二IP地址，获取所述部署在公有云中的虚拟机的MAC地址；
    所述第一通信接口，还用于向所述部署在私有云中的虚拟机发送所述部署在公有云中的虚拟机的MAC地址。
  20. 一种计算设备，其特征在于，所述计算设备包括第二通信接口、第二处理器和第二存储器，所述第二通信接口分别与所述第二处理器和所述第二存储器建立通信连接，所述第二处理器与所述第二存储器建立通信连接，所述第二存储器用于存储程 序代码；
    所述第二通信接口，用于接收所述混合云管理系统中的虚拟机发送的分配请求，所述分配请求携带所述虚拟机的媒体访问控制MAC地址；
    所述第二处理器，用于根据所述虚拟机的MAC地址，为所述虚拟机分配在私有云中的第二网络之间互联的协议IP地址；
    所述第二通信接口，还用于向所述虚拟机发送所述虚拟机的第二IP地址。
  21. 根据权利要求20所述的计算设备，其特征在于，
    所述第二处理器，还用于根据所述虚拟机的MAC地址，从MAC地址和IP地址的对应关系中确定为所述虚拟机分配在所述私有云中的第二IP地址。
PCT/CN2017/108197 2017-01-25 2017-10-28 混合云管理方法、装置和计算设备 WO2018137369A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710056696.3 2017-01-25
CN201710056696.3A CN108347493B (zh) 2017-01-25 2017-01-25 混合云管理方法、装置和计算设备

Publications (1)

Publication Number Publication Date
WO2018137369A1 true WO2018137369A1 (zh) 2018-08-02

Family

ID=62961819

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/108197 WO2018137369A1 (zh) 2017-01-25 2017-10-28 混合云管理方法、装置和计算设备

Country Status (2)

Country Link
CN (2) CN108347493B (zh)
WO (1) WO2018137369A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887278A (zh) * 2021-01-12 2021-06-01 北京东方网信科技股份有限公司 一种私有云和公有云的互联系统及方法
EP3975508A4 (en) * 2019-09-06 2022-07-06 Huawei Cloud Computing Technologies Co., Ltd. COMMUNICATION METHOD FOR HYBRID CLOUD ENVIRONMENT, GATEWAY AND MANAGEMENT METHOD AND DEVICE
CN114938309A (zh) * 2022-06-21 2022-08-23 北京华创方舟科技集团有限公司 一种私有云搭建与部署方法
CN115208891A (zh) * 2022-07-15 2022-10-18 济南浪潮数据技术有限公司 一种混合云弹性伸缩方法、装置、设备、存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108900637A (zh) * 2018-08-08 2018-11-27 北京百度网讯科技有限公司 用于传输信息的方法及装置
CN111130974B (zh) * 2018-11-01 2022-01-18 深信服科技股份有限公司 一种基于多云环境的网络互通系统及方法
CN109936629B (zh) * 2019-02-27 2021-09-03 浪潮云信息技术股份公司 一种混合云网络互连方法及系统
CN110213391B (zh) * 2019-07-12 2021-09-28 腾讯科技（深圳）有限公司 一种网络协议地址的配置方法及装置
CN110704167B (zh) * 2019-10-09 2023-09-19 腾讯科技（深圳）有限公司 一种创建虚拟机的方法、装置、设备和存储介质
CN111049925B (zh) * 2019-12-20 2022-07-19 网易（杭州）网络有限公司 混合云网络系统、通信系统和通信方法
CN111818081B (zh) * 2020-07-22 2023-05-23 腾讯科技（深圳）有限公司 虚拟加密机管理方法、装置、计算机设备和存储介质
CN111629084B (zh) * 2020-07-28 2020-11-03 腾讯科技（深圳）有限公司 数据传输方法和装置、存储介质及电子设备
CN112235400B (zh) * 2020-10-14 2024-02-02 腾讯科技（深圳）有限公司 通信方法、通信系统、装置、服务器及存储介质
CN112671859A (zh) * 2020-12-15 2021-04-16 中国人寿保险股份有限公司 一种混合云管理的方法及一种混合云系统
CN112738250B (zh) * 2020-12-30 2022-07-08 中国建设银行股份有限公司 一种混合云互联专线管理系统
CN115529245A (zh) * 2021-06-25 2022-12-27 深信服科技股份有限公司 流信息补全方法及装置、云主机设备和计算机存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102664972A (zh) * 2012-05-11 2012-09-12 中科方德软件有限公司 一种虚拟网络中地址映射方法和装置
WO2014182805A1 (en) * 2013-05-07 2014-11-13 Equinix, Inc. A direct connect virtual private interface for a one to many connection with multiple virtual private clouds
CN105657078A (zh) * 2015-12-29 2016-06-08 联想(北京)有限公司 一种数据传输方法、装置及多层网络管理器
CN105933235A (zh) * 2016-07-07 2016-09-07 北京邮电大学 数据通信方法及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104660479A (zh) * 2015-02-13 2015-05-27 南京华讯方舟通信设备有限公司 一种组网方法以及网络系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102664972A (zh) * 2012-05-11 2012-09-12 中科方德软件有限公司 一种虚拟网络中地址映射方法和装置
WO2014182805A1 (en) * 2013-05-07 2014-11-13 Equinix, Inc. A direct connect virtual private interface for a one to many connection with multiple virtual private clouds
CN105657078A (zh) * 2015-12-29 2016-06-08 联想(北京)有限公司 一种数据传输方法、装置及多层网络管理器
CN105933235A (zh) * 2016-07-07 2016-09-07 北京邮电大学 数据通信方法及装置

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3975508A4 (en) * 2019-09-06 2022-07-06 Huawei Cloud Computing Technologies Co., Ltd. COMMUNICATION METHOD FOR HYBRID CLOUD ENVIRONMENT, GATEWAY AND MANAGEMENT METHOD AND DEVICE
US11888809B2 (en) 2019-09-06 2024-01-30 Huawei Technologies Co., Ltd. Communication method, gateway, and management method and apparatus in hybrid cloud environment
CN112887278A (zh) * 2021-01-12 2021-06-01 北京东方网信科技股份有限公司 一种私有云和公有云的互联系统及方法
CN112887278B (zh) * 2021-01-12 2022-11-11 北京东方网信科技股份有限公司 一种私有云和公有云的互联系统及方法
CN114938309A (zh) * 2022-06-21 2022-08-23 北京华创方舟科技集团有限公司 一种私有云搭建与部署方法
CN115208891A (zh) * 2022-07-15 2022-10-18 济南浪潮数据技术有限公司 一种混合云弹性伸缩方法、装置、设备、存储介质

Also Published As

Publication number Publication date
CN108347493B (zh) 2020-06-26
CN111835878A (zh) 2020-10-27
CN108347493A (zh) 2018-07-31

Similar Documents

Publication Publication Date Title
WO2018137369A1 (zh) 混合云管理方法、装置和计算设备
CN111885075B (zh) 容器通信方法、装置、网络设备及存储介质
US11509577B2 (en) Linking resource instances to virtual network in provider network environments
CN112702252B (zh) 一种报文处理方法、系统及相关设备
US20230300105A1 (en) Techniques for managing software defined networking controller in-band communications in a data center network
TWI744359B (zh) 一種資料傳輸的方法及網路設備
CN116057910B (zh) 虚拟私有云通信及配置方法以及相关装置
JP6024474B2 (ja) マルチテナントシステム、管理装置、管理プログラム、およびマルチテナントシステムの制御方法
US9432287B2 (en) Virtual gateways and implicit routing in distributed overlay virtual environments
JP6475704B2 (ja) 適応オーバーレイネットワーキング
EP2982097B1 (en) Method and apparatus for exchanging ip packets among network layer 2 peers
WO2018112709A1 (zh) 一种数据包处理方法、主机和系统
US11522763B2 (en) Agent-based network scanning in software-defined networking (SDN) environments
JP7413415B2 (ja) ハイブリッドクラウド環境における通信方法、ゲートウェイ、並びに管理方法及び装置
US10530656B2 (en) Traffic replication in software-defined networking (SDN) environments
WO2018032910A1 (zh) 一种跨网络通信的方法、设备
US20150124823A1 (en) Tenant dhcp in an overlay network
US10594586B2 (en) Dialing test method, dialing test system, and computing node
WO2017113300A1 (zh) 路由确定方法、网络配置方法以及相关装置
WO2015149253A1 (zh) 数据中心的虚拟网络管理方法及数据中心系统
WO2018103043A1 (zh) 云计算系统中的报文处理方法及设备
WO2022063170A1 (zh) 一种公有云的网络配置方法及相关设备
JP2019041371A (ja) ネットワークリソースを共有するための方法およびシステム
WO2019214612A1 (zh) 传输报文的方法和装置
CN111294268B (zh) 避免ip地址冲突的方法及装置

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: 17893732

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: 17893732

Country of ref document: EP

Kind code of ref document: A1