Changes between Version 12 and Version 13 of Internal/OpenFlow/FloodlightFVModule

Timestamp:

Jun 20, 2012, 11:11:20 PM (12 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/FloodlightFVModule

@@ -8 +8 @@
 [#s Setup] [[BR]]
 [#bg Background] [[BR]]
-[#a Approach] -  a diary-style log of the implementation [[BR]]
+[#a Approach] -  a diary-style log of the implementation. 
+ * [#fl-1 Floodlight Module System]
+ * [#fv-1 Flowvisor FlowMap Overview]
 [#end jump to bottom.] 
 == Overview. == #o
@@ -91 +93 @@
  * finding a "nice" way to make the modules register with FVController. 
 
-==== (6/13): ====
+==== (6/13):[Floodlight Module System] ==== #fl-1
 A (not-so) quick revisit of the module loading system in Floodlight was done to figure out how exactly a module learns to subscribe to the main controller module. 
 
@@ -169 +171 @@
     context.getServiceImpl(IFloodlightProxy.class));
 }}}
+
+==== (6/20):[Flowvisor !FlowMap Overview] ==== #fv-1 
+The !FlowMap is one of Flowvisor's central components that must be ported. The first step, as always, is to understand how its components fit together. Hopefully there will be time for a clear re-write of the banter to follow...    
+
+A !FlowMap provides a uniform interface for the !FlowSpace. It can be thought of as a structure to hold the !FlowSpace, and to map it to proper slices. The two kinds of !FlowMaps supported by Flowvisor as of now (v.0.8.3) are the Linear and Federated !FlowMaps, both implementations of the Java interface, !FlowMap.java. A !FlowSpace, is represented by flow rules, which map actions to !OpenFlow pattern matches. The enum !MatchType defines how each header field of a (Flowvisor-defined) rule pattern and the received rule patterns relate. !FlowEntry.java implements the !FlowSpace. 
+
+''Intersections'' take two !FlowEntries and describe how they relate (via a !MatchType), and, if they overlap, a representation of the intersection in the form of a !FlowEntry built by choosing the more heavily constrained pattern for each header field and DPID(s). !FlowIntersect.java implements the representation of the intersection, and !FlowEntry defines matches(), which compares two !FlowEntries to produce the intersection. Comparisons are implemented in !FlowTestOp.java.  
+
+The "traditional" OFMatch construct doesn't so matching on DPID, so it is extended by FVMatch to do so.         
+
+
+
 == . ==#end