Oh, we definitely need to work-out/fix the following before we can
release:
* ZServ VRF ID negotation / registration? I think I sent Nicolas a little
PoC, or maybe add something to complement the ZEBRA_VRF_UNREGISTER
command. This has to go in for ZServ, at a minimum.
* how do VRFs get setup and passed to daemons? Is each daemon going to
have CLI commands for this in each daemon? How does this work for
per-netns^WVRF routing daemons?
* If we implement a management daemon for the other daemons and VRFs, how
will that interact with the commands currently added to zebra?
At the moment if you want to run Quagga in netns's you need to just set
them up with 'ip netns exec' and run a set of Quagga daemons per netns,
each with netns specific conf files and Zserv sockets (by daemon argument
or fs ns) and you have to *ignore* the stuff in zebra at present.
This needs finishing off, to a state that it makes sense for a release -
i.e. it needs to at least be a waypoint along a path to a coherent
end-state. Otherwise it can not go out in a release - and we're due a
release.
Need something more than the sound of crickets on this thread. :)
regards,
Paul
On Mon, 12 Oct 2015, Paul Jakma wrote:
Hi,
So..
There's the single-process VRF stuff in zebra, which, AFAICT, requires
something else to hand off the netns fd to it. We still need the patch to add
supported-VRF negotiation to ZServ, and patches to routing daemons, and some
way to setup a namespace.
The are multi-instance OSPF patches out there, that add instance arguments to
ospfd. Each runs separately.
Presumably some will also want to use namespaces to just run collections of
daemons in a namespace, as a way to do VRF.
I think it might be worth working out what the story is going to be for
users, before this gets messy.
E.g., do we need a daemon to manage namespaces and which daemon should be run
in what VRF/namespace? If so, should that be watchquaggga?
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
To have died once is enough.
-- Publius Vergilius Maro (Virgil)
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
