Changes in RouteFlow

[Allan Vidal]

Hello everyone!

Today we had a major change in RouteFlow. A big set of changes, improvements and extensions from the Vandervecken project were merged into our repository. For most people playing with RouteFlow, not much will change (apparently). However, for anyone interested in meddling with RouteFlow, the code has been made more extensible and powerful.

For those interested in details, Joe has compiled a nice list of the changes in his pull request: https://github.com/CPqD/RouteFlow/pull/40

A big thanks to thank everyone involved for their contributions: code, discussions, ideas, bug reports, mentoring... You're helping make RouteFlow stronger :)

And to make it even easier for collaborators, we will soon publish guidelines for contributing to RouteFlow. We will also keep on working on improving and writing more documentation.

For the students getting started on RouteFlow, if you have problems or questions, just send an e-mail to this list. These new patches should make your future work easier :)

Allan

[Marcos Rogerio Salvador]

This is AWESOME!

I would like to thank you all who contributed to the code somehow and in particular Allan and Joe for taking the lead!

Can´t wait to see what is coming next :-)

[]s

Marcos

2013/5/2 Allan Vidal <all...@cpqd.com.br>

--
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.
 
 

--
Marcos Rogério Salvador, Ph.D.
Network Technology Evolution Manager
CPqD - Center for Research and Development in Telecommunications
Tel +55 19 3705-4562
E-mail: marc...@cpqd.com.br
Skype: mr-salvador
URL: www.cpqd.com.br

[Joe Stringer]

Great news!

We've worked towards testing the new version in a variety of situations, and hopefully this will minimise disruption for people working with RouteFlow. It is worth noting that there are RFProtocol incompatibilities with the new version, so RFProxy implementations will need to be updated (in particular, following changes to rflib/defs.* and rflib/ipc/RFProtocol*). Updated NOX and Ryu versions are made available via the build.sh script.

If you have issues, please report which RouteFlow and RFProxy versions you are using and we'll do our best to help determine the root causes.