Hybrid Cloud Management Method, Apparatus, and Computing Device

Abstract

The present disclosure provides a hybrid cloud management method, apparatus, and computing device, belonging to the technical field of cloud computing. The method includes: receiving an access data packet; if the virtual machine to be accessed is a virtual machine deployed in a public cloud, obtaining a second IP address of the virtual machine deployed in the public cloud in a private cloud according to the protocol IP address for interconnection between the first networks of the virtual machine deployed in the public cloud carried in the access data packet, and modifying the destination IP address of the access data packet to the second IP address of the virtual machine deployed in the public cloud; if the virtual machine to be accessed is a virtual machine deployed in a public cloud, obtaining a first IP 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 carried in the access data packet, and modifying the source IP address of the access data packet to the first IP address of the virtual machine deployed in the public cloud; and sending the access data packet to the virtual machine to be accessed. The present disclosure realizes network interconnection.

Description

Technical Field

[0001] The present disclosure relates to the field of cloud computing technology, and particularly to a hybrid cloud management method, apparatus, and computing device. Background Art

[0002] With the development of cloud computing technology, the development of hybrid clouds has received increasing attention. Hybrid clouds integrate public clouds and private clouds and are the main mode and development direction of cloud computing in recent years. Hybrid clouds should be able to flexibly deploy and schedule policies between private clouds and public clouds for applications of the same enterprise tenant. When the applications in the private cloud generate explosive resource requirements and the resources in the private cloud are insufficient, elastic scaling is performed to temporarily lease resources from the public cloud. Application scenarios such as using the public cloud as a disaster recovery backup point for the private cloud also pose new challenges to hybrid clouds. Therefore, data centers need to be able to communicate at high speed and need to be able to uniformly manage the networks on the public cloud and the networks on the private cloud to achieve network interconnection.

[0003] A first virtual machine runs in the private cloud, and a second virtual machine runs in the public cloud; in order to achieve network interconnection between the network of the private cloud and the network of the public cloud, a first proxy device is deployed on the first virtual machine, and a second proxy device is deployed on the second virtual machine. When the first virtual machine accesses the second virtual machine, the first virtual machine sends an access request to the first proxy device, and 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 achieve access from the first virtual machine to the second virtual machine.

[0004] In the process of implementing the present disclosure, the inventors found that the prior art has at least the following problems:

[0005] In the above method, it is necessary to configure the virtual machines in the hybrid cloud, resulting in poor generality of the above method. Summary of the Invention

[0006] To solve the problems of the prior art, embodiments of the present disclosure provide a hybrid cloud management method, apparatus, and computing device.

[0007] The technical solutions are as follows:

[0008] In a first aspect, embodiments of the present disclosure provide a hybrid cloud management method, which is applied to a HyperNode in a hybrid cloud management system. The method includes:

[0009] Receiving an access data packet sent by an access virtual machine, where the access data packet is used to access an accessed virtual machine;

[0010] If the accessed virtual machine is a virtual machine deployed in a public cloud, obtain the second IP address of the virtual machine deployed in the public cloud in the private cloud according to the protocol IP address for interconnection between the first networks of the virtual machine deployed in the public cloud carried in the access data packet, modify the destination IP address of the access data packet to the second IP address of the virtual machine deployed in the public cloud, and send the access data packet to the accessed virtual machine;

[0011] If the accessing virtual machine is the virtual machine deployed in the public cloud, obtain the first IP 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 carried in the access data packet, modify the source IP address of the access data packet to the first IP address of the virtual machine deployed in the public cloud, and send the access data packet to the accessed virtual machine.

[0012] In the embodiments of the present disclosure, the source IP address or the destination IP address of the access data packet is modified by HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that network interconnection can be achieved without configuring the virtual machines in the hybrid cloud.

[0013] In a possible design, the obtaining the second IP address of the virtual machine deployed in the public cloud in the private cloud according to the protocol IP address for interconnection between the first networks of the virtual machine deployed in the public cloud carried in the access data packet includes:

[0014] Obtain the second IP address of the virtual machine deployed in the public cloud from the correspondence between the first IP address and the second IP address according to the first IP address of the virtual machine deployed in the public cloud;

[0015] Correspondingly, the obtaining the first IP 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 carried in the access data packet includes:

[0016] Obtain the first IP address of the virtual machine deployed in the public cloud 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.

[0017] In the embodiments of the present disclosure, the HyperNode stores the correspondence between the first IP address and the second IP address. Therefore, when obtaining the second IP address of the virtual machine deployed in the public cloud, according to the first IP address of the virtual machine deployed in the public cloud, 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. When obtaining the first IP 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 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, thereby improving the accuracy of obtaining the IP address.

[0018] In a possible design, before receiving the access data packet sent by the access virtual machine, the method further includes:

[0019] Receiving the first IP address and the second IP address of the virtual machine deployed in the public cloud sent by the second cloud gateway Cloud GW in the public cloud, where the first IP address of the virtual machine deployed in the public cloud is obtained by the second Cloud GW from the virtual machine deployed in the public cloud, and the second IP address of the virtual machine deployed in the public cloud is obtained by the second Cloud GW from the management module in the hybrid cloud management system;

[0020] Establishing the correspondence between the first IP address and the second IP address of the virtual machine deployed in the public cloud.

[0021] In the embodiments of the present disclosure, the HyperNode establishes the correspondence between the first IP address and the second IP address of the virtual machine deployed in the public cloud, so as to subsequently obtain the second IP address or the first IP address of the virtual machine deployed in the public cloud from the correspondence between the first IP address and the second IP address according to the first IP address or the second IP address of the virtual machine deployed in the public cloud.

[0022] In a possible design, the method further includes:

[0023] If the virtual machine deployed in the private cloud in the hybrid cloud management system is migrated to the public cloud, obtaining the first IP address of the virtual machine deployed in the private cloud in the public cloud;

[0024] Determining the second IP address of the virtual machine deployed in the private cloud in the private cloud;

[0025] Establishing the correspondence between the first IP address and the second IP address of the virtual machine deployed in the private cloud.

[0026] In an embodiment of the present disclosure, IP address spoofing is achieved through HyperNode. A new ARP Proxy is configured in HyperNode, and MAC address spoofing is achieved through the ARP Proxy, so that the IP address and MAC address of the virtual machine remain unchanged. Without any modification to the network configuration, the migration of virtual machines between clouds can be achieved.

[0027] In a possible design, if the accessed virtual machine is a virtual machine deployed in a private cloud and the accessed virtual machine is a virtual machine deployed in a public cloud, the access data packet also carries the media access control (MAC) address of the virtual machine deployed in the public cloud. Before receiving the access data packet sent by the accessed virtual machine, the method further includes:

[0028] Receiving an address resolution protocol (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;

[0029] Obtaining 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;

[0030] Sending the MAC address of the virtual machine deployed in the public cloud to the virtual machine deployed in the private cloud.

[0031] In an embodiment of the present disclosure, the corresponding relationship between the MAC address and the second IP address of the virtual machine deployed in the public cloud is stored in Hypernode. Therefore, Hypernode can obtain 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.

[0032] In a second aspect, an embodiment of the present disclosure provides a hybrid cloud management method, which is applied to a management module in a hybrid cloud management system. The method includes:

[0033] Receiving an allocation request sent by a virtual machine in the hybrid cloud management system, where the allocation request carries the media access control (MAC) address of the virtual machine;

[0034] Allocating an Internet protocol (IP) address for interconnection between the second networks in the private cloud for the virtual machine according to the MAC address of the virtual machine;

[0035] Sending the second IP address of the virtual machine to the virtual machine.

[0036] In an embodiment of the present disclosure, the management module allocates a second IP address for the virtual machine in the hybrid cloud management system, so that network intercommunication can be achieved without configuring the virtual machine in the hybrid cloud.

[0037] In a possible design, allocating a protocol IP address for interconnecting second networks in a private cloud for the virtual machine according to the MAC address of the virtual machine includes:

[0038] Determining, according to the MAC address of the virtual machine, a second IP address for the virtual machine allocated in the private cloud from the correspondence between the MAC address and the IP address.

[0039] In a third aspect, an embodiment of the present disclosure provides a hybrid cloud management device, which is applied to a HyperNode in a hybrid cloud management system, and the device includes at least one module for executing the hybrid cloud management method provided in the first aspect.

[0040] In a fourth aspect, an embodiment of the present disclosure provides a hybrid cloud management device, which is applied to a management module in a hybrid cloud management system, and the device includes at least one module for executing the hybrid cloud management method provided in the second aspect.

[0041] In a fifth aspect, an embodiment of the present disclosure provides a computing device, which includes a first communication interface, a first processor, and a first memory. The first communication interface respectively establishes communication connections with the first processor and the first memory. The first processor establishes a communication connection with the first memory. The first memory is used for storing program codes. The first communication interface and the first processor are used for executing the hybrid cloud management method provided in the first aspect.

[0042] In a sixth aspect, an embodiment of the present disclosure provides a computing device, which includes a second communication interface, a second processor, and a second memory. The second communication interface respectively establishes communication connections with the second processor and the second memory. The second processor establishes a communication connection with the second memory. The second memory is used for storing program codes. The second communication interface and the second processor are used for executing the hybrid cloud management method provided in the second aspect.

[0043] The beneficial effects brought by the technical solutions provided by the embodiments of the present disclosure include:

[0044] In the embodiments of the present disclosure, by modifying the source IP address or the destination IP address of the access data packet by the HyperNode and sending the modified access data packet to the accessed virtual machine, network intercommunication can be achieved without configuring the virtual machines in the hybrid cloud. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1-1 is a schematic diagram of a hybrid cloud management system provided by an embodiment of the present disclosure;

[0046] Figure 1-2 It is a schematic diagram of the hybrid cloud management system provided by an embodiment of the present disclosure;

[0047] Figure 1-3 It is a schematic diagram of the hybrid cloud management system provided by an embodiment of the present disclosure;

[0048] Figure 1-4 It is a schematic diagram of the hybrid cloud management system provided by an embodiment of the present disclosure;

[0049] Figure 2 It is a schematic diagram of the structure of the computing device provided by an embodiment of the present disclosure;

[0050] Figure 3 It is a flowchart of the hybrid cloud management method provided by an embodiment of the present disclosure;

[0051] Figure 4 It is a flowchart of the hybrid cloud management method provided by an embodiment of the present disclosure;

[0052] Figure 5 It is a flowchart of the hybrid cloud management method provided by an embodiment of the present disclosure;

[0053] Figure 6 It is a flowchart of the hybrid cloud management method provided by an embodiment of the present disclosure;

[0054] Figure 7 It is a flowchart of the hybrid cloud management method provided by an embodiment of the present disclosure;

[0055] Figure 8 It is a flowchart of the hybrid cloud management method provided by an embodiment of the present disclosure;

[0056] Figure 9 It is a flowchart of the hybrid cloud management method provided by an embodiment of the present disclosure;

[0057] Figure 10 It is a schematic diagram of the structure of the hybrid cloud management device provided by an embodiment of the present disclosure;

[0058] Figure 11 It is a schematic diagram of the structure of the hybrid cloud management device provided by an embodiment of the present disclosure. Detailed implementation manners

[0059] To make the objectives, technical solutions, and advantages of the present disclosure clearer, the following will further describe the embodiments of the present disclosure in detail with reference to the accompanying drawings.

[0060] All the above optional technical solutions can be combined arbitrarily to form optional embodiments of the present disclosure, which will not be elaborated herein one by one.

[0061] Throughout this specification, a flow table is used to control data flows in a software-defined network. In the embodiments of this application, a flow table compliant with the software-defined network (full English name: openflow) protocol is used as an example. In actual use, a flow table compliant with other protocols can also be used.

[0062] Throughout this specification, a common virtual switch (full English name: virtual switch, abbreviation: VS) includes an Open vSwitch (full English name: Open vSwitch, abbreviation: OVS). OVS is a virtual switch provided by an open-source project.

[0063] In this specification, during the process of data packets being transmitted between a public cloud and a private cloud, an overlay encapsulation technology is adopted. Specifically, any one of the following can be used: virtual extensible local area network (full English name: virtual extensible local area network, abbreviation: VXLAN) technology, network virtualization using generic routing encapsulation (full English name: network virtualization using generic routing encapsulation, abbreviation: NVGRE) technology, and stateless transport tunneling (full English name: stateless transport tunneling, abbreviation: STT) technology. In the exemplary specification, VXLAN technology is adopted.

[0064] A hybrid cloud management system is provided in this specification. Refer to Figure 1-1 , this system includes: a management module, a first Cloud Gateway (full English name: Cloud Gateway, abbreviation: Cloud GW), a second Cloud GW, a first Virtual Extensible LAN (full English name: Virtual Extensible LAN, abbreviation: VXLAN) GW, a second VXLAN GW, and a HyperNode (full English name: HyperNode). Among them, 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 (full English name: Dynamic Host Configuration Protocol, abbreviation: DHCP) server.

[0065] The management module, the first Cloud GW, the second Cloud GW, the first VXLAN GW, the second VXLAN GW, the HyperNode, and each virtual machine deployed in the public cloud and the private cloud in this specification all run on computing devices. The structural schematic diagram of each computing device is as Figure 2 . Each computing device can actually be a server.

[0066] Each computing device may include a communication interface 110, a processor 120, and a memory 130. The communication interface 110 establishes communication connections with the processor 120 and the memory 130 respectively, and the processor 120 and the memory 130 establish a communication connection.

[0067] The memory 130 may include volatile memory (English full name: volatile memory), such as random access memory (English full name: random-access memory, abbreviation: RAM); the memory may also include 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 drive (English full name: hard disk drive, abbreviation: HDD) or solid state drive (English full name: solid state drive, abbreviation: SSD); the memory 130 may also include a combination of the above types of memories. When implementing the technical solution provided in this application through software, the program code for implementing the hybrid cloud management method provided in this disclosure is stored in the memory 130 and executed by the processor 120.

[0068] Each computing device communicates with each module in the hybrid cloud management system through the communication interface 110.

[0069] The processor 120 may be a central processing unit (English full name: central processing unit, abbreviation: CPU).

[0070] Since both the management module, the first Cloud GW, the second Cloud GW, the first VXLAN GW, the second VXLAN GW, and the HyperNode can actually be implemented by software running on virtual machines, and the deployment of virtual machines is relatively flexible. Therefore, in actual deployment, the management module, the first Cloud GW, the second Cloud GW, the first VXLAN GW, the second VXLAN GW, the HyperNode, and each virtual machine deployed in the public cloud and the private cloud can also be combined for deployment. For example, the first VXLAN GW can also be deployed on the computing device of the private cloud where virtual machines have been deployed, the second VXLAN GW can also be deployed on the computing device of the public cloud where virtual machines have been deployed, the HyperNode and the second VXLAN GW can be deployed on the same computing device of the public cloud, etc. The first Cloud GW and the first VXLAN GW are respectively the Cloud GW and VXLAN GW corresponding to the private cloud, and the second Cloud GW and the second VXLAN GW are respectively the Cloud GW and VXLAN GW corresponding to the public cloud.

[0071] 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 respectively connected to the second VXLAN GW and the HyperNode. The first VXLAN GW is respectively connected to the host where the virtual machine deployed in the private cloud is located and the second VXLAN GW, and the second VXLAN GW is connected to the HyperNode.

[0072] The resource management module is used to provide hybrid cloud services for users, and the hybrid cloud services can include computing resource management (such as creating virtual machines), storage resource management (such as creating volumes), and network resource management (such as creating subnets).

[0073] The network service module is used to create the required network services according to the requirements of the resource management module, such as DHCP services, etc.

[0074] The first Cloud GW is used to operate on the resources in the cloud by providing a service access interface, and provide a set of unified interfaces for the hybrid cloud system to use for the private cloud; and perform network configuration on the private cloud according to the requirements of the hybrid cloud management system. For example, perform network configuration on the first VXLAN GW (such as generating a flow table and sending it to the first VXLAN GW).

[0075] The second Cloud GW is used to operate resources in the cloud for providing a service access interface, and provides a set of unified interfaces for the hybrid cloud system to use the public cloud; and performs network configuration on the public cloud according to the requirements of the hybrid cloud management system. For example, network configuration is performed on the second VXLAN GW (such as generating a flow table and sending it to the second VXLAN GW).

[0076] The HyperNode is used to intercept data packets of virtual machines deployed in the public cloud, and mutually convert the first IP address assigned to the virtual machines deployed in the public cloud by the second DHCP server in the public cloud and the second IP address assigned to the virtual machines deployed in the public cloud by the first DHCP server, so as to enable the virtual machines deployed in the public cloud to access each other with the second IP address.

[0077] The first VXLAN GW is used to communicate with the second VXLAN GW to achieve intercommunication between the public cloud and the private cloud.

[0078] The second VXLAN GW is used to communicate with the first VXLAN GW to achieve intercommunication between the public cloud and the private cloud.

[0079] The host where the virtual machine deployed in the private cloud is located may further include an Agent (English full name: Agent), and the Agent is used to cooperate with the hybrid cloud management system to complete the configuration of the host.

[0080] The public cloud further includes a Router (English full name: Router), and the Router is used to forward data for the HyperNode and the virtual machines deployed in the public cloud.

[0081] It should be noted that the HyperNode can run on a virtual machine in the public cloud. The first Cloud GW can be deployed inside or outside the private cloud; the second Cloud GW can be deployed inside or outside the public cloud. In the embodiments of the present disclosure, the deployment locations of the first Cloud GW and the second Cloud GW are not specifically limited, as long as network intercommunication can be ensured. The connections described in the embodiments of the present disclosure include wired connections or wireless connections.

[0082] In Figure 1-1 it is described by taking the first Cloud GW deployed outside the private cloud and the second Cloud GW deployed outside the public cloud as an example. Refer to Figure 1-2 , the first Cloud GW is deployed inside the private cloud and the second Cloud GW is deployed inside the public cloud. Refer to Figure 1-3 , the first Cloud GW is deployed outside the private cloud and the second Cloud GW is deployed inside the public cloud. Refer toFigure 1-4 The first Cloud GW is deployed inside the private cloud, and the second Cloud GW is deployed outside the public cloud. For example, the first Cloud GW is deployed on a computing device outside the private cloud, and the second Cloud GW is deployed on a computing device outside the private cloud.

[0083] It should be noted that when managing virtual machines deployed in the public cloud and virtual machines deployed in the private cloud through the hybrid cloud management system provided by this disclosure embodiment, it is necessary to deploy the first VXLAN GW, the second VXLAN GW, the first Cloud GW, the second Cloud GW, and the HyperNode according to the above connection relationship, and configure the network interconnection of the management plane data and the data plane; and configure the account information and network information used by the second Cloud GW to create virtual machines deployed in the public cloud. Configure routing rules in the second Cloud GW so that the network default next hop of the virtual machines created by the second Cloud GW deployed in the public cloud is the HyperNode.

[0084] It should be noted that Figures 1-1 to 1-4 The dotted line in indicates the transmission of control plane data flow between two network elements, and the solid line indicates the transmission of service plane data flow between two network elements.

[0085] When managing the hybrid cloud, it is first necessary to create a network in the hybrid cloud management system, and subsequently virtual machines in the private cloud and virtual machines in the public cloud can be hung up to this network. See Figure 3 The process of creating a network includes:

[0086] Step 201: The network service module obtains the subnet information of the network to be created.

[0087] When creating a network, the user can input subnet information to the network service module; the network service module receives the subnet information input by the user. Among them, the subnet information can be the protocol (English full name: Internet Protocol, abbreviation: IP) address for the interconnection between networks of the subnet segment. For example, the IP address of the subnet segment can be 192.168.0.0 / 24.

[0088] Step 202: The network service module creates a network according to the subnet information.

[0089] The network service module creates a VXLAN network according to the subnet information, and virtual machines in the hybrid cloud management system are hung up to this VXLAN network.

[0090] Step 203: The network service module configures a first DHCP server for this network.

[0091] The first DHCP server is used to allocate IP addresses to virtual machines accessing the VXLAN network.

[0092] Step 204: The network service module sends the identifier of the first DHCP server to the virtual machines accessing the network.

[0093] The network service module stores the Media Access Control (MAC) addresses of the virtual machines accessing the network. According to the MAC addresses of the virtual machines accessing the network, the network service module sends the identifier of the first DHCP server to the virtual machines accessing the network. The virtual machines accessing the network receive the identifier of the first DHCP server sent by the network service module. Herein, the server identifier of the first DHCP server may be the IP address or MAC address of the first DHCP server, etc. In the embodiments of the present disclosure, the server identifier of the first DHCP server is not specifically limited.

[0094] After the virtual machines deployed in the private cloud and the virtual machines deployed in the public cloud access the network, the first DHCP server allocates IP addresses to the virtual machines deployed in the private cloud and the virtual machines deployed in the public cloud. As Figure 4 shown, the process of the first DHCP server allocating an IP address to a virtual machine deployed in the private cloud includes:

[0095] Step 301: The virtual machine deployed in the private cloud in the private cloud sends a first allocation request to the first DHCP server, and the first allocation request carries the MAC address of the virtual machine deployed in the private cloud.

[0096] 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. The virtual machine deployed in the private cloud sends a first allocation request to the first Cloud GW. The first allocation request carries 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 and forwards the first allocation request to the first DHCP server according to the server identifier of the first DHCP server.

[0097] Wherein, a network connection is established between the host where the virtual machine deployed in the private cloud is located and the network service module. The virtual machine deployed in the private cloud sends a first allocation request to the first DHCP server through this network connection according to the server identifier of the first DHCP server.

[0098] 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 address of the virtual machine deployed in the private cloud according to the MAC address of the virtual machine deployed in the private cloud.

[0099] The correspondence between the MAC address and the IP address is configured in the first DHCP server; correspondingly, the step of the first DHCP server obtaining 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 can be:

[0100] 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.

[0101] For example, the correspondence between the MAC address and the IP address stored in the first DHCP server is shown in Table 1 below:

[0102] Table 1

[0103] MAC address IP address MAC1 192.168.0.3 MAC2 192.168.0.4 MAC3 192.168.0.5 MAC4 192.168.0.6

[0104] For example, if the MAC address of the virtual machine VM1 deployed in the private cloud is MAC1, the first DHCP server obtains the IP address of VM1 as 192.168.0.3 from Table 1 according to MAC1; again, if the MAC address of the virtual machine VM2 deployed in the private cloud is MAC2, the first DHCP server obtains the IP address of VM2 as 192.168.0.4 from Table 1 according to MAC2.

[0105] Step 303: The first DHCP server sends the IP address to the virtual machine deployed in the private cloud.

[0106] The first DHCP server sends a first allocation response to the first Cloud GW, and 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 and forwards the IP address to the virtual machine deployed in the private cloud according to the MAC address of the virtual machine deployed in the private cloud.

[0107] Step 304: The virtual machine deployed in the private cloud receives the IP address sent by the first DHCP server.

[0108] In the embodiments of the present disclosure, the first DHCP server in the hybrid cloud management system assigns IP addresses to virtual machines deployed in the public cloud, and the second DHCP server in the public cloud also assigns IP addresses to virtual machines deployed in the public cloud; for the sake of distinction, the IP addresses assigned by the second DHCP server to virtual machines deployed in the public cloud are called the first IP addresses, and the IP addresses assigned by the first DHCP server to virtual machines deployed in the public cloud are called the second IP addresses. The process of the first DHCP and the second DHCP servers assigning IP addresses to virtual machines deployed in the public cloud is as Figure 5 shown, including:

[0109] Step 401: A 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, and the second allocation request carries the MAC address of the virtual machine deployed in the public cloud.

[0110] After a virtual machine deployed in the public cloud in the public cloud is started, it obtains the server identifier of the second DHCP server in the public cloud and sends a second allocation request to the second Cloud GW. The second allocation request carries the MAC address of the virtual machine deployed in the public cloud and the server identifier of the second DHCP server; the second Cloud GW receives the second allocation request sent by the virtual machine deployed in the public cloud and forwards the second allocation request to the second DHCP server according to the server identifier of the second DHCP server.

[0111] It should be noted that before this step, when a user creates a virtual machine deployed in the public cloud in the hybrid cloud management system, the management module sends a creation request to the second Cloud GW, and the creation request carries the device identifier of the virtual machine deployed in the public cloud; the second Cloud GW receives the creation request sent by the management module and calls the interface of the public cloud to create a virtual machine deployed in the public cloud according to the configuration information. Among them, the configuration information includes account information and network identifier.

[0112] Step 402: The second DHCP server receives the second allocation request sent by the virtual machine deployed in the public cloud, and obtains the first 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.

[0113] The correspondence between the MAC address and the IP address is configured in the second DHCP server; correspondingly, the step of the second DHCP server obtaining the first 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 can be:

[0114] 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.

[0115] For example, the correspondence between the MAC addresses and IP addresses stored in the second DHCP server is shown in Table 2 below:

[0116] Table 2

[0117] MAC address IP address MAC3 172.16.0.101 MAC4 172.16.0.102

[0118] For example, if the MAC address of the virtual machine VM3 deployed in the public cloud is MAC3, the second DHCP server obtains the first IP address of VM3 as 172.16.0.101 from Table 2 according to MAC3; for another example, if the MAC address of the virtual machine VM4 deployed in the public cloud is MAC4, the second DHCP server obtains the first IP address of VM4 as 172.16.0.102 from Table 2 according to MAC4.

[0119] Step 403: The second DHCP server sends the first IP address to the virtual machine deployed in the public cloud.

[0120] The second DHCP server sends a second allocation response to the second Cloud GW, and the second allocation response carries the MAC address of the virtual machine deployed in the public cloud; the second Cloud GW receives the second allocation response sent by the second DHCP server and, according to the public

[0121] Step 404: The virtual machine deployed in the public cloud receives the first IP address sent by the second DHCP server.

[0122] Step 405: The second Cloud GW in the public cloud obtains the first IP address of the virtual machine deployed in the public cloud from the virtual machine deployed in the public cloud.

[0123] Step 406: The second Cloud GW obtains the second IP address of the virtual machine deployed in the public cloud from the first DHCP server.

[0124] The second Cloud GW sends a query request to the first DHCP server, and 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, obtains 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, and sends the second IP address of the virtual machine deployed in the public cloud to the second Cloud GW.

[0125] The steps for the first DHCP server to obtain the second IP address of the virtual machine deployed in the public cloud based on the MAC address of the virtual machine deployed in the public cloud can be as follows:

[0126] 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 based on the MAC address of the virtual machine deployed in the public cloud.

[0127] For example, if the MAC address of the virtual machine VM3 deployed in the public cloud is MAC3, the first DHCP server obtains the second IP address of VM3 as 192.168.0.5 from Table 1 based on MAC3; another example, if the MAC address of the virtual machine VM4 deployed in the public cloud is MAC4, the first DHCP server obtains the second IP address of VM4 as 192.168.0.6 from Table 1 based on MAC4.

[0128] 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.

[0129] 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 the correspondence between the first IP address and the second IP address of the virtual machine deployed in the public cloud.

[0130] Add a flow table in 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 into the flow table. Add an Address Resolution Protocol (English full name: Address Resolution Protocol, abbreviation: ARP) Proxy server (English full name: Proxy) in the HyperNode; the ARP Proxy is used to modify the IP address of the data packet sent by the virtual machine deployed in the public cloud and modify the IP address of the data packet sent to the virtual machine deployed in the public cloud.

[0131] For example, if the HyperNode receives a 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 first IP address of the virtual machine deployed in the public cloud based on the second IP address of the virtual machine deployed in the public cloud, and modifies the destination address of the data packet to the first IP address of the virtual machine deployed in the public cloud.

[0132] For another example, when the virtual machine deployed in the public cloud sends a data packet to other virtual machines in the hybrid cloud management system, the HyperNode modifies the source IP address of the data packet to the first IP address of the virtual machine deployed in the public cloud.

[0133] In the embodiments of the present disclosure, by modifying the source IP address or the destination IP address of the access data packet through the HyperNode and sending the modified access data packet to the accessed virtual machine, network interconnection can be achieved without configuring the virtual machines in the hybrid cloud.

[0134] In the hybrid cloud management system, virtual machines can access each other, that is, the virtual machine deployed in the private cloud can access the virtual machine deployed in the public cloud, the virtual machine deployed in the public cloud can access the virtual machine deployed in the private cloud, and the virtual machine deployed in the public cloud can also access the virtual machine deployed in the public cloud. Among them, the process of the virtual machine deployed in the private cloud accessing the virtual machine deployed in the public cloud is as follows Figure 6 shown, including:

[0135] Step 501: The virtual machine deployed in the private cloud sends an ARP request to the HyperNode, and the ARP request carries the second IP address of the virtual machine deployed in the public cloud to be accessed.

[0136] Since the virtual machine deployed in the private cloud needs to obtain the MAC address of the virtual machine deployed in the public cloud when accessing the virtual machine deployed in the public cloud, before the virtual machine deployed in the private cloud accesses the virtual machine 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.

[0137] This step can be implemented through the following steps 5011 - 5014, including:

[0138] 5011: 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, and the ARP request carries the second IP address of the virtual machine deployed in the public cloud to be accessed.

[0139] The virtual machine deployed in the private cloud obtains the second IP address of the virtual machine deployed in the public cloud to be accessed. According to the IP address of the virtual machine deployed in the private cloud and the second IP address of the virtual machine deployed in the public cloud, it is determined 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 an ARP request is sent to the virtual switch of the host where the virtual machine deployed in the private cloud is located.

[0140] For example, the IP address of the virtual machine deployed in the private cloud is 192.168.0.3, and the second IP address of the virtual machine deployed in the public cloud is 192.168.0.5. Since 192.168.0.3 and 192.168.0.5 belong to the same network segment, 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.

[0141] 5012: The virtual switch receives the ARP request sent by the virtual machine deployed in the private cloud and sends the ARP request to the second VXLAN GW.

[0142] The virtual switch encapsulates the ARP request into a VXLAN data packet and sends the VXLAN data packet to the second VXLAN GW.

[0143] 5013: The second VXLAN GW receives the ARP request sent by the virtual switch and sends the ARP request to the first VXLAN GW.

[0144] The second VXLAN GW obtains the identifier of the first VXLAN GW and sends the ARP request to the first VXLANGW according to the identifier of the first VXLAN GW.

[0145] The corresponding relationship between the vxlan network and the identifier of the VXLAN GW is configured in the second VXLAN GW; correspondingly, the step for the second VXLAN GW to obtain the identifier of the first VXLAN GW can be:

[0146] The second VXLAN GW determines the vxlan network where the virtual machine deployed in the public cloud is located according to the second IP address of the virtual machine deployed in the public cloud, and obtains the identifier of the first VXLAN GW from the corresponding relationship between the vxlan network and the identifier of the VXLAN GW according to the vxlan network where the virtual machine deployed in the public cloud is located.

[0147] It should be noted that the second VXLAN GW first re-encapsulates the vxlan data packet and sends the re-encapsulated vxlan data packet to the first VXLAN GW.

[0148] 5014: The first VXLAN GW receives the ARP request sent by the second VXLAN GW and sends the ARP request to the HyperNode.

[0149] 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.

[0150] The ARP Proxy in the HyperNode is configured with the correspondence between the MAC address and the second IP address of the virtual machine deployed in the public cloud; correspondingly, the step of the HyperNode obtaining 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 can be:

[0151] 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, 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; the HyperNode receives the MAC address of the virtual machine deployed in the public cloud sent by the ARP Proxy.

[0152] 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.

[0153] 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 of sending the ARP request. The process can be implemented through the following steps 5031 - 5034, including:

[0154] 5031: The HyperNode sends the MAC address of the virtual machine deployed in the public cloud to the first VXLAN GW.

[0155] 5032: 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.

[0156] 5033: 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 MAC address of the virtual machine deployed in the public cloud to the virtual switch of the host where the virtual machine deployed in the private cloud is located.

[0157] 5034: 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.

[0158] 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.

[0159] After the virtual machine deployed in the private cloud obtains the MAC address of the virtual machine deployed in the public cloud, it sends an access packet to the virtual machine deployed in the public cloud to access the virtual machine deployed in the public cloud through the following step 505.

[0160] Step 505: The virtual machine deployed in the private cloud sends an access packet to the HyperNode. The source IP address of the access packet is the IP address of the virtual machine deployed in the private cloud, the source MAC address is the MAC address of the virtual machine deployed in the private cloud, 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.

[0161] This step can be implemented through the following steps 5051 - 5054, including:

[0162] 5051: The virtual machine deployed in the private cloud sends an access packet to the virtual switch of the host where the virtual machine deployed in the private cloud is located.

[0163] 5052: The virtual switch receives the access packet sent by the virtual machine deployed in the private cloud and sends the access packet to the second VXLANGW.

[0164] The virtual switch encapsulates the access packet and encapsulates the access packet into an access packet in VXLAN format, and sends the encapsulated access packet to the second VXLAN GW.

[0165] 5053: The second VXLAN GW receives the access packet sent by the virtual switch and sends the access packet to the first VXLAN GW.

[0166] The second VXLAN GW re - encapsulates the access packet and sends the encapsulated access packet to the first VXLAN GW.

[0167] 5054: The first VXLAN GW receives the access packet sent by the second VXLAN GW and sends the access packet to the HyperNode.

[0168] Step 506: The HyperNode receives the access packet sent by the virtual machine deployed in the private cloud and modifies the destination IP address of the access packet to the first IP address.

[0169] The HyperNode unpacks the access data packet to obtain an access data packet in Ethernet format. According to the second IP address of the virtual machine deployed in the public cloud, it obtains the first IP address of the virtual machine deployed in the public cloud from the correspondence between the second IP address and the first IP address, and modifies the destination IP address of the access data packet to the first IP address.

[0170] Step 507: The HyperNode sends the access data packet to the virtual machine deployed in the public cloud according to the first IP address.

[0171] 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 address of the access data packet: the first IP address.

[0172] Step 508: The virtual machine deployed in the public cloud receives the access data packet sent by the HyperNode.

[0173] In the embodiment of the present disclosure, by modifying the source IP address or the destination IP address of the access data packet by the HyperNode and sending the modified access data packet to the accessed virtual machine, network interconnection can be achieved without configuring the virtual machines in the hybrid cloud.

[0174] The process of a virtual machine deployed in the public cloud accessing a virtual machine deployed in the private cloud is as follows Figure 7 as shown, including:

[0175] Step 601: The virtual machine deployed in the public cloud sends an access data packet to the HyperNode. The source IP of the access data packet is the first IP address of the virtual machine deployed in the public cloud, the source MAC address is the MAC address of the virtual machine deployed in the public cloud, the destination IP address is the IP address of the virtual machine to be accessed deployed in the private cloud, and the destination MAC address is the MAC address of the virtual machine deployed in the private cloud.

[0176] This step can be implemented through the following steps 6011-6012, including:

[0177] 6011: The virtual machine deployed in the public cloud sends an access data packet to the Router node in the public cloud.

[0178] A virtual machine deployed in a public cloud obtains the IP address of a virtual machine deployed in a private cloud to be accessed. Based on the IP address of the virtual machine deployed in the private cloud and the first IP address of the virtual machine deployed in the public cloud, it is determined that the virtual machine deployed in the public cloud and the virtual machine deployed in the private cloud are not in the same vxlan network, and the Router node in the public cloud needs to forward. Then, the virtual machine deployed in the public cloud sends an access packet to the Router node in the public cloud.

[0179] 6012: The Router node receives the access packet sent by the virtual machine deployed in the public cloud and forwards the access packet to the HyperNode.

[0180] The Router node forwards the access packet to the HyperNode according to the routing rule. Among them, the routing rule is that the next hop of the Router node is the HyperNode.

[0181] Step 602: The HyperNode receives the access packet sent by the virtual machine deployed in the public cloud and modifies the source IP address of the access packet to the second IP address of the virtual machine deployed in the public cloud.

[0182] The HyperNode obtains the second IP address of the virtual machine deployed in the public cloud from the correspondence between the first IP address and the second IP address according to the first IP address of the virtual machine deployed in the public cloud, and modifies the source IP address of the access packet to the second IP address of the virtual machine deployed in the public cloud.

[0183] Step 603: The HyperNode sends the access packet to the second VXLAN GW.

[0184] Step 604: The second VXLAN GW receives the access packet sent by the HyperNode and sends the access packet to the first VXLAN GW.

[0185] The second VXLAN GW encapsulates the access packet and sends the encapsulated access packet to the first VXLAN GW.

[0186] Step 605: The first VXLAN GW receives the access packet sent by the second VXLAN GW and sends the access packet to the virtual machine deployed in the private cloud.

[0187] The first VXLAN GW encapsulates the access packet and sends the access packet to the virtual machine deployed in the private cloud.

[0188] The first VXLAN GW sends the access packet to the virtual switch of the host where the virtual machine deployed in the private cloud is located. The virtual switch receives the access packet sent by the first VXLAN GW, de-encapsulates the access packet, and sends the de-encapsulated access packet to the virtual machine deployed in the private cloud.

[0189] Step 606: The virtual machine deployed in the private cloud receives the access packet sent by the first VXLAN GW.

[0190] The process of a virtual machine deployed in a public cloud accessing a virtual machine deployed in a public cloud is as follows Figure 8 As shown, for ease of description, the virtual machine accessing the virtual machine deployed in the public cloud is referred to as the first virtual machine deployed in the public cloud, and the virtual machine deployed in the public cloud to be accessed is referred to as the second virtual machine deployed in the public cloud, including:

[0191] Step 701: The first virtual machine deployed in the public cloud sends an access packet to the HyperNode. The source IP address of the access packet is the first IP address of the first virtual machine deployed in the public cloud, the source MAC address is the MAC address of the first virtual machine deployed in the public cloud, the destination IP address is the first IP address of the second virtual machine deployed in the public cloud, and the destination MAC address is the MAC address of the second virtual machine deployed in the public cloud.

[0192] This step can be implemented through the following steps 7011 - 7012, including:

[0193] 7011: The first virtual machine deployed in the public cloud sends an access packet to the Router node in the public cloud.

[0194] 7012: The Router node in the public cloud receives the access packet sent by the first virtual machine deployed in the public cloud and forwards the access packet to the HyperNode.

[0195] Step 702: The HyperNode receives the access packet sent by the first virtual machine deployed in the public cloud, modifies the source IP address of the access packet to the second IP address of the first virtual machine deployed in the public cloud, and modifies the destination IP address of the access packet to the second IP address of the second virtual machine deployed in the public cloud.

[0196] The HyperNode obtains the second IP address of the first virtual machine deployed in the public cloud and the second IP address of the second virtual machine deployed in the public cloud from the correspondence between the first IP address and the second IP address, modifies the source IP address of the access packet to the second IP address of the first virtual machine deployed in the public cloud, and modifies the destination IP address of the access packet to the second IP address of the second virtual machine deployed in the public cloud.

[0197] Step 703: The HyperNode sends the access packet to the second virtual machine deployed in the public cloud.

[0198] The HyperNode sends the access packet to the Router node. The Router node receives the access packet sent by the HyperNode and forwards the access packet to the second virtual machine deployed in the public cloud according to the second IP address of the second virtual machine deployed in the public cloud.

[0199] Step 704: The second virtual machine deployed in the public cloud receives the access packet sent by the HyperNode.

[0200] In the embodiments of the present disclosure, by modifying the source IP address or the destination IP address of the access packet by the HyperNode and sending the modified access packet to the accessed virtual machine, network interconnection can be achieved without configuring the virtual machines in the hybrid cloud.

[0201] In the hybrid cloud management system, a virtual machine can be migrated from the private cloud to the public cloud. And during the migration, without making any changes to the network configuration, it can ensure that the MAC address and the second and third IP addresses of the virtual machine deployed in the public cloud remain unchanged. Refer to Figure 9 , the migration process includes:

[0202] Step 801: The private cloud virtual machine sends a third allocation request to the second DHCP server. The third allocation request carries the MAC address of the virtual machine deployed in the private cloud.

[0203] When 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 an IP address in the public cloud from the second DHCP server in the public cloud.

[0204] 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 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.

[0205] For the sake of easy distinction, 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, and the IP address assigned by the first DHCP server to the virtual machine deployed in the private cloud is referred to as the second IP address.

[0206] 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.

[0207] 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.

[0208] Step 805: The second Cloud GW obtains the first IP address of the virtual machine deployed in the private cloud from the virtual machine deployed in the private cloud.

[0209] Step 806: The second Cloud GW obtains the second IP address of the virtual machine deployed in the private cloud from the first DHCP server.

[0210] 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.

[0211] 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 the corresponding relationship between the first IP address and the second IP address of the virtual machine deployed in the private cloud.

[0212] In the embodiment of the present disclosure, IP address spoofing is implemented through the HyperNode, and a new ARP Proxy is configured in the HyperNode to implement MAC address spoofing through the ARP Proxy, so as to keep the IP address and MAC address of the virtual machine unchanged, and the migration of virtual machines between clouds can be realized without any modification of network configuration.

[0213] The embodiment of the present disclosure also provides a hybrid cloud management device, which can pass through Figure 2The computing device implementation shown can also be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The above PLD can be a complex programmable logic device (CPLD), FPGA, generic array logic (GAL), or any combination thereof. The hybrid cloud management device is used for the above hybrid cloud management method. When the above hybrid cloud management method is implemented by software, the hybrid cloud management device can also be a software module.

[0214] The schematic diagram of the group leader structure of the data clustering device is as Figure 10 shown, including: a first receiving module 901, a first management module 902, and a second management module 903.

[0215] When the first receiving module 901 works, it executes the receiving process in the above hybrid cloud management method.

[0216] When the first management module 902 and the second management module 903 work, they execute the management process in the above hybrid cloud management method.

[0217] In addition, the device further includes a second receiving module and a first establishing module.

[0218] When the second receiving module works, it executes receiving the first IP address and the second IP address of the virtual machine deployed in the public cloud sent by the second CloudGW in the public cloud in the above hybrid cloud management method.

[0219] When the first establishing module works, it executes establishing the correspondence relationship between the first IP address and the second IP address of the virtual machine deployed in the public cloud in the above hybrid cloud management method.

[0220] In addition, the device further includes: a first obtaining module, a determining module, and a second establishing module.

[0221] When the first obtaining module works, it executes the obtaining process in the above hybrid cloud management method.

[0222] When the determining module works, it executes the determining process in the above hybrid cloud management method.

[0223] When the second establishing module works, it executes establishing the correspondence relationship between the first IP address and the second IP address of the virtual machine deployed in the private cloud in the above hybrid cloud management method.

[0224] In addition, the device further includes: a third receiving module, a second obtaining module, and a first sending module.

[0225] When the third receiving module is working, it performs the receiving process in the above-mentioned hybrid cloud management method.

[0226] When the second obtaining module is working, it performs the obtaining process in the above-mentioned hybrid cloud management method.

[0227] When the first sending module is working, it performs the sending process in the above-mentioned hybrid cloud management method.

[0228] In the embodiment of the present disclosure, the source IP address or the destination IP address of the access data packet is modified by HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that network interconnection can be achieved without configuring the virtual machines in the hybrid cloud.

[0229] The embodiment of the present disclosure further provides a hybrid cloud management device, which can be implemented by the Figure 2 computing device shown, and can also be implemented by ASIC or PLD. The above PLD can be CPLD, FPGA, GAL or any combination thereof. The hybrid cloud management device is used for the above-mentioned hybrid cloud management method. When the above-mentioned hybrid cloud management method is implemented by software, the hybrid cloud management device can also be a software module.

[0230] The schematic diagram of the group leader structure of the data clustering device is as Figure 11 shown, and includes: a fourth receiving module 1001, an allocation module 1002, and a second sending module 1003.

[0231] When the fourth receiving module 1001 is working, it performs the process of receiving the allocation request sent by the virtual machine in the above-mentioned hybrid cloud management method.

[0232] When the allocation module 1002 is working, it performs the process of allocating IP addresses in the above-mentioned hybrid cloud management method.

[0233] When the second sending module 1003 is working, it performs the process of sending IP addresses in the above-mentioned hybrid cloud management method.

[0234] In the embodiment of the present disclosure, the source IP address or the destination IP address of the access data packet is modified by HyperNode, and the modified access data packet is sent to the accessed virtual machine, so that network interconnection can be achieved without configuring the virtual machines in the hybrid cloud.

[0235] The embodiment of the present disclosure further provides a computing device, and its organizational structure schematic diagram is as Figure 2As shown, it includes a first communication interface, a first processor, and a first memory. The first communication interface establishes communication connections with the first processor and the first memory respectively. The first processor establishes a communication connection with the first memory. The first memory is used to store program codes.

[0236] The first processor executes the program codes stored in the first memory to execute the above-mentioned hybrid cloud management method. This computing device is also the computing device that runs the aforementioned HyperNode.

[0237] In the embodiments of the present disclosure, 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 virtual machine to be accessed, so that network interconnection can be achieved without configuring the virtual machines in the hybrid cloud.

[0238] The embodiments of the present disclosure also provide a computing device, and its organizational structure schematic diagram is as Figure 2 As shown, it includes a second communication interface, a second processor, and a second memory. The second communication interface establishes communication connections with the second processor and the second memory respectively. The second processor establishes a communication connection with the second memory. The second memory is used to store program codes.

[0239] The second processor executes the program codes stored in the second memory to execute the above-mentioned hybrid cloud management method. This computing device is also the computing device that runs the aforementioned management module.

[0240] In the embodiments of the present disclosure, 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 virtual machine to be accessed, so that network interconnection can be achieved without configuring the virtual machines in the hybrid cloud.

[0241] Those of ordinary skill in the art can understand that all or part of the steps to implement the above embodiments can be completed by hardware, or can be completed by a program instructing related hardware. The program can be stored in a computer-readable storage medium. The above-mentioned storage medium can be a read-only memory, a disk, or an optical disc, etc.

[0242] The above are only the preferred embodiments of the present disclosure, and are not intended to limit the present disclosure. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present disclosure shall be included within the protection scope of the present disclosure.

Claims

1. A hybrid cloud management method, characterized in that, The method is applied to a supernode in a cloud management system for managing public clouds and private clouds. Among them, a first virtual machine VM is deployed in the public cloud, and a second VM is deployed in the private cloud. The method includes: The supernode receives an access data packet sent by the second VM for accessing the first VM. The destination IP address of the access data packet is the second IP address of the first VM in the public cloud. The supernode obtains the first IP address of the first VM deployed in the public cloud from the correspondence between the first IP address and the second IP address, and modifies the destination IP address of the access data packet to the first IP address. The supernode sends the modified access data packet to the first VM.

2. The method according to claim 1, wherein Including: Receiving the first IP address and the second IP address of the first VM sent by the second cloud gateway Cloud GW in the public cloud. The first IP address of the first VM is obtained by the second Cloud GW from the first VM deployed in the public cloud, and the second IP address of the first VM is obtained by the second Cloud GW from the cloud management system. Establishing the correspondence between the first IP address and the second IP address of the first VM.

3. A hybrid cloud management method, characterized in that, The method is applied to a supernode in a cloud management system for managing public clouds and private clouds. Among them, a first virtual machine VM is deployed in the public cloud, and a second VM is deployed in the private cloud. The method includes: The supernode receives an access data packet sent by the first VM for accessing the second VM. The source IP address of the access data packet is the first IP address of the first VM in the public cloud, and the destination IP address of the access data packet is the IP address of the second VM in the private cloud. The supernode obtains the second IP address of the first VM deployed in the public cloud from the correspondence between the first IP address and the second IP address, and modifies the source IP address of the access data packet to the second IP address. The supernode sends the modified access data packet to the second VM.

4. The method according to claim 3, wherein Including: Receiving the first IP address and the second IP address of the first VM sent by the second cloud gateway Cloud GW in the public cloud. The first IP address of the first VM is obtained by the second Cloud GW from the first VM deployed in the public cloud, and the second IP address of the first VM is obtained by the second Cloud GW from the cloud management system. Establishing the correspondence between the first IP address and the second IP address of the first VM.

5. A hybrid cloud management device, characterized in that, The device is applied in a cloud management system which is used to manage public clouds and private clouds. Among them, a first virtual machine VM is deployed in the public cloud, and a second VM is deployed in the private cloud. The device includes: A receiving module, configured to receive an access data packet sent by the second VM, where the access data packet is used to access the first VM, and the destination IP address of the access data packet is the second IP address of the first VM in the public cloud; A management module, configured to obtain the first IP address of the first VM deployed in the public cloud from the correspondence between the first IP address and the second IP address according to the second IP address of the first VM deployed in the public cloud, modify the destination IP address of the access data packet to the first IP address; and send the modified access data packet to the first VM.

6. A hybrid cloud management device, characterized in that, The device is applied in a cloud management system which is used to manage public clouds and private clouds. Among them, a first virtual machine VM is deployed in the public cloud, and a second VM is deployed in the private cloud. The device includes: A receiving module, configured to receive an access data packet sent by the first VM, where the access data packet is used to access the second VM, the source IP address of the access data packet is the first IP address of the first VM in the public cloud, and the destination IP address of the access data packet is the IP address of the second VM in the private cloud; A management module, configured to obtain the second IP address of the first VM deployed in the public cloud from the correspondence between the first IP address and the second IP address according to the first IP address of the first VM deployed in the public cloud, modify the source IP address of the access data packet to the second IP address; and send the modified access data packet to the second VM.

7. A computing device, characterized in that, The computing device is applied in a cloud management system which is used to manage public clouds and private clouds. Among them, a first virtual machine VM is deployed in the public cloud, and a second VM is deployed in the private cloud. The computing device includes a communication interface, a processor, and a memory. The communication interface establishes a communication connection with the processor and the memory, the processor establishes a communication connection with the memory, and the memory is used to store program code; The communication interface is configured to receive an access data packet sent by the second VM, where the access data packet is used to access the first VM, and the destination IP address of the access data packet is the second IP address of the first VM in the public cloud; The processor is configured to execute the program code stored in the memory, obtain the first IP address of the first VM deployed in the public cloud from the correspondence between the first IP address and the second IP address according to the second IP address of the first VM deployed in the public cloud, modify the destination IP address of the access data packet to the first IP address; and send the modified access data packet to the first VM through the communication interface.

8. A computing device, characterized in that, The computing device is applied in a cloud management system for managing public clouds and private clouds. Among them, a first virtual machine VM is deployed in the public cloud, and a second VM is deployed in the private cloud. The computing device includes a communication interface, a processor, and a memory. The communication interface establishes communication connections with the processor and the memory. The processor establishes a communication connection with the memory. The memory is used to store program code; The communication interface is used to receive an access data packet sent by the first VM for accessing the second VM. The source IP address of the access data packet is the first IP address of the first VM in the public cloud, and the destination IP address of the access data packet is the IP address of the second VM in the private cloud; The processor is used to execute the program code stored in the memory, obtain the second IP address of the first VM deployed in the public cloud from the correspondence between the first IP address and the second IP address, modify the source IP address of the access data packet to the second IP address, and send the modified access data packet to the second VM through the communication interface.

Images