[ixpmanager] Is there template for route server & route collector configuration template for Quagga

[Nick Hilliard (INEX)]

FRR was forked from Quagga in around Oct 2016.  The Quagga project still 
exists, although there's not been much development since the fork happened.

 From what I can see of the git logs, the FRR project hasn't done too 
much with the route server code, so it's not clear that the underlying 
structural problems that caused issues with large RS configs have been 
addressed.

There's been no movement on implementing an atomic config change 
mechanism in FRR.  There's a tool in the FRR tree called frr-reload.py 
which kinda hacks around this, but it's a hack and it's trivially easy 
to break it.  In practice we found that we ended up having to write 
significantly more complex configuration templates in order to work 
within the limitations of frr-reload.py.  An atomic reload mechanism 
would be much more convenient from the point of view of operational 
management.

Nick


> Diarmuid O Briain <mailto:diarmuid at obriain.com>
> 25 January 2019 at 05:58
> Isn't Quagga not superseded by Free Range Routing (FRR) 
> {https://frrouting.org} these days ?
>
> Regards,
>
> Diarmuid
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: 
> https://www.inex.ie/mailman/listinfo/ixpmanager
> Nick Hilliard (INEX) <mailto:nick at inex.ie>
> 24 January 2019 at 19:02
>
>
> what this means in practice is that it's troublesome to automate 
> quagga effectively, and almost impossible to automate it fully.  
> Separate to this, Quagga has serious problems relating to resource 
> scheduling on busy route servers, and some has some race conditions 
> which can cause the daemon to crash if you remove peers too quickly 
> under conditions of high load.  There is no way of fixing these 
> problems other than redesigning and rewriting large chunks of quagga.
>
> We used to use Quagga at INEX several years ago (there are still bits 
> of config buried deep in the IXP Manager git repo) but never released 
> what we ran in production for the route servers because it was too 
> fragile to be able to support properly outside INEX.  The entire 
> framework that this coded used has now been removed, so any future 
> attempt to support quagga would mean rewriting things from scratch.
>
> I can see the attraction of running a route server with a cisco-style 
> CLI, but quagga is unsuitable for reliable route server functionality 
> in its current state.
>
> Nick
> Barry O'Donovan <mailto:barry.odonovan at inex.ie>
> 24 January 2019 at 08:45
>
>
>
>
> No. Quagga wouldn't be the most suitable daemon for IXP Manager as IXP 
> Manager doesn't maintain state. This is an issue because Quagga (last 
> time I checked which, admittedly, is quite a while) does not support a 
> complete configuration reload function and so - for example - sessions 
> would not be removed.
>
> After we complete Bird v2, we're thinking of looking at OpenBGPd and 
> possibly GoBGP.
>
> For complete IXP Manager integration, the only way to go currently is 
> Bird v1.6 and shortly Bird v2 also.
>
>  - Barry
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: 
> https://www.inex.ie/mailman/listinfo/ixpmanager
> Teodor Haralambiev <mailto:teodor.haralambiev at x3me.net>
> 24 January 2019 at 08:39
> Hello,
>
> Is there template for route server & route collector configuration for 
> Quagga?
>
>
> -- 
> Best Regards,
>
> Teodor Haralambiev
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: 
> https://www.inex.ie/mailman/listinfo/ixpmanager

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20190125/f25307d6/attachment.html>