Changes between Version 62 and Version 63 of OpenFlow/FOAM


Ignore:
Timestamp:
09/16/13 11:10:02 (11 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • OpenFlow/FOAM

    v62 v63  
    1919Most 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).
    2020
    21 FOAM 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.
    22 
    23 If you're setting up a multi-campus topology, note that your sliver will need to be approved separately at each FOAM aggregate.
     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 the address in your slice credential isn't valid, 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. (This should generally not be a problem for GENI CH, Emulab, or PLC credentials.)
    2422
    2523= Info for admins =
    … …  
    3735== Version ==
    3836
    39 The GPO currently recommends version 0.12.2 (the latest stable release) for GENI sites.
     37The GPO currently recommends version 0.12.3 (the latest stable release) for GENI sites.
    4038
    4139In the very unlikely event that you're interested in versions of FOAM previous to 0.8, http://groups.geni.net/geni/wiki/OpenFlow/FOAM?version=22 has the last version of this page with 0.6-specific information.
    … …  
    248246sudo apt-get update
    249247sudo service foam stop
    250 sudo apt-get install -y --ignore-hold --allow-unauthenticated foam
     248sudo apt-get install --ignore-hold --allow-unauthenticated foam
    251249sudo service foam start
    252250}}}
    … …  
    297295== Auto-approval ==
    298296
    299 FOAM 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.
     297FOAM includes a simple analysis engine which can be used to inform auto-approval decisions. The analysis is done by default (whether or not it's acted on), but can be disabled if you really want to for some reason.
    300298
    301299=== Auto-approval mode ===
    … …  
    333331=== Analysis and VLANs ===
    334332
    335 In principle, traffic in GENI is sliced by VLAN, such that each slice has one or more private VLANs that carry traffic only for that slice. In practice, the current GENI mesoscale OpenFlow network consists mainly of VLAN-hybrid switches, and thus uses a single shared VLAN (colloquially "1750", the VLAN ID number used by many (but not all) sites), where traffic is then sliced by other features, such as MAC address, ethertype, or IP subnet. The [wiki:NetworkCore GENI network core page] has more details about that. (FIXME: No it doesn't. But it really should. Or maybe there's some other page that does, or should.)
    336 
    337 Prior to FOAM 0.12, the analysis engine only supports VLAN-hybrid datapaths, and could not auto-approve any sliver that included a VLAN-based match (the dl_vlan match attribute).
    338 
    339 As of FOAM 0.12, the analysis engine also supports dl_vlan matches, and differentiates between "exclusive" VLANs, "reserved" VLANs, and "shared" VLANs. The shared mesoscale VLAN (and other VLAN-hybrid datapaths) is effectively a special case of a shared VLAN, one in which no dl_vlan attribute is specified ("dl_vlan=none" is one way to think about it).
     333In principle, traffic in GENI is sliced by VLAN, such that each slice has one or more private VLANs that carry traffic only for that slice. In practice, the current GENI mesoscale OpenFlow network consists mainly of VLAN-hybrid switches, and thus uses a single shared VLAN (colloquially "1750", the VLAN ID number used by many (but not all) sites), where traffic is then sliced by other features, such as MAC address, ethertype, or IP subnet. The [wiki:NetworkCore GENI network core page] has more details about that.
     334
     335The analysis engine differentiates between "exclusive" VLANs, "reserved" VLANs, and "shared" VLANs. The shared mesoscale VLAN (and other VLAN-hybrid datapaths) is effectively a special case of a shared VLAN, one in which no dl_vlan attribute is specified ("dl_vlan=none" is one way to think about it).
    340336
    341337By default, FOAM treates each VLAN as exclusive, unless a FOAM admin has added the VLAN to the list of reserved or shared VLANs. (A VLAN can be on both lists, although there's not really any reason to do that; but if you want to change a VLAN from one to the other, for example, you need to both remove it from the old list and add it to the new one.)
    … …  
    393389These commands all assume that you're running them on the FOAM server, and that you have a file /etc/foam.passwd, containing the FOAM admin password.
    394390
     391=== Re-approve all previously-approved slivers ===
     392
     393If your !FlowVisor dies badly or otherwise gets into a bad state, you can now re-approve all FOAM slivers that were previously approved, with one command:
     394
     395{{{
     396foamctl geni:reapprove-slivers
     397}}}
     398
    395399=== Get a list of slivers ===
    396400