Virtual network data exchange method and device

Abstract

The embodiment of the invention discloses a virtual network data exchange method and device. A specific embodiment of the method comprises the following steps: responding to a received service request, taking a virtual IP address of a target virtual machine of the service request as a target IP address of the service request, taking an IP address of a source host machine of the service request as a source IP address of the service request, and sending a data packet corresponding to the service request to an exchange kernel; in the exchange kernel, querying an outbound transmission rule represented by the virtual IP address of the target virtual machine according to a pre-configured outbound rule table; packaging a data packet corresponding to the service request according to an outbound transmission rule, and sending the packaged data packet to the overlay network from the underlay network. According to the embodiment, the virtual network does not need to create numerous additional devices on each service host machine, and a large amount of memory occupied by the host machine due to device creation is saved.

Description

technical field [0001] The embodiments of the present disclosure relate to the field of computer technology, and in particular to a virtual network data exchange method and device. Background technique [0002] With the continuous innovation and development of Internet technology, an important capability for cloud computing service providers is to provide virtual private cloud VPC (Virtual Private Cloud) services to isolate the virtual machine VM (Virtual Machine) of many users in a way that facilitates fault migration open. For the currently mainly used tunnel technology, public services need to support the encapsulation of the traffic of each user VPC into the tunnel of its corresponding VPC, and complete the switching of user data flow from the physical network underlay to the virtual network overlay in the tunnel. The data flow of the VM in the VPC enters the public service, and the public service needs to support decapsulation to the tunnel corresponding to each user's...

AI Technical Summary

Problems solved by technology

However, because each device only encapsulates / decapsulates the data flow corresponding to the tunnel of one VPC, and the public service supports thousands of VPCs, it is necessary to create a large number of tunnel devices on each public service host, which takes up a lot of resources on the host. Memory, and it is very difficult to query, configure, and count data streams based on VPC information in many tunnel devices, making it very difficult to operate and maintain in the scenario of creating a large number of tunnel devices. In addition, due to the lack of interfaces that can be directly invoked by applications , making it very difficult to set and maintain data flow exchange rules for a huge number of VPCs in cloud computing multi-tenant scenarios; second, create a separate protocol stack, dynamically manage the tunnel information of each VPC in the protocol stack, and based on these information Encapsulate and decapsulate the data flow to realize the dynamic conversion of the data flow between the underlay network and the overlay network. However, for each public service, it is difficult to create a separate set of protocol stacks and support data flow exchange in it. Later maintenance very expensive

Images