GoBGP: BGP Implemented in Go

#1

Post by ryancox » Mon, Apr 18, 2016, 4:11 PM UTC

GoBGP: BGP Implemented in Go
github.com

Re: GoBGP: BGP Implemented in Go

#2

Post by dragonshed » Mon, Apr 18, 2016, 4:54 PM UTC

I assume BGP == Border Gateway Protocol https://en.wikipedia.org/wiki/Border_Gateway_Protocol

Suggestion: include a quick abstract what what BGP is with a link for more information.

Re: GoBGP: BGP Implemented in Go

#3

Post by stingraycharles » Mon, Apr 18, 2016, 5:14 PM UTC

dragonshed wrote: post #2

I assume BGP == Border Gateway Protocol https://en.wikipedia.org/wiki/Border_Gateway_Protocol Suggestion: include a quick abstract what what BGP is with a link for more information.

I don't think this is necessary. If this is relevant to you, you will know exactly what it is, in the same way that GoDNS would be obvious to people who know what DNS is.

Re: GoBGP: BGP Implemented in Go

#4

Post by devnull42 » Mon, Apr 18, 2016, 5:15 PM UTC

So at the moment I see no reason why Go written BGP would be better than standard Quagga/Zebra. There aren't really concurrency or resource issues with large scale Quagga in my experience.

Re: GoBGP: BGP Implemented in Go

#5

Post by misframer » Mon, Apr 18, 2016, 5:16 PM UTC

dragonshed wrote: post #2

I assume BGP == Border Gateway Protocol https://en.wikipedia.org/wiki/Border_Gateway_Protocol Suggestion: include a quick abstract what what BGP is with a link for more information.

Is that necessary? I'm not sure how many people are unaware of what BGP is.

Re: GoBGP: BGP Implemented in Go

#6

Post by jimbokun » Mon, Apr 18, 2016, 5:17 PM UTC

misframer wrote: post #5

dragonshed wrote: post #2

I assume BGP == Border Gateway Protocol https://en.wikipedia.org/wiki/Border_Gateway_Protocol Suggestion: include a quick abstract what what BGP is with a link for more information.

Is that necessary? I'm not sure how many people are unaware of what BGP is.

I'm not aware what BGP is, clicked hoping to find out, was sorely disappointed.

Re: GoBGP: BGP Implemented in Go

#7

Post by tptacek » Mon, Apr 18, 2016, 5:19 PM UTC

devnull42 wrote: post #4

So at the moment I see no reason why Go written BGP would be better than standard Quagga/Zebra. There aren't really concurrency or resource issues with large scale Quagga in my experience.

Quagga/Zebra is a giant C project. The industry is moving away, as much as it can, from serving critical infrastructure on giant C programs.

Re: GoBGP: BGP Implemented in Go

#8

Post by misframer » Mon, Apr 18, 2016, 5:20 PM UTC

jimbokun wrote: post #6

misframer wrote: post #5

Earlier quoted context omitted.

Is that necessary? I'm not sure how many people are unaware of what BGP is.

I'm not aware what BGP is, clicked hoping to find out, was sorely disappointed.

I guess it couldn't hurt then!

Re: GoBGP: BGP Implemented in Go

#9

Post by elliotf » Mon, Apr 18, 2016, 5:20 PM UTC

devnull42 wrote: post #4

So at the moment I see no reason why Go written BGP would be better than standard Quagga/Zebra. There aren't really concurrency or resource issues with large scale Quagga in my experience.

I would imagine/hope that it's more about integration with other code than using it solely as a BGP daemon. The repo seems to be related to http://osrg.github.io/ryu/ which is a "software-defined networking framework"

Off-hand, you could use GoBGP to do cheap loadbalancing-ish things without external dependencies.

Re: GoBGP: BGP Implemented in Go

#10

Post by misframer » Mon, Apr 18, 2016, 5:21 PM UTC

devnull42 wrote: post #4

So at the moment I see no reason why Go written BGP would be better than standard Quagga/Zebra. There aren't really concurrency or resource issues with large scale Quagga in my experience.

Go is easier to profile and test.