This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 1896551 - [RFE][Tracker] Enable BGP Routing For Spine-Leaf Deployments
Summary: [RFE][Tracker] Enable BGP Routing For Spine-Leaf Deployments
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ga
: ---
Assignee: Dan Sneddon
QA Contact: David Rosenfeld
URL:
Whiteboard:
: 1895458 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-10 21:01 UTC by Dan Sneddon
Modified: 2023-05-09 06:07 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Technology Preview
Doc Text:
In Red Hat OpenStack Platform (RHOSP) 17.0, a technology preview is available for Border Gateway Protocol (BGP) to route the control plane, floating IPs, and workloads in provider networks. By using BGP advertisements, you do not need to configure static routes in the fabric, and RHOSP can be deployed in a pure Layer 3 data center. RHOSP uses Free Range Routing (FRR) as the dynamic routing solution to advertise and withdraw routes to control plane endpoints as well as to VMs in provider networks and Floating IPs.
Clone Of:
Environment:
Last Closed: 2023-05-09 06:07:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 763657 0 None master: MERGED tripleo-heat-templates: Add FRR service (I7cef73c57e7b69f4d031e220c954803afd5e0b8c) 2022-12-06 17:10:28 UTC
Red Hat Bugzilla 1458198 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1788993 0 high CLOSED [RFE] Support Controller HA deployment across multiple L2 networks / Multirack-HA 2022-10-14 10:38:41 UTC
Red Hat Bugzilla 1791821 0 unspecified CLOSED [RFE] Neutron add BGP dynamic routing support with dragent 2024-01-06 04:27:34 UTC
Red Hat Bugzilla 1861527 0 high CLOSED Excessive memory and CPU usage on a router with IPv6 BGP feed. 2022-05-10 15:57:23 UTC
Red Hat Bugzilla 1868802 0 unspecified CLOSED [RFE] Neutron routing with BGP FRR 2022-06-20 12:45:09 UTC
Red Hat Bugzilla 1889323 1 None None None 2023-06-26 11:45:43 UTC
Red Hat Bugzilla 1895448 1 None None None 2022-10-17 13:15:17 UTC
Red Hat Bugzilla 1908719 1 medium CLOSED [RFE] Create FRRouting Container For BGP Routing 2022-10-07 08:45:32 UTC
Red Hat Bugzilla 1997510 1 unspecified CLOSED [RFE] BGP HA Control Plane For OSP 2022-10-07 09:01:43 UTC
Red Hat Bugzilla 1997518 1 unspecified CLOSED [RFE] BGP ECMP and BFD Support For OSP Overcloud Nodes 2022-10-07 08:45:28 UTC
Red Hat Bugzilla 2059862 0 medium CLOSED [RFE] Productization of OVN BGP Agent: TripleO integration 2022-10-17 13:13:55 UTC
Red Hat Bugzilla 2059983 0 high CLOSED [RFE] Support Controller HA deployment across multiple L2 networks / Multirack-HA 2022-10-17 12:35:13 UTC
Red Hat Issue Tracker OSP-2412 0 None None None 2021-11-18 15:14:22 UTC
Red Hat Issue Tracker   OSP-3883 0 None None None 2023-05-09 06:07:36 UTC

Internal Links: 1908719 1997510 1997518

Description Dan Sneddon 2020-11-10 21:01:19 UTC
Description of problem:
Routed spine-and-leaf networking is becoming a de-facto standard architecture for cloud networking and overall datacenter design. Increasingly operators are using dynamic routing between the spines and leaves. Some operators would benefit from extending dynamic routing down to the cloud bare metal nodes so that cloud resources can participate in the dynamic routing fabric. This is a tracker bug to add support for dynamic routing using FRRouter (FRR) and BGP.

Version-Release number of selected component (if applicable):
16.2

Expected results:
The operator should be able to peer with the gateway routers (often layer 3 switches installed at the top of the rack) using BGP. The Overcloud node would optionally receive gateway routes and advertise routes to local IP addresses depending on the role. For example an HA Controller node would advertise a route to a virtual IP address using a route to the /32 IPv4 or /128 IPv6 address and a Compute node would advertise a VM real or floating IP address. Some roles may only receive routes in order to take advantage of optimized routing including equal-cost multipath (ECMP) routing, which can act as a viable alternative to bonds for nodes with dual or quad 25+ Gb uplinks.


Additional info:
This is an overall tracker bug, and will link to upstream and downstream RFEs, bugs, and code reviews.

Comment 3 Dan Sneddon 2020-11-10 22:39:42 UTC
There are requests for RHOSP to go beyond some of the current network design, centered on:
* removing layer-2 connectivity requirements
* have layer-3 dynamic routing support for both control plane and data plane.
Routing on both should happen via BGP-announced routes

This is a tracker RFE to regroup all parts needed to achieve this goal:
* TripleO templates and Ansible playbook for installing FRR
* Support HA VIP endpoints advertised via BGP
* Dynamic routing support for OVN
* Proxy ARP in core OVN

Comment 4 Dan Sneddon 2020-11-10 22:42:10 UTC
*** Bug 1895458 has been marked as a duplicate of this bug. ***

Comment 7 Alex Stupnikov 2021-02-12 11:24:47 UTC
FYI. One of the customers showed interest in this feature.


Note You need to log in before you can comment on or make changes to this bug.