Bug 1433532 (ovnl3ha)

Summary: [RFE] [Neutron] [OVN] L3 HA
Product: Red Hat OpenStack Reporter: Assaf Muller <amuller>
Component: openvswitchAssignee: Miguel Angel Ajo <majopela>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: apevec, chrisw, dalvarez, ekuris, jlibosva, majopela, nyechiel, rhos-maint, sclewis, srevivo, tfreger
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openvswitch-2.9.0-3.el7fdb Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:29:18 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:
Bug Depends On:    
Bug Blocks: 1498491, 1548947    

Description Assaf Muller 2017-03-17 23:09:38 UTC
OVN L3 is currently a single point of failure and it should be highly available.

Comment 3 Miguel Angel Ajo 2017-04-24 13:15:30 UTC
Discussing up with the community

And talking about limitations of the planned approach to do L3 HA Active/Standby, which are also present on VRRP or other protocols.

Comment 4 Assaf Muller 2017-04-24 13:28:12 UTC
This will require OVS 2.8, pushed to OSP 13.

Comment 5 Miguel Angel Ajo 2017-07-17 15:50:27 UTC
ovn-core patches merged, now we need to work on the networking-ovn side.

Comment 7 Nir Yechiel 2017-10-03 15:00:29 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 8 Nir Yechiel 2017-10-03 15:00:44 UTC
*** Bug 1498109 has been marked as a duplicate of this bug. ***

Comment 12 Eran Kuris 2018-04-10 06:34:08 UTC
verified on OSP13 puddle 2018-04-03.3

there are some bugs. All the results updated in test run:


Comment 14 errata-xmlrpc 2018-06-27 13:29:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.