Transitive routing in public cloud
Some embodiments provide a centralized overlay-network cloud gateway and a set of centralized services in a transit virtual cloud network (VCN) connected to multiple other compute VCNs hosting compute nodes (VMs, containers, etc.) that are part of (belong to) the overlay network. The centralized overlay-network cloud gateway provides connectivity between compute nodes of the overlay network (e.g., a logical network spanning multiple VCNs) and compute nodes in external networks. Some embodiments use the centralized overlay-network cloud gateway to provide transitive routing (e.g., routing through a transit VCN) in the absence of direct peering between source and destination VCNs. The overlay network, of some embodiments, uses the same subnetting and default gateway address for each compute node as the cloud provider network provided by the virtual private cloud provider.
1. A method of processing, at a transit gateway operating in a first virtual private cloud (VPC), a data message exchanged between first and second machines of a tenant, said first and second machines operating in second and third VPCs, the method comprising:
at the transit gateway operating in the first VPC;
receiving the data message forwarded to the transit gateway by a managed forwarding element (MFE) that (1) executes in the second VPC for the tenant and (2) implements a logical routing element of a logical network for the tenant, wherein the data message originates from the first machine in the second VPC and is destined to the second machine in the third VPC;
forwarding the data message to a service virtual machine (SVM) operating in the first VPC to perform a middlebox service operation on the data message;
after the SVM performs the middlebox service operation and returns the data message to the transit gateway, performing logical routing for the data message; and
forwarding the data message to the second machine in the third VPC,
wherein the first, second and third VPCs are defined in a set of one or more public cloud datacenters.
2. The method of claim 1 , wherein performing the middlebox service operation comprises:
forwarding the data message to a set of service appliances; and
receiving the data message from the set of service appliances after a set of middlebox services has been provided.
3. The method of claim 2 , wherein the set of service appliances comprises at least one third party service appliance.
4. The method of claim 3 , wherein the third-party service appliance executes in the first VPC.
5. The method of claim 1 , wherein the middlebox service operation comprises one of a network address translation, a firewall service, a load balancing service, and an intrusion detection service.
6. The method of claim 1 , wherein the MFE of the second VPC is a first MFE, and the second VPC comprises a second MFE that implements a logical switching element that connects to the first machine, and that forwards the data message to the first MFE.
7. The method of claim 1 , wherein the MFE further implements a logical switching element of the tenant logical network that connects to the first machine.
8. The method of claim 1 , wherein the MFE forwards the data message to the transit gateway using encapsulation.
9. The method of claim 1 , wherein the encapsulation is a generic network virtualization encapsulation (GENEVE).
10. The method of claim 1 , wherein the MFE is an open vSwitch executing on a computer that is used in the public cloud to implement the second VPC.
11. The method of claim 1 , wherein the MFE is configured to route all tenant logical network traffic destined to VPCs of the tenant to which the second VPC is not directly peered to a set of one or more transit gateways of a set of one or more transit VPCs of the tenant in the set of one or more public cloud datacenters.
12. A method of processing a data message exchanged between first and second machines of a tenant operating in first and second virtual private clouds (VPCs) at a managed forwarding element (MFE) executing in the first VPC to implement at least one logical forwarding element (LFE) of a logical network for the tenant, the method comprising:
at the MFE executing in the first VPC;
receiving, from the first machine in the first VPC, the data message, which is destined to the second machine in the second VPC;
performing ingress processing for the data message; and
forwarding the data message to a transit gateway operating in a third VPC for the third VPC to use a service virtual machine in the third VPC to perform at least one middlebox service operation on the data message and then to forward the data message to the second machine in the second VPC.
13. The method of claim 12 , wherein the transit gateway performs logical routing in order to forward the data message to the second machine in the second VPC.
14. The method of claim 12 , wherein performing the middlebox service operation comprises:
forwarding the data message to a set of service appliances; and
receiving the data message from the set of service appliances after a set of middlebox service operations has been provided.
15. The method of claim 12 , wherein the MFE implements a logical switching element of the logical network for the tenant that connects to the source compute node.
16. The method of claim 12 , wherein the MFE forwards the data message to the transit gateway using encapsulation.
17. The method of claim 12 , wherein the MFE is an open vSwitch executing on a computer that is used in the public cloud to implement the first VPC.
18. The method of claim 12 , wherein the MFE is configured to route all tenant logical network traffic destined to cloud-provider virtual networks of the tenant to which the first VPC is not directly peered to a set of one or more transit gateways of a set of one or more VPCs of the tenant in a set of one or more public cloud datacenters.