On Tue, 24 Nov 2015, Daniel Walton wrote:
Since we are brainstorming here I will throw this out there for
thought....what about a relational database? I did a routing stack (bgp,
ospf and a rib) in python using sqlite for the database. Storing all of
the bgp state and the routing table in a real database saved me a TON of
development time. The ability to just add a column, index, etc to a
table was a big win. Also any possible query question you can conceive
of has already been asked and answered on stackoverflow :)
So, OpenSwitch has gone down that path, in a way. It stores the Quagga
state in an OVSDB instance (the OpenVSwitch database, which has an
info-RFC ReST/JSON RPC protocol).
So, yeah, allowing 'backends' to be written that can support various
databases is definitely a goal! Relational, sqlite, LDAP, etc.. ;)
regards,
--
Paul Jakma p...@jakma.org @pjakma Key ID: 64A2FF6A
Fortune:
Have a place for everything and keep the thing somewhere else; this is not
advice, it is merely custom.
-- Mark Twain
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
