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

Bug 1426119

Summary:	Enhancement: Allow configuration of inactivity_probe and max_backoff for OVS
Product:	Red Hat OpenStack	Reporter:	Sridhar Gaddam <sgaddam>
Component:	opendaylight	Assignee:	Sridhar Gaddam <sgaddam>
Status:	CLOSED ERRATA	QA Contact:	Itzik Brown <itbrown>
Severity:	high	Docs Contact:
Priority:	high
Version:	10.0 (Newton)	CC:	mkolesni, nyechiel, sgaddam
Target Milestone:	async	Keywords:	ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	opendaylight-5.2.0-6.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	N/A
Last Closed:	2017-03-23 16:15:49 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 Sridhar Gaddam 2017-02-23 08:58:01 UTC

Description of problem:
Echo request from OVS uses default value today, which is 5 seconds. In scale setups, Full GC can take more than 5 seconds which will result in a disconnection from all OVSs. 
To control this behavior, inactivity_probe can be increased when creating a bridge.
OVSDB already created a patch that will allow its clients to define their desired inactivity_probe:
https://git.opendaylight.org/gerrit/#/c/50643/

Now Netvirt needs to expose an ability to configure this externally.

Comment 1 Sridhar Gaddam 2017-02-23 08:59:16 UTC

Proposed the following downstream patch:
https://code.engineering.redhat.com/gerrit/#/c/98244/

Comment 3 Itzik Brown 2017-03-06 14:12:12 UTC

Hi,
Please specify how to verify.

Comment 4 Sridhar Gaddam 2017-03-07 10:13:22 UTC

Steps to verify:

Create the file “etc/opendaylight/datastore/initial/config/netvirt-elanmanager-config.xml” with the following params before starting karaf.

<elanmanager-config xmlns="urn:opendaylight:netvirt:elan:config">
 <auto-create-bridge>true</auto-create-bridge>
 <int-bridge-gen-mac>true</int-bridge-gen-mac>
 <temp-smac-learn-timeout>10</temp-smac-learn-timeout>
 <punt-lldp-to-controller>false</punt-lldp-to-controller>
 <controller-max-backoff>10000</controller-max-backoff>
 <controller-inactivity-probe>300000</controller-inactivity-probe>
</elanmanager-config>

Now, start the controller and continue with stacking.

On one of the compute nodes look at the "inactivity_probe" and "max_backoff" configured in the OVSDB Controller table.

[vagrant@f23_aione_newton_odl_setup3 ~]$ sudo ovsdb-client dump unix:/var/run/openvswitch/db.sock Controller inactivity_probe max_backoff
Controller table
inactivity_probe max_backoff
---------------- -----------
300000             10000

Comment 5 Itzik Brown 2017-03-09 08:46:18 UTC

Checked with version: 
opendaylight-5.2.0-6.el7ost.noarch

I changed the file 
/opt/opendaylight/etc/opendaylight/datastore/initial/config/netvirt-elanmanager-config.xml during installation with the following content:

<elanmanager-config xmlns="urn:opendaylight:netvirt:elan:config">
<controller-max-backoff>10000</controller-max-backoff>
<controller-inactivity-probe>400000</controller-inactivity-probe>
</elanmanager-config>


Then ran on a compute node:
$ sudo ovsdb-client dump unix:/var/run/openvswitch/db.sock Controller inactivity_probe max_backoff

And got:
Controller table
inactivity_probe max_backoff
---------------- -----------
300000           10000

Comment 7 errata-xmlrpc 2017-03-23 16:15:49 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://rhn.redhat.com/errata/RHBA-2017-0840.html