Hi Steven and fellows,
first of all happy new year to all RouteFlow list members!
This year promises production use cases for RouteFlow and related SDN
technologies.
Steven, thanks for bringing this subject up! I have been following the
NANOG discussion and the Vyatta fork of VyOS. Indeed, VyOS plus
RouteFlow look like a powerful combination. I agree that the end user
usability of Routeflow has a lot of room to improve, so far it is
somehow restrict to those handy with linux, virtualization,
programming and OpenFlow (plus traditional IP routing).
We looked at Vyatta in the early days of RouteFlow but we discarded to
use use it for our prototyping efforts as it was somewhat more
complete than what we were looking for, a simple Linux-based routing
stack like Quagga. AFAIK, Vyatta used Quagga in the beginnings and
moved then to XORP.
We did not test RouteFlow as is with Vyatta but being Linux-based and
having tested RouteFlow with Quagga, XORP and Bird without requiring
modifications to the routing stacks, I am pretty confident it will
work, at least for plain IP plus Ethernet forwarding. Certainly, other
features provided by Vyatta / VyOS like firewalling, QoS, multicast,
or L2 protocols may need extensions to have them captured by RouteFlow
and transformed into equivalent OpenFlow rules.
Lets keep the dialogue open on this opportunity, if anyone is
interested in working on that direction let me know, I will try to
start one thread on basic testing of VyOS + RouteFlow with University
students.
Cheers,
Christian
> --
> You received this message because you are subscribed to the Google Groups
> "RouteFlow" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
routeflow-disc...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.
--
Christian