| 2021-04-06 11:19:56 |
Manu B |
bug |
|
|
added bug |
| 2021-04-06 11:47:29 |
Akihiro Motoki |
tags |
|
rfe |
|
| 2021-04-06 11:47:35 |
Akihiro Motoki |
summary |
BFD for BGP Dynamic Routing |
[RFE] BFD for BGP Dynamic Routing |
|
| 2021-04-06 12:36:16 |
Manu B |
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“,
}
} |
#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“,
}
}
#Dependency
bug 1907089 |
|
| 2021-04-06 13:14:10 |
Manu B |
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“,
}
}
#Dependency
bug 1907089 |
#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 [1] 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“,
}
}
#Dependency
bug 1907089
[1] https://review.opendev.org/c/openstack/neutron-specs/+/767337/9/specs/wallaby/bfd_support.rst |
|
| 2021-04-09 10:24:55 |
Manu B |
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 [1] 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“,
}
}
#Dependency
bug 1907089
[1] https://review.opendev.org/c/openstack/neutron-specs/+/767337/9/specs/wallaby/bfd_support.rst |
#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 [1] 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“,
}
}
#Dependency
bug 1907089
bug 1921461
[1] https://review.opendev.org/c/openstack/neutron-specs/+/767337/9/specs/wallaby/bfd_support.rst |
|
| 2021-04-11 22:25:21 |
Miguel Lavalle |
neutron: importance |
Undecided |
Wishlist |
|
| 2021-04-11 22:27:04 |
Miguel Lavalle |
neutron: status |
New |
Confirmed |
|
| 2021-04-15 13:00:04 |
Slawek Kaplonski |
tags |
rfe |
rfe-triaged |
|
| 2021-04-30 14:17:35 |
Slawek Kaplonski |
tags |
rfe-triaged |
rfe-approved |
|
