On 3/10/21 2:09 PM, Sergey Chekanov wrote:
I am looking to Gobgp (BGP implementation in Go) + go-openvswitch for
communicate with OVN Northbound Database right now, but not sure yet.
FRR I think will be too heavy for it...
On 10.03.2021 05:05, Raymond Burkholder wrote:
You could look at it from a Free Range Routing perspective. I've used
it in combination with OVS for layer 2 and layer 3 handling.
On 3/8/21 3:40 AM, Sergey Chekanov wrote:
Hello!
Is there are any plans for support BGP EVPN for extending virtual
networks to ToR hardware switches?
Or why it is bad idea?
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
FRR is delivered as a set of daemons which perform specific functions.
If you only need BGP functionality, you can just run bgpd. The zebra
daemon adds routing exchange between BGP and the kernel. The vtysh
daemon provides a command-line interface to interact with the FRR
processes. There is also a bi-directional forwarding detection (BFD)
daemon that can be run to detect unidirectional forwarding failures.
Other daemons provide other services and protocols. For this reason, I
felt that it was lightweight enough to just run a few daemons in a
container.
A secondary concern for my use case was support on Red Hat Enterprise
Linux, which will be adding FRR to the supported packages shortly.
I'm curious to hear any input that anyone has on FRR compared with GoBGP
and other daemons. Please feel free to respond on-list if it involves
OVS, or off-list if not. Thanks.
--
Dan Sneddon | Senior Principal Software Engineer
dsned...@redhat.com | redhat.com/cloud
dsneddon:irc | @dxs:twitter
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
