Changes between Version 20 and Version 21 of Internal/OpenFlow/FloodlightFVModule

Timestamp:

Jul 3, 2012, 5:29:50 PM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVModule

@@ -247 +247 @@
  * A Slicer knows the name, controller/TCP port, and switch ports associated with a slice.  
  * Each !FlowSpaceRule entry (flow entry) stores which DPID and slice (by name and permissions, via !SliceAction.java) it is associated with.
-Unlike the !FlowMap, a Slice does not seem to be a concrete object, but a collection of information shared amongst the Slicers and Classifiers. We create a new configuration option, "module_name," to replace the controller information stored in a "slice". For now we keep the old parameters for each Slice, but modified:
+Unlike the !FlowMap, a Slice does not seem to be a concrete object, but a collection of information the Slicers and Classifiers access using !FlowSpaceUtil. We create a new configuration option, "module_name," to replace the controller information stored in a "slice". For now we keep the old parameters for each Slice, but modified:
 {{{
          "controller_hostname": "localhost",
@@ -253 +253 @@
          "module_name": "forwarding",                 
 }}}  
-In any case, we need an easily manipulated mapping of DPIDs to slices, and slices to their modules, where modules are specified by the names returned by getName().    
+Another way to do this would be to re-use the existing fields (e.g. "controller_hostname") to hold the module's name, but that might become rather confusing despite keeping the syntax compatible with that of Flowvisor's configuration file. In any case, we need an easily manipulated mapping of DPIDs to slices, and slices to their modules, where modules are specified by the names returned by getName().    
+
+==== (7/3) ====
+Since we don't rely on storage (for now), the same class handling the initialization of the Flowvisor components may also provide the functions of FlowSpaceUtil e.g. supply the means for the proxy module to access slice configurations.
+
+ * in FVAcceptor, switch DPIDs may be lifted when the switch joins. 
+ * the origin of the message can be (mostlly) determined by OFP message type (OFType). 
+
+For now, a sane goal is probably to have the proxy identify which slice a message belongs to based on the contents of the configuration file.  
+   
 == . ==#end