Bug 1400122 - Is there a timeline or roadmap for the introduction of quagga / ripd in OpenStack?
Summary: Is there a timeline or roadmap for the introduction of quagga / ripd in OpenS...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Assaf Muller
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-30 13:46 UTC by David Peacock
Modified: 2017-05-01 12:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-01 12:39:58 UTC
Target Upstream Version:


Attachments (Terms of Use)

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!


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