Changes between Version 26 and Version 27 of OpenFlow/FOAM

Timestamp:

07/17/12 15:28:37 (12 years ago)

Author:

Josh Smift

Comment:

--

OpenFlow/FOAM

@@ -70 +70 @@
  * Mode 0, "never": Newly created slivers are never automatically approved.
  * Mode 1, "always": Newly created slivers are always automatically approved.
- * Mode 2, "analsys": Newly created slivers are automatically approved if they pass all the checks in the analysis engine.
-
-The default value is "0", for safety. You can turn it on with foamctl:
+ * Mode 2, "analysis": Newly created slivers are automatically approved if they pass all the checks in the analysis engine.
+
+The default value is "0", for safety, so no slivers will be auto-approved.
+
+The rest of this section is only really relevant if you use mode 2. If you've read the rest of this section and want to do that, you can do it with foamctl:
 
 {{{
@@ -78 +80 @@
 }}}
 
-The analysis engine performs three tests related to your flowspace:
+The analysis engine performs three tests related to the sliver's flowspace:
 
  1. If the sliver's flowspace includes IP space: That IP space must not overlap with the IP space of any already-approved slivers.
@@ -88 +90 @@
 It also performs three tests related to datapaths, ports, and VLANs:
 
- 1. The sliver's flowspace must include at least one datapath. (no 'any')
- 2. The sliver's flowspace must not include more than one port in any port group. (if any port groups are defined)
+ 1. The sliver's flowspace must include at least one datapath.
+ 2. The sliver's flowspace must not include more than one of the ports in any port group.
  3. The sliver's flowspace must not include any flowspace defined by VLAN. (no 'dl_vlan')
 
-The sliver is automatically approved if at least one test in the first group passes, and no test fails (in either group). (When FOAM is in mode 2 -- in the other modes, the analysis is still done, but the results are ignored.)
+In mode 2, the sliver is automatically approved if at least one test in the first group passes, and no test fails (in either group).
 
 In practice, this implements a policy somewhat like: "Auto-approve a sliver that includes IP, MAC, or ethertype flowspace, doesn't overlap with anything else, and doesn't include more than one port in these port groups". Port groups might include things like cross-connects, or any other collection of ports where you only want a given sliver to have one port in the group.