Changes between Version 31 and Version 32 of Internal/OpenFlow/FloodlightFVModule

Timestamp:

Jul 24, 2012, 1:04:14 AM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVModule

@@ -314 +314 @@
  1. We can swap between normal and proxy mode by merely changing the entries in the config file.  
 
+The overall structure of Floodlight, then, returns to the original form e.g. like in (7/10). 
+
 In addition to these changes, we have the following:
  * net.floodlightcontroller.flowvisor : !FlowMap and Flowspace-related code
@@ -334 +336 @@
  * figure out how the message.actions classes fit into everything else. 
     
+==== (7/23) ====
+Since we decided that the messgae processing scheme used in Flowvisor is the way to go (e.g. each message is its own class, and implements sliceFromController() and classifyFromSwitch() for modification according to the Flowspace), the plan is to implement the FVClassifier/Slicer interfaces available to these message classes. 
+
+Other points from discussion:
+ * Floodlight's native topology discovery should be used for Flowvisor's topology controller functions.
+ * The FVClassifier's slicerMap can be used as a quick-fetch mechanism for the slices associated with a DPID, but with the faster Federated !FlowMap this should not be an issue.
+ * The modifications of the messaged actually happen in message.actions.*  
+
 == . ==#end