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

Bug 1503502 (ovndvr)

Summary:	[RFE] [Neutron] [OVN] DVR support
Product:	Red Hat OpenStack	Reporter:	Miguel Angel Ajo <majopela>
Component:	python-networking-ovn	Assignee:	Miguel Angel Ajo <majopela>
Status:	CLOSED ERRATA	QA Contact:	Eran Kuris <ekuris>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	amuller, apevec, bcafarel, dalvarez, jlibosva, lhh, majopela, nyechiel, oblaut
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	13.0 (Queens)	Flags:	ekuris: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-networking-ovn-4.0.0-0.20171205134230.746cae0.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-27 13:37:31 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:
Bug Depends On:
Bug Blocks:	1498491, 1548947

Description Miguel Angel Ajo 2017-10-18 09:51:38 UTC

Description of problem:
While the OVN C core supports DVR, the implementation on the mechanism driver isn't still merged. We need to help with review capacity and ensure proper testing of the feature.

Expected results:

FIPs can be exposed from compute nodes directly (DVR) when the compute nodes have external connectivity.

DVR related tests pass.

Comment 7 Eran Kuris 2018-04-25 13:23:14 UTC

verifed : 
rpm -qa | grep  python-networking-ovn-4
python-networking-ovn-4.0.1-0.20180405185449.b9e550d.el7ost.noarch

test runs on Genenve & VLAN tetnat network type : 
https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/testrun?id=20180410-0800

https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/testrun?id=20180415%2D0649

Comment 9 errata-xmlrpc 2018-06-27 13:37:31 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.

https://access.redhat.com/errata/RHEA-2018:2086