Juniper Networks, Inc.

Yuvaraja Mariappan

Sachchidanand Vaidya

Shailender Sharma

Jude Pragash Vedam

Aniket J Gawade

Dinesh Bakiaraj

Rakesh Kumar Reddy Varimalla

Raja Kommula

Thayumanavan Sridhar

Raj Yavatkar

Kiran K N

Rudramahesh S Rugge

James Nicholas Davey

Margarida Correia

Prasad Miriyala

Anantharamu Suryanarayana

Richard Roberts

Sangarshan Pillareddy

Dilip Sundarraj

Pragash Vijayaragavan

Prasanna D Mucharikar

Haji Mohamed Ashraf Ali

Mahesh Sivakumar

Vinay K Nallamothu

Ashutosh K Grewal

Venkatraman Venkatapathy

Pranavadatta D N

Sajeesh Mathew

Srinivas Akkipeddi

Darrell Ball

Senthilnathan Murugappan

Madhukar Nayakbomman

Narendranath Karjala Subramanyam

Pavan Kumar Kurapati

Philip M Goddard

Rudhraraju Narasimha Kishore Varma

Nagendra E S

Sivakumar Ganapathy

Vikram Singh

Vinay Chandrakant Rao

Ganesh Byagoti Matad Sunkada

Santha Nagesh Ayyagari

An example system comprises a plurality of servers comprising respective network interface cards (NICs) connected by physical links in a physical topology, wherein each NIC of the plurality of NICs comprises an embedded switch and a processing unit coupled to the embedded switch; and an edge services controller configured to program the processing unit of a network interface card of the plurality of network interface cards to: receive, at a first network interface of the NIC, a data packet from a physical device; based on the data packet being received at the first network interface, modify the data packet to generate a modified data packet; and output the modified data packet to the physical device via a second network interface of the NIC.

Extending switch fabric processing to network interface cards

A container-based orchestration system includes a master node and a plurality of worker nodes. The master node can receive, from each agent executing on a corresponding worker node, node characteristics associated with the worker node. The master node can determine, for each worker node, one or more parameters corresponding to the node characteristics associated with the corresponding worker node and a node profile of the worker node and provide the parameters to the agent executing on the corresponding worker node. The agent configures the worker node in accordance with the parameters. In response to receiving a request to deploy a pod to a worker node, the master node can select a worker node to receive the pod based on the node characteristics and the pod characteristics. The agent can configure the selected worker node to execute workloads of the pod in accordance with the one or more parameters.

Dynamically adjusting performance tuning parameters in a network system

Techniques are described for creating isolated pools of external, failover, and/or floating IP addresses. In one example, this disclosure describes a method including creating a plurality of virtual networks, creating a plurality of pools of external IP addresses, detecting a request to instantiate an object that identifies a specific pool from the plurality of pools of external IP addresses; and instantiating the object and configuring the object with an external IP address drawn from the specific pool. The pools of external IP addresses may be created and isolated on a per-namespace, per-service, or per-ingress basis.

Allocating addresses from pools

In general, this disclosure describes techniques for a containerized router operating within a cloud native orchestration framework. In an example, a virtualized cell site router comprises a computing device configured with a containerized router, the computing device comprising: a containerized virtual router configured to execute on the processing circuitry and configured to implement a data plane for the containerized router; a containerized routing protocol process configured to execute on the processing circuitry and configured to implement a control plane for the containerized router; and a pod comprising a containerized distributed unit, wherein the containerized routing protocol process is configured to advertise routing information comprising reachability information for the containerized distributed unit.

Containerized router with virtual networking

A container orchestration platform manages a plurality of instances of resources including a first custom resource and a second custom resource. An API server of the container orchestration platform receives a request to delete an instance of the second custom resource; determines whether instance data associated with the instance of the second custom resource has a backreference identifying an instance of the first custom resource, the backreference indicating the instance of the first custom resource is dependent on the instance of the second custom resource; and in response to determining that the instance data has the backreference to the instance of the first custom resource, bypasses deletion of the instance of the second custom resource.

Protecting instances of resources of a container orchestration platform from unintentional deletion

Techniques are described for learning an unknown virtual network information, such as an virtual Internet Protocol (IP) address, of a pod in a virtual network. In some examples, a virtual router executing at a computing device may receive an Address Resolution Protocol (ARP) packet from a virtual execution element in the virtual network, the virtual execution element executing at the computing device. The virtual router may determine, based at least in part on the ARP packet, whether virtual network information for the virtual execution element in a virtual network is known to the virtual router. The virtual router may, in response to determining that the virtual network information of the virtual execution element in the virtual network is not known to the virtual router, perform learning of the virtual network information for the virtual execution element.

Dynamically learning media access control and internet protocol addresses

In general, techniques are described for a computing device including a virtual router, a pod comprising a container, and a network plugin. The virtual router includes a virtual router agent. The network plugin includes processing circuitry configured to receive, from the virtual router agent, an indication of an interface type for a virtual network for the pod and to configure, for the pod, a virtual network interface having the interface type, the virtual network interface for communicating on the virtual network.

Container networking interface for multiple types of interfaces

Techniques are described for performing latency-aware load balancing. In some examples, a computing device communicably coupled to a plurality of service endpoints that are in motion with respect to the computing device may receive data to be processed. The computing device may select, based at least in part on a communication latency of each of the plurality of service endpoints and a predicted compute latency of each of the plurality of service endpoints, a service endpoint out of the plurality of service endpoints to process the data. The computing device may send the data to the selected service endpoint for processing.

Latency-aware load balancer for topology-shifting software defined networks

In general, techniques are described for deploying a logically-related group of one or more containers ('pod') that supports the Data Plane Development Kit (DPDK) to support fast path packet communication on a data channel between a virtual router and the pod. In an example, a computing device comprises a virtual router comprising processing circuitry and configured to implement, in a computing infrastructure that includes the computing device, a virtual network to enable communications among virtual network endpoints connected via the virtual network. The computing devices comprises a pod comprising a containerized application, wherein the virtual router and the pod are configured to create a Unix domain socket using a file system resource that is accessible by the pod and by the virtual router and is not accessible by any other pods deployed to the computing device.

Data interfaces with isolation for containers deployed to compute nodes

A system comprises an edge services controller configured to: compute, based on a physical topology of physical links that connect a plurality of network interface cards (NICs) that comprise embedded switches and processing units coupled to the embedded switches, a virtual topology comprising a strict subset of the physical links; and program the virtual topology into the respective processing units of the NICs to cause the processing units of the NICs to send data packets via physical links in the strict subset of the physical links.

Dynamic network interface card fabric

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.

Configuring service load balancers with specified backend virtual networks

Allocating external IP addresses from isolated pools

A software defined networking (SDN) controller is configured to receive, from a Top-Of-Rack (TOR) switch, a first multicast route and a second multicast route. In response to determining that the first multicast route is an assisted replication route, the SDN controller is configured to add a first nexthop specified by the first multicast route to a list of nexthops for Broadcast, Unknown-Unicast, and Multicast (BUM) traffic. In response to determining that the second multicast route is not the assisted replication route, the SDN controller is configured to refrain from adding a second nexthop specified by the second multicast route to the list of nexthops. After adding the first nexthop, the SDN controller is configured to provision the list of nexthops at a virtual router.

Assisted replication in software defined network

Growing community of inventors

San Jose, CA, United States of America

Yuvaraja Mariappan