IP Library Granted Patent US 11,792,126
Granted Patent B2
US 11,792,126 · App. 16/949,684 · Granted Oct 17, 2023

Configuring service load balancers with specified backend virtual networks

Inventors: Yuvaraja Mariappan (San Jose, CA); Sachchidanand Vaidya (Santa Clara, CA); Pragash Vijayaragavan (Sunnyvale, CA); Prasanna D. Mucharikar (Fremont, CA)
Assignee: Juniper Networks, Inc.
H04L47/125G06F9/45558G06F9/5077H04L61/5007G06F2009/45595
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,792,126
App. No.
16/949,684
Granted
Oct 17, 2023
Kind
B2
Abstract

Techniques are described for specifying a backend virtual network for a service load balancer. An example orchestrator of this disclosure is configured to receive a service definition for a service implemented by load balancing service traffic for the service among a plurality of backend virtual execution elements, wherein the service definition specifies a first virtual network to use as a backend virtual network for the service, to instantiate, in a selected one of the computing devices, a backend virtual execution element for the service, and to configure, based on the service definition specifying the first virtual network to use as the backend virtual network for the service, a network controller for the virtualized computing infrastructure to configure a load balancer to load balance service traffic to a first virtual network interface, of the backend virtual element, for the first virtual network.

Claims (57)

1. A system comprising:

an orchestrator for a virtualized computing infrastructure, wherein the orchestrator comprises processing circuitry coupled to memory, configured to:

receive a service definition for a service, wherein the service definition specifies an identifier of a backend virtual network for the service, wherein the backend virtual network is one of a plurality of virtual networks implemented on a physical network for the virtualized computing infrastructure,

create a load balancer object for a load balancer, wherein the load balancer object comprises a load balancer member object, and

annotate the load balancer member object to specify a virtual network interface corresponding to a network label identifying the backend virtual network; and

a network controller, wherein the network controller comprises processing circuitry coupled to memory, configured to:

send, to a computing device that hosts a backend virtual execution element for the service, interface configuration data to configure, for the backend virtual execution element, the virtual network interface for the backend virtual network to enable communications with the load balancer on the backend virtual network, and

configure, based on the load balancer member object annotation specifying the virtual network interface, the load balancer to load balance service traffic for the service in part to the virtual network interface for the backend virtual network.

2. The system of claim 1 , wherein the orchestrator is configured to direct the network controller to create the load balancer for the service.

3. The system of claim 1 , wherein the network controller is configured to:

allocate a service Internet Protocol (IP) address for the service; and

configure the service with the service IP address.

4. The system of claim 1 ,

wherein the orchestrator is configured to annotate configuration data for the backend virtual execution element to specify the backend virtual network, and

wherein the network controller is configured to, based on the annotated configuration data for the backend virtual execution element, send the interface configuration data to configure, for the backend virtual execution element, the virtual network interface for the backend virtual network.

5. The system of claim 1 , wherein to configure the load balancer, the network controller is configured to:

receive a virtual network address for the virtual network interface for the backend virtual network; and

configure the load balancer to load balance the service traffic in part to the virtual network address.

6. The system of claim 1 , wherein to configure the load balancer, the network controller is configured to:

receive a virtual network address for the virtual network interface for the backend virtual network in association with a service Internet Protocol (IP) address for the service; and

configure the load balancer to load balance the service traffic, sent to the service IP address, in part to the virtual network address.

7. The system of claim 1 ,

wherein the virtual network interface for the backend virtual network is the primary interface of the backend virtual execution element.

8. The system of claim 1 , wherein the backend virtual execution element comprises a Kubernetes pod.

9. The system of claim 8 , wherein the load balancer comprises a Kubernetes service that provides access to the Kubernetes pod via a service Internet Protocol (IP) address assigned to the Kubernetes service.

10. The system of claim 1 , wherein the orchestrator is configured to:

select the network label identifying the backend virtual network, and configure the load balancer object based on the network label.

11. The system of claim 1 , wherein the load balancer object comprises a load balancer listener object, and a load balancer pool object.

12. An orchestrator for a virtualized computing infrastructure, the orchestrator comprising:

processing circuitry coupled to memory, configured to:

receive a service definition for a service, wherein the service definition specifies an identifier of a backend virtual network for the service, wherein the backend virtual network is one of a plurality of virtual networks implemented on a physical network for the virtualized computing infrastructure;

create a load balancer object for a load balancer, wherein the load balancer object comprises a load balancer member object;

annotate the load balancer member object to specify a virtual network interface corresponding to a network label identifying the backend virtual network; and

configure, based in part on the load balancer member object annotation specifying the virtual network interface, a network controller to configure the load balancer to load balance service traffic for the service in part to the virtual network interface, of a backend virtual execution element, for the backend virtual network to enable communications with the load balancer on the backend virtual network.

13. A method comprising:

receiving, by an orchestrator for a virtualized computing infrastructure, a service definition for a service, wherein the service definition specifies an identifier of a backend virtual network for the service, wherein the backend virtual network is one of a plurality of virtual networks implemented on a physical network for the virtualized computing infrastructure;

creating, by the orchestrator, a load balancer object for a load balancer, wherein the load balancer object comprises a load balancer member object;

annotating the load balancer member object to specify a virtual network interface corresponding to a network label identifying the backend virtual network;

sending, by a network controller, to a computing device that hosts a backend virtual execution element for the service, interface configuration data to configure, for the backend virtual execution element, the virtual network interface for the backend virtual network to enable communications with the load balancer on the backend virtual network; and

configuring, by the network controller and based on the load balancer member object annotation specifying the virtual network interface, the load balancer to load balance service traffic for the service in part to the virtual network interface for the backend virtual network.

14. The method of claim 13 , further comprising creating the load balancer for the service.

15. The method of claim 13 , further comprising:

allocating a service Internet Protocol (IP) address for the service; and

configuring the service with the service IP address.

16. The method of claim 13 , further comprising:

annotating, by the orchestrator, configuration data for the backend virtual execution element to specify the backend virtual network; and

sending, based on the annotated configuration data for the backend virtual execution element, the interface configuration data to configure, for the backend virtual execution element, the virtual network interface for the backend virtual network.

17. The method of claim 13 , wherein configuring the load balancer further comprises:

receiving a virtual network address for the virtual network interface for the backend virtual network; and

configuring the load balancer to load balance the service traffic in part to the virtual network address.

18. The method of claim 13 , wherein configuring the load balancer further comprises:

receiving a virtual network address for the virtual network interface for the backend virtual network in association with a floating Internet Protocol (IP) address for the service; and

configuring the load balancer to load balance the service traffic, sent to the service IP address, in part to the virtual network address.

19. The method of claim 13 , further comprising:

selecting, by the orchestrator, the network label identifying the backend virtual network; and

configuring, by the orchestrator, the load balancer object based on the network label.

20. The method of claim 13 , wherein the load balancer object comprises a load balancer listener object, and a load balancer pool object.

Assignments (1)
NUNC PRO TUNC ASSIGNMENT Recorded May 6, 2026
From: JUNIPER NETWORKS, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 075513/0034 →
Continuity (2)
Continuation 16369169 · Mar 29, 2019
Related Publication 20210058327A1 · Feb 25, 2021
Cited By (1)
US 12,695,701