Changes between Version 49 and Version 50 of OpenFlow/FOAM


Ignore:
Timestamp:
05/30/13 12:10:33 (6 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/FOAM

    v49 v50  
    55FOAM is an OpenFlow aggregate manager, which sites in GENI use to allow experimenters to allocate !OpenFlow resources.
    66
    7 https://openflow.stanford.edu/display/FOAM has more information about FOAM (from the official site at Stanford), including [https://openflow.stanford.edu/display/FOAM/0.8.x+Install+Guide installation instructions], [https://openflow.stanford.edu/display/FOAM/FAQ a FAQ] with common error messages (for both experimenters and admins), etc.
     7https://openflow.stanford.edu/display/FOAM has more information about FOAM (from the official site at Stanford), including [https://openflow.stanford.edu/display/FOAM/0.10.x+Install+Guide installation instructions], [https://openflow.stanford.edu/display/FOAM/FAQ a FAQ] with common error messages (for both experimenters and admins), etc.
    88
    99= Info for experimenters =
     
    1717== Getting your sliver approved ==
    1818
    19 If you allocate a shared resource that connects to an !OpenFlow aggregate (e.g. a MyPLC plnode or ProtoGENI host), you'll typically also need to reserve some !OpenFlow resources. When you do this, your reservation request may be held for approval, in which case a local FOAM admin will need to approve your request before your sliver actually becomes live. You should get e-mail from FOAM when your sliver is created, and another message when it's been approved; if you don't hear back, you may be able to reach a FOAM admin by replying to that message (or to the contact information in the body of the message).
    20 
    21 As of FOAM 0.8, FOAM can read your e-mail address from your slice credential. If that address is valid, then you don't need to include an e-mail address in your rspec, but make sure it is! If it isn't, make sure that you also provide a valid email address in your rspec so that you can get the notifications about status changes of your !OpenFlow sliver.
     19Many FOAM aggregates have enabled automatic approval of slivers whose flowspace doesn't overlap with any existing slivers. If your flowspace does overlap with someone else's, or if auto-approval isn't enabled, your reservation request may be held for approval, in which case a local FOAM admin at that site will need to approve your request before your sliver actually becomes live. You should get e-mail from FOAM when your sliver is created, and another message when it's been approved; if you don't hear back, you may be able to reach a FOAM admin by replying to that message (or to the contact information in the body of the message).
     20
     21FOAM can read your e-mail address from your slice credential, so if that address is valid, then you don't need to include an e-mail address in your rspec. If it isn't, make sure that you also provide a valid email address in your rspec so that you can get the notifications about status changes of your !OpenFlow sliver.
    2222
    2323If you're setting up a multi-campus topology, note that your sliver will need to be approved separately at each FOAM aggregate.
     
    4343=== Administrative e-mail ===
    4444
    45 When you install FOAM for the first time (i.e. not an upgrade to an existing installation), you should configure its ability to send you administrative e-mail; those steps are part of the official [https://openflow.stanford.edu/display/FOAM/0.8.x+Install+Guide FOAM 0.8 install guide].
     45When you install FOAM for the first time (i.e. not an upgrade to an existing installation), you should configure its ability to send you administrative e-mail; those steps are part of the official [https://openflow.stanford.edu/display/FOAM/0.10.x+Install+Guide FOAM 0.10 install guide].
    4646
    4747=== Admin password ===
     
    116116}}}
    117117
    118 If you own any slivers on the server, you can also do a listresources and sliverstatus for a sliver or two.
     118If you own any slivers on the server, you can also do a listresources and sliverstatus for a sliver or two, and save that output for later comparison.
    119119
    120120Then do the upgrade, as usual. For simple upgrades:
     
    153153You should typically expect no differences.
    154154
     155If you own any slivers on the server, you can also do a listresources and sliverstatus for a sliver or two, compare that output to the output from before the upgrade.
     156
    155157== Advisories ==
    156158
    157159Here are some things that FOAM admins should be aware of and watch out for.
    158 
    159 === Rspecs that include both cross-connect ports ===
    160 
    161 In the current standard [wiki:OpenFlow/CampusTopology campus topology], a local !OpenFlow-controlled VLAN (often VLAN 1750) is cross-connected to multiple inter-campus VLANs, and a given sliver typically only includes one cross-connect port. FOAM admins should be careful not to approve rspecs that include both cross-connect ports (either explicitly or implicitly, e.g. by requesting the entire local DPID for VLAN 1750).
    162 
    163 Some experimenters may have good reasons for wanting to use both cross-connects; if they do, make sure they understand that this is a risky topology before you approve their sliver.
    164160
    165161=== Rspecs that include match rules with no protocol specified ===
     
    176172== Auto-approval ==
    177173
    178 FOAM 0.8 includes a simple analysis engine which can be used to inform auto-approval decisions. The analysis is done by default, but can be disabled if you really want to for some reason.
     174FOAM 0.10 includes a simple analysis engine which can be used to inform auto-approval decisions. The analysis is done by default, but can be disabled if you really want to for some reason.
    179175
    180176The action taken on a newly created sliver depends on the geni.approval.approve-on-creation configuration option. It has three possible values:
     
    216212== Sliver approval workflow ==
    217213
    218 This section describes our workflow for approving slivers at BBN.
     214This section describes our workflow at BBN for approving slivers which aren't approved automatically.
    219215
    220216FOAM sends e-mail about new slivers to the FOAM admin e-mail address that you configured when you set up FOAM. If further communication about a sliver request is needed, we copy that address on the e-mail, so that everyone will see it. We also send mail to to that address when we approve or reject the sliver (or if we review the request and we're not sure whether to approve or reject it), so everyone knows who did it.