Changes between Version 2 and Version 3 of OpenFlow/FOAM/AdminIntro

Timestamp:

07/15/13 10:36:38 (11 years ago)

Author:

Josh Smift

Comment:

--

OpenFlow/FOAM/AdminIntro

@@ -7 +7 @@
 Our [wiki:OpenFlow/FOAM main FOAM page] and [wiki:FlowVisor main FlowVisor page] have much more information, and many of the sections below link to things on those pages.
 
+We also have a page about [wiki:GENIConcepts general GENI concepts], and a [wiki:GENIGlossary glossary of GENI terms].
+
 There are also usually GPO and other GENI FOAM/FV/!OpenFlow-savvy folks on the #geni-openflow channel on the Freenode IRC network; see [wiki:HowTo/ConnectToGENIChatRoom our general IRC page] to get connected there.
 
@@ -13 +15 @@
 Here's a simplified overview of how FOAM (and !FlowVisor, and !OpenFlow in general) works.
 
-A physical !OpenFlow switch has one or more "datapaths", each of which connects to one !OpenFlow controller. To allow multiple GENI experimenters to use a datapath, we use !FlowVisor to slice traffic based on match criteria ("flowspace rules" in FV terms). For example, the flowspace rules for a FV slice might match any traffic on VLAN 1755 (dl_vlan=1755), or IP subnet 10.42.15.0/24 (dl_type=0x800,nw_dst=10.42.109.0/24,nw_src=10.42.109.0/24), etc.
+A physical !OpenFlow switch has one or more "datapaths", each of which connects to one !OpenFlow controller. To allow multiple GENI experimenters to use a datapath, we use !FlowVisor to slice traffic based on match criteria ("flowspace rules" in FV terms). For example, the flowspace rules for a FV slice might match any traffic on VLAN 1755 (`dl_vlan=1755`), or IP subnet 10.42.15.0/24 (`dl_type=0x800,nw_dst=10.42.109.0/24,nw_src=10.42.109.0/24`), etc.
 
 (Note that a "!FlowVisor slice" isn't a slice in the GENI sense; they're very different, they just happen to use the same term. There's typically a one-to-one relationship between a FOAM sliver and a FV slice, so it may be helpful to think of a FV slice as the resources belonging to a FOAM sliver.)