On Fri, Dec 11, 2020 at 09:54:47PM +0100, Ilya Maximets wrote: > Currently, ovsdb-server stores complete value for the column in a database > file and in a raft log in case this column changed. This means that > transaction that adds, for example, one new acl to a port group creates > a log entry with all UUIDs of all existing acls + one new. Same for > ports in logical switches and routers and more other columns with sets > in Northbound DB.
One question I have about this is about downgrades, in the context of standalone databases. It would be good to document a procedure for downgrading from the new format to the old one. I haven't studied the new format but it's possible that, for example, running "ovsdb-tool compact" before the downgrade would make it acceptable to the old version of ovsdb-server. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
