[ovs-git] [ovn-org/ovn] 71e2fd: ovn-controller: Propagate nb_cfg to the local OVS DB.

[Dumitru Ceara]

  Branch: refs/heads/master
  Home:   https://github.com/ovn-org/ovn
  Commit: 71e2fd244fcaf249cbf513124fdc7dbdb2a1a770
      https://github.com/ovn-org/ovn/commit/71e2fd244fcaf249cbf513124fdc7dbdb2a1a770
  Author: Dumitru Ceara <dceara at redhat.com>
  Date:   2020-11-19 (Thu, 19 Nov 2020)

  Changed paths:
    M NEWS
    M controller/ovn-controller.8.xml
    M controller/ovn-controller.c
    M tests/ovn-controller.at

  Log Message:
  -----------
  ovn-controller: Propagate nb_cfg to the local OVS DB.

The NB.NB_Global.nb_cfg value gets propagated to
Chassis_Private.nb_cfg (and then to NB.NB_Global.hv_cfg) as soon as
ovn-controller has finished installing OVS flows corresponding to
the NB DB state.

However, if the CMS runs monitoring applications on the chassis itself,
in order to detect that the NB changes have been applied, it has to
connect to the NB/SB database.  In a scaled deployment this additional
connection might induce performance issues.

In order to avoid that we now (also) propagate nb_cfg to the local OVS
DB, in the record corresponding to the integration bridge in table
Bridge, as external_id "ovn-nb-cfg".

Signed-off-by: Dumitru Ceara <dceara at redhat.com>
Signed-off-by: Numan Siddique <numans at ovn.org>