Context Navigation

OFIntro

Timestamp:: Jul 31, 2013, 8:13:40 PM (11 years ago)
Author:: akoshibe
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

Internal/OpenFlow/OFIntro

-              v8
+              v9
 This page is meant to get you up and running quickly with !OpenFlow-related experiments/development on the ORBIT testbeds.
+= I. A simple OpenFlow Network =
+=== sections ===
+ [#I I. A simple OpenFlow Network][[BR]]
+ [#II II. More complex examples][[BR]]
+ [#III III. Installation][[BR]]
+= I. A simple OpenFlow Network = #I
 We begin with a simple setup of a Mininet network controlled by a controller (Floodlight) running on a separate Sandbox node, which looks like this:
 {{{
 …
  * [http://docs.projectfloodlight.org/display/floodlightcontroller/Cbench+(New) cbench] : Controller benchmarking tool
  * [http://www.openflow.org/wk/index.php/Liboftrace liboftrace] : !OpenFlow message parser/analyzer for pcap files
  * [https://bitbucket.org/barnstorm/of-dissector Wireshark+OF dissector] : Wireshark with a dissector for !OpenFlow messages
+ * [https://bitbucket.org/barnstorm/of-dissector Wireshark+OF dissector] : Wireshark with a plugin for !OpenFlow messages
 This makes things easy since you can image multiple nodes with the same image, and pick and choose what to run where.
 …
 === Sections ===
  [#multi ][[BR]]
  [#fv ][[BR]]
+ [#multi 2.1 Multiple Controllers ][[BR]]
+ [#fv 2.2 With !FlowVisor (Network virtualization/slicing) ][[BR]]
 == 2.1 Multiple Controllers == #multi
 You may have multiple controllers in the same logical space of the control plane for various reasons - special applications, failover, etc.
 …
 === 2.1.1 On multiple hosts ===
 If each controller is running on its own host, there is little to change; if you have hosts A,B, and C, and Floodlight instances running on each, switches can be pointed to targets A:6633, B:6633, C:6633, or any combination thereof (switches can be pointed to multiple controllers).
+If each controller is running on its own host (machine, VM, etc.), there is little to change; if you have hosts A,B, and C, and Floodlight instances running on each, switches can be pointed to targets A:6633, B:6633, C:6633, or any combination thereof (switches can be pointed to multiple controllers).
 === 2.1.2 On the same host ===
 …
 Several entries can be added to this list to tweak TCP port values. Unfortunately, these entries may change fairly frequently due to active development.
  * net.floodlightcontroller.restserver.RestApiServer.port = 8080
  * net.floodlightcontroller.core.internal.FloodlightProvider.openflowport = 6633
  * net.floodlightcontroller.jython.JythonDebugInterface.port = 6655
+ * !net.floodlightcontroller.restserver.RestApiServer.port = 8080
+ * !net.floodlightcontroller.core.internal.FloodlightProvider.openflowport = 6633
+ * !net.floodlightcontroller.jython.JythonDebugInterface.port = 6655
 Each entry should be on its own line, with no spaces or newlines in between lines. For example, to change the port that Floodlight listens for switches on from the default of 6633 to 6634, append:
 …
 }}}
+Each instance of the controller run on the same host can then be pointed to its own .properties file with this flag, with different port value parameters.
+== 2.2 With FlowVisor == #fv
+Each instance of the controller run on the same host can then be pointed to its own .properties file with the `-cf` flag, with different port value parameters. Going with a similar example from earlier, you may have one host A and three Floodlight instances 1,2, and 3, configured as below:
+ || || 1 || 2 || 3 ||
+ || !FloodlightProvider.openflowport || 6633  || 6634  || 6635  ||
+ || !RestApiServer.port || 8080 || 8081 || 8082 ||
+ || !JythonDebugInterface.port || 6655 || 6656 || 6657 ||
+No ports should be shared by the three instances, or else they will likely throw errors at startup, exiting shortly after.
+With a .properties file for each instance under resources/ (named 1,2, and 3.properties for this example), you may launch the controllers in a loop:
+{{{
+for i in `seq 1 3`; do
+   java -jar target/floodlight.jar -cf src/main/resources/$i.properties 1>/dev/null 2>&1 &
+done
+}}}
+This should launch three backgrounded instances of Floodlight.
+== 2.2 With !FlowVisor (Network virtualization/slicing) == #fv
+A virtualized network is organized as below:
+{{{
+[controller 1] [controller 2] [controller 3]
+             \       |       /
+              \      |      /
+            [network hypervisor]-[policies]
+                     |
+                  [network]
+}}}
+The network hypervisor provides each controller with an illusion that it is the only controller in the network. The analogy used in the !FlowVisor whitepaper is that of multiple VMs sharing the same physical machine.
 ----