When synching from a database that doesn't exist, the entire database will wipe. This is obviously very bad, because synching is typically used to handle scenarios where a service is unreachable.
Actions:1. Start ovn-central via 'service ovn-central start'2. Add an item to the database via 'ovn-nbc
Actions:
1. Spin up 2 ovsdb databases
2. Run the following to start synchronzing:
ovs-appctl -t /var/run/openvswitch/ovnnb_db.ctl ovsdb-server/set-remote-ovsdb-server tcp:{IP}:{PORT}
ovs-appctl -t /var/run/openvswitch/ovnnb_db.ctl ovsdb-server/connect-remote-ovsdb-server
3. Restart the database tha
Actions
1. Run 2 ovsdb databases (in my test scenario they are northbound databases started from ovn-central).
2. Synch 1 database to the other using app-ctl:
ovs-appctl -t /var/run/openvswitch/ovnnb_db.ctl ovsdb-server/set-remote-ovsdb-server tcp:{IP}:{PORT}
ovs-appctl -t /var/run/openvswitch/ovnn
>There has been a lot of discussion around replacing ovsdb with etcd
>and using RAFT for active/active ovsdb clustering (please look
>through the ML archives for specific references). At this point,
>I don't believe those efforts will be landing in 2.6.0, so we've
>had some folks here working on a
Hi all,
My name is Daniel Levy and I work with IBM on one of our Openstack provider teams. We are currently looking into OVNÂ and some of us will be contributing code / working on defects.
As a first dive for myself to get more into the code, I'll be working on the "Support reject actio
