openstack
/
tripleo-heat-templates
Code Issues Proposed changes

Sets ODL OVSDB inactivity probe timer 

Defaults the ODL OVSDB inactivity probe timer to 180s. This value is
more suitable for large number of compute nodes as the default ODL value
of 5s causes too much stress on the controller in large scale
environments.

Closes-Bug: 1797128

Change-Id: I74a8c40b609adec97a27602700bbfa7203ad031f
Signed-off-by: Tim Rozet <trozet@redhat.com>
This commit is contained in:
Tim Rozet 2018-10-10 10:49:42 -04:00
parent f4b4804be7
commit 2006b8218d
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
puppet/services/opendaylight-api.yaml
View File

@ -90,6 +90,11 @@ parameters:
Note, these options are in addition to the default Java
options set by the karaf/ODL boot scripts and IP version
based flag set by 'opendaylight' class.
OpenDaylightInactivityProbe:
description: Time in millseconds before an inactivity probe is sent via
OVSDB to OVS
type: number
default: 180000
conditions:
@ -126,6 +131,7 @@ outputs:
opendaylight::log_mechanism: {get_param: OpenDaylightLogMechanism}
opendaylight::inherit_dscp_marking: {get_param: OpenDaylightInheritDSCPMarking}
opendaylight::java_opts: {get_param: OpenDaylightJavaOpts}
opendaylight::inactivity_probe: {get_param: OpenDaylightInactivityProbe}
-
if:
- internal_tls_enabled

6
puppet/services/releasenotes/notes/add-opendaylight-inactivity-probe-config-a89f6dcd204192a8.yaml Normal file
View File

@ -0,0 +1,6 @@
---
fixes:
- |
OpenDaylight inactivity probe for setting the OVSDB timeout now defaults
to 180s. This helps fix scale issues for large number of computes nodes
in OpenDaylight deployments.