Paul,
Is there a way to bring in / run ovsdb with out all of ovs?
Lou
On 5/18/2016 10:43 AM, Paul Jakma wrote:
> On Wed, 18 May 2016, Vincent JARDIN wrote:
>
>> I would like to see splited patch series:
>> 1- the features only so it can be used with Linux kernel, BSD, etc...
>> 2- ovsdb related ones, json,
>>
>> so it'll be easier to understand. The current OpenSwitch Quagga trie is
>> mixing both.
> Yes, there's a bunch of other stuff in there too.
>
>> First, starting with 1- would help to understand the remaining part for 2-
> I think there's an architecture discussion that can be had, without having
> to have the "cleaned up and rebased onto head, ready to be applied"
> patches. Though, the link to the diff can still be used to guage roughly
> the extent of what's being proposed. Which is basically:
>
> - Replace the code serialising between telnet/Zserv and internal state
> with code to do so to the OVSDB embedded DB, via the the OVSDB API.
>
> (I could see a case for writing a lighter API to the OVSDB protocol
> though, but the OVS OVSDB-API mods exist, at least for bgpd and ospfd;
> and there's a bunch of engineers who understand that API and
> could help port the rest of the protocols).
>
> - not done in OPS I think, but move the old telnet/string-vty code out to
> old files, make it build-time conditional, and deprecate.
>
> - Replace vtysh/ with the OpenSwitch ops-cli vtysh, which uses OVSDB.
>
> - Potentially suck in the OPS ReST daemon?
>
> regards,
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
