Auto discovery and auto scaling of services in software-defined network environment

• US 10,992,577 B2
• Filed: 02/19/2019
• Issued: 04/27/2021
• Est. Priority Date: 06/30/2016
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Mutnuru, Rishi K., Nayak, Narasimha Talapady, Nallur, Padmanabha, Chen, Huei-ping, Sanghavi, Dilip H.
• Primary Examiner(s): Mills, Donald L
• Application Number:
  US16/279,897
• Publication Number:
  US 20190190824A1
• Time in Patent Office: 798 Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/033 by updating distance vector protocols
• CPC Class Codes: H04L 45/0377 for service chaining
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/42 Centralised routing
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 45/507 Label distribution
• CPC Class Codes: H04L 45/64 using an overlay routing layer
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers

Abstract

Techniques are described for automatic discovery of two or more virtual service instances configured to apply a given service to a packet in a software-defined networking (SDN)/network functions virtualization (NFV) environment. Virtual service instances may be deployed as virtual entities hosted on one or more physical devices to offer individual services or chains of services from a service provider. The use of virtual service instances enables automatic scaling of the services on-demand. The techniques of this disclosure enable automatic discovery by a gateway network device of virtual service instances for a given service as load balancing entities. According to the techniques, the gateway network device automatically updates a load balancing group for the given service to include the discovered virtual service instances on which to load balance traffic for the service. In this way, the disclosed techniques provide auto-scaling and auto-discovery of services in an SDN/NFV environment.

Claims

1. A method comprising:

calculating, by a software-defined networking (SDN) controller, border gateway protocol (BGP) routes for a front-end service of a first service chain within a services complex, wherein each of the BGP routes represents one of a plurality of unique tunnels that extends from a gateway network device to one of a plurality of first virtual service instances for the front-end service of the first service chain on one or more physical network devices within the services complex;

advertising, by the SDN controller and to the gateway network device, the BGP routes for the front-end service of the first service chain as load balancing entities to be included in a first load balancing group for the front-end service of the first service chain;

calculating, by the SDN controller, BGP routes for a front-end service of a second service chain within the services complex, wherein the front-end service of the second service chain is different than the front-end service of the first service chain, and wherein each of the BGP routes represents one of a plurality of unique tunnels that extends from the gateway network device to one of a plurality of second virtual service instances for the front-end service of the second service chain on one or more physical network devices within the services complex; and

advertising, by the SDN controller and to the gateway network device, the BGP routes for the front-end service of the second service chain as load balancing entities to be included in a second load balancing group for the front-end service of the second service chain.

2. The method of claim 1, wherein calculating the BGP routes for the front-end service of the first service chain comprises calculating an equal cost multipath (ECMP) next hop route set having a plurality of member routes to reach the plurality of first virtual service instances for the front-end service of the first service chain.

3. The method of claim 1, wherein the one of the unique tunnels that extends from the gateway network device to the one of the first virtual service instances is identified by a tunnel address of a generic routing encapsulation (GRE) tunnel with a label assigned to the one of the first virtual service instances.

4. The method of claim 1, further comprising advertising, by the SDN controller and to the gateway network device, BGP route updates for the front-end service of the first service chain, wherein the BGP route updates include notifications of new first virtual service instances for the front-end service of the first service chain or notifications of removed first virtual service instances for the front-end service of the first service chain.

5. The method of claim 1, further comprising establishing, by the SDN controller, the plurality of first virtual service instances for the front-end service of the first service chain as a plurality of virtual machines running on the one or more physical network devices within the services complex.

6. A method comprising:

receiving, by a gateway network device and from a software-defined networking (SDN) controller, advertisements of border gateway protocol (BGP) routes for a front-end service of a first service chain within a services complex as load balancing entities, wherein each of the BGP routes represents one of a plurality of unique tunnels that extends from the gateway network device to one of a plurality of first virtual service instances for the front-end service of the first service chain on one or more physical network devices within the services complex;

maintaining, by the gateway network device, a first load balancing group for the front-end service of the first service chain that includes each of the BGP routes for the front-end service of the first service chain;

selecting, by the gateway network device and according to a first load balancing algorithm, one of the BGP routes from the first load balancing group used to forward a packet via the one of the unique tunnels to the one of the first virtual service instances for application of the front-end service of the first service chain to the packet;

receiving, by the gateway network device and from the SDN controller, advertisements of BGP routes for a front-end service of a second service chain within the services complex as load balancing entities, wherein the front-end service of the second service chain is different than the front-end service of the first service chain, and wherein each of the BGP routes represents one of a plurality of unique tunnels that extends from the gateway network device to one of a plurality of second virtual service instances for the front-end service of the second service chain on one or more physical network devices within the services complex;

maintaining, by the gateway network device, a second load balancing group for the front-end service of the second service chain that includes each of the BGP routes for the front-end service of the second service chain; and

selecting, by the gateway network device and according to a second load balancing algorithm, one of the BGP routes from the second load balancing group used to forward a packet via the one of the unique tunnels to the one of the second virtual service instances for application of the front-end service of the second service chain to the packet.

7. The method of claim 6, wherein the BGP routes for the front-end service of the first service chain comprise an equal cost multipath (ECMP) next hop route set having a plurality of member routes to reach the plurality of first virtual service instances for the front-end service of the first service chain.

8. The method of claim 6, wherein maintaining the first load balancing group for the front-end service of the first service chain comprises maintaining the first load balancing group in a virtual routing and forwarding (VRF) table for the front-end service of the first service chain, wherein, for each of the BGP routes, the VRF table includes a tunnel identifier for the one of the unique tunnels that extends to the one of the first virtual service instances for the front-end service of the first service chain.

9. The method of claim 8, further comprising:

upon selecting the one of the BGP routes from the first load balancing group, encapsulating the packet with the tunnel identifier for the one of the unique tunnels that extends to the one of the first virtual service instances for the front-end service of the first service chain; and

forwarding the encapsulated packet based on the tunnel identifier to the one of the first virtual service instances for application of the front-end service of the first service chain to the packet.

10. The method of claim 6, further comprising receiving, by the gateway network device and from the SDN controller, advertisements of BGP route updates including at least one of notifications of new first virtual service instances for the front-end service of the first service chain or notifications of removed first virtual service instances for the front-end service of the first service chain.

11. The method of claim 10, further comprising updating the first load balancing group for the front-end service of the first service chain based on the BGP route updates, wherein updating the first load balancing group includes at least one of adding BGP routes to the first load balancing group for any new first virtual service instances or deleting BGP routes from the first load balancing group for any removed first virtual service instances.

12. A gateway network device comprising:

a control unit comprising a processor configured to;

receive, from a software-defined networking (SDN) controller, advertisements of border gateway protocol (BGP) routes for a front-end service of a first service chain within a services complex as first load balancing entities, wherein each of the BGP routes represents one of a plurality of unique tunnels that extends from the gateway network device to one of a plurality of first virtual service instances for the front-end service of the first service chain on one or more physical network devices within the services complex,

maintain a first load balancing group for the front-end service of the first service chain that includes each of the BGP routes for the front-end service of the first service chain,

receive, from the SDN controller, advertisements of BGP routes for a front-end service of a second service chain within the services complex as load balancing entities, wherein the front-end service of the second service chain is different than the front-end service of the first service chain, and wherein each of the BGP routes represents one of a plurality of unique tunnels that extends from the gateway network device to one of a plurality of second virtual service instances for the front-end service of the second service chain on one or more physical network devices within the services complex, and

maintain a second load balancing group for the front-end service of the second service chain that includes each of the BGP routes for the front-end service of the second service chain; and

a forwarding circuit programmed with forwarding information associated with the BGP routes, the forwarding circuit configured to;

select, according to a first load balancing algorithm, one of the BGP routes from the first load balancing group used to forward a packet via the one of the unique tunnels to the one of the first virtual service instances for application of the front-end service of the first service chain to the packet, and

select, according to a second load balancing algorithm, one of the BGP routes from the second load balancing group used to forward a packet via the one of the unique tunnels to the one of the second virtual service instances for application of the front-end service of the second service chain to the packet.

13. The gateway network device of claim 12, wherein the BGP routes for the front-end service of the first service chain comprise an equal cost multipath (ECMP) next hop route set having a plurality of member routes to reach the plurality of first virtual service instances for the front-end service of the first service chain.

14. The gateway network device of claim 12, wherein, to maintain the first load balancing group, the processor is configured to maintain a virtual routing and forwarding (VRF) table for the front-end service of the first service chain, wherein, for each of the BGP routes, the VRF table includes a tunnel identifier for the one of the unique tunnels that extends to the one of the first virtual service instances for the front-end service of the first service chain.

15. The gateway network device of claim 14, wherein the forwarding circuit is configured to:

upon selection of the one of the BGP routes from the first load balancing group, encapsulate the packet with the tunnel identifier for the one of the unique tunnels that extends to the one of the first virtual service instances for the front-end service of the first service chain; and

forward the encapsulated packet based on the tunnel identifier to the one of the first virtual service instances for application of the front-end service of the first service chain to the packet.

16. The gateway network device of claim 12, wherein the processor is configured to receive, from the SDN controller, advertisements of BGP route updates including at least one of notifications of new first virtual service instances for the front-end service of the first service chain or notifications of removed first virtual service instances for the front-end service of the first service chain.

17. The gateway network device of claim 16, wherein the processor is configured to update the first load balancing group for the front-end service of the first service chain based on the BGP route updates, wherein to update the first load balancing group, the processor is further configured to at least one of add BGP routes to the first load balancing group for any new first virtual service instances or delete BGP routes from the first load balancing group for any removed first virtual service instances.

18. A software-defined networking (SDN) controller comprising:

a plurality of network interfaces; and

a control unit comprising a processor in communication with the plurality of network interfaces, the control unit configured to;

calculate border gateway protocol (BGP) routes for a front-end service of a first service chain within a services complex, wherein each of the BGP routes represents one of a plurality of unique tunnels that extends from a gateway network device to one of a plurality of first virtual service instances for the front-end service of the first service chain on one or more physical network devices within the services complex;

advertise, via the plurality of network interfaces to the gateway network device, the BGP routes for the front-end service of the first service chain as load balancing entities to be included in a first load balancing group for the front-end service of the first service chain;

calculate BGP routes for a front-end service of a second service chain within the services complex, wherein the front-end service of the second service chain is different than the front-end service of the first service chain, and wherein each of the BGP routes represents one of a plurality of unique tunnels that extends from the gateway network device to one of a plurality of second virtual service instances for the front-end service of the second service chain on one or more physical network devices within the services complex; and

advertise, via the plurality of network interfaces to the gateway network device, the BGP routes for the front-end service of the second service chain as load balancing entities to be included in a second load balancing group for the front-end service of the second service chain.

19. The SDN controller of claim 18, wherein the control unit is configured to advertise, via the plurality of network interfaces to the gateway network device, BGP route updates for the front-end service of the first service chain, wherein the BGP route updates include notifications of new first virtual service instances for the front-end service of the first service chain or notifications of removed first virtual service instances for the front-end service of the first service chain.

20. The SDN controller of claim 18, wherein the control unit is configured to establish the plurality of first virtual service instances for the front-end service of the first service chain as a plurality of virtual machines running on the one or more physical network devices within the services complex.