Changes between Version 34 and Version 35 of OpenFlow/FOAM


Ignore:
Timestamp:
11/19/12 16:59:58 (7 years ago)
Author:
Josh Smift
Comment:

No more FOAM 0.6, added some FV 0.8.13 stuff

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/FOAM

    v34 v35  
    2929== Version ==
    3030
    31 The GPO currently recommends version 0.8.2 (the latest stable release) for GENI sites. There are many changes from 0.8 to 0.6, and we recommend working with the GPO to help the upgrade process go smoothly. Contact us at gpo-infra@geni.net and we'll be happy to help!
    32 
    33 NOTE that much of this page is FOAM 0.8 specific. http://groups.geni.net/geni/wiki/OpenFlow/FOAM?version=22 has the last 0.6 specific version.
     31The GPO currently recommends version 0.8.2 (the latest stable release) for GENI sites.
     32
     33Note that there were significant changes between FOAM 0.6 and FOAM 0.8; http://groups.geni.net/geni/wiki/OpenFlow/FOAM?version=22 has the last version of this page with 0.6-specific information.
    3434
    3535== Initial configuration ==
     
    6767
    6868Here are some before-and-after tests you can do when you upgrade FOAM, to confirm that your state hasn't changed unexpectedly.
    69 
    70 Note that if you're upgrading from FOAM 0.6 to 0.8, you'll need to modify the foamctl commands in the "before" section, changing "geni:list-slivers" to "list-slivers".
    7169
    7270On the FOAM server, get a "before" list of slivers, active and deleted:
     
    131129We don't currently think that there's a valid use case for an experimenter wanting to specify a match at one layer without specifying the protocol at a lower layer, but will amend this advisory if we encounter one.
    132130
    133 === Administrative list-resources blocks other FOAM operations ===
    134 
    135 In FOAM 0.6, an administrative list-resources call locks the FOAM database, and thus blocks other FOAM operations. If an experimenter tries to use FOAM while this is happening, they'll get a "database is locked" error; if they retry, it should work. (If the error persists, something else is probably wrong.)
    136 
    137 The FOAM monitoring code (from the 'tango-monitor-foam' package) does an administrative list-slivers whenever it runs, and it runs once per minute by default, so there's small window each minute (a second or two) when this can happen.
    138 
    139 This issue is fixed in FOAM 0.8.
    140 
    141131== Auto-approval ==
    142132
    143 FOAM 0.8 adds 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.
     133FOAM 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.
    144134
    145135The action taken on a newly created sliver depends on the geni.approval.approve-on-creation configuration option. It has three possible values:
     
    350340== Changing the !FlowVisor password ==
    351341
    352 FOAM's database stores information about the !FlowVisor it manages, including its hostname and password. If you want to change that !FlowVisor's password, you need to change it both in FV itself, and also in FOAM.
    353 
    354  * Change the password in !FlowVisor: this assumes `/etc/flowvisor/config.xml` !FlowVisor's config, and is owned by user `openflow`:
    355    * Change the password in !FlowVisor's config:
    356 {{{
    357 $ sudo service flowvisor stop
    358 $ sudo -u openflow fvconfig chpasswd /etc/flowvisor/config.xml fvadmin
    359 Enter password for account 'fvadmin' on the flowvisor:
    360 Enter password again
    361 $ sudo service flowvisor start 
    362 }}}
    363    * If you store the password in `/etc/flowvisor/fvpasswd`, change it there too by hand:
    364 {{{
    365 $ sudo vi /etc/flowvisor/fvpasswd
    366 }}}
    367  * Change the password in FOAM:
     342FOAM's database stores information about the !FlowVisor it manages, including its hostname and password. If you want to change that !FlowVisor's fvadmin password, you need to change it both in FV itself, and also in FOAM.
     343
     344=== Change the fvadmin password in FlowVisor ===
     345
     346First, change the password in Flowvisor. NOTE that this procedure differs depending on whether you're running FV 0.8.1.2 or 0.8.13; only do one of the following!
     347
     348For FV 0.8.1.2, use fvconfig; NOTE that this requires an outage, as you need to stop and restart FlowVisor:
     349
     350{{{
     351sudo service flowvisor stop
     352sudo -u openflow fvconfig chpasswd /etc/flowvisor/config.xml fvadmin
     353(enter the new password, twice)
     354sudo service flowvisor start 
     355}}}
     356
     357'''OR'''
     358
     359For FV 0.8.13, use fvctl; this does not cause an outage:
     360
     361{{{
     362fvctl --passwd-file=/etc/flowvisor/fvpasswd changePasswd fvadmin
     363(enter the new password)
     364}}}
     365
     366=== Update /etc/flowvisor/fvpsaswd ===
     367
     368In either case, update /etc/flowvisor/fvpasswd to contain the new password when you're done.
     369
     370=== Change the fvadmin password in FOAM ===
     371
     372Change the password in FOAM:
     373
    368374{{{
    369375foamctl config:set-value --key="flowvisor.passwd" --value="$(cat /etc/flowvisor/fvpasswd)" --passwd-file=/opt/foam/etc/foampasswd