CN108347493A - Mixed cloud management method, device and computing device - Google Patents
Mixed cloud management method, device and computing device Download PDFInfo
- Publication number
- CN108347493A CN108347493A CN201710056696.3A CN201710056696A CN108347493A CN 108347493 A CN108347493 A CN 108347493A CN 201710056696 A CN201710056696 A CN 201710056696A CN 108347493 A CN108347493 A CN 108347493A
- Authority
- CN
- China
- Prior art keywords
- virtual machine
- address
- deployed
- public cloud
- cloud
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 105
- 238000000034 method Methods 0.000 claims abstract description 33
- 238000004891 communication Methods 0.000 claims description 24
- 230000005540 biological transmission Effects 0.000 claims description 18
- 239000011800 void material Substances 0.000 claims description 13
- 230000005012 migration Effects 0.000 claims description 7
- 238000013508 migration Methods 0.000 claims description 7
- 238000005516 engineering process Methods 0.000 abstract description 9
- 238000010586 diagram Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 12
- 230000004048 modification Effects 0.000 description 10
- 238000012986 modification Methods 0.000 description 10
- 238000005538 encapsulation Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 239000003795 chemical substances by application Substances 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 238000013461 design Methods 0.000 description 5
- 210000004209 hair Anatomy 0.000 description 4
- 101100059544 Arabidopsis thaliana CDC5 gene Proteins 0.000 description 3
- 101100244969 Arabidopsis thaliana PRL1 gene Proteins 0.000 description 3
- 102100039558 Galectin-3 Human genes 0.000 description 3
- 101100454448 Homo sapiens LGALS3 gene Proteins 0.000 description 3
- 101150115300 MAC1 gene Proteins 0.000 description 3
- 101150051246 MAC2 gene Proteins 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 241000208340 Araliaceae Species 0.000 description 1
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 description 1
- 235000003140 Panax quinquefolius Nutrition 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 235000008434 ginseng Nutrition 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
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
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
Present disclose provides a kind of mixed cloud management method, device and computing devices, belong to field of cloud computer technology.Method includes:It receives and accesses data packet, if accessed virtual machine is the virtual machine being deployed in public cloud, the Protocol IP address that the virtual machine being deployed in public cloud carried according to access data packet interconnects between the first network in public cloud, second IP address of the virtual machine in private clound being deployed in public cloud is obtained, the purpose IP address for accessing data packet is revised as being deployed in the second IP address of the virtual machine in public cloud;If it is the virtual machine being deployed in public cloud to access virtual machine, according to the second IP address for accessing the virtual machine being deployed in public cloud that data packet carries, the first IP address for being deployed in the virtual machine in public cloud is obtained, the source IP address for accessing data packet is revised as being deployed in the first IP address of the virtual machine in public cloud;It is sent to accessed virtual machine and accesses data packet.The disclosure realizes network interworking.
Description
Technical field
This disclosure relates to field of cloud computer technology, more particularly to a kind of mixed cloud management method, device and computing device.
Background technology
With the development of cloud computing technology, the development of mixed cloud has obtained more and more concerns, and mixed cloud has merged public affairs
There are cloud and private clound, is the Main Patterns and developing direction of cloud computing in recent years.Mixed cloud is wanted can be towards same enterprise tenant
Apply between private clound and public cloud flexible policy deployment and scheduling.The application of private clound generates explosive resource requirement,
When the inadequate resource of private clound, elastic telescopic to the interim borrowing resource of public cloud.Disaster-tolerant backup point of the public cloud as private clound
Etc. these application scenarios new challenge is also proposed to mixed cloud.Therefore, data center wants to interconnect at a high speed, it is desirable to be able to
The network being managed collectively on the network and private clound in public cloud, realizes network interworking.
Operation has the first virtual machine in private clound, and being run in public cloud has the second virtual machine;In order to realize the net of private clound
The network interworking of network and public cloud disposes first agent's equipment on the first virtual machine, the second generation is disposed on the second virtual machine
Manage equipment.When the first virtual machine accesses the second virtual machine, the first virtual machine sends access request, the visit to first agent's equipment
Ask that request carries the IP address of the second virtual machine;First agent's equipment is to second agent's device forwards access request;The second generation
Reason equipment forwards the access request to the second virtual machine, to realize that the first virtual machine accesses the second virtual machine.
During realizing the disclosure, the inventor finds that the existing technology has at least the following problems:
In the above method, needs to configure the virtual machine in mixed cloud, lead to the poor universality of the above method.
Invention content
In order to solve problems in the prior art, the embodiment of the present disclosure provides a kind of mixed cloud management method, device and meter
Calculate equipment.The technical solution is as follows:
In a first aspect, the embodiment of the present disclosure provides a kind of mixed cloud management method, the method is applied in mixed cloud pipe
In supernode HyperNode in reason system, the method includes:
It receives and accesses the access data packet that virtual machine is sent, the access data packet is for accessing accessed virtual machine;
If the accessed virtual machine is the virtual machine being deployed in public cloud, carried according to the access data packet
The Protocol IP address that the virtual machine being deployed in public cloud interconnects between the first network in the public cloud obtains institute
Second IP address of the virtual machine being deployed in public cloud in private clound is stated, the purpose IP address for accessing data packet is repaiied
It is changed to the second IP address of the virtual machine being deployed in public cloud, the access data are sent to the accessed virtual machine
Packet;
If the virtual machine that accesses is the virtual machine being deployed in public cloud, carried according to the access data packet
The virtual machine being deployed in public cloud the second IP address, first of the virtual machine in public cloud is deployed in described in acquisition
IP address, the source IP address for accessing data packet is revised as to the first IP of the virtual machine being deployed in public cloud
Location sends the access data packet to the accessed virtual machine.
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
It is described according to the void being deployed in described in the access data packet carrying in public cloud in a possible design
Intend the Protocol IP address interconnected between first network of the machine in the public cloud, is deployed in described in acquisition virtual in public cloud
Second IP address of the machine in private clound, including:
According to the first IP address of the virtual machine being deployed in public cloud, from the first IP address and the second IP address
The second IP address of the virtual machine in public cloud is deployed in described in being obtained in correspondence;
Correspondingly, the 2nd IP according to the virtual machine being deployed in described in the access data packet carrying in public cloud
Address is deployed in the first IP address of the virtual machine in public cloud described in acquisition, including:
According to the second IP address of the virtual machine being deployed in public cloud, from the first IP address and the second IP address
The first IP address of the virtual machine in public cloud is deployed in described in being obtained in correspondence.
In the embodiments of the present disclosure, HyperNode stores the correspondence of the first IP address and the second IP address, therefore,
When obtaining the second IP address for being deployed in the virtual machine in public cloud, according to the first IP of the virtual machine being deployed in public cloud
Address, from obtaining the 2nd IP for being deployed in the virtual machine in public cloud in the correspondence of the first IP address and the second IP address
Location, when obtaining the first IP address for being deployed in virtual machine in public cloud, according to the of the virtual machine being deployed in public cloud
Two IP address are deployed in second of the virtual machine in public cloud from acquisition in the correspondence of the first IP address and the second IP address
IP address, to improve the accuracy for obtaining IP address.
In a possible design, described to receive before accessing the access data packet that virtual machine is sent, the method is also
Including:
Receive the virtual machine being deployed in public cloud that the second cloud gateway Cloud GW in the public cloud are sent
The first IP address and the second IP address, the first IP address of the virtual machine being deployed in public cloud is described second
What Cloud GW were obtained from the virtual machine being deployed in public cloud, the second of the virtual machine being deployed in public cloud
IP address is that the 2nd Cloud GW are obtained from the management module in the mixing cloud management system;
The correspondence of the first IP address and the second IP address of the virtual machine in public cloud is deployed in described in foundation.
In the embodiments of the present disclosure, HyperNode establishes the first IP address for being deployed in virtual machine in public cloud and the
The correspondence of two IP address, in order to follow-up the first IP address according to the virtual machine being deployed in public cloud or the 2nd IP
Location is deployed in the second IP address of the virtual machine in public cloud from acquisition in the correspondence of the first IP address and the second IP address
Or first IP address.
In a possible design, the method further includes:
If by the virtual machine (vm) migration being deployed in private clound to the public cloud in the mixing cloud management system,
First IP address of the virtual machine in private clound in the public cloud is deployed in described in acquisition;
Second IP address of the virtual machine in private clound in the private clound is deployed in described in determination;
The correspondence of the first IP address and the second IP address of the virtual machine in private clound is deployed in described in foundation.
In the embodiments of the present disclosure, IP address camouflage is realized by HyperNode, new ARP is configured in HyperNode
Proxy realizes that MAC Address camouflage, IP address and MAC Address to realize virtual machine remain unchanged, no by ARP Proxy
It needs to do any network configuration change, you can realize virtual machine (vm) migration between cloud.
In a possible design, if the access virtual machine is the virtual machine being deployed in private clound, the quilt
It is the virtual machine being deployed in public cloud to access virtual machine, it is described access data packet also carry described in be deployed in void in public cloud
The media control of quasi- machine accesses MAC Address, and described to receive before accessing the access data packet that virtual machine is sent, the method is also wrapped
It includes:
The Address Resolution Protocol ARP request that the virtual machine being deployed in described in reception in private clound is sent, the ARP request are taken
The second IP address of the virtual machine in public cloud is deployed in described in band;
According to the second IP address of the virtual machine being deployed in public cloud, the void that is deployed in described in acquisition in public cloud
The MAC Address of quasi- machine;
To the MAC Address for the virtual machine being deployed in described in the virtual machine transmission being deployed in private clound in public cloud.
In the embodiments of the present disclosure, the MAC Address and second for being deployed in the virtual machine in public cloud is stored in Hypernode
The correspondence of IP address, therefore, Hypernode can be obtained according to the second IP address of the virtual machine being deployed in public cloud
Take the MAC Address for the virtual machine being deployed in public cloud.
Second aspect, the embodiment of the present disclosure provide a kind of mixed cloud management method, and the method is applied in mixed cloud pipe
Management module in reason system, the method includes:
The distribution request that the virtual machine in the mixing cloud management system is sent is received, the distribution request carries the void
The MAC address of quasi- machine;
According to the MAC Address of the virtual machine, interconnected between second network of the virtual machine distribution in private clound
Protocol IP address;
The second IP address of the virtual machine is sent to the virtual machine.
In the embodiments of the present disclosure, management module is that the virtual machine mixed in cloud management system distributes the second IP address, from
Without being configured to the virtual machine in mixed cloud, you can realize network interworking.
In a possible design, the MAC Address according to the virtual machine distributes for the virtual machine privately owned
The Protocol IP address interconnected between the second network in cloud, including:
According to the MAC Address of the virtual machine, it is determined as the virtual machine from MAC Address and the correspondence of IP address
Distribute the second IP address in the private clound.
The third aspect, the embodiment of the present disclosure provide a kind of mixed cloud managing device, and described device is applied in mixed cloud pipe
In supernode HyperNode in reason system, and described device includes the mixing cloud management for executing first aspect offer
At least one module of method.
Fourth aspect, the embodiment of the present disclosure provide a kind of mixed cloud managing device, and described device is applied in mixed cloud pipe
In management module in reason system, and described device includes for executing the mixed cloud management method of second aspect offer extremely
A few module.
5th aspect, the embodiment of the present disclosure provide a kind of computing device, the computing device include the first communication interface,
First processor and first memory, first communication interface are built with the first processor and the first memory respectively
Vertical communication connection, the first processor are established with the first memory and are communicated to connect, and the first memory is for storing
Program code;First communication interface and the first processor are used to execute the mixed cloud manager of first aspect offer
Method.
6th aspect, the embodiment of the present disclosure provide a kind of computing device, the computing device include the second communication interface,
Second processor and second memory, second communication interface are built with the second processor and the second memory respectively
Vertical communication connection, the second processor are established with the second memory and are communicated to connect, and the second memory is for storing
Program code;Second communication interface and the second processor are used to execute the mixed cloud manager of second aspect offer
Method.
The advantageous effect brought of technical solution that the embodiment of the present disclosure provides includes:
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
Description of the drawings
Fig. 1-1 is the schematic diagram for the mixing cloud management system that the embodiment of the present disclosure provides;
Fig. 1-2 is the schematic diagram for the mixing cloud management system that the embodiment of the present disclosure provides;
Fig. 1-3 is the schematic diagram for the mixing cloud management system that the embodiment of the present disclosure provides;
Fig. 1-4 is the schematic diagram for the mixing cloud management system that the embodiment of the present disclosure provides;
Fig. 2 is the structural schematic diagram for the computing device that the embodiment of the present disclosure provides;
Fig. 3 is the mixed cloud management method flow chart that the embodiment of the present disclosure provides;
Fig. 4 is the mixed cloud management method flow chart that the embodiment of the present disclosure provides;
Fig. 5 is the mixed cloud management method flow chart that the embodiment of the present disclosure provides;
Fig. 6 is the mixed cloud management method flow chart that the embodiment of the present disclosure provides;
Fig. 7 is the mixed cloud management method flow chart that the embodiment of the present disclosure provides;
Fig. 8 is the mixed cloud management method flow chart that the embodiment of the present disclosure provides;
Fig. 9 is the mixed cloud management method flow chart that the embodiment of the present disclosure provides;
Figure 10 is the structural schematic diagram for the mixed cloud managing device that the embodiment of the present disclosure provides;
Figure 11 is the structural schematic diagram for the mixed cloud managing device that the embodiment of the present disclosure provides.
Specific implementation mode
To keep the purpose, technical scheme and advantage of the disclosure clearer, below in conjunction with attached drawing to disclosure embodiment party
Formula is described in further detail.
The alternative embodiment that any combination forms the disclosure may be used, herein no longer in above-mentioned all optional technical solutions
It repeats one by one.
Through this specification, flow table uses in the embodiment of the present application for controlling data flow in software defined network
Meet software defined network (full name in English:Openflow) flow table of agreement is as an example, can also use symbol in actual use
Close the flow table of other agreements.
Through this specification, common virtual switch (full name in English:Virtual switch, abbreviation:VS include) opening
Put virtualization software interchanger (full name in English:Open vSwitch, abbreviation:OVS), OVS is the void that an open source projects provide
Quasi- interchanger.
In this specification, data packet uses overlay encapsulation skills during transmission between public cloud and private clound
Art specifically may be used following any:Virtual expansible LAN (full name in English:virtual extensible local
Area network, abbreviation:VXLAN) technology uses the network virtualization (full name in English of general routing:network
Virtualization using generic routing encapsulation, abbreviation:NVGRE) technology and stateless biography
Defeated tunnel (full name in English:Stateless transport tunneling, abbreviation:STT) technology.In illustrative specification,
Use VXLAN technologies.
A kind of mixing cloud management system is provided in this specification, referring to Fig. 1-1, which includes:Management module, first
Cloud gateway (full name in English:Cloud Gateway, abbreviation:Cloud GW), the 2nd Cloud GW, the first virtual expansible local
Net (full name in English:Virtual Extensible LAN, abbreviation:VXLAN) (English is complete for GW, the 2nd VXLAN GW and supernode
Claim:HyperNode).Wherein, management module includes resource management module and network service module, and network service module includes the
One dynamic host configuration protocol (full name in English:Dynamic Host Configuration Protocol, abbreviation:DHCP it) takes
Business device.
Management module, the first Cloud GW in this specification, the 2nd Cloud GW, the first VXLAN GW, the 2nd VXLAN
GW, HyperNode, and be deployed in public cloud and run on computing device with each virtual machine for being deployed in private clound.Often
The structural schematic diagram of a computing device such as Fig. 2.Each computing device can be actually server.
Each computing device may include communication interface 110, processor 120 and memory 130, and communication interface 110 is distinguished
It establishes and communicates to connect with processor 120 and memory 130, processor 120 and memory 130 establish communication connection.
Memory 130 may include volatile memory (full name in English:Volatile memory), such as arbitrary access
Memory (full name in English:Random-access memory, abbreviation:RAM);Memory can also include nonvolatile memory
(full name in English:Non-volatile memory), such as read-only memory (full name in English:Read-only memory, abbreviation:
ROM), flash memory (full name in English:Flash memory), hard disk (full name in English:Hard disk drive, abbreviation:
) or solid state disk (full name in English HDD:Solid state drive, abbreviation:SSD);Memory 130 can also include above-mentioned kind
The combination of the memory of class.It when realizing technical solution provided by the present application, is provided for realizing the disclosure by software
The program code of mixed cloud management method preserves in memory 130, and is executed by processor 120.
Each computing device is communicated by communication interface 110 with each module in mixing cloud management system.
Processor 120 can be central processing unit (full name in English:Central processing unit, abbreviation:CPU).
Due to either management module, the first Cloud GW, the 2nd Cloud GW, the first VXLAN GW, the 2nd VXLAN
GW, HyperNode actually can be by running on the software realization on virtual machine, and the deployment of virtual machine is more flexible.Therefore,
Management module, the first Cloud GW, the 2nd Cloud GW, the first VXLAN GW, the 2nd VXLAN GW, HyperNode and portion
Be deployed on public cloud and be deployed in private clound each virtual machine in actual deployment, deployment can also be merged.For example, first
VXLAN GW can also be deployed on the computing device for the private clound for having deployed virtual machine, and the 2nd VXLAN GW can also portion
On the computing device for the public cloud for having deployed virtual machine, HyperNode and the 2nd VXLAN GW can be deployed in together for administration
The computing device of one public cloud is first-class.First Cloud GW and the first VXLAN GW be respectively the corresponding Cloud GW of private clound and
VXLAN GW, the 2nd Cloud GW and the 2nd VXLAN GW are respectively public cloud corresponding Cloud GW and VXLAN GW.
Management module connects with the first Cloud GW, the 2nd Cloud GW, the first VXLAN GW and the 2nd VXLAN GW respectively
It connects.First Cloud GW respectively with where the virtual machine being deployed in private clound host and the first VXLAN GW be connected, second
Cloud GW are connected with the 2nd VXLAN GW and HyperNode respectively.First VXLAN GW respectively be deployed in private clound
Host where virtual machine is connect with the 2nd VXLAN GW, and the 2nd VXLAN GW are connected with HyperNode.
Resource management module, for providing mixing cloud service to the user, which can be managing computing resources
(for example, creating virtual machine), storage resource management (for example, creating volume), network resource management (for example, creating subnet).
Network service module creates the network service of needs, such as DHCP clothes for the demand according to resource management module
Business etc..
First Cloud GW provide a set of system for the resource to provide in service access interface operation cloud for private clound
One interface is used for mixing cloud system;And network configuration is carried out to private clound according to mixing cloud management system requirements, for example, to the
One VXLAN GW carry out network configuration (as generated flow table issuance to the first VXLAN GW).
2nd Cloud GW provide a set of system for the resource to provide in service access interface operation cloud for public cloud
One interface is used for mixing cloud system;And network configuration is carried out to public cloud according to mixing cloud management system requirements, for example, to the
Two VXLAN GW carry out network configuration (as generated flow table issuance to the 2nd VXLAN GW).
The HyperNode passes through second in public cloud for intercepting and capturing the data packet for being deployed in the virtual machine in public cloud
Dynamic Host Configuration Protocol server is that same first Dynamic Host Configuration Protocol server of the first IP address for the virtual machine distribution being deployed in public cloud is that this is deployed in
In public cloud virtual machine distribution the second IP address converted mutually, to realization be deployed in the virtual machine in public cloud with
Second IP address accesses mutually.
First VXLAN GW realize the intercommunication between public cloud and private clound for being communicated with the 2nd VXLAN GW.
2nd VXLAN GW realize the intercommunication between public cloud and private clound for being communicated with the first VXLAN GW.
Host where being deployed in the virtual machine in private clound can also include agency's (full name in English:Agent), should
Agent, for coordinating mixing cloud management system to complete the configuration of host.
It further include router (full name in English in public cloud:Router), which is used for as HyperNode and is deployed in
Virtual machine in public cloud carries out data forwarding.
It should be noted that HyperNode may operate in public cloud virtual machine.First Cloud GW can
To be deployed in inside private clound, can also be deployed in outside private clound;2nd Cloud GW can be deployed in inside public cloud,
It can be deployed in outside public cloud.In the embodiment of the present disclosure, not to the deployed position of the first Cloud GW and the 2nd Cloud GW
Make specific restriction, as long as can guarantee network interworking.Connection described in the embodiment of the present disclosure includes wired connection or wireless
Connection.
In Fig. 1-1 it is deployed in outside private clound with the first Cloud GW, the 2nd Cloud GW are deployed in outside public cloud
It is illustrated for portion.Referring to Fig. 1-2, the first Cloud GW are deployed in inside private clound, and the 2nd Cloud GW are deployed in publicly-owned
Inside cloud.Referring to Fig. 1-3, the first Cloud GW are deployed in outside private clound, and the 2nd Cloud GW are deployed in inside public cloud.Ginseng
See that Fig. 1-4, the first Cloud GW are deployed in inside private clound, the 2nd Cloud GW are deployed in outside public cloud.For example, first
Cloud GW are deployed on the computing device outside private clound, and the 2nd Cloud GW are deployed in the computing device outside private clound
On.
It should be noted that being deployed in public cloud in the mixing cloud management system administration provided by the embodiment of the present disclosure
Virtual machine and be deployed in private clound virtual machine when, need according to the first VXLAN GW of the above connection relation pair, second
VXLAN GW, the first Cloud GW, the 2nd Cloud GW, HyperNode are disposed, and configuration management face data and data surface
Network interworking;And the 2nd Cloud GW of configuration create the account information used when the virtual machine being deployed in public cloud and
The network information.Routing rule is configured in the 2nd Cloud GW kinds so that the 2nd Cloud GW were created is deployed in public cloud
The network default next-hop of virtual machine is HyperNode.
It should be noted that the dotted line in Fig. 1-1 to 1-4 indicates to transmit control plane data flow, solid line between two network elements
Transmission services face data stream between two network elements of expression.
When being managed to mixed cloud, it is necessary first to network is created in mixing cloud management system, in follow-up private clound
Virtual machine and public cloud in virtual machine can be in on-hook to this network.Referring to Fig. 3, the process for creating network includes:
Step 201:Network service module obtains the subnet information of network to be created.
When creating network, user can input subnet information to network service module;Network service module receives user
The subnet information of input.Wherein, the agreement (full name in English that subnet information can interconnect between the network of subnet section:
Internet Protocol, abbreviation:IP) address, for example, the IP address of subnet section can be 192.168.0.0/24.
Step 202:Network service module creates network according to the subnet information.
Network service module creates VXLAN networks according to the subnet information, mixes the virtual machine mounting in cloud management system
Into the VXLAN networks.
Step 203:Network service module is first Dynamic Host Configuration Protocol server of network configuration.
First Dynamic Host Configuration Protocol server is used to distribute IP address for the virtual machine accessed in the VXLAN networks.
Step 204:Network service module sends the mark of the first Dynamic Host Configuration Protocol server to the virtual machine accessed in the network.
Media access control (the full name in English for accessing the virtual machine in the network is stored in network service module:Media
Access Control, abbreviation:MAC) address, according to access the network in virtual machine MAC Address, to access the network in
Virtual machine send the first Dynamic Host Configuration Protocol server mark.Access that virtual machine in the network receives that network service module sends the
The mark of one Dynamic Host Configuration Protocol server.Wherein, the server identification of the first Dynamic Host Configuration Protocol server can be the IP of first Dynamic Host Configuration Protocol server
Location or MAC Address etc. are in the embodiments of the present disclosure not especially limited the server identification of the first Dynamic Host Configuration Protocol server.
After the virtual machine being deployed in private clound and the virtual machine being deployed in public cloud access the network, the first DHCP clothes
Business device is the virtual machine being deployed in private clound and the virtual machine being deployed in public cloud distribution IP address.As shown in figure 4, first
Dynamic Host Configuration Protocol server is the process for the virtual machine distribution IP address being deployed in private clound, including:
Step 301:The virtual machine being deployed in private clound in private clound sends the first distribution to the first Dynamic Host Configuration Protocol server
Request, the first distribution request carry the MAC Address of the virtual machine being deployed in private clound.
The virtual machine being deployed in private clound in private clound has got the first Dynamic Host Configuration Protocol server in step 202
Server identification, the virtual machine being deployed in private clound send the first distribution request, the first distribution request to the first Cloud GW
Carry the server identification of the MAC Address and the first Dynamic Host Configuration Protocol server of the virtual machine being deployed in private clound;First Cloud
GW receives the first distribution request that the virtual machine being deployed in private clound is sent, according to the server mark of the first Dynamic Host Configuration Protocol server
Know, the first distribution request is forwarded to the first Dynamic Host Configuration Protocol server.
Wherein, this is deployed in the host where the virtual machine in private clound and establishes network company between network service module
It connects, this is deployed in server identification of the virtual machine in private clound according to the first Dynamic Host Configuration Protocol server, by the network connection, to
One Dynamic Host Configuration Protocol server sends the first distribution request.
Step 302:First Dynamic Host Configuration Protocol server receives the first distribution request of the virtual machine being deployed in private clound transmission,
It is deployed in the MAC Address of the virtual machine in private clound according to this, obtains the IP address of the virtual machine being deployed in private clound.
MAC Address and the correspondence of IP address are configured in first Dynamic Host Configuration Protocol server;Correspondingly, the first Dynamic Host Configuration Protocol server
It is deployed in the MAC Address of the virtual machine in private clound according to this, obtains the IP address of the virtual machine being deployed in private clound
Step can be:
First Dynamic Host Configuration Protocol server is deployed in the MAC Address of the virtual machine in private clound according to this, from MAC Address and IP address
Correspondence in obtain the IP address of the virtual machine being deployed in private clound.
For example, the correspondence of the MAC Address and IP address that are stored in the first Dynamic Host Configuration Protocol server is as shown in table 1 below:
Table 1
MAC Address | IP address |
MAC1 | 192.168.0.3 |
MAC2 | 192.168.0.4 |
MAC3 | 192.168.0.5 |
MAC4 | 192.168.0.6 |
For example, the MAC Address for the virtual machine VM1 being deployed in private clound be MAC1, then the first Dynamic Host Configuration Protocol server according to
The IP address that MAC1 obtains VM1 from table 1 is 192.168.0.3;For another example, with being deployed in the MAC of the virtual machine VM2 in private clound
Location is MAC2, then the IP address that the first Dynamic Host Configuration Protocol server obtains VM2 according to MAC2 from table 1 is 192.168.0.4.
Step 303:First Dynamic Host Configuration Protocol server is deployed in the virtual machine in private clound to this and sends the IP address.
First Dynamic Host Configuration Protocol server sends the first assignment response to the first Cloud GW, and the first assignment response carries this and is deployed in
The MAC Address of virtual machine in private clound;First Cloud GW receive the first assignment response that the first Dynamic Host Configuration Protocol server is sent, root
The MAC Address of the virtual machine in private clound is deployed according to this, being deployed in the virtual machine in private clound to this forwards the IP address.
Step 304:The virtual machine being deployed in private clound receives the IP address that the first Dynamic Host Configuration Protocol server is sent.
In the embodiments of the present disclosure, the first Dynamic Host Configuration Protocol server mixed in cloud management system can be to be deployed in public cloud
Virtual machine distributes IP address, and the second Dynamic Host Configuration Protocol server in public cloud also can be the virtual machine distribution IP that is deployed in public cloud
Location;For the ease of distinguishing, the IP address that the second Dynamic Host Configuration Protocol server is the virtual machine distribution being deployed in public cloud is known as first
The IP address that first Dynamic Host Configuration Protocol server is the virtual machine distribution being deployed in public cloud is known as the second IP address, then by IP address
First DHCP and the second Dynamic Host Configuration Protocol server are the process for the virtual machine distribution IP address being deployed in public cloud as shown in figure 5, packet
It includes:
Step 401:Second Dynamic Host Configuration Protocol server hair of the virtual machine being deployed in public cloud into public cloud in public cloud
The second distribution request, the second distribution request is sent to carry the MAC Address of the virtual machine being deployed in public cloud.
After the virtual machine being deployed in public cloud in public cloud starts, the second Dynamic Host Configuration Protocol server in public cloud is obtained
Server identification sends the second distribution request to the 2nd Cloud GW, and the second distribution request carries this and is deployed in public cloud
The server identification of the MAC Address of virtual machine and the second Dynamic Host Configuration Protocol server;2nd Cloud GW receptions are deployed in public cloud
The second distribution request that virtual machine is sent is forwarded according to the server identification of the second Dynamic Host Configuration Protocol server to the second Dynamic Host Configuration Protocol server
Second distribution request.
It should be noted that before this step, user creates in mixing cloud management system and is deployed in public cloud
When virtual machine, management module sends to the 2nd Cloud GW and establishes request, and foundation request carries this and is deployed in public cloud
The device identification of virtual machine;2nd Cloud GW receive the foundation request that management module is sent and are called publicly-owned according to configuration information
The interface of cloud creates the virtual machine being deployed in public cloud.Wherein, which includes account information and network identity.
Step 402:Second Dynamic Host Configuration Protocol server receives the second distribution request of the virtual machine being deployed in public cloud transmission,
The MAC Address of the virtual machine in public cloud is deployed according to this, with obtaining the first IP of the virtual machine being deployed in public cloud
Location.
MAC Address and the correspondence of IP address are configured in second Dynamic Host Configuration Protocol server;Correspondingly, the second Dynamic Host Configuration Protocol server
The MAC Address of the virtual machine in public cloud is deployed according to this, with obtaining the first IP of the virtual machine being deployed in public cloud
The step of location can be:
Second Dynamic Host Configuration Protocol server is deployed in the MAC Address of the virtual machine in public cloud according to this, from MAC Address and IP address
Correspondence in obtain the first IP address of the virtual machine being deployed in public cloud.
For example, the correspondence of the MAC Address and IP address that are stored in the second Dynamic Host Configuration Protocol server is as shown in table 2 below:
Table 2
MAC Address | IP address |
MAC3 | 172.16.0.101 |
MAC4 | 172.16.0.102 |
For example, the MAC Address for the virtual machine VM3 being deployed in public cloud be MAC3, then the second Dynamic Host Configuration Protocol server according to
The first IP address that MAC3 obtains VM3 from table 2 is 172.16.0.101;For another example, it is deployed in the virtual machine VM4's in public cloud
MAC Address is MAC4, then the first IP address that the second Dynamic Host Configuration Protocol server obtains VM4 according to MAC4 from table 2 is
172.16.0.102。
Step 403:Second Dynamic Host Configuration Protocol server is deployed in the virtual machine in public cloud to this and sends the first IP address.
Second Dynamic Host Configuration Protocol server sends the second assignment response to the 2nd Cloud GW, and the second assignment response carries this and is deployed in
The MAC Address of virtual machine in public cloud;2nd Cloud GW receive the second assignment response that the second Dynamic Host Configuration Protocol server is sent, root
It is publicly-owned according to this
Step 404:The virtual machine being deployed in public cloud receives the first IP address that the second Dynamic Host Configuration Protocol server is sent.
Step 405:The 2nd Cloud GW in public cloud are obtained from the virtual machine being deployed in public cloud is deployed in public affairs
There is the first IP address of the virtual machine in cloud.
Step 406:2nd Cloud GW obtain the of the virtual machine being deployed in public cloud from the first Dynamic Host Configuration Protocol server
Two IP address.
2nd Cloud GW send inquiry request to the first Dynamic Host Configuration Protocol server, and inquiry request carrying is deployed in public cloud
Virtual machine MAC Address;First Dynamic Host Configuration Protocol server receives the inquiry request that the 2nd Cloud GW are sent, and public affairs are deployed according to this
The MAC Address for having the virtual machine in cloud obtains the second IP address of the virtual machine being deployed in public cloud, to the 2nd Cloud
GW sends the second IP address for being deployed in the virtual machine in public cloud.
First Dynamic Host Configuration Protocol server is deployed in the MAC Address of the virtual machine in public cloud according to this, obtain this be deployed in it is publicly-owned
The step of second IP address of the virtual machine in cloud can be:
First Dynamic Host Configuration Protocol server is deployed in the MAC Address of the virtual machine in public cloud according to this, from MAC Address and IP address
Correspondence in obtain the second IP address of the virtual machine being deployed in public cloud.
For example, the MAC Address for the virtual machine VM3 being deployed in public cloud be MAC3, then the first Dynamic Host Configuration Protocol server according to
The second IP address that MAC3 obtains VM3 from table 1 is 192.168.0.5;For another example, it is deployed in the virtual machine VM4's in public cloud
MAC Address is MAC4, then the second IP address that the first Dynamic Host Configuration Protocol server obtains VM4 according to MAC4 from table 1 is
192.168.0.6。
Step 407:2nd Cloud GW are with sending the first IP of the virtual machine being deployed in public cloud to HyperNode
Location and the second IP address.
Step 408:This of the 2nd Cloud GW transmissions of HyperNode receptions is deployed in first of the virtual machine in public cloud
IP address and the second IP address establish the correspondence of the first IP address and the second IP address of the virtual machine being deployed in public cloud
Relationship.
Increase flow table in HyperNode;This is deployed in the first IP address of the virtual machine in public cloud by HyperNode
It is configured to the flow table with the correspondence of the second IP address.Increase address resolution protocol (full name in English in HyperNode:
Address Resolution Protocol, abbreviation:ARP) proxy server (full name in English:Proxy);ARP Proxy are used for
It changes the IP address of the data packet of the virtual machine being deployed in public cloud transmission and changes and be deployed in public cloud to this
The IP address for the data packet that virtual machine is sent.
For example, if HyperNode receives the data packet that the 2nd VXLAN GW are sent, the purpose IP address of the data packet
For the second IP address, then HyperNode is deployed in the second IP address of the virtual machine in public cloud according to this, obtains this and is deployed in
First IP address of the virtual machine in public cloud, by the destination address of the data packet be revised as this be deployed in it is virtual in public cloud
First IP address of machine.
For another example, if this is deployed in the virtual machine in public cloud, other virtual machines into the mixing cloud management system are sent
When data packet, which is revised as the source IP address of the data packet the first of the virtual machine being deployed in public cloud
IP address.
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
In mixing cloud management system, it can be accessed mutually between virtual machine, namely the void being deployed in private clound
Quasi- machine can access the virtual machine being deployed in public cloud, and the virtual machine being deployed in public cloud can access and be deployed in private clound
In virtual machine, the virtual machine being deployed in public cloud can also access the virtual machine being deployed in public cloud.Wherein, it is deployed in
The process that virtual machine in private clound accesses the virtual machine being deployed in public cloud is illustrated in fig. 6 shown below, including:
Step 501:The virtual machine being deployed in private clound sends ARP request to HyperNode, and ARP request carrying waits for
Second IP address of the virtual machine being deployed in public cloud accessed.
When being deployed in the virtual machine in public cloud due to the virtual machine access being deployed in private clound, acquisition is needed to be deployed in
Therefore the MAC Address of virtual machine in public cloud accesses the void being deployed in public cloud in the virtual machine in being deployed in private clound
Before quasi- machine, the virtual machine being deployed in private clound sends ARP request to HyperNode, and the ARP request is for obtaining the deployment
The MAC Address of virtual machine in public cloud.
This step can be realized by following steps 5011-5014, including:
5011:The virtual friendship of host where from the virtual machine being deployed in private clound to the virtual machine being deployed in private clound
It changes planes and sends ARP request, which carries the second IP address of the virtual machine being deployed in public cloud to be visited.
The virtual machine being deployed in private clound obtains the second IP address of the virtual machine being deployed in public cloud to be visited,
The IP address for the virtual machine being deployed according to this in private clound is deployed in the second IP address of the virtual machine in public cloud with this, really
The fixed virtual machine being deployed in public cloud is deployed in the virtual machine in private clound in the same VXLAN networks with this, to portion
The virtual switch for affixing one's name to the host where the virtual machine in private clound sends ARP request.
For example, the IP address for being deployed in the virtual machine in private clound is 192.168.0.3, this is deployed in public cloud
Second IP address of virtual machine is 192.168.0.5.Since 192.168.0.3 and 192.168.0.5 belong to the same network segment, because
This, this is deployed in the virtual machine in private clound and determines that this is deployed in the void that the virtual machine in public cloud is deployed in this in private clound
Quasi- machine is in the same vxlan networks.
5012:Virtual switch receives the ARP request that the virtual machine being deployed in private clound is sent, to the 2nd VXLAN GW
Send the ARP request.
The ARP request is packaged into VXLAN data packets by virtual switch, and the VXLAN data are sent to the 2nd VXLAN GW
Packet.
5013:2nd VXLAN GW receive the ARP request that virtual switch is sent, and being sent to the first VXLAN GW should
ARP request.
2nd VXLAN GW obtain the mark of the first VXLAN GW, according to the mark of the first VXLAN GW to the first VXLAN
GW sends the ARP request.
The correspondence of mark configured with vxlan networks and VXLAN GW in 2nd VXLAN GW;Correspondingly, second
VXLAN GW, which obtain the step of mark of the first VXLAN GW, to be:
2nd VXLAN GW are deployed in the second IP address of the virtual machine in public cloud according to this, and it is publicly-owned to determine that this is deployed in
Vxlan networks where virtual machine in cloud are deployed in the vxlan networks where the virtual machine in public cloud according to this, from
The mark of the first VXLAN GW is obtained in the correspondence of the mark of vxlan networks and VXLAN GW.
It should be noted that the 2nd VXLAN GW first encapsulate the vxlan data packets, to the first VXLAN GW hairs again
Send the vxlan data packets after encapsulation again.
5014:First VXLAN GW receive the ARP request that the 2nd VXLAN GW are sent, and the ARP is sent to HyperNode
Request.
Step 502:HyperNode receives the ARP request that the virtual machine being deployed in private clound is sent, according to the deployment
Second IP address of the virtual machine in public cloud, obtains the MAC Address of the virtual machine being deployed in public cloud.
MAC Address and the 2nd IP configured with the virtual machine being deployed in public cloud in ARP Proxy in HyperNode
The correspondence of address;Correspondingly, HyperNode is deployed in the second IP address of the virtual machine in public cloud according to this, obtain
This, which is deployed in the step of MAC Address of the virtual machine in public cloud, to be:
HyperNode sends the second IP address of the virtual machine being deployed in public cloud to ARP Proxy;ARP
Proxy receives this that HyperNode sends and is deployed in the second IP address of the virtual machine in public cloud, according to this be deployed in it is publicly-owned
Second IP address of the virtual machine in cloud, from MAC Address and the correspondence of the second IP address obtaining this is deployed in public cloud
In virtual machine MAC Address, the MAC Address of the virtual machine being deployed in public cloud is sent to HyperNode;
HyperNode receives the MAC Address that this that ARP Proxy send is deployed in the virtual machine in public cloud.
Step 503:HyperNode sends the virtual machine being deployed in public cloud to the virtual machine being deployed in private clound
MAC Address.
HyperNode can be deployed in the transmission of the virtual machine in private clound along the request path for sending ARP request to this should
It is deployed in the MAC Address of the virtual machine in public cloud, process can be realized by following steps 5031-5034, including:
5031:HyperNode sends the MAC Address of the virtual machine being deployed in public cloud to the first VXLAN GW.
5032:First VXLAN GW receive the MAC that this that HyperNode sends is deployed in the virtual machine in public cloud
Location sends the MAC Address of the virtual machine being deployed in public cloud to the 2nd VXLAN GW.
5033:2nd VXLAN GW receive the MAC that this that the first VXLAN GW send is deployed in the virtual machine in public cloud
Address sends the void being deployed in public cloud to the virtual switch of the host where being deployed in the virtual machine in private clound
The MAC Address of quasi- machine.
5034:Virtual switch receives the MAC that this that the 2nd VXLAN GW send is deployed in the virtual machine in public cloud
Location is deployed in the MAC Address that the virtual machine in private clound sends the virtual machine being deployed in public cloud to this.
Step 504:This for the virtual machine reception HyperNode transmissions being deployed in private clound is deployed in the void in public cloud
The MAC Address of quasi- machine.
After the virtual machine being deployed in private clound gets the MAC Address of the virtual machine being deployed in public cloud, lead to
Following steps 505 are crossed to be deployed in public cloud to access this to the virtual machine being deployed in public cloud transmission access data packet
Virtual machine.
Step 505:The virtual machine being deployed in private clound is sent to HyperNode accesses data packet, the access data packet
Source IP address be that this is deployed in IP address of the virtual machine in private clound, source MAC is that this is deployed in the void in private clound
The MAC Address of quasi- machine, destination IP are second IP address for being deployed in the virtual machine in public cloud, and target MAC (Media Access Control) address is the portion
Affix one's name to the MAC Address of the virtual machine in public cloud.
This step can be realized by following steps 5051-5054, including:
5051:The virtual friendship of host where from the virtual machine being deployed in private clound to the virtual machine being deployed in private clound
Transmission of changing planes accesses data packet.
5052:Virtual switch receives the access data packet that the virtual machine being deployed in private clound is sent, to the 2nd VXLAN
GW sends the access data packet.
Virtual switch is packaged the access data packet, by the access that the access packet encapsulation is VXLAN formats
Data packet sends the access data packet after encapsulation to the 2nd VXLAN GW.
5053:2nd VXLAN GW receive the access data packet that virtual switch is sent, and being sent to the first VXLAN GW should
Access data packet.
2nd VXLAN GW re-start encapsulation to the access data packet, and the visit after encapsulation is sent to the first VXLAN GW
Ask data packet.
5054:First VXLAN GW receive the access data packet that the 2nd VXLAN GW are sent, and being sent to HyperNode should
Access data packet.
Step 506:HyperNode receives the access data packet that the virtual machine being deployed in private clound is sent, by the access
The purpose IP address of data packet is revised as the first IP address.
HyperNode decapsulates the access data packet, the access data packet of ethernet format is obtained, according to the portion
The second IP address for affixing one's name to virtual machine in public cloud, from obtaining the portion in the correspondence of the second IP address and the first IP address
The first IP address of the virtual machine in public cloud is affixed one's name to, with being revised as the first IP by the purpose IP address of the access data packet
Location.
Step 507:HyperNode is deployed in the virtual machine in public cloud according to the first IP address, to this and sends the access
Data packet.
HyperNode sends the access data packet to Router nodes;Router nodes receive being somebody's turn to do for HyperNode transmissions
Data packet is accessed, according to the destination address of the access data packet:First IP address is deployed in the hair of the virtual machine in public cloud to this
Give the access data packet.
Step 508:This is deployed in the virtual machine in public cloud and receives the access data packet that HyperNode is sent.
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
The process that the virtual machine being deployed in public cloud accesses the virtual machine being deployed in private clound is illustrated in fig. 7 shown below, and is wrapped
It includes:
Step 601:The virtual machine being deployed in public cloud is sent to HyperNode accesses data packet, the access data packet
Source IP be the virtual machine being deployed in public cloud the first IP address, source MAC be this be deployed in it is virtual in public cloud
The MAC Address of machine, purpose IP address are the IP address of the virtual machine being deployed in private clound to be visited, and target MAC (Media Access Control) address is
This is deployed in the MAC Address of the virtual machine in private clound.
This step can be realized by following steps 6011-6012, including:
6011:It is deployed in Router node of the virtual machine in public cloud into public cloud and sends access data packet.
The virtual machine being deployed in public cloud obtains the IP address of the virtual machine being deployed in private clound to be visited, according to
The IP address for being deployed in the virtual machine in private clound is deployed in the first IP address of the virtual machine in public cloud with this, and determining should
The virtual machine being deployed in public cloud is deployed in the virtual machine in private clound not in the same vxlan networks with this, needs public affairs
There are the Router nodes in cloud to be forwarded, is then deployed in Router node of the virtual machine in public cloud into public cloud and sends
Access data packet.
6012:Router nodes receive the access data packet that the virtual machine being deployed in public cloud is sent, to
HyperNode forwards the access data packet.
Router nodes are transmitted to HyperNode according to routing rule, by the access data packet.Wherein, the routing rule
Next-hop for the Router nodes is HyperNode.
Step 602:HyperNode receives the access data packet that the virtual machine being deployed in public cloud is sent, by the access
The source IP address of data packet is revised as being deployed in the second IP address of the virtual machine in public cloud.
HyperNode is deployed in the first IP address of the virtual machine in public cloud according to this, from the first IP address and second
The second IP address that the virtual machine being deployed in public cloud is obtained in the correspondence of IP address, by the source of the access data packet
IP address is revised as being deployed in the second IP address of the virtual machine in public cloud.
Step 603:HyperNode sends the access data packet to the 2nd VXLAN GW.
Step 604:2nd VXLAN GW receive the access data packet that HyperNode is sent, to the first VXLAN GW hairs
Give the access data packet.
The access data packet is packaged by the 2nd VXLAN GW, and the access number after encapsulation is sent to the first VXLAN GW
According to packet.
Step 605:First VXLAN GW receive the access data packet that the 2nd VXLAN GW are sent, to this be deployed in it is privately owned
Virtual machine in cloud sends the access data packet.
The access data packet is packaged by the first VXLAN GW, and being deployed in the virtual machine in private clound to this sends the visit
Ask data packet.
First VXLAN GW send the visit to the virtual switch of the host where being deployed in the virtual machine in private clound
Ask data packet, which receives the access data packet that the first VXLAN GW are sent, and is solved to the access data packet
Encapsulation is deployed in the access data packet after the virtual machine in private clound sends decapsulation to this.
Step 606:This is deployed in the virtual machine in private clound and receives the access data packet that the first VXLAN GW are sent.
The process that the virtual machine being deployed in public cloud accesses the virtual machine being deployed in public cloud is illustrated in fig. 8 shown below, and is
Convenient for description, the virtual machine being deployed in public cloud will be accessed and be known as being deployed in the first virtual machine in public cloud, will be interviewed
The virtual machine being deployed in public cloud asked is known as being deployed in the second virtual machine in public cloud, including:
Step 701:The first virtual machine being deployed in public cloud is sent to HyperNode accesses data packet, the access number
Source IP address according to packet is the first IP address of the first virtual machine being deployed in public cloud, and source MAC is publicly-owned to be deployed in
The MAC Address of the first virtual machine in cloud, purpose IP address are the first IP address of the second virtual machine being deployed in public cloud,
Target MAC (Media Access Control) address is the MAC Address for the second virtual machine being deployed in public cloud.
This step can be realized by following steps 7011-7012, including:
7011:It is deployed in Router node of the first virtual machine in public cloud into public cloud and sends access data packet.
7012:Router nodes in public cloud receive the access number that the first virtual machine being deployed in public cloud is sent
According to packet, the access data packet is forwarded to HyperNode.
Step 702:HyperNode receives the access data packet that the first virtual machine being deployed in public cloud is sent, will
The source IP address of the access data packet is revised as being deployed in the second IP address of the first virtual machine in public cloud, by the access number
It is revised as being deployed in the second IP address of the second virtual machine in public cloud according to the purpose IP address of packet.
HyperNode is according to the first IP address of the first virtual machine being deployed in public cloud and is deployed in public cloud
First IP address of the second virtual machine is deployed in from being obtained in the correspondence of the first IP address and the second IP address in public cloud
The first virtual machine the second IP address and the second IP address of the second virtual machine for being deployed in public cloud, by the access data
The source IP address of packet is revised as being deployed in the second IP address of the first virtual machine in public cloud, by the purpose of the access data packet
IP address is revised as being deployed in the second IP address of the second virtual machine in public cloud.
Step 703:HyperNode sends the access data packet to the second virtual machine being deployed in public cloud.
HyperNode sends the access data packet to Router nodes, which receives what HyperNode was sent
The access data packet, according to the second IP address of the second virtual machine being deployed in public cloud, to be deployed in public cloud
Two virtual machines forward the access data packet.
Step 704:The second virtual machine being deployed in public cloud receives the access data packet that HyperNode is sent.
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
In mixing cloud management system, virtual machine can be moved to from private clound in public cloud, and in migration, be not required to
Do the change of any network configuration, you can with ensureing MAC Address and the second the 3rd IP for the virtual machine being deployed in public cloud
Location remains unchanged.Referring to Fig. 9, the process of migration includes:
Step 801:Private clound virtual machine sends third distribution request to the second Dynamic Host Configuration Protocol server, and third distribution request carries
This is deployed in the MAC Address of the virtual machine in private clound.
When mixing cloud management system moves to the virtual machine being deployed in private clound in private clound from private clound, private clound
Virtual machine needs the second Dynamic Host Configuration Protocol server into public cloud to ask the IP address in public cloud.
Step 802:Second Dynamic Host Configuration Protocol server receives the third distribution request that the virtual machine being deployed in private clound is sent, root
It is deployed in the MAC Address of the virtual machine in private clound according to this, obtains the first IP address of the virtual machine being deployed in private clound.
It is that the IP address for being deployed in the distribution of the virtual machine in private clound claims by the second Dynamic Host Configuration Protocol server for the ease of distinguishing
It is that the IP address for being deployed in the distribution of the virtual machine in private clound is known as the 2nd IP by the first Dynamic Host Configuration Protocol server for the first IP address
Address.
Step 803:Second Dynamic Host Configuration Protocol server, which to this is deployed in the virtual machine in private clound and sends this, to be deployed in private clound
Virtual machine the first IP address.
Step 804:This for virtual machine reception the second Dynamic Host Configuration Protocol server transmission being deployed in private clound is deployed in private clound
In virtual machine the first IP address.
Step 805:2nd Cloud GW, which are deployed in from this in the virtual machine in private clound, to be obtained this and is deployed in private clound
Virtual machine the first IP address.
Step 806:2nd Cloud GW obtain the virtual machine being deployed in private clound from the first Dynamic Host Configuration Protocol server
Second IP address.
Step 807:2nd Cloud GW are with sending the first IP of the virtual machine being deployed in private clound to HyperNode
Location and the second IP address.
Step 808:This of the 2nd Cloud GW transmissions of HyperNode receptions is deployed in first of the virtual machine in private clound
IP address and the second IP address establish the correspondence of the first IP address and the second IP address of the virtual machine being deployed in private clound
Relationship.
In the embodiments of the present disclosure, IP address camouflage is realized by HyperNode, new ARP is configured in HyperNode
Proxy realizes that MAC Address camouflage, IP address and MAC Address to realize virtual machine remain unchanged, no by ARP Proxy
It needs to do any network configuration change, you can realize virtual machine (vm) migration between cloud.
The embodiment of the present disclosure additionally provides a kind of mixed cloud managing device, which can be set by calculating shown in Fig. 2
It is standby to realize, application-specific integrated circuit (full name in English can also be passed through:application-specific integrated
Circuit, abbreviation:ASIC) realization or programmable logic device (full name in English:Programmable logic device, contracting
It writes:PLD it) realizes.Above-mentioned PLD can be Complex Programmable Logic Devices (full name in English:complex programmable
Logic device, abbreviation:CPLD), FPGA, Universal Array Logic (full name in English:Generic array logic, abbreviation:
GAL) or it is arbitrarily combined.The mixed cloud managing device is used for above-mentioned mixed cloud management method.Pass through the above-mentioned mixing of software realization
When cloud management method, mixed cloud managing device may be software module.
Group leader's structural schematic diagram of data clusters device is as shown in Figure 10, including:First receiving module 901, first manages
Module 902 and the second management module 903.
When first receiving module 901 works, the reception processing in above-mentioned mixed cloud management method is executed.
When first management module 902 and the second management module 903 work, the management in above-mentioned mixed cloud management method is executed
Processing.
In addition, the device, which further includes the second receiving module and first, establishes module.
When second receiving module works, the 2nd Cloud in the reception public cloud in above-mentioned mixed cloud management method is executed
The first IP address and the second IP address for the virtual machine being deployed in public cloud that GW is sent.
First establish module work when, execute the foundation in above-mentioned mixed cloud management method be deployed in it is virtual in public cloud
The correspondence of the first IP address and the second IP address of machine.
In addition, the device further includes:First acquisition module, determining module and second establish module.
When first acquisition module works, the acquisition processing in above-mentioned mixed cloud management method is executed.
Determining module at work, executes in above-mentioned mixed cloud management method and determines processing.
Second establishes module at work, executes the void that the foundation in above-mentioned mixed cloud management method is deployed in private clound
The correspondence of the first IP address and the second IP address of quasi- machine.
In addition, the device further includes:Third receiving module, the second acquisition module and the first sending module.
Third receiving module at work, executes the reception processing in above-mentioned mixed cloud management method.
Second acquisition module at work, executes the acquisition processing in above-mentioned mixed cloud management method.
First sending module at work, executes the transmission processing in above-mentioned mixed cloud management method.
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
The embodiment of the present disclosure additionally provides a kind of mixed cloud managing device, which can be set by calculating shown in Fig. 2
It is standby to realize, it can also be realized by ASIC or PLD is realized.Above-mentioned PLD can be CPLD, FPGA, GAL or its arbitrary combination.It should
Mixed cloud managing device is used for above-mentioned mixed cloud management method.When mixed cloud management method above-mentioned by software realization, mixed cloud
Managing device may be software module.
Group leader's structural schematic diagram of data clusters device is as shown in figure 11, including:4th receiving module 1001, distribution module
1002 and second sending module 1003.
4th receiving module 1001 at work, executes point for receiving virtual machine and sending in above-mentioned mixed cloud management method
Processing with request.
Distribution module 1002 at work, executes the processing of the distribution IP address in above-mentioned mixed cloud management method.
Second sending module 1003 at work, executes the processing of the transmission IP address in above-mentioned mixed cloud management method.
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
The embodiment of the present disclosure additionally provides a kind of computing device, and institutional framework schematic diagram is as shown in Fig. 2, logical including first
Believe that interface, first processor and first memory, the first communication interface are established with first processor and first memory logical respectively
Letter connection, first processor are established with first memory and are communicated to connect, and first memory is for storing program code.
First processor executes the program code stored in first memory to execute above-mentioned mixed cloud management method.The meter
It calculates equipment namely has run the computing device of aforementioned HyperNode.
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
The embodiment of the present disclosure additionally provides a kind of computing device, and institutional framework schematic diagram is as shown in Fig. 2, logical including second
Believe that interface, second processor and second memory, the second communication interface are established with second processor and second memory logical respectively
Letter connection, second processor are established with second memory and are communicated to connect, and second memory is for storing program code.
Second processor executes the program code stored in second memory to execute above-mentioned mixed cloud management method.The meter
It calculates equipment namely has run the computing device of aforementioned management module.
In the embodiments of the present disclosure, by HyperNode to access data packet source IP address or purpose IP address into
Row modification sends modified access data packet to accessed virtual machine, without being carried out to the virtual machine in mixed cloud
Configuration, you can realize network interworking.
One of ordinary skill in the art will appreciate that realizing that all or part of step of above-described embodiment can pass through hardware
It completes, relevant hardware can also be instructed to complete by program, the program can be stored in a kind of computer-readable
In storage medium, storage medium mentioned above can be read-only memory, disk or CD etc..
The foregoing is merely the preferred embodiments of the disclosure, not to limit the disclosure, all spirit in the disclosure and
Within principle, any modification, equivalent replacement, improvement and so on should be included within the protection domain of the disclosure.
Claims (21)
1. a kind of mixed cloud management method, which is characterized in that the method applies the supernode in mixing cloud management system
In HyperNode, the method includes:
It receives and accesses the access data packet that virtual machine is sent, the access data packet is for accessing accessed virtual machine;
If the accessed virtual machine is the virtual machine being deployed in public cloud, according to access data packet carrying
The Protocol IP address that the virtual machine being deployed in public cloud interconnects between the first network in the public cloud, obtains the portion
Second IP address of the virtual machine in private clound in public cloud is affixed one's name to, the purpose IP address for accessing data packet is revised as
Second IP address of the virtual machine being deployed in public cloud sends the access data packet to the accessed virtual machine;
If the virtual machine that accesses is the virtual machine being deployed in public cloud, the institute carried according to the access data packet
The second IP address of the virtual machine being deployed in public cloud is stated, the first IP of the virtual machine in public cloud is deployed in described in acquisition
The source IP address for accessing data packet is revised as the first IP address of the virtual machine being deployed in public cloud by location, to
The accessed virtual machine sends the access data packet.
2. according to the method described in claim 1, it is characterized in that, the deployment carried according to the access data packet
The Protocol IP address interconnected between first network of the virtual machine in the public cloud in public cloud is deployed in described in acquisition
Second IP address of the virtual machine in private clound in public cloud, including:
According to the first IP address of the virtual machine being deployed in public cloud, from the correspondence of the first IP address and the second IP address
The second IP address of the virtual machine in public cloud is deployed in described in being obtained in relationship;
Correspondingly, the 2nd IP according to the virtual machine being deployed in described in the access data packet carrying in public cloud
Location is deployed in the first IP address of the virtual machine in public cloud described in acquisition, including:
According to the second IP address of the virtual machine being deployed in public cloud, from the correspondence of the first IP address and the second IP address
The first IP address of the virtual machine in public cloud is deployed in described in being obtained in relationship.
3. method according to claim 1 or 2, which is characterized in that described receive accesses the access data that virtual machine is sent
Before packet, the method further includes:
Receive the of the virtual machine being deployed in public cloud that the second cloud gateway Cloud GW in the public cloud are sent
First IP address of one IP address and the second IP address, the virtual machine being deployed in public cloud is the 2nd Cloud GW
It is obtained from the virtual machine being deployed in public cloud, the second IP address of the virtual machine being deployed in public cloud is
What the 2nd Cloud GW were obtained from the management module in the mixing cloud management system;
The correspondence of the first IP address and the second IP address of the virtual machine in public cloud is deployed in described in foundation.
4. according to the method described in claim 1, it is characterized in that, the method further includes:
If by the virtual machine (vm) migration being deployed in private clound to the public cloud in the mixing cloud management system, obtain
First IP address of the virtual machine being deployed in private clound in the public cloud;
Second IP address of the virtual machine in private clound in the private clound is deployed in described in determination;
The correspondence of the first IP address and the second IP address of the virtual machine in private clound is deployed in described in foundation.
5. according to the method described in claim 1, it is characterized in that, if the access virtual machine is to be deployed in private clound
Virtual machine, the accessed virtual machine are the virtual machine being deployed in public cloud, and the access data packet also carries the deployment
Virtual machine in public cloud media control access MAC Address, it is described receive access virtual machine send access data packet it
Before, the method further includes:
The Address Resolution Protocol ARP request that the virtual machine being deployed in described in reception in private clound is sent, the ARP request carry institute
State the second IP address of the virtual machine being deployed in public cloud;
According to the second IP address of the virtual machine being deployed in public cloud, the virtual machine that is deployed in described in acquisition in public cloud
MAC Address;
To the MAC Address for the virtual machine being deployed in described in the virtual machine transmission being deployed in private clound in public cloud.
6. a kind of mixed cloud management method, which is characterized in that the method applies the management module in mixing cloud management system,
The method includes:
The distribution request that the virtual machine in the mixing cloud management system is sent is received, the distribution request carries the virtual machine
MAC address;
According to the MAC Address of the virtual machine, the association interconnected between second network of the virtual machine distribution in private clound
Discuss IP address;
The second IP address of the virtual machine is sent to the virtual machine.
7. according to the method described in claim 6, it is characterized in that, the MAC Address according to the virtual machine, is the void
The Protocol IP address that quasi- machine distribution interconnects between the second network in private clound, including:
According to the MAC Address of the virtual machine, it is determined as the virtual machine distribution from MAC Address and the correspondence of IP address
The second IP address in the private clound.
8. a kind of mixed cloud managing device, which is characterized in that described device applies the supernode in mixing cloud management system
In HyperNode, described device includes:
First receiving module, for receiving the access data packet for accessing virtual machine and sending, the access data packet is for accessing quilt
Access virtual machine;
First management module, if being the virtual machine being deployed in public cloud for the accessed virtual machine, according to the visit
Ask the association interconnected between first network of the virtual machine being deployed in public cloud of data packet carrying in the public cloud
Discuss IP address, second IP address of the virtual machine in private clound being deployed in described in acquisition in public cloud, by the access data
The purpose IP address of packet is revised as the second IP address of the virtual machine being deployed in public cloud, to the accessed virtual machine
Send the access data packet;
Second management module, if being the virtual machine being deployed in public cloud for the access virtual machine, according to described
The second IP address of the virtual machine being deployed in public cloud that data packet carries is accessed, is deployed in public cloud described in acquisition
Virtual machine the first IP address, by the source IP address for accessing data packet be revised as it is described be deployed in it is virtual in public cloud
First IP address of machine sends the access data packet to the accessed virtual machine.
9. device according to claim 8, which is characterized in that
First management module is additionally operable to the first IP address of the virtual machine being deployed according in public cloud, from first
The second IP address of the virtual machine in public cloud is deployed in described in being obtained in the correspondence of IP address and the second IP address;
Second management module is additionally operable to the second IP address of the virtual machine being deployed according in public cloud, from first
The first IP address of the virtual machine in public cloud is deployed in described in being obtained in the correspondence of IP address and the second IP address.
10. device according to claim 8 or claim 9, which is characterized in that described device further includes:
Second receiving module, the second cloud gateway Cloud GW for receiving in the public cloud send described in be deployed in it is publicly-owned
The first IP address and the second IP address of virtual machine in cloud, the first IP address of the virtual machine being deployed in public cloud are
What the 2nd Cloud GW were obtained from the virtual machine being deployed in public cloud, it is described be deployed in it is virtual in public cloud
Second IP address of machine is that the 2nd Cloud GW are obtained from the management module in the mixing cloud management system;
First establishes module, the first IP address and the second IP address for establishing the virtual machine being deployed in public cloud
Correspondence.
11. device according to claim 8, which is characterized in that described device further includes:
First acquisition module, if for arriving the virtual machine (vm) migration being deployed in private clound in the mixing cloud management system
First IP address of the virtual machine in private clound in the public cloud is deployed in the public cloud, described in acquisition;
Determining module, second IP address of the virtual machine in the private clound for being deployed in described in determination in private clound;
Second establishes module, the first IP address and the second IP address for establishing the virtual machine being deployed in private clound
Correspondence.
12. device according to claim 8, which is characterized in that if the access virtual machine is to be deployed in private clound
Virtual machine, the accessed virtual machine is the virtual machine being deployed in public cloud, and the access data packet also carries the portion
The media control for affixing one's name to the virtual machine in public cloud accesses MAC Address, and described device further includes:
Third receiving module, the Address Resolution Protocol ARP request sent for receiving the virtual machine being deployed in private clound,
The second IP address of the virtual machine in public cloud is deployed in described in the ARP request carrying;
Second acquisition module, the second IP address for being deployed in the virtual machine in public cloud according to, obtains the deployment
The MAC Address of virtual machine in public cloud;
First sending module, for virtual in public cloud to being deployed in described in the virtual machine transmission being deployed in private clound
The MAC Address of machine.
13. a kind of mixed cloud managing device, which is characterized in that described device applies the management mould in mixing cloud management system
Block, described device include:
4th receiving module, the distribution request sent for receiving the virtual machine in the mixing cloud management system, the distribution
Request carries the MAC address of the virtual machine;
Distribution module distributes the second network in private clound for the MAC Address according to the virtual machine for the virtual machine
Between the Protocol IP address that interconnects;
Second sending module, the second IP address for sending the virtual machine to the virtual machine.
14. device according to claim 13, which is characterized in that
The distribution module is additionally operable to the MAC Address according to the virtual machine, from MAC Address and the correspondence of IP address
It is determined as the virtual machine and distributes the second IP address in the private clound.
15. a kind of computing device, which is characterized in that the computing device includes the first communication interface, first processor and first
Memory, first communication interface is established with the first processor and the first memory communicate to connect respectively, described
First processor is established with the first memory and is communicated to connect, and the first memory is for storing program code;
First communication interface, for receiving the access data packet for accessing virtual machine and sending, the access data packet is for visiting
Ask accessed virtual machine;
The first processor, if being the virtual machine being deployed in public cloud for the accessed virtual machine, according to described
What the virtual machine being deployed in public cloud that access data packet carries interconnected between the first network in the public cloud
Protocol IP address, second IP address of the virtual machine in private clound being deployed in described in acquisition in public cloud, by the access number
It is revised as the second IP address of the virtual machine being deployed in public cloud according to the purpose IP address of packet, is accessed virtually to described
Machine sends the access data packet;
The first processor, if it is the virtual machine being deployed in public cloud to be additionally operable to the access virtual machine, according to
It is deployed in the second IP address of the virtual machine in public cloud described in the access data packet carrying, is deployed in described in acquisition publicly-owned
The source IP address for accessing data packet is revised as described be deployed in public cloud by the first IP address of the virtual machine in cloud
First IP address of virtual machine sends the access data packet to the accessed virtual machine.
16. computing device according to claim 15, which is characterized in that
The first processor is additionally operable to the first IP address of the virtual machine being deployed according in public cloud, from the first IP
The second IP address of the virtual machine in public cloud is deployed in described in being obtained in the correspondence of address and the second IP address;
The first processor is additionally operable to the second IP address of the virtual machine being deployed according in public cloud, from the first IP
The first IP address of the virtual machine in public cloud is deployed in described in being obtained in the correspondence of address and the second IP address.
17. computing device according to claim 15 or 16, which is characterized in that
First communication interface is additionally operable to receive the deployment that the second cloud gateway Cloud GW in the public cloud are sent
The first IP address and the second IP address of virtual machine in public cloud, the first IP of the virtual machine being deployed in public cloud
Address is what the 2nd Cloud GW were obtained from the virtual machine being deployed in public cloud, described to be deployed in public cloud
Virtual machine the second IP address be the 2nd Cloud GW from it is described mixing cloud management system in management module in obtain
's;
The first processor, with being additionally operable to the first IP address and the 2nd IP for the virtual machine being deployed in described in establishing in public cloud
The correspondence of location.
18. computing device according to claim 15, which is characterized in that
The first processor, if being additionally operable to move the virtual machine being deployed in private clound in the mixing cloud management system
It moves on in the public cloud, first IP address of the virtual machine in private clound in the public cloud is deployed in described in acquisition;
The first processor is additionally operable to be deployed in twoth IP of the virtual machine in private clound in the private clound described in determination
Address;
The first processor, with being additionally operable to the first IP address and the 2nd IP for the virtual machine being deployed in described in establishing in private clound
The correspondence of location.
19. computing device according to claim 15, which is characterized in that
First communication interface, the address resolution protocol that the virtual machine for being additionally operable to be deployed in private clound described in receiving is sent
ARP request, the ARP request carry described in be deployed in the second IP address of virtual machine in public cloud;
The first processor is additionally operable to be deployed in the second IP address of virtual machine in public cloud according to, described in acquisition
It is deployed in the MAC Address of the virtual machine in public cloud;
First communication interface, be additionally operable to the virtual machine that is deployed in private clound send described in be deployed in public cloud
Virtual machine MAC Address.
20. a kind of computing device, which is characterized in that the computing device includes the second communication interface, second processor and second
Memory, second communication interface is established with the second processor and the second memory communicate to connect respectively, described
Second processor is established with the second memory and is communicated to connect, and the second memory is for storing program code;
Second communication interface, the distribution request sent for receiving the virtual machine in the mixing cloud management system are described
Distribution request carries the MAC address of the virtual machine;
The second processor, for according to the MAC Address of the virtual machine, be virtual machine distribution in private clound the
The Protocol IP address interconnected between two networks;
Second communication interface is additionally operable to send the second IP address of the virtual machine to the virtual machine.
21. computing device according to claim 20, which is characterized in that
The second processor is additionally operable to the MAC Address according to the virtual machine, from the correspondence of MAC Address and IP address
In be determined as the virtual machine and distribute the second IP address in the private clound.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710056696.3A CN108347493B (en) | 2017-01-25 | 2017-01-25 | Hybrid cloud management method and device and computing equipment |
CN202010526862.3A CN111835878A (en) | 2017-01-25 | 2017-01-25 | Hybrid cloud management method and device and computing equipment |
PCT/CN2017/108197 WO2018137369A1 (en) | 2017-01-25 | 2017-10-28 | Hybrid cloud management method, device, and computing apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710056696.3A CN108347493B (en) | 2017-01-25 | 2017-01-25 | Hybrid cloud management method and device and computing equipment |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010526862.3A Division CN111835878A (en) | 2017-01-25 | 2017-01-25 | Hybrid cloud management method and device and computing equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN108347493A true CN108347493A (en) | 2018-07-31 |
CN108347493B CN108347493B (en) | 2020-06-26 |
Family
ID=62961819
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010526862.3A Pending CN111835878A (en) | 2017-01-25 | 2017-01-25 | Hybrid cloud management method and device and computing equipment |
CN201710056696.3A Active CN108347493B (en) | 2017-01-25 | 2017-01-25 | Hybrid cloud management method and device and computing equipment |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010526862.3A Pending CN111835878A (en) | 2017-01-25 | 2017-01-25 | Hybrid cloud management method and device and computing equipment |
Country Status (2)
Country | Link |
---|---|
CN (2) | CN111835878A (en) |
WO (1) | WO2018137369A1 (en) |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108900637A (en) * | 2018-08-08 | 2018-11-27 | 北京百度网讯科技有限公司 | Method for transmitting information and device |
CN109936629A (en) * | 2019-02-27 | 2019-06-25 | 山东浪潮云信息技术有限公司 | A kind of mixed cloud network interconnecting method and system |
CN110213391A (en) * | 2019-07-12 | 2019-09-06 | 腾讯科技(深圳)有限公司 | A kind of configuration method and device of internet protocol address |
CN110704167A (en) * | 2019-10-09 | 2020-01-17 | 腾讯科技(深圳)有限公司 | Method, device, equipment and storage medium for creating virtual machine |
CN111049925A (en) * | 2019-12-20 | 2020-04-21 | 网易(杭州)网络有限公司 | Hybrid cloud network system, communication system and communication method |
CN111130974A (en) * | 2018-11-01 | 2020-05-08 | 深信服科技股份有限公司 | Network intercommunication system and method based on multi-cloud environment |
CN111629084A (en) * | 2020-07-28 | 2020-09-04 | 腾讯科技(深圳)有限公司 | Data transmission method and device, storage medium and electronic equipment |
CN111818081A (en) * | 2020-07-22 | 2020-10-23 | 腾讯科技(深圳)有限公司 | Virtual encryption machine management method and device, computer equipment and storage medium |
CN112235400A (en) * | 2020-10-14 | 2021-01-15 | 腾讯科技(深圳)有限公司 | Communication method, communication system, communication apparatus, server, and storage medium |
CN112671859A (en) * | 2020-12-15 | 2021-04-16 | 中国人寿保险股份有限公司 | Hybrid cloud management method and hybrid cloud system |
CN112738250A (en) * | 2020-12-30 | 2021-04-30 | 中国建设银行股份有限公司 | Hybrid cloud interconnection special line management system |
CN112887278A (en) * | 2021-01-12 | 2021-06-01 | 北京东方网信科技股份有限公司 | Interconnection system and method of private cloud and public cloud |
JP2022541381A (en) * | 2019-09-06 | 2022-09-26 | ホアウェイ クラウド コンピューティング テクノロジーズ カンパニー リミテッド | COMMUNICATION METHOD, GATEWAY, AND MANAGEMENT METHOD AND APPARATUS IN HYBRID CLOUD ENVIRONMENT |
CN115529245A (en) * | 2021-06-25 | 2022-12-27 | 深信服科技股份有限公司 | Stream information completion method and device, cloud host equipment and computer storage medium |
CN115865862A (en) * | 2022-11-21 | 2023-03-28 | 北京奇艺世纪科技有限公司 | Data access method, system, device, electronic equipment and storage medium |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114938309A (en) * | 2022-06-21 | 2022-08-23 | 北京华创方舟科技集团有限公司 | Private cloud building and deploying method |
CN115208891A (en) * | 2022-07-15 | 2022-10-18 | 济南浪潮数据技术有限公司 | Hybrid cloud elastic expansion method, device, equipment and storage medium |
CN116208482A (en) * | 2023-03-10 | 2023-06-02 | 深圳市星卡科技股份有限公司 | Project hybrid cloud deployment method and device |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102664972A (en) * | 2012-05-11 | 2012-09-12 | 中科方德软件有限公司 | Method and device for mapping address in virtual network |
CN104660479A (en) * | 2015-02-13 | 2015-05-27 | 南京华讯方舟通信设备有限公司 | Networking method and network system |
CN105657078A (en) * | 2015-12-29 | 2016-06-08 | 联想(北京)有限公司 | Data transmission method, data transmission device and multi-layer network manager |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9584445B2 (en) * | 2013-05-07 | 2017-02-28 | Equinix, Inc. | Direct connect virtual private interface for a one to many connection with multiple virtual private clouds |
CN105933235B (en) * | 2016-07-07 | 2019-02-19 | 北京邮电大学 | Data communications method and device |
-
2017
- 2017-01-25 CN CN202010526862.3A patent/CN111835878A/en active Pending
- 2017-01-25 CN CN201710056696.3A patent/CN108347493B/en active Active
- 2017-10-28 WO PCT/CN2017/108197 patent/WO2018137369A1/en active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102664972A (en) * | 2012-05-11 | 2012-09-12 | 中科方德软件有限公司 | Method and device for mapping address in virtual network |
CN104660479A (en) * | 2015-02-13 | 2015-05-27 | 南京华讯方舟通信设备有限公司 | Networking method and network system |
CN105657078A (en) * | 2015-12-29 | 2016-06-08 | 联想(北京)有限公司 | Data transmission method, data transmission device and multi-layer network manager |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108900637A (en) * | 2018-08-08 | 2018-11-27 | 北京百度网讯科技有限公司 | Method for transmitting information and device |
CN111130974A (en) * | 2018-11-01 | 2020-05-08 | 深信服科技股份有限公司 | Network intercommunication system and method based on multi-cloud environment |
CN109936629A (en) * | 2019-02-27 | 2019-06-25 | 山东浪潮云信息技术有限公司 | A kind of mixed cloud network interconnecting method and system |
CN109936629B (en) * | 2019-02-27 | 2021-09-03 | 浪潮云信息技术股份公司 | Hybrid cloud network interconnection method and system |
CN110213391A (en) * | 2019-07-12 | 2019-09-06 | 腾讯科技(深圳)有限公司 | A kind of configuration method and device of internet protocol address |
JP2022541381A (en) * | 2019-09-06 | 2022-09-26 | ホアウェイ クラウド コンピューティング テクノロジーズ カンパニー リミテッド | COMMUNICATION METHOD, GATEWAY, AND MANAGEMENT METHOD AND APPARATUS IN HYBRID CLOUD ENVIRONMENT |
JP7413415B2 (en) | 2019-09-06 | 2024-01-15 | ホアウェイ クラウド コンピューティング テクノロジーズ カンパニー リミテッド | Communication method, gateway, and management method and device in a hybrid cloud environment |
US11888809B2 (en) | 2019-09-06 | 2024-01-30 | Huawei Technologies Co., Ltd. | Communication method, gateway, and management method and apparatus in hybrid cloud environment |
CN110704167A (en) * | 2019-10-09 | 2020-01-17 | 腾讯科技(深圳)有限公司 | Method, device, equipment and storage medium for creating virtual machine |
CN110704167B (en) * | 2019-10-09 | 2023-09-19 | 腾讯科技(深圳)有限公司 | Method, device, equipment and storage medium for creating virtual machine |
CN111049925A (en) * | 2019-12-20 | 2020-04-21 | 网易(杭州)网络有限公司 | Hybrid cloud network system, communication system and communication method |
CN111049925B (en) * | 2019-12-20 | 2022-07-19 | 网易(杭州)网络有限公司 | Hybrid cloud network system, communication system and communication method |
CN111818081A (en) * | 2020-07-22 | 2020-10-23 | 腾讯科技(深圳)有限公司 | Virtual encryption machine management method and device, computer equipment and storage medium |
CN111818081B (en) * | 2020-07-22 | 2023-05-23 | 腾讯科技(深圳)有限公司 | Virtual encryption machine management method, device, computer equipment and storage medium |
CN111629084A (en) * | 2020-07-28 | 2020-09-04 | 腾讯科技(深圳)有限公司 | Data transmission method and device, storage medium and electronic equipment |
CN111629084B (en) * | 2020-07-28 | 2020-11-03 | 腾讯科技(深圳)有限公司 | Data transmission method and device, storage medium and electronic equipment |
CN112235400A (en) * | 2020-10-14 | 2021-01-15 | 腾讯科技(深圳)有限公司 | Communication method, communication system, communication apparatus, server, and storage medium |
CN112235400B (en) * | 2020-10-14 | 2024-02-02 | 腾讯科技(深圳)有限公司 | Communication method, communication system, communication device, server, and storage medium |
CN112671859A (en) * | 2020-12-15 | 2021-04-16 | 中国人寿保险股份有限公司 | Hybrid cloud management method and hybrid cloud system |
CN112738250A (en) * | 2020-12-30 | 2021-04-30 | 中国建设银行股份有限公司 | Hybrid cloud interconnection special line management system |
CN112887278A (en) * | 2021-01-12 | 2021-06-01 | 北京东方网信科技股份有限公司 | Interconnection system and method of private cloud and public cloud |
CN112887278B (en) * | 2021-01-12 | 2022-11-11 | 北京东方网信科技股份有限公司 | Interconnection system and method of private cloud and public cloud |
CN115529245A (en) * | 2021-06-25 | 2022-12-27 | 深信服科技股份有限公司 | Stream information completion method and device, cloud host equipment and computer storage medium |
CN115865862A (en) * | 2022-11-21 | 2023-03-28 | 北京奇艺世纪科技有限公司 | Data access method, system, device, electronic equipment and storage medium |
CN115865862B (en) * | 2022-11-21 | 2024-06-04 | 北京奇艺世纪科技有限公司 | Data access method, system, device, electronic equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
CN108347493B (en) | 2020-06-26 |
CN111835878A (en) | 2020-10-27 |
WO2018137369A1 (en) | 2018-08-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108347493A (en) | Mixed cloud management method, device and computing device | |
CN112470436B (en) | Systems, methods, and computer-readable media for providing multi-cloud connectivity | |
WO2021135344A1 (en) | Virtual private cloud and non-public cloud data center communication method, virtual private cloud and non-public cloud data center communication configuration method, and related apparatuses | |
US11102079B2 (en) | Cross-regional virtual network peering | |
US12081451B2 (en) | Resource placement templates for virtual networks | |
CN105657081B (en) | The method, apparatus and system of DHCP service are provided | |
CN104115453B (en) | A kind of method and apparatus realizing virtual machine communication | |
TWI744359B (en) | Method for data transmission and network equipment | |
US8725898B1 (en) | Scalable port address translations | |
EP2982097B1 (en) | Method and apparatus for exchanging ip packets among network layer 2 peers | |
WO2018054177A1 (en) | Inter-cloud communication method and related device, inter-cloud communication configuration method and related device | |
JP7413415B2 (en) | Communication method, gateway, and management method and device in a hybrid cloud environment | |
CN105634770B (en) | The method and apparatus for disposing virtual extended local area network | |
CN116210204A (en) | System and method for VLAN switching and routing services | |
CN109716717A (en) | From software-defined network controller management virtual port channel switching equipment peer-to-peer | |
CN109791482A (en) | Scalable service is found in micro services environment | |
CN112702252A (en) | Message processing method, system and related equipment | |
CN105656796B (en) | The method and apparatus for realizing three layers of virtual extended local area network forwarding | |
US20140233569A1 (en) | Distributed Gateway in Virtual Overlay Networks | |
CN114338606B (en) | Public cloud network configuration method and related equipment | |
CN113660164B (en) | Message forwarding method and network equipment | |
CN113542111B (en) | Message forwarding method and network equipment | |
CN116982295A (en) | Packet flow in cloud infrastructure based on cached and non-cached configuration information | |
CN116982306A (en) | Extending IP addresses in overlay networks | |
Vrijders et al. | Reducing the complexity of virtual machine networking |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant | ||
TR01 | Transfer of patent right | ||
TR01 | Transfer of patent right |
Effective date of registration: 20220211 Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province Patentee after: Huawei Cloud Computing Technologies Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |