Changes between Version 34 and Version 35 of OpenFlow/FOAM

Timestamp:

11/19/12 16:59:58 (11 years ago)

Author:

Josh Smift

Comment:

No more FOAM 0.6, added some FV 0.8.13 stuff

OpenFlow/FOAM

@@ -29 +29 @@
 == Version ==
 
-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!
-
-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.
+The GPO currently recommends version 0.8.2 (the latest stable release) for GENI sites.
+
+Note 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.
 
 == Initial configuration ==
@@ -67 +67 @@
 
 Here are some before-and-after tests you can do when you upgrade FOAM, to confirm that your state hasn't changed unexpectedly.
-
-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".
 
 On the FOAM server, get a "before" list of slivers, active and deleted: 
@@ -131 +129 @@
 We 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.
 
-=== Administrative list-resources blocks other FOAM operations ===
-
-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.)
-
-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.
-
-This issue is fixed in FOAM 0.8.
-
 == Auto-approval ==
 
-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.
+FOAM 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.
 
 The action taken on a newly created sliver depends on the geni.approval.approve-on-creation configuration option. It has three possible values:
@@ -350 +340 @@
 == Changing the !FlowVisor password ==
 
-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.
-
- * Change the password in !FlowVisor: this assumes `/etc/flowvisor/config.xml` !FlowVisor's config, and is owned by user `openflow`:
-   * Change the password in !FlowVisor's config:
-{{{
-$ sudo service flowvisor stop
-$ sudo -u openflow fvconfig chpasswd /etc/flowvisor/config.xml fvadmin
-Enter password for account 'fvadmin' on the flowvisor:
-Enter password again
-$ sudo service flowvisor start  
-}}}
-   * If you store the password in `/etc/flowvisor/fvpasswd`, change it there too by hand:
-{{{
-$ sudo vi /etc/flowvisor/fvpasswd
-}}}
- * Change the password in FOAM:
+FOAM'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.
+
+=== Change the fvadmin password in FlowVisor ===
+
+First, 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!
+
+For FV 0.8.1.2, use fvconfig; NOTE that this requires an outage, as you need to stop and restart FlowVisor:
+
+{{{
+sudo service flowvisor stop
+sudo -u openflow fvconfig chpasswd /etc/flowvisor/config.xml fvadmin
+(enter the new password, twice)
+sudo service flowvisor start  
+}}}
+
+'''OR'''
+
+For FV 0.8.13, use fvctl; this does not cause an outage:
+
+{{{
+fvctl --passwd-file=/etc/flowvisor/fvpasswd changePasswd fvadmin
+(enter the new password)
+}}}
+
+=== Update /etc/flowvisor/fvpsaswd ===
+
+In either case, update /etc/flowvisor/fvpasswd to contain the new password when you're done.
+
+=== Change the fvadmin password in FOAM ===
+
+Change the password in FOAM:
+
 {{{
 foamctl config:set-value --key="flowvisor.passwd" --value="$(cat /etc/flowvisor/fvpasswd)" --passwd-file=/opt/foam/etc/foampasswd