Changes between Version 4 and Version 5 of Internal/OpenFlow/topoMapping

Timestamp:

Jul 26, 2012, 6:56:13 PM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/topoMapping

@@ -26 +26 @@
 ==== !OpenFlow topology setup ==== 
 It is assumed that [http://floodlight.openflowhub.org Floodlight] will be used for development. Several methods to enforce topology using SDN methods come to mind:
- 1. '''''re-writing switch capabilities''''' : expose just the switch ports included in the desired topology to the modules involved in the experiment. This may be done by over-writing the FEATURE_REPLY messages that the controller receives from the switches during the initial handshake or later status changes.
+ 1. '''''re-writing switch capabilities''''' : expose just the switch ports included in the desired topology to the modules involved in the experiment. This may be done by over-writing the FEATURE_REPLY messages that the controller receives from the switches during the initial handshake. Forging FEATURE_REPLY messages may be needed if topologies need to be dynamic. 
  
  2. '''''static flow entries, via Static Flow Pusher''''' : very high-priority flows may be proactively pushed to the controller via its RESTFul API. This would not require a module within Floodlight, but rather an external script that communicates with it.