Changes between Version 40 and Version 41 of Internal/OpenFlow/FloodlightFVModule

Timestamp:

Aug 18, 2012, 9:53:43 PM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVModule

@@ -441 +441 @@
 
 '''Issues''' - There are many. The biggest above is probably the way the writer is chosen, which can totally be destroyed by one slice setting it, then another coming along and setting it to something else mid-processing. The way the deny list is built and used also seems kludgy. 
- 
+
+==== (8/16) ====
+Instead of having a global writer slice that a process chain sets, the slice that needs to process a particular message is now added to the context (!FloodlightContext) carried with the message. This will hopefully reduce potential conflicts of the writer being reset to something else mid-processing. 
+
+The !FloodlightContext is a tiny class containing just a !HashMap of a String to some Object. !FloodlightContextStore can be used to add/remove entries from the map. One major example of something stored as a context is the contents of an Ethernet header. 
+
+Next major steps:
+ * unit testing 
+ * adding functionality to generate config files (currently we need fvctl to create the base files).  
+
 ===== --- =====
 [#top home] [[BR]]