Changes between Version 6 and Version 7 of OpenFlow/FOAM/AdminIntro


Ignore:
Timestamp:
12/19/13 14:06:29 (6 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/FOAM/AdminIntro

    v6 v7  
    4545== E-mail ==
    4646
    47 FOAM 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, so please try to act on those expeditiously. 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. 
     47FOAM 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, so please try to act on those expeditiously. 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.
    4848
    49 FOAM has two places where e-mail is configured: The site.admin.email setting, which shows up in getversion output, and the configuration for administrative e-mail. Racks generally come with the latter pre-configured, and you can set the former if you like, or not if you don't (see http://groups.geni.net/geni/wiki/OpenFlow/FOAM#Othersettings for instructions).
     49Here's an example of what the "pending slivers" cron job mail looks like:
     50
     51{{{
     52From: FOAM at BBN <foam-admin@gpolab.bbn.com>
     53To: foam-admin@gpolab.bbn.com
     54Subject: [gpo-ops] FOAM Pending Queue
     55Date: Thu, 12 Sep 2013 09:52:02 -0400 (EDT)
     56 
     57(This is an automated message from FOAM.)
     58 
     59The following slivers at foam.gpolab.bbn.com are pending admin approval:
     60 
     61Sliver URN: urn:publicid:IDN+ch.geni.net:JBS+slice+jbsfoamtest:a4ee89ac-3f7b-46fa-a78f-bf24a22f9474
     62     User: jbs@bbn.com [urn:publicid:IDN+ch.geni.net+user+jbs]
     63}}}
     64
     65You 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}}} cnofiguration variables to false, like so:
     66
     67{{{
     68variables='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'
     69(or some subset of those)
     70
     71for key in $variables ; do foamctl config:set-value --key="$key" --value="False" --passwd-file=/etc/foam.passwd
     72}}}
     73
     74You should leave {{{email.event.pendingqueue.admin}}} turned on, so that you'll still get mail about the pending queue.
     75
     76FOAM has two places where e-mail addresses are configured: The site.admin.email setting, which shows up in getversion output, and the configuration for administrative e-mail. Racks generally come with the latter pre-configured, and you can set the former if you like, or not if you don't (see http://groups.geni.net/geni/wiki/OpenFlow/FOAM#Othersettings for instructions).
    5077
    5178== Configuration ==