[RFE] bgp-dragent-hosting-multiple-speakers

Bug #1528003 reported by vikram.choudhary
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

[Existing problem]
The number of BGP speakers a BGP driver can host may vary. For instance Ryu can support only 1 BGP Speaker while Quagga can host multiple. In the current BGP dynamic routing implementation [1]_, the BGP DrAgent and DrScheduler cannot adjust themselves as per the driver support which might be required for effective scheduling.

There could be 2 ways for achieving this:
1. Admin can hard code the support information in the configuration file and the same could be read by BGP DrAgent and DrScheduler during start-up.
2. New interface can be exposed by BGP DrAgent to DrScheduler using which DrScheduler retrieve this information during start-up.

- Effective scheduling.

[What is the enhancement?]
- Configuration file changes. [Proposal-1]
- New interface between BGP DrAgent and DrScheduler will be designed. [Proposal-2]

[Related information]
[1] Dynamic Advertising Routes for Public Ranges

Akihiro Motoki (amotoki)
summary: - bgp-dragent-hosting-multiple-speakers
+ [RFE] bgp-dragent-hosting-multiple-speakers
Changed in neutron:
importance: Undecided → Wishlist
Revision history for this message
Akihiro Motoki (amotoki) wrote :

The feature which this RFE depends on is not yet implemented.
The requested feature can be implemented during the current proposed implementation.
is it really an RFE or a feature-backlog bug?

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

I marked this as Incomplete temporarily.

Changed in neutron:
status: New → Incomplete
Revision history for this message
Akihiro Motoki (amotoki) wrote :

On a second thought, it is reasonable and valid as a feature request, so I reset the status to New.
I would like to check how we will deal with this kind of RFEs.

Changed in neutron:
status: Incomplete → New
status: New → Confirmed
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

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
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
Changed in neutron:
status: Triaged → Confirmed
tags: added: rfe-postponed
removed: rfe
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers