On 10/19/2015 4:49 AM, Nicolas Dichtel wrote:
Le 16/10/2015 14:24, Paul Jakma a écrit :
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.

I agree with Nicolas on this point. namespace management should be left outside of Quagga. In fact, part of our discussion earlier this year ended with asking Nicolas to change some of the terminology (netns/vrf vs logical tables) in the CLI and in the code to decouple the the concept of having multiple tables in Quagga with how/where there are managed in the underlying system. According to the design, you can have multiple logical tables (vrfs) within the same network namespace.

I see this abstraction as a very strong design point for VRF support in Quagga. It would be nice if we could keep it that way. Of course that doesn't prevent the inclusion of a script/daemon
that manages network namespaces if the user/setup needs that.

Regards,
Jafar





_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev

Reply via email to