On Wed, 2 Mar 2016, Alexander Turner wrote:
What's the consensus amongst the community? Has anyone tried this or
spoken about this previously?
Someone mentioned Vyatta had done some work in this area. I think
Cumulus might have done some work on other interfaces into things too,
but I'm not sure.
Interested to hear thoughts and get a discussion going...
The one I know about is OpenSwitch (OpenSwitch.net). They've modified
the daemons to publish their configuration state (and routing state)
into the OpenvSwitch "OVSDB" embedded DB via the OVSDB / RFC7047
protocol, and pick up on changes in that DB.
See:
http://openswitch.net/documents/user/architecture#top-level-view-of-the-system
That DB has a schema, and the protocol supports transactions, so with
that you can at least have an entire configuration verified against the
schema and published to the daemons atomically, as a transaction.
However, the schema might not fully capture all the requirements.
I would like to get support for atomically applied configurations, and
more structured storage of config (and maybe other) state. So we can
support architectures like the above. It would solve problems for users
and it would make certain technical problems easier to fix.
We probably have to find a way to get there in smaller, more manageable
chunks.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
Never do today what you can put off until tomorrow.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
