This version of RouteFlow for High Availability is a beta developers' release intended to evaluate RouteFlow for providing virtualized IP routing services on one or more OpenFlow switches.
You can learn more about RouteFlow in our main page in GitHub and in our website.
Please be aware of Ryu, POX, OpenFlow, Open vSwitch, Quagga, MongoDB, jQuery, JIT and RouteFlow licenses and terms.
RouteFlow is a distribution composed by four basic applications: RFClient, RFServer, RFMonitor and RFProxy.
-
RFClient runs as a daemon in the Virtual Machine (VM), detecting changes in the Linux ARP and routing tables. Routing information is sent to the RFServer when there's an update.
-
RFServer is a standalone application that manages the VMs running the RFClient daemons. The RFServer keeps the mapping between the RFClient VM instances and interfaces and the corresponding switches and ports. It connects to RFProxy to instruct it about when to configure flows and also to configure the Open vSwitch to maintain the connectivity in the virtual environment formed by the set of VMs.
-
RFMonitor is an application to monitor all running controllers and elect new master in case of master failure. The RFMonitor keeps a mapping between all controllers and their role and number of devices to which the controller is connected to. It checks all controllers periodically if they are up and running. In case a master controller dies it elects the new master and informs RFProxy about the new master which informs all the devices about the new master controller.
-
RFProxy is an application (for POX and other controllers) responsible for the interactions with the OpenFlow switches (identified by datapaths) via the OpenFlow protocol. It listens to instructions from the RFServer and notifies it about events in the network. We recommend running POX when you are experimenting and testing your network. Other implementations in different controllers will be available soon.
There is also a library of common functions (rflib). It has implementations of the IPC, utilities like custom types for IP and MAC addresses manipulation and OpenFlow message creation.
Additionally, there's rfweb, an extra module that provides an web interface for RouteFlow.
The RouteFlow Architecture
+--------VM---------+
| Quagga | RFClient |
+-------------------+
\
M:1 \ RFProtocol
\
+-------------------+
| RFServer |
+-------------------+
+-------------------+
| RFMonitor |
+-------------------+
\
1:M \ RFProtocol
\
+-------------------+
| RFProxy |
|-------------------|
| Controller |
+-------------------+
\
1:N \ OpenFlow Protocol
\
+-------------------+
| OpenFlow Switch |
+-------------------+
RouteFlow runs on Ubuntu 12.04.
- Install the dependencies and setup the application:
$ sudo ./build.sh
2. Install compatible version of ryu
$ git clone https://github.com/routeflow/ryu.git
$ cd ryu; python ./setup.py install
That's it! Now you can run tests 1,2, High Availability test. The setup to run them is described in the "Running" section.
# Running
The folder rftest contains all that is needed to create and run three test cases.
## Virtual environment
First, create the default LXC containers that will run as virtual machines:
$ cd rftest $ sudo ./create
The containers will have a default ubuntu/ubuntu user/password combination. **You should change that if you plan to deploy RouteFlow**.
By default, the tests below will use the LXC containers created by the `create` script. You can use other virtualization technologies. If you have experience with or questions about setting up RouteFlow on a particular technology, contact us! See the "Support" section.
## Test cases
Default configuration files are provided for these tests in the `rftest` directory (you don't need to change anything).
You can stops them at any time by pressing CTRL+C.
### rftest1
1. Run:
$ sudo ./rftest1
2. You can then log in to the LXC container b1 and try to ping b2:
$ sudo lxc-console -n b1
3. Inside b1, run:
For more details on this test, see its [tutorial](https://github.com/routeflow/RouteFlow/wiki/Tutorial-1:-rftest1).
### rftest2
This test should be run with a [Mininet](http://mininet.org/) simulated network.
In the steps below, replace [guest address] with the IP address you use to access your Mininet VM.
The same applies to [host address], that should be the address to access the host from inside the VM.
1. Run:
$ sudo ./rftest2
2. Once you have a Mininet VM up and running, copy the network topology files in rftest to the VM:
$ scp topo-4sw-4host.py mininet@[guest address]:/home/mininet/mininet/custom $ scp ipconf mininet@[guest address]:/home/mininet
3. Then start the network:
$ sudo mn --custom mininet/custom/topo-4sw-4host.py --topo=rftest2 --controller=remote,ip=[host address],port=6633 --pre=ipconf
Wait for the network to converge (it should take a few seconds), and try to ping:
mininet> pingall ... mininet> h2 ping h3
For more details on this test, see its [tutorial](https://github.com/CPqD/RouteFlow/wiki/Tutorial-2:-rftest2).
# Now what?
If you want to use the web interface to inspect RouteFlow behavior, see the wiki page on [rfweb](https://github.com/CPqD/RouteFlow/wiki/The-web-interface).
If you want to create your custom configurations schemes for a given setup, check out the [configuration section of the first tutorial](https://github.com/CPqD/RouteFlow/wiki/Tutorial-1:-rftest1#configuration-file) and the guide on [how to create your virtual environment](https://github.com/CPqD/RouteFlow/wiki/Virtual-environment-creation).
If you're developing for RouteFlow, there are more advanced options and components that can be installed through the `build.sh` script. See its [source](https://github.com/CPqD/RouteFlow/blob/master/build.sh) for more information.
# Support
If you want to know more or need to contact us regarding the project for anything (questions, suggestions, bug reports, discussions about RouteFlow and SDN in general) you can use the following resources:
* RouteFlow repository [wiki](https://github.com/CPqD/RouteFlow/wiki) and [issues](https://github.com/CPqD/RouteFlow/issues) in GitHub
* Google Groups [mailing list](http://groups.google.com/group/routeflow-discuss?hl=en_US)
_RouteFlow - Copyright (c) 2012 CPqD_