On 11/19/20 8:31 AM, Numan Siddique wrote: > On Wed, Nov 18, 2020 at 6:27 PM Dumitru Ceara <[email protected]> wrote: >> >> 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 <[email protected]> > > Thanks for v2. I applied this patch to master. >
Thanks! _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
