Implementing logical metadata proxy servers in logical networks

• US 10,484,515 B2
• Filed: 01/30/2017
• Issued: 11/19/2019
• Est. Priority Date: 04/29/2016
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Masurekar, Uday, Jain, Jayant, Zhang, Ronghua, Kancherla, Mani, Agarwal, Minjal
• Primary Examiner(s): Sefcheck, Gregory B
• Assistant Examiner(s): Van, Jenkey
• Application Number:
  US15/420,059
• Publication Number:
  US 20170317974A1
• Time in Patent Office: 1,023 Days
• Field of Search: None
• CPC Class Codes: H04L 2101/663 Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/325 in the network layer [OSI layer 3], e.g. X.25 H04L69/16 takes precedence
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

Some embodiments provide a method for providing metadata proxy services to different data compute nodes that are associated with different logical networks (e.g., for different tenants of a datacenter). When a data compute node (DCN) is instantiated (i.e., starts executing) in a host machine, the DCN requests for metadata associated with the DCN from a metadata server. The requested metadata includes identification and configuration data (e.g., name and description, amount of virtual memory, number of allocated virtual CPUs, etc.) for the DCN. Each DCN generates and sends out a metadata request packet after an IP address is assigned to the DCN (e.g., by a DHCP server). In some embodiments, a metadata proxy server (1) receives the metadata request packets that are sent by different DCNs associated with different logical networks, (2) adds logical network identification data to the packets, and (3) forwards the packets to a metadata server.

Claims

1. A method for enabling a metadata proxy server to provide metadata proxy services for a plurality of logical networks, the method comprising:

at a managed forwarding element (MFE) that executes on a same host computer as the metadata proxy server,

receiving a first packet sent from a first data compute node (DCN) of a first logical network requesting metadata for the first DCN, said first packet comprising a particular layer four destination port number;

receiving a second packet sent from a second DCN of a second logical network requesting metadata for the second DCN, said second packet comprising the same particular layer four destination port number;

replacing (i) the particular destination port number in the first packet with a first port number that corresponds to a first port of the metadata proxy server that is associated with the first logical network and (ii) the particular destination port number in the second packet with a second different port number that corresponds to a second port of the metadata proxy server that is associated with the second logical network; and

forwarding the first and second packets with their replaced port numbers to the metadata proxy server on the host computer for the metadata proxy server to provide metadata for the first DCN through the first port number and provide metadata for the second DCN through the second port number.

2. The method of claim 1, wherein the first DCN is logically coupled to a first logical switch in the first logical network and the second DCN is logically coupled to a second logical switch in the second logical network.

3. The method of claim 2, wherein the first logical switch is in a first subnet that has a first IP address range and the second logical switch is in a second, different subnet that has a second IP address range, wherein the first and second IP address ranges comprise one or more overlapping IP addresses.

4. The method of claim 3, wherein the metadata proxy server comprises (i) a first metadata proxy instance that listens to the first port to provide metadata proxy service for the first logical switch and (ii) a second metadata proxy instance that listens to the second port to provide metadata proxy service for the second logical switch.

5. The method of claim 1, wherein the metadata proxy server is a namespace operating on a physical host computer, said namespace comprising a plurality of ports and a plurality of metadata proxy instances, wherein each particular metadata proxy instance listens to a different particular port to provide metadata proxy service to a particular logical switch of a logical network.

6. The method of claim 1, wherein the first and second packets each further comprise a layer three destination address header that includes a same destination address in both packets.

7. The method of claim 6, wherein the layer three destination address and the particular layer four destination port number are associated with an address and a port number of the metadata proxy server.

8. The method of claim 1, wherein the requested metadata for the first DCN comprises at least one of a name and a description for the first DCN and the requested metadata for the second DCN comprises at least one of a name and a description for the second DCN.

9. The method of claim 1, wherein the requested metadata for the first DCN comprises at least one of an amount of virtual memory and a number of virtual processors that should be allocated to the first DCN and the requested metadata for the second DCN comprises at least one of a name and a description for the second DCN.

10. The method of claim 1 further comprising:

creating a first flow entry for the first packet and a second flow entry for the second packet to establish a first data flow for the first request and a second data flow for the second request; and

sending the requested metadata back to the first and second DCNs using the established first and second data flows.

11. The method of claim 1, wherein the metadata proxy server, based on the first port number from which the first packet is received, adds a first logical network identification data to the first packet and forwards the first packet to a metadata server that provides the requested metadata for the first DCN.

12. The method of claim 1, wherein the first and second logical networks are implemented by the MFE.

13. The method of claim 12, wherein the host computer on which the MFE executes is an edge node of a hosting system over network infrastructure of which the first and second logical networks are implemented.

14. A non-transitory machine readable medium storing a managed forwarding element (MFE) which when executed by at least one processing unit of a host computer enables a metadata proxy server to provide metadata proxy services for a plurality of logical networks, the MFE comprising sets of instructions for:

receiving a first packet sent from a first data compute node (DCN) of a first logical network requesting metadata for the first DCN, said first packet comprising a particular layer four destination port number;

receiving a second packet sent from a second DCN of a second logical network requesting metadata for the second DCN, said second packet comprising the same particular layer four destination port number;

replacing (i) the particular destination port number in the first packet with a first port number that corresponds to a first port of the metadata proxy server that is associated with the first logical network and (ii) the particular destination port number in the second packet with a second different port number that corresponds to a second port of the metadata proxy server that is associated with the second logical network; and

forwarding the first and second packets with their replaced port numbers to the metadata proxy server on the host computer for the metadata proxy server to provide metadata for the first DCN through the first port number and provide metadata for the second DCN through the second port number.

15. The non-transitory machine readable medium of claim 14, wherein the metadata proxy server comprises (i) a first metadata proxy instance that listens to the first port to provide metadata proxy services for the first logical network and (ii) a second metadata proxy instance that listens to the second port to provide metadata proxy services for the second logical network.

16. The non-transitory machine readable medium of claim 15, wherein the metadata proxy server comprises a plurality of other metadata proxy instances, each of which provides metadata proxy services to a plurality of DCNs associated with a particular logical network of the plurality of logical networks.

17. The non-transitory machine readable medium of claim 15, wherein the metadata proxy server is a namespace and each of the first and second proxy instances is a process of the namespace.

18. The non-transitory machine readable medium of claim 14, wherein the MFE further comprises sets of instructions for:

creating a first flow entry for the first packet and a second flow entry for the second packet to establish a first data flow for the first request and a second data flow for the second request; and

sending the requested metadata back to the first and second DCNs using the established first and second data flows.

19. The non-transitory machine readable medium of claim 14, wherein the metadata proxy server, based on the first port number from which the first packet is received, adds a first logical network identification data to the first packet and forwards the first packet to a remote metadata server to receive the requested metadata for the first DCN.

20. The non-transitory machine readable medium of claim 14, wherein the requested metadata for the first DCN comprises at least one of a name for the first DCN, a description for the first DCN, an amount of virtual memory that should be allocated to the first DCN, and a number of virtual processors that should be allocated to the first DCN, wherein the requested metadata for the second DCN comprises at least one of a name for the second DCN, a description for the second DCN, an amount of virtual memory that should be allocated to the second DCN, and a number of virtual processors that should be allocated to the second DCN.