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

Timestamp:

Jul 2, 2012, 10:55:50 PM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVModule

@@ -243 +243 @@
 With the database components removed, we need to re-build the components that parse the Flowvisor configs and initialize everything (!FlowMap definitions, slices, etc.). FVConfSetup.java is intended for this purpose. So far, it uses Jackson (used in Floodlight for the Static Flow Pusher) to parse the Flowvisor configuration file to initialize the !FlowMap (linear for now, since it is simple than the federated). 
 
+==== (7/2) ====
+ * A Classifier knows about the Slicers associated with the DPID it is associated with. This is kept in a Java !HashMap. 
+ * 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:
+{{{
+         "controller_hostname": "localhost",
+         "controller_port": 0,
+         "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().    
 == . ==#end