On Thu, Jul 28, 2016 at 01:14:37PM -0700, Amitabha Biswas wrote:
> So v2 of this patch will contain Manager Table in the NB and SB
> database. Does that sounds reasonable?
Yes, that sounds OK to me.
___
dev mailing list
dev@openvswitch.org
http://openvsw
Hi Ben,
No there is no advantage for having a separate database, we can incorporate a
Manager Table into the Northbound and Southbound database. This was an initial
hack (with minimal code and schema change) to verify the efficacy of disabling
the probe timer on our cloud setups and get some fe
On Mon, Jul 18, 2016 at 10:21:09PM -0700, Amitabha Biswas wrote:
> NB and SB dbs are handled by separate ovsdb-server processes. The
> ovsdb-server processes manage dbs based on the schemas for OVN NorthBound
> and SouthBound. These schemas do not have any Manager Options similar
> to the Open_vSwi
On Tue, Jul 19, 2016 at 12:21 AM, Amitabha Biswas wrote:
> NB and SB dbs are handled by separate ovsdb-server processes. The
> ovsdb-server processes manage dbs based on the schemas for OVN NorthBound
> and SouthBound. These schemas do not have any Manager Options similar
> to the Open_vSwitch sch
NB and SB dbs are handled by separate ovsdb-server processes. The
ovsdb-server processes manage dbs based on the schemas for OVN NorthBound
and SouthBound. These schemas do not have any Manager Options similar
to the Open_vSwitch schema. As a result, for e.g., the frequency of
inactivity probes sen