Browse Source

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/+/816955
Closes-Bug: #1936781
Signed-off-by: Kamil Sambor <ksambor@redhat.com>
Change-Id: I9014ad0c7fae391dec4ad70bcbc0728667d413c5
(cherry picked from commit bc934d18a4)
changes/59/816959/1
Kamil Sambor 12 months ago
parent
commit
ba0ef35293
  1. 1
      deployment/ovn/ovn-controller-container-puppet.yaml
  2. 8
      releasenotes/notes/ovn-monitor-all-2fefb215c6f7166c.yaml

1
deployment/ovn/ovn-controller-container-puppet.yaml

@ -211,6 +211,7 @@ outputs:
ovn::controller::hostname: "%{hiera('fqdn_canonical')}"
ovn::controller::ovn_remote_probe_interval: {get_param: OVNRemoteProbeInterval}
ovn::controller::ovn_openflow_probe_interval: {get_param: OVNOpenflowProbeInterval}
ovn::controller::ovn_monitor_all: true
- if:
- force_config_drive
- nova::compute::force_config_drive: true

8
releasenotes/notes/ovn-monitor-all-2fefb215c6f7166c.yaml

@ -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.
Loading…
Cancel
Save