d35c27bf71
Allow configuration of `inactivity_probe` in Connection table in NB and SB for new installations. Issues, which successfully resolve by using this as a workaround: 1. https://www.mail-archive.com/ovs-discuss@openvswitch.org/msg07431.html 2. https://bugs.launchpad.net/kolla-ansible/+bug/1917484 According to the OVN ML, specifically this part [1], there is no other way to set `inactivity_probe` other than using Connection table. And the only valid option for it would be `0.0.0.0`, so that it could be applied to all connections. `ovn-ctl` forces `ovsdb-server` to look for addresses to listen on in Connection table with `db-nb-use-remote-in-db` and `db-sb-use-remote-in-db` options which are enabled by default. If `db-nb-create-insecure-remote` and `db-sb-create-insecure-remote` are set to `yes` (when `neutron_ovn_ssl` is `False`), this would result in flooding OVN logs with `Address already in use` errors. So we will rely on default value `no` for them from now on and only listen on and with whatever options are provided in Connection tables. [1] https://www.mail-archive.com/ovs-discuss@openvswitch.org/msg07476.html Change-Id: If87cf7cfa1788d68c9a4013d7f4877692f2bb11c |
||
|---|---|---|
| .. | ||
| dvr_config.yml | ||
| opendaylight_config.yml | ||
| ovn_cluster_setup.yml | ||
| ovn_config.yml | ||
| ovs_config.yml | ||
| setup_ovs_dpdk.yml | ||
| setup_ovs_opendaylight.yml | ||
| setup_ovs_ovn.yml | ||