Changes between Version 7 and Version 8 of Internal/OpenFlow/OFIntro

Timestamp:

Jul 31, 2013, 7:48:00 PM (11 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/OFIntro

@@ -125 +125 @@
 Mininet's datapaths are backed by OVS. Therefore, if you have a Mininet install, you get OVS for "free". You can use OVS directly for your data plane. 
 
-= II More complex examples = 
-You can launch multiple instances of Floodlight on one or more nodes. If you decide to run the instances on a single host, the ports used by the Floodlight instances must not conflict i.e. each instance must be assigned a different ports.
+= II More complex examples = #II
+It is possible to run multiple instances of controllers (for whatever reason), or different logical components together in the same network. 
+This section shows two examples of more complex SDN network setups - multiple controller instances and with !FlowVisor, a network hypervisor.
+
+=== Sections ===
+ [#multi ][[BR]]
+ [#fv ][[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 Multiple Controllers ==  
-
-== 2.2 With FlowVisor == 
+ * 2.1.1 On multiple hosts
+ * 2.1.2 On the same host
+
+=== 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).  
+
+=== 2.1.2 On the same host ===
+Multiple instances of Floodlight may be run on the same host, as long as each controller listens on a separate set of sockets. In this case, all controllers would be on the same IP address(es), so you must change the ports they are listening on. These ports include the !OpenFlow control port (TCP 6633), REST API (TCP 8080), and debug (TCP 6655). 
+
+In Floodlight, this value can be changed by modifying the file floodlightdefault.properties, located in src/main/resources/ of the Floodlight sources. (Currently) It looks like this:
+{{{
+floodlight.modules=\
+net.floodlightcontroller.jython.JythonDebugInterface,\
+net.floodlightcontroller.counter.CounterStore,\
+net.floodlightcontroller.storage.memory.MemoryStorageSource,\
+net.floodlightcontroller.core.internal.FloodlightProvider,\
+net.floodlightcontroller.threadpool.ThreadPool,\
+net.floodlightcontroller.devicemanager.internal.DeviceManagerImpl,\
+net.floodlightcontroller.devicemanager.internal.DefaultEntityClassifier,\
+net.floodlightcontroller.staticflowentry.StaticFlowEntryPusher,\
+net.floodlightcontroller.firewall.Firewall,\
+net.floodlightcontroller.forwarding.Forwarding,\
+net.floodlightcontroller.linkdiscovery.internal.LinkDiscoveryManager,\
+net.floodlightcontroller.topology.TopologyManager,\
+net.floodlightcontroller.flowcache.FlowReconcileManager,\
+net.floodlightcontroller.debugcounter.DebugCounter,\
+net.floodlightcontroller.debugevent.DebugEvent,\
+net.floodlightcontroller.perfmon.PktInProcessingTime,\
+net.floodlightcontroller.ui.web.StaticWebRoutable,\
+net.floodlightcontroller.loadbalancer.LoadBalancer,\
+org.sdnplatform.sync.internal.SyncManager,\
+org.sdnplatform.sync.internal.SyncTorture,\ 
+net.floodlightcontroller.devicemanager.internal.DefaultEntityClassifier
+org.sdnplatform.sync.internal.SyncManager.authScheme=CHALLENGE_RESPONSE
+org.sdnplatform.sync.internal.SyncManager.keyStorePath=/etc/floodlight/auth_credentials.jceks
+org.sdnplatform.sync.internal.SyncManager.dbPath=/var/lib/floodlight/
+}}} 
+
+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
+
+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:
+{{{
+net.floodlightcontroller.core.internal.FloodlightProvider.openflowport = 6634
+}}}  
+To the .properties file. Then, point Floodlight to the configuration file with the `-cf` flag:
+{{{
+java -jar target/floodlight.jar -cf src/main/resources/floodlightdefault.properties
+}}} 
+The file specified after -cf will be read in, and the values in it used to configure the controller instance. You should be able to confirm the change:
+{{{
+# netstat -nlp | grep 6634
+...
+tcp6       0      0 :::6634                 :::*                    LISTEN      2029/java       
+...
+}}}
+
+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
 
 ----
-= III Installation = #install
+= III Installation = #III
 The following are the installation steps and basic usage for the software that are found on the image. For more information, refer to their respective pages; Floodlight and Mininet in particular have very thorough docs. 
 
@@ -338 +404 @@
 ./configure
 sudo make && sudo make install
-#cd ../oflops/netfpga-packet-generator-c-library/
-#./autogen.sh && ./configure && make
+cd ../oflops/
 sh ./boot.sh ; ./configure --with-openflow-src-dir=${OF_PATH}/openflow/
 make install