Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1498109

Summary:	[RFE] L3HA support
Product:	Red Hat OpenStack	Reporter:	Miguel Angel Ajo <majopela>
Component:	python-networking-ovn	Assignee:	Assaf Muller <amuller>
Status:	CLOSED DUPLICATE	QA Contact:	Ofer Blaut <oblaut>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	apevec, lhh, majopela, nyechiel
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-10-03 15:00:44 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 Miguel Angel Ajo 2017-10-03 13:58:09 UTC

Support for basic L3HA has landed U/S in both ovn (ovs 2.8) and neworking-ovn (Queens) mechanism driver.

But we need to polish it and add support to let the admin discover which controller is the master through the API (without looking at the SBDB manually).

Comment 1 Russell Bryant 2017-10-03 14:44:11 UTC

An idea we just discussed was extending the northbound database with a simple boolean on the Gateway_Chassis table to reflect if it's the current master or not.  That information is already available through the southbound database by examining the Port_Binding table, but doing something in the northbound db would be a usability improvement.

One catch is that the current db schema allows you to reference a single Gateway_Chassis for multiple gateways, so maybe putting the column on Gateway_Chassis doesn't work.  Another option could be a new column on Logical_Router_Port that references a single gateway_chassis row to indicate which is the current master.

Comment 2 Nir Yechiel 2017-10-03 15:00:44 UTC


*** This bug has been marked as a duplicate of bug 1433532 ***