On 5/19/2016 4:54 AM, Paul Jakma wrote: > On Wed, 18 May 2016, Lou Berger wrote: > >> Is there a way to bring in / run ovsdb with out all of ovs? > That depends on your distro. Most package ovsdb along with the rest of > openvswitch, but it could easily be packaged separately.
or just import it as a new quagga daemon? > Or, we could have our own OVSDB data-store implementation, in extremis. This is what's done on the commercial side. (e.g., I've used Berkeley DB for this in the past, but the selection of this was done in the late 90s.) > At Sun I was making an argument for a project to update Quagga, using a > DBus architecture to decouple internal components. I had a talk with the > OPS architect and asked him why not go with a more bus based architecture, > and he somewhat convinced me the DB based architecture has significant > benefits in terms of the separation of state and function that it can > bring. > > Or something else... But it seems the time is ripe to have a discussion on > this. sure lots of message buses and DBs out there now. I think this is a fine *long term* direction/architecture discussion. Lou > > regards, _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
