Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Subnet based Route Aggregation

Description

Since all the IPs from a subnet reside on the same node in our k8s deployment, route aggregation will ensure minimal configuration update during pod bring up.

  • Instead of /32 prefixes in FIB (as of today), the entries contain a subnet route whose next hop is the node to which that subnet is assigned

  • When a pod is brought up on a node, ODL will only update the FIB on that node to handle packets destined to the pod.

  • Note: Route Aggregation is NOT present in ODL today, since it does not make sense in the NFVi deployment model. Route aggregation must be added to ODL

Activity

Show:

Abhinav Gupta November 27, 2019 at 9:59 AM

CoE is removed in Magnesium, hence no further work on this will be done

Won't Do

Details

Assignee

Reporter

Components

Fix versions

Priority

Parent

Created October 31, 2018 at 4:44 PM
Updated November 27, 2019 at 9:59 AM
Resolved November 27, 2019 at 9:59 AM
Configure