Bug 1400122

Summary:	Is there a timeline or roadmap for the introduction of quagga / ripd in OpenStack?
Product:	Red Hat OpenStack	Reporter:	David Peacock <dpeacock>
Component:	openstack-neutron	Assignee:	Assaf Muller <amuller>
Status:	CLOSED NOTABUG	QA Contact:	Toni Freger <tfreger>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	amuller, chrisw, dpeacock, nyechiel, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-01 12:39:58 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:

Description David Peacock 2016-11-30 13:46:06 UTC

Description of problem:

I've had a low-priority query from a customer, asking when quagga and ripd will be supported in Red Hat OpenStack Platform.  Please can anyone comment on this with regards to our roadmap?

I see some noises here and there about this - our own Bugzilla has something about quagga for controllers here in the recent BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1309533

Also, there is documentation regarding this in upstream RDO:

https://wiki.openstack.org/wiki/Neutron/DynamicRouting/TestingDynamicRouting

Is there anyone working on this at Red Hat?

Thank you.

Comment 1 David Peacock 2016-11-30 13:47:17 UTC

Salesforce case: 01742242

Comment 2 Nir Yechiel 2016-11-30 14:04:53 UTC

Hello David,

This is a very general question, and I am not sure I understand why the customer wants to use something like quagga or ripd. 

BZ #1309533 is talking about using something like quagga instead of HAProxy in front of the OpenStack services APIs. This needs to be discussed with our HA team.

The dynamic routing project you listed enables advertisement of self-service (private) network prefixes to physical network devices that support BGP such as routers, thus removing the conventional dependency on static routes. The feature relies on address scopes and requires knowledge of their operation for proper deployment. This allows a routed model for floating IPs and support for directly routable IPv4/IPv6 networks. Based on the current architecture, Neutron will advertise prefixes to peers, but will not learn from peers. 

I can confirm that Red Hat is not actively working on the Dynamic Routing project and we have no concrete plan to support it. But concrete feedback/use-case are always welcome.

Hope it helps,
Nir

Comment 3 David Peacock 2016-11-30 14:52:01 UTC

Thank you Nir; I've reached out to the customer and requested clarity and detail with regards to their intentions and ideal use case in their environment.

I'll be in touch as soon as they get back to me with the information; please keep this BZ open for the meanwhile.

Thank you,
David

Comment 4 Assaf Muller 2017-04-20 20:43:15 UTC

Any news?

Comment 5 David Peacock 2017-05-01 11:39:35 UTC

I think this may be abandoned Assaf, sorry!