On 5/26/2015 9:37 AM, Paul Jakma wrote:
They can co-exist, sure. The question is, if you have the multi-daemon approach, do you need the single-daemon way?
Muli-daemon (MD) support is very desirable; it scales better on multi-core systems as you pointed out earlier, but there is a great benefit in also supporting the single daemon (SD) approach, here are a few reasons:
1- Scalability: Its is true that MD scales better on multi-core systems, but when it comes to single core systems, scalability favors the SD approach. There is still a (big) market and use cases for low powered and cheap routers. I have a network of old Raspberry Pi's( among other low powered devices), they run Quagga and they do the job well enough. There is an overhead for VRFs/SD but the overhead is much greater with MD!
2-Configuration: SD is simpler to configure - one file. The same old configuration with backward compatible commands. The only change is a VRF ID added to the command when the config targets a specific VFR
3- Maintainability (Watchdog): Nothing changes here in SD land. More work for MD. This is not only true for Quagga's watchdog, but also other users processes that talks Quagga. It is easier to keep track of one process.
Again, I'm not saying that SD is better than MD, I just think Quagga should support both and leave it up to the user to decide based on the environment and constraints. 6WIND seems to have a good handle on VRF-SD support. It is limited to Zebra at the moment, but if it is gets merged it would get people incentives to move forward to make the various daemons VRF-aware and and also multiple-daemon support.
Regards, Jafar _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
