Changes between Version 20 and Version 21 of FlowVisor

Timestamp:

06/06/13 23:11:21 (11 years ago)

Author:

Josh Smift

Comment:

--

FlowVisor

@@ -33 +33 @@
 == System requirements ==
 
-Existing sites are running their FlowVisor on a variety of hardware (including in VMs); ONL currently recommends that a FlowVisor system should have at least 3 GB of RAM and at least two CPUs. These requirements may increase for larger scale deployments.
-
-It's also advantageous to have a robust control network interface to FlowVisor. ONL currently recommends two gigabit interfaces, one to communicate with switches ("downstream") and one to communicate with controllers ("upstream"), if your network design permits. If your upstream and downstream traffic need to share an interface, it might be prudent to have a 10 GB NIC if possible.
+Existing sites are running their !FlowVisor on a variety of hardware (including in VMs); ONL currently recommends that a !FlowVisor system should have at least 3 GB of RAM and at least two CPUs. These requirements may increase for larger scale deployments.
+
+It's also advantageous to have a robust control network interface to !FlowVisor. ONL currently recommends two gigabit interfaces, one to communicate with switches ("downstream") and one to communicate with controllers ("upstream"), if your network design permits. If your upstream and downstream traffic need to share an interface, it might be prudent to have a 10 GB NIC if possible.
 
 == Version ==
@@ -41 +41 @@
 The GPO currently recommends version 1.0.8 for GENI sites.
 
-We're currently (May 2013) in the proess of working with sites to upgrade to that version. Sites that haven't yet upgraded are mostly running 0.8.17; existing GENI racks may be running even older versions of 0.8.
+As of June 2013, we're in the proess of working with sites to upgrade to that version. Sites that haven't yet upgraded are mostly running 0.8.17; existing GENI racks may be running even older versions of 0.8.
 
 == !FlowVisor APIs ==
@@ -61 +61 @@
 == Initial configuration ==
 
-The default configuration of !FlowVisor is general suitable for GENI sites, except that we recommend the XMLRPC API for now. (See above for more info, including commands to make `/usr/bin/fvctl` point to the XML version.)
+The default configuration of !FlowVisor is generally suitable for GENI sites, except that we recommend the XMLRPC API for now. (See above for more info, including commands to make `/usr/bin/fvctl` point to the XML version.)
+
+=== Admin password ===
 
 We typically put the !FlowVisor fvadmin password into /etc/flowvisor.passwd, so you don't have to type it every time you run an fvctl command. Make sure that it's only readable by people who should have full admin access to !FlowVisor on your system! (World-readable might be fine if only FV admins have accounts on your FV server; or you might want to make it only group-readable by a group that includes the FV admins.) The examples on the rest of this page assume that you've done that.
@@ -77 +79 @@
 The rest of this page assumes that you've done that.
 
+=== Version holding ===
+
+We also recommend telling your package management system to hold !FlowVisor at its current version, so that if you do a general upgrade of all of the packages on your system, it won't get updated along with that, but will only update when you explicitly say so.
+
+To do that on systems that use dpkg type packages:
+
+{{{
+echo "flowvisor hold" | sudo dpkg --set-selections
+}}}
+
+To do that on systems that use RPM type packages:
+
+{{{
+sudo sed -i -e 's/enabled=1/enabled=0/' /etc/yum.repos.d/onlab.repo
+}}}
+
+(To re-enable the repo when you really do want to upgrade, just change back to `enabled=1`.)
+
+We also recommend [wiki:OpenFlow/FOAM#Versionholding doing this for FOAM].
+
 == Backups ==
 
@@ -93 +115 @@
 === Restore ===
 
-NOTE that fvconfig can only be run when FlowVisor is '''not running'''.
-
-NOTE that this completely and irrevocably overwrites your existing FlowVisor database! Use with caution.
+NOTE that fvconfig can only be run when !FlowVisor is '''not running'''.
+
+NOTE that this completely and irrevocably overwrites your existing !FlowVisor database! Use with caution.
 
 You need to run the restore as the 'flowvisor' user, since that user has the right permissions to create the DB files:
@@ -117 +139 @@
 == Upgrading ==
 
-Here are some before-and-after tests you can do when you upgrade FlowVisor, to confirm that your state hasn't changed unexpectedly.
+Here are some before-and-after tests you can do when you upgrade !FlowVisor, to confirm that your state hasn't changed unexpectedly.
 
 First, get a "before" dump of the flowspace and slice info:
@@ -132 +154 @@
 }}}
 
-Next do the upgrade, as usual. Then make sure `/usr/bin/fvctl` points to `fvctl-xml`:
-
-{{{
-sudo rm /usr/bin/fvctl
-sudo ln -s fvctl-xml /usr/bin/fvctl
+Next do the upgrade, as usual. For simple upgrades, on systems that use dpkg type packages:
+
+{{{
+sudo apt-get update
+sudo service flowvisor stop
+sudo apt-get -y install flowvisor=1.0.8-1
+sudo service flowvisor start
+}}}
+
+On systems that use RPM type packages:
+
+{{{
+sudo service flowvisor stop
+sudo yum -y install flowvisor-1.0.8-1
+sudo service flowvisor start
+}}}
+
+More complex upgrades might have additional steps, which will generally be described on a separate page, in the announcement of the upgrade, and/or in the release notes.
+
+Then make sure `/usr/bin/fvctl` points to `fvctl-xml`:
+
+{{{
+sudo ln -f -s fvctl-xml /usr/bin/fvctl
 sudo sed -i -e 's/echo "Warning: The XMLRPC interface is deprecated/#echo "Warning: The XMLRPC interface is deprecated/' /usr/bin/fvctl-xml
 }}}