On 6/28/22 17:27, Dumitru Ceara wrote: > On 6/28/22 16:54, Terry Wilson wrote: >> The only way to configure settings on a remote (e.g. inactivity_probe) >> is via --remote=db:DB,table,row. There is no way to do this via the >> existing CLI options. >> >> For a clustered DB with multiple servers listening on unique addresses >> there is no way to store these entries in the DB as the DB is shared. >> For example, three servers listening on 1.1.1.1, 1.1.1.2, and 1.1.1.3 >> respectively would require a Manager/Connection row each, but then >> all three servers would try to listen on all three addresses. >> >> It is possible for ovsdb-server to serve multiple databases. This >> means that we can have a local "config" database in addition to >> the main database we are servering (Open_vSwitch, OVN_Southbound, etc.) >> and this patch adds a Local_Config schema that currently just mirrors >> the Connection table and a Config table with a 'connections' row that >> stores each Connection. >> >> Signed-off-by: Terry Wilson <[email protected]> >> --- > > Looks good to me, thanks! > > Acked-by: Dumitru Ceara <[email protected]>
Thanks, Terry and Dumitru! There was a few issues with fedora and debian packaging, primarily because the new schema file itself wasn't added to packages. I fixed those and applied the patch. Also applied to branch-2.17 taking into account that the change is critical for OpenStack deployments with a clustered database model and the fact that OVS 2.17 will be our new LTS. The change itself should also be a low risk, because it only adds a few files without changing any functionality. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
