Make it more clear that ovn-monitor-all option has effect on OVN Southbound database rather than local OVS.
Reported-at: https://mail.openvswitch.org/pipermail/ovs-discuss/2023-May/052421.html Reported-by: Ilya Maximets <i.maxim...@ovn.org> Signed-off-by: Vladislav Odintsov <odiv...@gmail.com> --- controller/ovn-controller.8.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/controller/ovn-controller.8.xml b/controller/ovn-controller.8.xml index ab52e2d34..7c0855603 100644 --- a/controller/ovn-controller.8.xml +++ b/controller/ovn-controller.8.xml @@ -121,11 +121,11 @@ that is needed in the current chassis. </p> <p> - It is more optimal to set it to <code>true</code> in use cases when - the chassis would anyway need to monitor most of the records in - <var>ovs-database</var>, which would save the overhead of conditions - processing, especially for server side. Typically, set it to - <code>true</code> for environments that all workloads need to be + It is more efficient to set it to <code>true</code> in use cases + where the chassis would anyway need to monitor most of the records in + <var>OVN Southbound</var> database, which would save the overhead of + conditions processing, especially for server side. Typically, set it + to <code>true</code> for environments that all workloads need to be reachable from each other. </p> <p> -- 2.36.1 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
