On Wed, Dec 23, 2015 at 10:49:41AM -0800, Guru Shetty wrote: > On 23 December 2015 at 09:28, Ben Pfaff <b...@ovn.org> wrote: > > > On Wed, Dec 16, 2015 at 07:30:48AM -0800, Guru Shetty wrote: > > > > I'm not sure about the dependency on openvswitch-switch. One could run > > > > northd and the nb and sb database on a machine that does not have an > > > > openvswitch switch running; it might even be preferred in a large > > > > deployment. What do you think? > > > > > > openvswitch-switch has ovs-lib and ovn-ctl depends on it, hence the > > > dependency. > > > > If it's just a matter of ovs-lib, then we could easily move that into > > openvswitch-common. > > > > I understand why we'd want those utilities here, just not why we'd want > > to run an Open vSwitch switch on OVN database nodes. > > Purely for the above statement, the answer is what Russell mentioned. A > database node needs ovsdb-server. > > But ovn-common need not depend on openvswitch-switch if ovs-lib is moved to > openvswitch-common. ovn-central should depend on openvswitch-switch though.
This seems like an artificial restriction. ovsdb-server is just a database server and there's no reason to tie it to ovs-vswitchd. The only reason we tie it now is that, until now, there wasn't a reason to run it without ovs-vswitchd. I think it's OK to do it this way now but we might want to consider separating ovsdb-server from openvswitch-switch in the future; for example we could move it into openvswitch-common. Don't remember whether I acked this, so: Acked-by: Ben Pfaff <b...@ovn.org> _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
