[NETVIRT-1498] Subnet based Route Aggregation Created: 31/Oct/18  Updated: 27/Nov/19  Resolved: 27/Nov/19

Status: Resolved
Project: netvirt
Component/s: coe, elanmanager, vpnmanager
Affects Version/s: None
Fix Version/s: Magnesium

Type: Story Priority: Medium
Reporter: Faseela K Assignee: Faseela K
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: COE

 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

 Comments   
Comment by Abhinav Gupta [ 27/Nov/19 ]

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

Generated at Wed Feb 07 20:24:12 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.