Le 16/10/2015 14:24, Paul Jakma a écrit :
On Fri, 16 Oct 2015, Nicolas Dichtel wrote:
Hi Paul,
we are pausing with this project right now, due to some other priorities. We
still plan to upstream vrf support in ospf, but it is delayed. As you said, a
first milestone has been reached, I'm not sur to see why it blocks the release.
Concerning the zAPI, we can obviously agree on the general direction. What
you've proposed in your small PoC was (and is) ok for me. What do you expect
exactly?
So that can go in?
I think so.
That was one thing blocking. The other is the current patch, being only a part
of the story, is somewhat confusing. It is still not clear to me how we will
make this "support both in-daemon VRFs and 1-daemon:VRF and shades in between"
work. And myself and Donald spent a while yesterday on IRC discussing the
issues.
E.g., what is going to be responsible for creating the namespaces? zebra? How
will 1:1 daemon:VRF work if zebra creates them? So we probably need another
daemon setup the namespaces. Should that new daemon also then be responsible for
starting daemons (side-effect: then 'router ospf|bgp|etc' potentially could be
commands that start daemons, which might interest some)? Should it be
watchquagga? How will the applicable VRFs be communicated to the daemons? How
will this sync up with zebra?
I'm not sure that this part must be handled by quagga. Setting up namespaces is
part of the global configuration. You will have to put some interfaces inside
and maybe configure firewall or ipsec. It's like interfaces: quagga is not in
charge of creating them.
Regards,
Nicolas
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
