Changes between Version 33 and Version 34 of OpenFlow/FOAM


Ignore:
Timestamp:
10/05/12 15:46:45 (7 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/FOAM

    v33 v34  
    3737When you install FOAM for the first time (i.e. not an upgrade to an existing installation), you should configure 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].
    3838
    39 You'll need to configure FOAM to point to your FlowVisor, which you can do interactively with {{{foamctl config:set-flowvisor-info}}}, or non-interactively like this (with values that work for your installation):
     39We typically put the FOAM admin password into /opt/foam/etc/foampasswd, so you don't have to type it every time you run a foamctl command. Make sure that it's only readable by people who should have full admin access to FOAM on your system! (World-readable might be fine if only FOAM admins have accounts on your FOAM server; or you might want to make it only group-readable by a group that includes the FOAM admins.) The examples on the rest of this page assume that you've done that.
     40
     41You'll then need to configure FOAM to point to your FlowVisor, which you can do interactively with {{{foamctl config:set-flowvisor-info}}}, or non-interactively like this (with values that work for your installation):
    4042
    4143{{{
     
    4446}}}
    4547
    46 For GENI purposes, we recommend also configuring your site tag, admin e-mail (which causes it to show up in sliverstatus), and max lease:
    47 
    48  * Your site tag should be something that uniquely identifies this FOAM instance. We use foam.gpolab.bbn.com (a CNAME that points to our FOAM server) at BBN.
     48In order to work smoothly with GENI monitoring, you'll also need to set your site tag to a name that resolves, in DNS, to the system where your FOAM server runs (i.e. the hostname part of the GENI AM API URL). It defaults to the system's FQDN, and that's fine if you don't want to change it. You can also change it to something more abstract, like a CNAME such as "foam.gpolab.bbn.com", which is what we do. To change it, use a command like this, replacing the "value=" part with a good value for your site:
     49
     50{{{
     51foamctl config:set-value --key="geni.site-tag" --value="foam.gpolab.bbn.com" --passwd-file=/opt/foam/etc/foampasswd
     52}}}
     53
     54Finally, for GENI purposes, we recommend also configuring your admin e-mail (which causes it to show up in sliverstatus), and max lease:
     55
    4956 * The admin e-mail setting should generally be the same address you used when you set up e-mail. We use foam-admin@gpolab.bbn.com (a list with a couple of admins on it) at BBN.
    5057 * The max lease setting controls how the maximum value of the sliver expiration date (e.g. when an experimenter does a renewsliver). We use 9000 hours (about a year) at BBN, and recommend that; making this short just means that experimenters who want a long-lived sliver have to do a renewsliver more frequently.
    5158
    52 We also typically put the FOAM admin password into /opt/foam/etc/foampasswd, so you don't have to type it every time you run a foamctl command. Make sure that it's only readable by people who should have full admin access to FOAM on your system! (World-readable might be fine if only FOAM admins have accounts on your FOAM server; or you might want to make it only group-readable by a group that includes the FOAM admins.)
    53 
    5459To set those with foamctl (replace the "value" part with the values you want to use):
    5560
    5661{{{
    57 foamctl config:set-value --key="geni.site-tag" --value="foam.gpolab.bbn.com" --passwd-file=/opt/foam/etc/foampasswd
    5862foamctl config:set-value --key="site.admin.email" --value="foam-admin@gpolab.bbn.com" --passwd-file=/opt/foam/etc/foampasswd
    5963foamctl config:set-value --key="geni.max-lease" --value=9000 --passwd-file=/opt/foam/etc/foampasswd