Changes between Version 15 and Version 16 of OpenFlow/FOAM/AdminIntro


Ignore:
Timestamp:
01/30/14 15:29:28 (10 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/FOAM/AdminIntro

    v15 v16  
    1717Here's a simplified overview of how FOAM (and !FlowVisor, and !OpenFlow in general) works.
    1818
    19 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.
     19A physical !OpenFlow switch has one or more "datapaths", each of which connects to one !OpenFlow controller. Each datapath has a unique identifier ("DPID"), often including the MAC address of the management interface on the switch, and on VLAN-hybrid switchs, the VLAN ID corresponding to that datapath.
     20
     21To allow multiple GENI experimenters to use a datapath, we use !FlowVisor to slice traffic into multiple "flowspaces", based on criteria that match various characteristics of the traffic ("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.
    2022
    2123(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 that have been allocated to a FOAM sliver.)
     
    4749FOAM will send mail to the FOAM admins and to experimenters when it does various things, such as when a sliver is created, approved, and deleted. There's also a nightly FOAM cron job that reports on "pending" slivers, i.e. anything that wasn't automatically approved; those generally reflect an experimenter who's waiting for resources. '''In practice, a pending sliver is the main thing that will fall through the cracks if you don't handle it, so please do keep an eye on it, and try to act on those messages expeditiously (even if all you do is drop a note to gpo-infra asking for help).''' You can generally skim the other messages to make sure they don't contain anything unusual, and otherwise, archive them in case you ever need them later.
    4850
    49 Here's an example of what the "pending slivers" cron job mail looks like:
     51Here's an example of one of those important "pending slivers" cron job messages:
    5052
    5153{{{
     
    6365}}}
    6466
    65 You can also configure FOAM not to send you so much e-mail, if you'd rather it not. To do that, set any or all of the {{{email.event.<thing>.admin}}} configuration variables to false, like so:
     67Here's an example of a routine sliver creation message, which you can safely ignore:
    6668
    6769{{{
    68 variables='email.event.createsliver.admin email.event.disablesliver.admin email.event.rejectsliver.admin email.event.json-deletesliver.admin email.event.gapi-deletesliver.admin email.event.renewsliver.admin email.event.approvesliver.admin email.event.expiresliver.admin email.event.expiresliverday.admin email.event.expiresliverweek.admin email.event.shutdownsliver.admin'
     70From: FOAM at BBN <foam-admin@gpolab.bbn.com>
     71To: foam-admin@gpolab.bbn.com
     72Subject: FOAM sliver created
     73Date: Fri, 10 Jan 2014 13:29:27 -0500 (EST)
     74 
     75(This is an automated message from FOAM.)
     76 
     77A FOAM sliver at foam.gpolab.bbn.com
     78has been created:
     79 
     80  Sliver URN: urn:publicid:IDN+ch.geni.net:gpo-infra+slice+gpoN15:ce46ec0e-e297-4569-bb21-b7a370e1afbe
     81  Owner URN: urn:publicid:IDN+ch.geni.net+user+jbs
     82  Owner e-mail: jbs@bbn.com
     83 
     84If the sliver was not automatically approved or rejected, please check
     85FOAM's pending queue to approve or reject it.
     86}}}
     87
     88You can also configure FOAM not to send you those sorts of messages at all, if you'd rather it not. To do that, set any or all of the {{{email.event.<thing>.admin}}} configuration variables to false, like so:
     89
     90{{{
     91variables="email.event.createsliver.admin email.event.disablesliver.admin \
     92email.event.rejectsliver.admin email.event.json-deletesliver.admin \
     93email.event.gapi-deletesliver.admin email.event.renewsliver.admin \
     94email.event.approvesliver.admin email.event.expiresliver.admin \
     95email.event.expiresliverday.admin email.event.expiresliverweek.admin \
     96email.event.shutdownsliver.admin"
     97
    6998(or some subset of those)
    7099
    71 for key in $variables ; do foamctl config:set-value --key="$key" --value="False" --passwd-file=/etc/foam.passwd
     100for var in $variables ; do foamctl config:set-value --key="$var" --value="False" --passwd-file=/etc/foam.passwd
    72101}}}
    73102