[RFE] bgp-route-aggregation

Bug #1528000 reported by vikram.choudhary
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Wishlist
Na Zhu

Bug Description

[Existing problem]
Current BGP dynamic routing proposal [1]_ doesn't have support for route aggregation. Route aggregation could be extremely useful in reducing the size of the routing table and improves CPU utilization [2]_.

[Proposal]
- Add route-aggregation support to BGP dynamic routing.

[Benefits]
- Route aggregation is good as it reduces the size, and slows the growth, of the Internet routing table.
- Amount of resources (e.g., CPU and memory) required to process routing information is reduced and route calculation is sped up.
- Route flaps becomes limited in number

[What is the enhancement?]
- - Additional API, CLI and DB model will be added.

[Related information]
[1] Dynamic Advertising Routes for Public Ranges
    https://specs.openstack.org/openstack/neutron-specs/specs/mitaka/bgp-dynamic-routing.html
[2] A Framework for Inter-Domain Route Aggregation
    https://tools.ietf.org/html/rfc2519

Akihiro Motoki (amotoki)
summary: - bgp-route-aggregation
+ [RFE] bgp-route-aggregation
Changed in neutron:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Akihiro Motoki (amotoki) wrote :

The feature which this RFE depends on is not yet implemented.
It is valid as a feature request, but the requested feature can be implemented during the current proposed implementation.

Revision history for this message
Akihiro Motoki (amotoki) wrote :

We need to revisit this after BGP-DR blueprint completes.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Thanks for the update. I think it's fair to say that until [1] is feature complete (blueprints implemented - i.e. basic code, tests, docs), bugs [2-7] are blocked. My suggestion would be to go and yell/help the assignee/approver of [1] and make sure that the work can complete successfully asap so that we can start focusing on 2-7 knowing on what grounds we can continue building.

[1] https://blueprints.launchpad.net/neutron/+spec/bgp-dynamic-routing
[2] https://bugs.launchpad.net/neutron/+bug/1509431
[3] https://bugs.launchpad.net/neutron/+bug/1509436
[4] https://bugs.launchpad.net/neutron/+bug/1527993
[5] https://bugs.launchpad.net/neutron/+bug/1528000
[6] https://bugs.launchpad.net/neutron/+bug/1528002
[7] https://bugs.launchpad.net/neutron/+bug/1528003

Revision history for this message
Carl Baldwin (carl-baldwin) wrote :

This should be considered with Host Aware IPAM [1]

[1] https://bugs.launchpad.net/neutron/+bug/1540512

tags: added: bgp l3-ipam-dhcp
Changed in neutron:
assignee: nobody → vikram.choudhary (vikschw)
tags: added: l3-bgp
removed: bgp
Revision history for this message
vikram.choudhary (vikschw) wrote :

Let's wait for driver's team confirmation..

Changed in neutron:
assignee: vikram.choudhary (vikschw) → nobody
Revision history for this message
Ryan Tidwell (ryan-tidwell) wrote :

This will become more of a priority when DVR can route for a local fixed IP and we start sending announcements for each fixed IP. I think there is a host-aware IPAM component to this as well

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Assumed that by the end of Newton (or sooner if possible) the BGP repo is up and running and rock solid based on the efforts put into Mitaka, I see no reason why these requests should not be vetted and addressed by the BGP team directly. So please make a recommendation.

Changed in neutron:
status: Confirmed → Triaged
tags: removed: l3-ipam-dhcp
Na Zhu (nazhu)
Changed in neutron:
assignee: nobody → Na Zhu (nazhu)
Changed in neutron:
status: Triaged → Confirmed
tags: added: rfe-postponed
removed: rfe
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Bug closed due to lack of activity, please feel free to reopen if needed.

Changed in neutron:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.