On Sat, 30 May 2015, David Lamparter wrote:
To get to actual use, all of these protocols mandate some level of single-process multi-VRF support at least in bgpd. A "maximum split process" approach would need to demultiplex the data from one bgpd onto different zebra processses.
Or just speak BGP-over-AF-Unix between the bgpds, with some tweaks to make such 'internal' sessions more auto-magic. (Which could also help with applying divide-and-conquer to tame other scaling issues - already possible today by running multiple bgpds with manually configured peerings locally between each).
Even if BGP is special and one bgpd is preferred, you could easily teach it to speak ZServ to multiple zebras, and direct routes to the relevant socket based on RD. So it isn't at all clear it /requires/ the single-daemon VRF patch and can only be fulfilled by the single-daemon patch.
So it doesn't look like this design discussion was held before, nor is that patch a user for this patchset, at this time?
regards, -- Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A Fortune: What sin has not been committed in the name of efficiency? _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
