Enable ovn-monitor-all option to ovn-controller

With conditional monitoring enabled in OVN, southbound ovsdb-serve
takes lot of time in handling the monitoring and sending the updates
to all its connected clients. Its takes lot of CPU. With monitor-all
option, all ovn-controllers do not enable conditional monitoring there
by reducing the load on the Southbound ovsdb-server.
Enable this for all deployments is-lowrisk and user shoudn't have
posibilities to modified this manually form tht level.

Depends-On: https://review.opendev.org/c/openstack/puppet-ovn/+/801455
Closes-Bug: #1936781
Signed-off-by: Kamil Sambor <ksambor@redhat.com>
Change-Id: I9014ad0c7fae391dec4ad70bcbc0728667d413c5
This commit is contained in:
Kamil Sambor 2021-07-20 14:23:31 +02:00
parent d4f45a6350
commit e6de1f0827
2 changed files with 9 additions and 0 deletions

View File

@ -228,6 +228,7 @@ outputs:
- enable_vlan_transparency
- vswitch::ovs::vlan_limit: 0
- {}
ovn::controller::ovn_monitor_all: true
service_config_settings: {}
# BEGIN DOCKER SETTINGS
puppet_config:

View File

@ -0,0 +1,8 @@
---
features:
- |
With conditional monitoring enabled in OVN, southbound ovsdb-serve
takes lot of time in handling the monitoring and sending the updates
to all its connected clients. Its takes lot of CPU. With monitor-all
option, all ovn-controllers do not enable conditional monitoring there
by reducing the load on the Southbound ovsdb-server.