yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #85720
[Bug 1922716] [NEW] BFD for BGP Dynamic Routing
Public bug reported:
#Problem Description
Improve network convergence for the BGP Control Plane .
#Proposed Change
To improve network convergence for the BGP Control Plane, the proposal is to integrate BFD-Service with the BGP dynamic routing. To achieve this, APIs available from bfd-as-a-service initiative will be leveraged , and BFD-Monitors created using these APIs will be used while configuring BGP-Peering for BGPSpeakers.
Use-cases)
~~~~~~~~~~~~~
1.Provide the ability to configure bfd-monitoring when configuring BGP peering, to enable BFD monitoring of BGP-Peering-Link between the BGP Speaker and the BGP Peer
2.Provide the ability to unconfigure bfd-monitor from an existing BGP peering
* Modify the following APIs to Neutron:
1. POST /v2.0/bgp-peers/
{
"bgp_peer":{
"auth_type":"none",
"remote_as":"1001",
"name":"bgppeer1",
"peer_ip":"10.0.0.3“,
“bfd_monitor_id”: “b930d7f6-ceb7-40a0-8b81-a425dd994ccf”
}
}
2. PUT /v2.0/bgp-peers/{bgp-peer-id}
Remove bfd_monitor_id and update
{
"bgp_peer":{
"auth_type":"none",
"remote_as":"1001",
"name":"bgppeer1",
"peer_ip":"10.0.0.3“,
}
}
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1922716
Title:
BFD for BGP Dynamic Routing
Status in neutron:
New
Bug description:
#Problem Description
Improve network convergence for the BGP Control Plane .
#Proposed Change
To improve network convergence for the BGP Control Plane, the proposal is to integrate BFD-Service with the BGP dynamic routing. To achieve this, APIs available from bfd-as-a-service initiative will be leveraged , and BFD-Monitors created using these APIs will be used while configuring BGP-Peering for BGPSpeakers.
Use-cases)
~~~~~~~~~~~~~
1.Provide the ability to configure bfd-monitoring when configuring BGP peering, to enable BFD monitoring of BGP-Peering-Link between the BGP Speaker and the BGP Peer
2.Provide the ability to unconfigure bfd-monitor from an existing BGP peering
* Modify the following APIs to Neutron:
1. POST /v2.0/bgp-peers/
{
"bgp_peer":{
"auth_type":"none",
"remote_as":"1001",
"name":"bgppeer1",
"peer_ip":"10.0.0.3“,
“bfd_monitor_id”: “b930d7f6-ceb7-40a0-8b81-a425dd994ccf”
}
}
2. PUT /v2.0/bgp-peers/{bgp-peer-id}
Remove bfd_monitor_id and update
{
"bgp_peer":{
"auth_type":"none",
"remote_as":"1001",
"name":"bgppeer1",
"peer_ip":"10.0.0.3“,
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1922716/+subscriptions