Bug 1896551

Summary:	[RFE][Tracker] Enable BGP Routing For Spine-Leaf Deployments
Product:	Red Hat OpenStack	Reporter:	Dan Sneddon <dsneddon>
Component:	rhosp-director	Assignee:	Dan Sneddon <dsneddon>
Status:	CLOSED MIGRATED	QA Contact:	David Rosenfeld <drosenfe>
Severity:	low	Docs Contact:
Priority:	medium
Version:	17.0 (Wallaby)	CC:	astupnik, bcafarel, bdobreli, cgoncalves, dalvarez, gregraka, hakhande, lpeer, ltamagno, ltomasbo, mburns, michele, moddi, morazi, pweeks, sbaker
Target Milestone:	ga	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-09 06:07:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.