[RFE] bgp-dragent-hosting-multiple-speakers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Unassigned |
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.
[Proposal]
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.
[Benefits]
- 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
https:/
summary: |
- bgp-dragent-hosting-multiple-speakers + [RFE] bgp-dragent-hosting-multiple-speakers |
Changed in neutron: | |
importance: | Undecided → Wishlist |
tags: | added: bgp l3-ipam-dhcp |
Changed in neutron: | |
assignee: | nobody → vikram.choudhary (vikschw) |
tags: |
added: l3-bgp removed: bgp |
tags: | removed: l3-ipam-dhcp |
Changed in neutron: | |
status: | Triaged → Confirmed |
tags: |
added: rfe-postponed removed: rfe |
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?