Dear OpenFlow fellows, I thought you might be interested in the newly released version of RouteFlow, a platform that runs on top of NOX, POX (and soon Floodlight and Trema) that allows you to run traditional IP routing protocols on your OpenFlow network.
See below the newly introduced features or check here for the full post and the updated architecture: https://sites.google.com/site/routeflow/updates/announcingthenewrouteflowdesign Best regards, Christian ---------- Forwarded message ---------- From: Christian Esteve Rothenberg <est...@cpqd.com.br> Date: Thu, May 31, 2012 at 2:08 PM Subject: [RouteFlow-discuss] Announcing the new RouteFlow design To: routeflow-disc...@googlegroups.com What's new? We're glad to announce an entirely new version of RouteFlow, with many new features in response to our first year´s experiences and the requests from users and developers! The version has been in an experimental branch for some time now and is stable enough to become mainstream. In this new version, we have introduced: #Centralized database and IPC We leverage MongoDB for storing the core system´s state and the OpenFlow network statistics. A JSON-based IPC service (aka RouteFlow protocol) is also implemented on top of it. #Cleaner code base Much of the code was rewritten and organized, making it easier for developers to play with RouteFlow. This includes the renaming of some components: RF-Slave becomes RFClient, RF-Controller becomes RFProxy. #POX support Support for using the new POX controller was added. #Web monitoring interface (requires POX) Inspect network topology, RouteFlow internal messages and network state. #Open vSwich v1.4 To attach the virtual interfaces (eth1 to ethX) of the VMs. Used also in the control network that (attaching et0) and running in bridge mode removes the requirement of a second controller instance to act as a simple L2 switch. #Tools for testing A new module (rftest) introduces several scripts to facilitate testing and environment creation. #SNMP support Export OpenFlow stats via SNMP. [Contribution by Joe Stringer] The detailed description of these new features is available in the README file. You can download the new pre-configured VM (3.7GB) from here: ftp://ftp.cpqd.com.br/pub/routeflow/RouteFlow.zip or get it via github. What's next The list is long! -Foremost we want to make RouteFlow more and easier configurable. Currently, there's no trivial way to associate VMs and datapaths statically, but we want to solve this through a new configuration apporach. -RouteFlow with NOX requires Ubuntu 11.04 (POX users should be fine in newer versions). We will be adding support for Ubuntu 11.10 and 12.04. -Embrace OpenFlow v1.X. We have working prototypes of NOX and software-based reference switch using OpenFlow 1.1 and 1.2. -Extensions to support LDP label information. -Exploration of possibilities opened by the use of a central database (e.g., keep state history and allow queries like "show me flow table at timestamp x"). -Address High Availability. -New routing abstractions implemented as Services on top of the RF-Server. -... a number of additions under investigation by students and project collaborators. Stay tuned for further news! Thank you all! -- Christian Esteve Rothenberg, Ph.D. Converged Networks Business Unit CPqD - Center for Research and Development in Telecommunications Tel. (+55 19) 3705 4479 / Cel. (+55 19) 8193-7087 _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
