A method and system for VPC peering connection

Abstract

The application discloses a VPC peer-to-peer connection method and system, and belongs to the technical field of cloud computing, which comprises the following steps: configuring a local VPP in a local VPC, wherein the local VPP comprises a local subnet IpTable, a local subnet BridgeDomain, a local subnet VxlanTunnel, a local subnet LOOP, a local interconnection BridgeDomain, a local interconnection IpTable, a local interconnection LOOP and a local interconnection VxlanTunnel; configuring a peer VPP in the local VPC, wherein the peer VPP comprises a peer subnet IpTable, a peer subnet BridgeDomain, a peer subnet VxlanTunnel, a peer subnet LOOP, a peer interconnection BridgeDomain, a peer interconnection IpTable, a peer interconnection LOOP and a peer interconnection VxlanTunnel; transmitting a data packet to the local VPP by a local cloud host; transmitting the data packet to the peer VPP by the local VPP; and transmitting the data packet to a peer cloud host by the peer VPP, so as to establish a peer-to-peer connection between the local cloud host and the peer cloud host. The VPC peer-to-peer connection method provided by the application can realize data intercommunication between cloud hosts in different VPCs, and is convenient for system management and data delivery.

Description

Technical Field

[0001] This invention belongs to the field of cloud computing technology, specifically relating to a VPC peer-to-peer connection method and system. Background Technology

[0002] Virtual Private Cloud (VPC) is a core concept in IaaS (Infrastructure as a Service) cloud networking, allowing multiple user cloud hosts to communicate with each other within the same VPC. In cloud networking services, users typically need to create the cloud hosts they want to communicate with within the same VPC to facilitate network configuration management and data distribution.

[0003] However, in the actual application of IaaS network services, due to rapid business growth, incomplete initial planning, security requirements, and other issues, users often need to achieve interoperability between cloud hosts in different VPCs. Currently, there is a lack of technology to achieve interoperability between cloud hosts in different VPCs, making data exchange between cloud hosts in different VPCs difficult and hindering system management. Summary of the Invention

[0004] The purpose of this invention is to provide a VPC peering connection method and system that can solve the technical problems of data interoperability and system management difficulties between cloud hosts under different VPCs.

[0005] To solve the above-mentioned technical problems, the present invention is implemented as follows:

[0006] First aspect

[0007] This invention provides a VPC peering connection method, including:

[0008] S101: Configure the local VPP in the local VPC. The local VPP includes the local subnet IpTable, local subnet BridgeDomain, local subnet VxlanTunnel, local subnet LOOP, local interconnect BridgeDomain, local interconnect IpTable, local interconnect LOOP, and local interconnect VxlanTunnel.

[0009] S102: Configure the peer VPP in the local VPC. The peer VPP includes the peer subnet IpTable, peer subnet BridgeDomain, peer subnet VxlanTunnel, peer subnet LOOP, peer interconnect BridgeDomain, peer interconnect IpTable, peer interconnect LOOP and peer interconnect VxlanTunnel.

[0010] S103: The local cloud host transmits the data packet to the local VPP, and the local VPP transmits the data packet to the peer VPP;

[0011] S104: The peer VPP transmits the data packet to the peer cloud host to establish a peer connection between the local cloud host and the peer cloud host.

[0012] Second aspect

[0013] This invention provides a VPC peer-to-peer connection system, comprising:

[0014] The local configuration module is used to configure the local VPP in the local VPC. The local VPP includes the local subnet IpTable, local subnet BridgeDomain, local subnet VxlanTunnel, local subnet LOOP, local interconnect BridgeDomain, local interconnect IpTable, local interconnect LOOP and local interconnect VxlanTunnel.

[0015] The peer configuration module is used to configure the peer VPP in the peer VPC. The peer VPP includes the peer subnet IpTable, peer subnet BridgeDomain, peer subnet VxlanTunnel, peer subnet LOOP, peer interconnect BridgeDomain, peer interconnect IpTable, peer interconnect LOOP and peer interconnect VxlanTunnel.

[0016] The local transmission module is used for the local cloud host to transmit data packets to the local VPP, and the local VPP to transmit the data packets to the peer VPP;

[0017] The peer transmission module is used by the peer VPP to transmit the data packet to the peer cloud host, so as to establish a peer connection between the local cloud host and the peer cloud host through the local VPP and the peer VPP.

[0018] The present invention has at least the following beneficial effects:

[0019] In this embodiment of the invention, the local cloud host transmits data packets to the local VPP, the local VPP transmits the data packets to the peer VPP, and the peer VPP transmits the data packets to the peer cloud host, thereby establishing a peer-to-peer connection between the local cloud host and the peer cloud host. Through the VPC peer-to-peer connection method provided by this invention, data communication can be achieved between cloud hosts in different VPCs, facilitating system management and data distribution. Attached Figure Description

[0020] Figure 1 This is a flowchart illustrating a VPC peer-to-peer connection method provided in an embodiment of the present invention;

[0021] Figure 2 This is a schematic diagram of data traffic during a VPC peering connection provided in an embodiment of the present invention;

[0022] Figure 3 This is a schematic diagram of a VPC peer-to-peer connection system provided in an embodiment of the present invention.

[0023] The realization of the objective, functional characteristics and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0025] The following description, in conjunction with the accompanying drawings, details the VPC peer-to-peer connection method and system provided by the present invention through specific embodiments and application scenarios.

[0026] Example 1

[0027] Reference Figure 1 The diagram shows a flowchart of a VPC peer-to-peer connection method provided by an embodiment of the present invention.

[0028] Reference Figure 2 The diagram illustrates the data traffic during a VPC peering connection according to an embodiment of the present invention.

[0029] An embodiment of the present invention provides a VPC peering connection method, comprising:

[0030] S101: Configure the local VPP in the local VPC. The local VPP includes the local subnet IpTable, local subnet BridgeDomain, local subnet VxlanTunnel, local subnet LOOP, local interconnect BridgeDomain, local interconnect IpTable, local interconnect LOOP, and local interconnect VxlanTunnel.

[0031] VPP (Vector Packet Processor) is an extensible framework that provides high-quality L2, L3, and NAT functionality, characterized by high performance, modularity, and rich features. VPP's forwarding plane can utilize DPDK (DataPlane Development Kit) technology, providing a data plane library to handle packet transmission and reception. This bypasses the Linux kernel protocol stack, improving packet processing speed and achieving high forwarding performance, potentially even meeting network interface card (NIC) rate limiting.

[0032] In one possible implementation, S101 specifically includes:

[0033] S1011: Create the local subnet IpTable in the local VPC, and use the VPCID as the name of the local subnet IpTable;

[0034] S1012: Create the local subnet BridgeDomain in the local VPC, and use the VPCID as the name of the local subnet BridgeDomain;

[0035] S1013: Create the local cloud host VxlanTunnel in the local VPC. The tunnel source IP of the local cloud host VxlanTunnel is the tunnel address of the host machine where the cloud host is located, the destination IP is the VPP tunnel address, the VNI is the VNI corresponding to the local VPC, add it to the local subnet BridgeDomain, add the cloud host MAC address to the l2fib table of the local subnet BridgeDomain, and the outgoing interface is the local cloud host VxlanTunnel.

[0036] In particular, static configuration in the l2fib table of the BridgeDomain can prevent data flooding.

[0037] S1014: Create the local subnet LOOP in the local VPC, add the local subnet BridgeDomain to the local subnet LOOP using Bvi, configure the MAC address as the subnet gateway MAC address and the IP as the subnet gateway address in the local subnet LOOP, and add it to the local subnet IpTable;

[0038] S1015: Create the local interconnect BridgeDomain in the local VPC, and use the peer connection ID as the name of the local interconnect BridgeDomain;

[0039] S1016: Create the local interconnection IpTable in the local VPC, and add a default route skip table to the local subnet IpTable in the local interconnection IpTable;

[0040] S1017: Create the local interconnection LOOP in the local VPC, configure the IP address in the local interconnection LOOP as the local interconnection IP, the MAC address as the local interconnection MAC address, add it to the local interconnection BridgeDomain, add it to the local subnet IpTable, and add the peer interconnection IP and MAC address to the LoopArp table of the local interconnection LOOP.

[0041] In particular, static configuration in the LoopArp table of the local interconnection LOOP can avoid ARP learning;

[0042] S1018: Create the local interconnect VxlanTunnel in the local VPC. The tunnel source IP of the local interconnect VxlanTunnel is the local VPP tunnel IP, the destination IP is the peer VPP tunnel IP, the VNI is the peer connection VNI, add it to the peer connection BridgeDomain, add the peer interconnect MAC address to the l2fib table of the peer connection BridgeDomain, and the outgoing interface is the local interconnect VxlanTunnel.

[0043] Static configuration in the l2fib table of the peer-to-peer connection BridgeDomain can prevent data flooding.

[0044] S1019: Add a route to the local subnet IpTable with the destination being the peer subnet, the next-hop address being the peer interconnection address, and the outgoing interface being the local interconnection LOOP.

[0045] S102: Configure the peer VPP in the local VPC. The peer VPP includes the peer subnet IpTable, peer subnet BridgeDomain, peer subnet VxlanTunnel, peer subnet LOOP, peer interconnect BridgeDomain, peer interconnect IpTable, peer interconnect LOOP, and peer interconnect VxlanTunnel.

[0046] In one possible implementation, S102 specifically includes:

[0047] S1021: Create the peer subnet IpTable in the peer VPC, and name the peer subnet IpTable using VPCID;

[0048] S1022: Create the peer subnet BridgeDomain in the peer VPC, and name the peer subnet BridgeDomain using VPCID;

[0049] S1023: Create the peer cloud host VxlanTunnel in the peer VPC. The tunnel source IP of the peer cloud host VxlanTunnel is the tunnel address of the host machine where the cloud host is located, the destination IP is the VPP tunnel address, the VNI is the VNI corresponding to the peer VPC, add it to the peer subnet BridgeDomain, add the cloud host MAC address to the l2fib table of the peer subnet BridgeDomain, and the outgoing interface is the peer cloud host VxlanTunnel.

[0050] In particular, static configuration in the l2fib table of the BridgeDomain can prevent data flooding;

[0051] S1024: Create the peer subnet LOOP in the peer VPC, add the peer subnet BridgeDomain to the peer subnet LOOP using Bvi, configure the MAC address as the subnet gateway MAC address and the IP as the subnet gateway address in the peer subnet LOOP, and add it to the peer subnet IpTable.

[0052] S1025: Create the peer interconnect BridgeDomain in the peer VPC, the name of the peer interconnect BridgeDomain using the peer connection ID;

[0053] S1026: Create the peer interconnection IpTable in the peer VPC, and add a default route jump table to the peer subnet IpTable in the peer interconnection IpTable;

[0054] S1027: Create the peer interconnection LOOP in the peer VPC, configure the IP address in the peer interconnection LOOP as the peer interconnection IP, the MAC address as the peer interconnection MAC address, add it to the peer interconnection BridgeDomain, add it to the peer subnet IpTable, and add the local interconnection IP and MAC address to the LoopArp table of the peer interconnection LOOP.

[0055] In particular, static configuration in the LoopArp table of the local interconnection LOOP can avoid ARP learning;

[0056] S1028: Create the peer interconnect VxlanTunnel in the peer VPC. The tunnel source IP of the peer interconnect VxlanTunnel is the local VPP tunnel IP, the destination IP is the peer VPP tunnel IP, the VNI is the peer connection VNI, add it to the peer connection BridgeDomain, add the local interconnect MAC address to the l2fib table of the peer connection BridgeDomain, and the outgoing interface is the peer interconnect VxlanTunnel.

[0057] Static configuration in the l2fib table of the peer-to-peer connection BridgeDomain can prevent data flooding.

[0058] S1029: Add a route to the peer subnet IpTable with the destination being this subnet, the next hop address being the local interconnect address, and the outgoing interface being the peer interconnect LOOP.

[0059] S103: The local cloud host transmits the data packet to the local VPP, and the local VPP transmits the data packet to the peer VPP.

[0060] In one possible implementation, S103 specifically includes:

[0061] S1031: The local cloud host sends a data packet, which is determined by the compute node Vswitch to be peer-to-peer connection traffic. The destination MAC is the subnet gateway MAC, which is encapsulated as a VXLAN packet. The VXLAN destination IP is the VPP tunnel IP, and the VNI is the VNI corresponding to the local VPC. The packet is then sent to the local VPP.

[0062] S1032: The local cloud host VxlanTunnel receives VXLAN packets from the local cloud host, decapsulates the VXLAN packets, and hands them over to the peer-connected local subnet BridgeDomain;

[0063] S1033: The local VPP queries the l2fib table of the local subnet BridgeDomain through the destination MAC of the data packet, and forwards the decapsulated VXLAN packet to the local subnet LOOP;

[0064] S1034: The destination MAC address of the data packet is the MAC address of the local subnet LOOP. Query the local subnet IpTable where the local subnet LOOP is located, match the route of the peer subnet, the next hop address is the peer interconnection address, and the outgoing interface is the local interconnection LOOP.

[0065] S1035: Query the LoopArp table of the local interconnection LOOP, obtain the MAC address of the peer interconnection, and set the destination MAC of the data packet to the MAC address of the peer interconnection;

[0066] S1036: Query the l2fib table of the local interconnection VxlanTunnel corresponding to the local interconnection LOOP, and match the peer interconnection MAC to the local interconnection VxlanTunnel;

[0067] S1037: Send the encapsulated VXLAN packet to the peer VPP.

[0068] S104: The peer VPP transmits the data packet to the peer cloud host to establish a peer connection between the local cloud host and the peer cloud host.

[0069] In one possible implementation, S104 specifically includes:

[0070] S1041: The peer VPP has received the encapsulated VXLAN packet;

[0071] S1042: Query the l2fib table of the peer interconnection BridgeDomain where the peer interconnection VxlanTunnel is located, and match the peer interconnection LOOP;

[0072] S1043: Match the MAC address of the peer interconnection loop according to the destination MAC of the data packet, and query the peer interconnection IpTable corresponding to the peer interconnection loop;

[0073] S1044: Configure the peer interconnection IpTable jump table to the peer subnet IpTable in the destination IP of the data packet;

[0074] S1045: The peer subnet IpTable matches the direct route of the peer subnet LOOP and sends a data packet from the peer subnet LOOP;

[0075] S1046: Query the peer IP in the LoopArp table of the peer subnet LOOP to obtain the peer cloud host MAC;

[0076] S1047: Query the l2fib table of the peer interconnection BridgeDomain corresponding to the peer subnet LOOP, and match the peer cloud host MAC address output interface as the peer cloud host VXLAN port.

[0077] S1048: The peer VPP encapsulates VXLAN data packets, with the destination IP being the peer VPP tunnel IP, the tunnel source IP being the local VPP tunnel IP, and the VNI being the VNI corresponding to the VPC.

[0078] S1049: The host machine where the peer cloud host is located receives the VXLAN packet, decapsulates it, and then hands it over to the peer cloud host through vSwitch.

[0079] The present invention has at least the following beneficial effects:

[0080] In this embodiment of the invention, the local cloud host transmits data packets to the local VPP, the local VPP transmits the data packets to the peer VPP, and the peer VPP transmits the data packets to the peer cloud host, thereby establishing a peer-to-peer connection between the local cloud host and the peer cloud host. Through the VPC peer-to-peer connection method provided by this invention, data communication can be achieved between cloud hosts in different VPCs, facilitating system management and data distribution.

[0081] Example 2

[0082] Reference Figure 3 The diagram shows a structural schematic of a VPC peer-to-peer connection system provided by an embodiment of the present invention.

[0083] This invention provides a VPC peering system 20, comprising:

[0084] Local configuration module 201 is used to configure local VPP in local VPC. The local VPP includes local subnet IpTable, local subnet BridgeDomain, local subnet VxlanTunnel, local subnet LOOP, local interconnect BridgeDomain, local interconnect IpTable, local interconnect LOOP and local interconnect VxlanTunnel.

[0085] The peer configuration module 202 is used to configure the peer VPP in the peer VPC. The peer VPP includes the peer subnet IpTable, the peer subnet BridgeDomain, the peer subnet VxlanTunnel, the peer subnet LOOP, the peer interconnect BridgeDomain, the peer interconnect IpTable, the peer interconnect LOOP, and the peer interconnect VxlanTunnel.

[0086] Local transmission module 203 is used for the local cloud host to transmit data packets to the local VPP, and the local VPP to transmit the data packets to the peer VPP;

[0087] The peer transmission module 204 is used by the peer VPP to transmit the data packet to the peer cloud host, so as to establish a peer connection between the local cloud host and the peer cloud host through the local VPP and the peer VPP.

[0088] In one possible implementation, the local configuration module 201 is specifically used for:

[0089] Create the local subnet IpTable in the local VPC, and name the local subnet IpTable using the VPCID;

[0090] Create the local subnet BridgeDomain in the local VPC, and name the local subnet BridgeDomain using the VPCID;

[0091] Create the local cloud host VxlanTunnel in the local VPC. The source IP of the local cloud host VxlanTunnel is the tunnel address of the host machine where the cloud host is located, the destination IP is the VPP tunnel address, the VNI is the VNI corresponding to the local VPC, add it to the local subnet BridgeDomain, add the cloud host MAC address to the l2fib table of the local subnet BridgeDomain, and the outgoing interface is the local cloud host VxlanTunnel.

[0092] Create the local subnet LOOP in the local VPC, add the local subnet BridgeDomain to the local subnet LOOP using Bvi, configure the MAC address to the subnet gateway MAC address and the IP address to the subnet gateway address in the local subnet LOOP, and add it to the local subnet IpTable;

[0093] Create the local interconnect BridgeDomain in the local VPC, and name the local interconnect BridgeDomain using the peer connection ID;

[0094] Create the local interconnection IpTable in the local VPC, and add a default route skip table to the local subnet IpTable in the local interconnection IpTable;

[0095] Create the local interconnection LOOP in the local VPC, configure the IP address and MAC address of the local interconnection LOOP as the local interconnection IP and the local interconnection MAC address, add it to the local interconnection BridgeDomain, add it to the local subnet IpTable, and add the peer interconnection IP and MAC address of the peer interconnection in the LoopArp table of the local interconnection LOOP.

[0096] Create the local interconnect VxlanTunnel in the local VPC. The tunnel source IP of the local interconnect VxlanTunnel is the local VPP tunnel IP, the destination IP is the peer VPP tunnel IP, the VNI is the peer connection VNI, add it to the peer connection BridgeDomain, add the peer interconnect MAC address to the l2fib table of the peer connection BridgeDomain, and the outgoing interface is the local interconnect VxlanTunnel.

[0097] Add a route to the peer subnet in the local subnet IpTable, with the next hop address being the peer interconnect address and the outgoing interface being the local interconnect LOOP.

[0098] In one possible implementation, the peer configuration module 202 is specifically used for:

[0099] Create the peer subnet IpTable in the peer VPC, and name the peer subnet IpTable using the VPCID;

[0100] Create the peer subnet BridgeDomain in the peer VPC, and name the peer subnet BridgeDomain using VPCID;

[0101] Create the peer cloud host VxlanTunnel in the peer VPC. The tunnel source IP of the peer cloud host VxlanTunnel is the tunnel address of the host machine where the cloud host is located, the destination IP is the VPP tunnel address, the VNI is the VNI corresponding to the peer VPC, add it to the peer subnet BridgeDomain, add the cloud host MAC address to the l2fib table of the peer subnet BridgeDomain, and the outgoing interface is the peer cloud host VxlanTunnel.

[0102] Create the peer subnet LOOP in the peer VPC, add the peer subnet BridgeDomain to the peer subnet LOOP using Bvi, configure the MAC address to the subnet gateway MAC address and the IP address to the subnet gateway address in the peer subnet LOOP, and add it to the peer subnet IpTable.

[0103] Create the peer interconnect BridgeDomain in the peer VPC, and name the peer interconnect BridgeDomain using the peer connection ID;

[0104] Create the peer interconnection IpTable in the peer VPC, and add a default route skip table to the peer subnet IpTable in the peer interconnection IpTable;

[0105] Create the peer interconnection LOOP in the peer VPC, configure the IP address in the peer interconnection LOOP to be the peer interconnection IP, the MAC address to be the peer interconnection MAC address, add it to the peer interconnection BridgeDomain, add it to the peer subnet IpTable, and add the local interconnection IP and MAC address to the LoopArp table of the peer interconnection LOOP.

[0106] Create the peer interconnect VxlanTunnel in the peer VPC. The tunnel source IP of the peer interconnect VxlanTunnel is the local VPP tunnel IP, the destination IP is the peer VPP tunnel IP, the VNI is the peer connection VNI, add it to the peer connection BridgeDomain, add the local interconnect MAC address to the l2fib table of the peer connection BridgeDomain, and the outgoing interface is the peer interconnect VxlanTunnel.

[0107] Add a route to the peer subnet's IpTable with the destination being this subnet, the next-hop address being the local interconnect address, and the outgoing interface being the peer interconnect LOOP.

[0108] In one possible implementation, the local transmission module 203 is specifically used for:

[0109] When the local cloud host sends a data packet, the compute node Vswitch determines it to be peer-to-peer connection traffic. The destination MAC is the subnet gateway MAC, which is encapsulated in a VXLAN packet. The VXLAN destination IP is the VPP tunnel IP, and the VNI is the VNI corresponding to the local VPC. The packet is then sent to the local VPP.

[0110] The local cloud host VxlanTunnel receives VXLAN packets from the local cloud host, decapsulates the VXLAN packets, and hands them over to the peer-connected local subnet BridgeDomain;

[0111] The local VPP queries the l2fib table of the local subnet BridgeDomain through the destination MAC of the data packet, and forwards the decapsulated VXLAN packet to the local subnet LOOP.

[0112] The destination MAC address of the data packet is the MAC address of the local subnet loop. The local subnet IpTable where the local subnet loop is located is queried to match the route of the peer subnet. The next hop address is the peer interconnection address, and the outgoing interface is the local interconnection loop.

[0113] Query the LoopArp table of the local interconnection LOOP to obtain the MAC address of the peer interconnection, and set the destination MAC of the data packet to the MAC address of the peer interconnection;

[0114] Query the l2fib table of the local interconnection VxlanTunnel corresponding to the local interconnection LOOP, and match the peer interconnection MAC to the local interconnection VxlanTunnel;

[0115] Send the encapsulated VXLAN packet to the peer VPP.

[0116] In one possible implementation, the peer transmission module 204 is specifically used for:

[0117] The peer VPP receives the encapsulated VXLAN packet;

[0118] Query the l2fib table of the peer interconnection BridgeDomain where the peer interconnection VxlanTunnel is located, and match the peer interconnection LOOP;

[0119] Match the MAC address of the peer interconnection loop based on the destination MAC of the data packet, and query the peer interconnection IpTable corresponding to the peer interconnection loop;

[0120] Configure the peer interconnection IpTable jump table to the peer subnet IpTable in the destination IP of the data packet;

[0121] The peer subnet IpTable matches the direct route of the peer subnet LOOP and sends data packets from the peer subnet LOOP.

[0122] Query the peer IP in the LoopArp table of the peer subnet LOOP to obtain the peer cloud host MAC;

[0123] Query the l2fib table of the peer interconnection BridgeDomain corresponding to the peer subnet LOOP, and match the peer cloud host MAC address outgoing interface to the peer cloud host VXLAN port.

[0124] The peer VPP encapsulates VXLAN data packets, with the destination IP being the peer VPP tunnel IP, the tunnel source IP being the local VPP tunnel IP, and the VNI being the VNI corresponding to the VPC.

[0125] The host machine where the peer cloud host is located receives the VXLAN packet, decapsulates it, and then hands it over to the peer cloud host through vSwitch.

[0126] The present invention has at least the following beneficial effects:

[0127] In this embodiment of the invention, the local cloud host transmits data packets to the local VPP, the local VPP transmits the data packets to the peer VPP, and the peer VPP transmits the data packets to the peer cloud host, thereby establishing a peer-to-peer connection between the local cloud host and the peer cloud host. Through the VPC peer-to-peer connection method provided by this invention, data communication can be achieved between cloud hosts in different VPCs, facilitating system management and data distribution.

[0128] The virtual system provided by this invention can be a system, or a component, integrated circuit, or chip in a terminal.

[0129] The above are merely embodiments of the present invention and are not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the present invention should be included within the scope of the claims of the present invention.

Claims

1. A VPC peering connection method, characterized in that, include: S101: Configure the local VPP in the local VPC. The local VPP includes the local subnet IpTable, local subnet BridgeDomain, local subnet VxlanTunnel, local subnet LOOP, local interconnect BridgeDomain, local interconnect IpTable, local interconnect LOOP, and local interconnect VxlanTunnel. S102: Configure the peer VPP in the peer VPC, wherein the peer VPP includes the peer subnet IpTable, the peer subnet BridgeDomain, the peer subnet VxlanTunnel, the peer subnet LOOP, the peer interconnect BridgeDomain, the peer interconnect IpTable, the peer interconnect LOOP, and the peer interconnect VxlanTunnel. S103: The local cloud host transmits the data packet to the local VPP, and the local VPP transmits the data packet to the peer VPP; S104: The peer VPP transmits the data packet to the peer cloud host to establish a peer connection between the local cloud host and the peer cloud host through the local VPP and the peer VPP. The source IP of the local interconnect VxlanTunnel is the local VPP tunnel IP, the destination IP is the peer VPP tunnel IP, the VNI is the peer connection VNI, it is added to the peer connection BridgeDomain, the peer interconnect MAC address is added to the l2fib table of the peer connection BridgeDomain, and the outgoing interface is the local interconnect VxlanTunnel. Specifically, S103 includes: S1031: The local cloud host sends a data packet, which is determined by the compute node Vswitch to be peer-to-peer connection traffic. The destination MAC is the subnet gateway MAC, which is encapsulated as a VXLAN packet. The VXLAN destination IP is the VPP tunnel IP, and the VNI is the VNI corresponding to the local VPC. The packet is then sent to the local VPP. S1032: The local cloud host VxlanTunnel receives the VXLAN packet from the local cloud host, decapsulates the VXLAN packet, and hands it over to the peer-connected local subnet BridgeDomain; S1033: The local VPP queries the l2fib table of the local subnet BridgeDomain through the destination MAC of the data packet, and forwards the decapsulated VXLAN packet to the local subnet LOOP; S1034: The destination MAC address of the data packet is the MAC address of the local subnet LOOP. Query the local subnet IpTable where the local subnet LOOP is located, match the route of the peer subnet, the next hop address is the peer interconnection address, and the outgoing interface is the local interconnection LOOP. S1035: Query the LoopArp table of the local interconnection LOOP, obtain the MAC address of the peer interconnection, and set the destination MAC of the data packet to the MAC address of the peer interconnection; S1036: Query the l2fib table of the local interconnection VxlanTunnel corresponding to the local interconnection LOOP, and match the peer interconnection MAC to the local interconnection VxlanTunnel; S1037: Send the encapsulated VXLAN packet to the peer VPP.

2. The VPC peer-to-peer connection method according to claim 1, characterized in that, S101 specifically includes: S1011: Create the local subnet IpTable in the local VPC, and use the VPCID as the name of the local subnet IpTable; S1012: Create the local subnet BridgeDomain in the local VPC, and use the VPCID as the name of the local subnet BridgeDomain; S1013: Create a local cloud host VxlanTunnel in the local VPC. The source IP of the local cloud host VxlanTunnel is the tunnel address of the host machine where the cloud host is located, the destination IP is the VPP tunnel address, the VNI is the VNI corresponding to the local VPC, add it to the local subnet BridgeDomain, add the cloud host MAC address to the l2fib table of the local subnet BridgeDomain, and the outgoing interface is the local cloud host VxlanTunnel. S1014: Create the local subnet LOOP in the local VPC, add the local subnet BridgeDomain to the local subnet LOOP using Bvi, configure the MAC address as the subnet gateway MAC address and the IP as the subnet gateway address in the local subnet LOOP, and add it to the local subnet IpTable; S1015: Create the local interconnect BridgeDomain in the local VPC, and use the peer connection ID as the name of the local interconnect BridgeDomain; S1016: Create the local interconnection IpTable in the local VPC, and add a default route skip table to the local subnet IpTable in the local interconnection IpTable; S1017: Create the local interconnection LOOP in the local VPC, configure the IP address in the local interconnection LOOP as the local interconnection IP, the MAC address as the local interconnection MAC address, add it to the local interconnection BridgeDomain, add it to the local subnet IpTable, and add the peer interconnection IP and MAC address to the LoopArp table of the local interconnection LOOP. S1018: Create the local interconnect VxlanTunnel in the local VPC; S1019: Add a route to the local subnet IpTable with the destination being the peer subnet, the next-hop address being the peer interconnection address, and the outgoing interface being the local interconnection LOOP.

3. The VPC peering connection method according to claim 1, characterized in that, S102 specifically includes: S1021: Create the peer subnet IpTable in the peer VPC, and name the peer subnet IpTable using VPCID; S1022: Create the peer subnet BridgeDomain in the peer VPC, and name the peer subnet BridgeDomain using VPCID; S1023: Create the peer cloud host VxlanTunnel in the peer VPC. The tunnel source IP of the peer cloud host VxlanTunnel is the tunnel address of the host machine where the cloud host is located, the destination IP is the VPP tunnel address, the VNI is the VNI corresponding to the peer VPC, add it to the peer subnet BridgeDomain, add the cloud host MAC address to the l2fib table of the peer subnet BridgeDomain, and the outgoing interface is the peer cloud host VxlanTunnel. S1024: Create the peer subnet LOOP in the peer VPC, add the peer subnet BridgeDomain to the peer subnet LOOP using Bvi, configure the MAC address as the subnet gateway MAC address and the IP as the subnet gateway address in the peer subnet LOOP, and add it to the peer subnet IpTable. S1025: Create the peer interconnect BridgeDomain in the peer VPC, the name of the peer interconnect BridgeDomain using the peer connection ID; S1026: Create the peer interconnection IpTable in the peer VPC, and add a default route jump table to the peer subnet IpTable in the peer interconnection IpTable; S1027: Create the peer interconnection LOOP in the peer VPC, configure the IP address in the peer interconnection LOOP as the peer interconnection IP, the MAC address as the peer interconnection MAC address, add it to the peer interconnection BridgeDomain, add it to the peer subnet IpTable, and add the local interconnection IP and MAC address to the LoopArp table of the peer interconnection LOOP. S1028: Create the peer interconnect VxlanTunnel in the peer VPC. The tunnel source IP of the peer interconnect VxlanTunnel is the local VPP tunnel IP, the destination IP is the peer VPP tunnel IP, the VNI is the peer connection VNI, add it to the peer connection BridgeDomain, add the local interconnect MAC address to the l2fib table of the peer connection BridgeDomain, and the outgoing interface is the peer interconnect VxlanTunnel. S1029: Add a route to the peer subnet IpTable with the destination being this subnet, the next hop address being the local interconnect address, and the outgoing interface being the peer interconnect LOOP.

4. The VPC peering connection method according to claim 1, characterized in that, S104 specifically includes: S1041: The peer VPP has received the encapsulated VXLAN packet; S1042: Query the l2fib table of the peer interconnection BridgeDomain where the peer interconnection VxlanTunnel is located, and match the peer interconnection LOOP; S1043: Match the MAC address of the peer interconnection loop according to the destination MAC of the data packet, and query the peer interconnection IpTable corresponding to the peer interconnection loop; S1044: Configure the peer interconnection IpTable jump table to the peer subnet IpTable in the destination IP of the data packet; S1045: The peer subnet IpTable matches the direct route of the peer subnet LOOP and sends a data packet from the peer subnet LOOP; S1046: Query the peer IP in the LoopArp table of the peer subnet LOOP to obtain the peer cloud host MAC; S1047: Query the l2fib table of the peer interconnection BridgeDomain corresponding to the peer subnet LOOP, and match the peer cloud host MAC address output interface as the peer cloud host VXLAN port. S1048: The peer VPP encapsulates VXLAN data packets, the destination IP is the peer VPP tunnel IP, the tunnel source IP is the local VPP tunnel IP, and the VNI is the VNI corresponding to the VPC. S1049: The host machine where the peer cloud host is located receives the VXLAN packet, decapsulates it, and then hands it over to the peer cloud host through vSwitch.

5. A VPC peer-to-peer connection system, characterized in that, include: The local configuration module is used to configure the local VPP in the local VPC. The local VPP includes the local subnet IpTable, local subnet BridgeDomain, local subnet VxlanTunnel, local subnet LOOP, local interconnect BridgeDomain, local interconnect IpTable, local interconnect LOOP and local interconnect VxlanTunnel. The peer configuration module is used to configure the peer VPP in the peer VPC. The peer VPP includes the peer subnet IpTable, peer subnet BridgeDomain, peer subnet VxlanTunnel, peer subnet LOOP, peer interconnect BridgeDomain, peer interconnect IpTable, peer interconnect LOOP and peer interconnect VxlanTunnel. The local transmission module is used for the local cloud host to transmit data packets to the local VPP, and the local VPP to transmit the data packets to the peer VPP; The peer transmission module is used by the peer VPP to transmit the data packet to the peer cloud host, so as to establish a peer connection between the local cloud host and the peer cloud host through the local VPP and the peer VPP. The source IP of the local interconnect VxlanTunnel is the local VPP tunnel IP, the destination IP is the peer VPP tunnel IP, the VNI is the peer connection VNI, it is added to the peer connection BridgeDomain, the peer interconnect MAC address is added to the l2fib table of the peer connection BridgeDomain, and the outgoing interface is the local interconnect VxlanTunnel. Specifically, the local transmission module is used for: When the local cloud host sends a data packet, the compute node Vswitch determines it to be peer-to-peer connection traffic. The destination MAC is the subnet gateway MAC, which is encapsulated in a VXLAN packet. The VXLAN destination IP is the VPP tunnel IP, and the VNI is the VNI corresponding to the local VPC. The packet is then sent to the local VPP. The local cloud host VxlanTunnel receives VXLAN packets from the local cloud host, decapsulates the VXLAN packets, and hands them over to the peer-connected local subnet BridgeDomain; The local VPP queries the l2fib table of the local subnet BridgeDomain through the destination MAC of the data packet, and forwards the decapsulated VXLAN packet to the local subnet LOOP. The destination MAC address of the data packet is the MAC address of the local subnet loop. The local subnet IpTable where the local subnet loop is located is queried to match the route of the peer subnet. The next hop address is the peer interconnection address, and the outgoing interface is the local interconnection loop. Query the LoopArp table of the local interconnection LOOP to obtain the MAC address of the peer interconnection, and set the destination MAC of the data packet to the MAC address of the peer interconnection; Query the l2fib table of the local interconnection VxlanTunnel corresponding to the local interconnection LOOP, and match the peer interconnection MAC to the local interconnection VxlanTunnel; Send the encapsulated VXLAN packet to the peer VPP.

6. The VPC peer-to-peer connection system according to claim 5, characterized in that, The local configuration module is specifically used for: Create the local subnet IpTable in the local VPC, and name the local subnet IpTable using the VPCID; Create the local subnet BridgeDomain in the local VPC, and name the local subnet BridgeDomain using the VPCID; Create a local cloud host VxlanTunnel in the local VPC. The source IP of the local cloud host VxlanTunnel is the tunnel address of the host machine where the cloud host is located, the destination IP is the VPP tunnel address, the VNI is the VNI corresponding to the local VPC, and it is added to the local subnet BridgeDomain. The MAC address of the cloud host is added to the l2fib table of the local subnet BridgeDomain, and the outgoing interface is the local cloud host VxlanTunnel. Create the local subnet LOOP in the local VPC, add the local subnet BridgeDomain to the local subnet LOOP using Bvi, configure the MAC address to the subnet gateway MAC address and the IP address to the subnet gateway address in the local subnet LOOP, and add it to the local subnet IpTable; Create the local interconnect BridgeDomain in the local VPC, and name the local interconnect BridgeDomain using the peer connection ID; Create the local interconnection IpTable in the local VPC, and add a default route skip table to the local subnet IpTable in the local interconnection IpTable; Create the local interconnection LOOP in the local VPC, configure the IP address and MAC address of the local interconnection LOOP as the local interconnection IP and the local interconnection MAC address, add it to the local interconnection BridgeDomain, add it to the local subnet IpTable, and add the peer interconnection IP and MAC address of the peer interconnection in the LoopArp table of the local interconnection LOOP. Create the local interconnect VxlanTunnel in the local VPC; Add a route to the peer subnet in the local subnet IpTable, with the next hop address being the peer interconnect address and the outgoing interface being the local interconnect LOOP.

7. The VPC peer-to-peer connection system according to claim 5, characterized in that, The peer configuration module is specifically used for: Create the peer subnet IpTable in the peer VPC, and name the peer subnet IpTable using the VPCID; Create the peer subnet BridgeDomain in the peer VPC, and name the peer subnet BridgeDomain using VPCID; Create the peer cloud host VxlanTunnel in the peer VPC. The tunnel source IP of the peer cloud host VxlanTunnel is the tunnel address of the host machine where the cloud host is located, the destination IP is the VPP tunnel address, the VNI is the VNI corresponding to the peer VPC, add it to the peer subnet BridgeDomain, add the cloud host MAC address to the l2fib table of the peer subnet BridgeDomain, and the outgoing interface is the peer cloud host VxlanTunnel. Create the peer subnet LOOP in the peer VPC, add the peer subnet BridgeDomain to the peer subnet LOOP using Bvi, configure the MAC address to the subnet gateway MAC address and the IP address to the subnet gateway address in the peer subnet LOOP, and add it to the peer subnet IpTable. Create the peer interconnect BridgeDomain in the peer VPC, and name the peer interconnect BridgeDomain using the peer connection ID; Create the peer interconnection IpTable in the peer VPC, and add a default route skip table to the peer subnet IpTable in the peer interconnection IpTable; Create the peer interconnection LOOP in the peer VPC, configure the IP address in the peer interconnection LOOP to be the peer interconnection IP, the MAC address to be the peer interconnection MAC address, add it to the peer interconnection BridgeDomain, add it to the peer subnet IpTable, and add the local interconnection IP and MAC address to the LoopArp table of the peer interconnection LOOP. Create the peer interconnect VxlanTunnel in the peer VPC. The tunnel source IP of the peer interconnect VxlanTunnel is the local VPP tunnel IP, the destination IP is the peer VPP tunnel IP, the VNI is the peer connection VNI, add it to the peer connection BridgeDomain, add the local interconnect MAC address to the l2fib table of the peer connection BridgeDomain, and the outgoing interface is the peer interconnect VxlanTunnel. Add a route to the peer subnet's IpTable with the destination being this subnet, the next-hop address being the local interconnect address, and the outgoing interface being the peer interconnect LOOP.

8. The VPC peer-to-peer connection system according to claim 5, characterized in that, The peer transmission module is specifically used for: The peer VPP receives the encapsulated VXLAN packet; Query the l2fib table of the peer interconnection BridgeDomain where the peer interconnection VxlanTunnel is located, and match the peer interconnection LOOP; Match the MAC address of the peer interconnection loop based on the destination MAC of the data packet, and query the peer interconnection IpTable corresponding to the peer interconnection loop; Configure the peer interconnection IpTable jump table to the peer subnet IpTable in the destination IP of the data packet; The peer subnet IpTable matches the direct route of the peer subnet LOOP and sends data packets from the peer subnet LOOP. Query the peer IP in the LoopArp table of the peer subnet LOOP to obtain the peer cloud host MAC; Query the l2fib table of the peer interconnection BridgeDomain corresponding to the peer subnet LOOP, and match the peer cloud host MAC address outgoing interface to the peer cloud host VXLAN port. The peer VPP encapsulates VXLAN data packets, with the destination IP being the peer VPP tunnel IP, the tunnel source IP being the local VPP tunnel IP, and the VNI being the VNI corresponding to the VPC. The host machine where the peer cloud host is located receives the VXLAN packet, decapsulates it, and then hands it over to the peer cloud host through vSwitch.

Images