Changes between Version 20 and Version 21 of FlowVisor
- Timestamp:
- 06/06/13 23:11:21 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FlowVisor
v20 v21 33 33 == System requirements == 34 34 35 Existing sites are running their FlowVisor on a variety of hardware (including in VMs); ONL currently recommends that aFlowVisor system should have at least 3 GB of RAM and at least two CPUs. These requirements may increase for larger scale deployments.36 37 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.35 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. 36 37 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. 38 38 39 39 == Version == … … 41 41 The GPO currently recommends version 1.0.8 for GENI sites. 42 42 43 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.43 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. 44 44 45 45 == !FlowVisor APIs == … … 61 61 == Initial configuration == 62 62 63 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.) 63 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.) 64 65 === Admin password === 64 66 65 67 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. 78 80 81 === Version holding === 82 83 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. 84 85 To do that on systems that use dpkg type packages: 86 87 {{{ 88 echo "flowvisor hold" | sudo dpkg --set-selections 89 }}} 90 91 To do that on systems that use RPM type packages: 92 93 {{{ 94 sudo sed -i -e 's/enabled=1/enabled=0/' /etc/yum.repos.d/onlab.repo 95 }}} 96 97 (To re-enable the repo when you really do want to upgrade, just change back to `enabled=1`.) 98 99 We also recommend [wiki:OpenFlow/FOAM#Versionholding doing this for FOAM]. 100 79 101 == Backups == 80 102 … … 93 115 === Restore === 94 116 95 NOTE that fvconfig can only be run when FlowVisor is '''not running'''.96 97 NOTE that this completely and irrevocably overwrites your existing FlowVisor database! Use with caution.117 NOTE that fvconfig can only be run when !FlowVisor is '''not running'''. 118 119 NOTE that this completely and irrevocably overwrites your existing !FlowVisor database! Use with caution. 98 120 99 121 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 == 118 140 119 Here are some before-and-after tests you can do when you upgrade FlowVisor, to confirm that your state hasn't changed unexpectedly.141 Here are some before-and-after tests you can do when you upgrade !FlowVisor, to confirm that your state hasn't changed unexpectedly. 120 142 121 143 First, get a "before" dump of the flowspace and slice info: … … 132 154 }}} 133 155 134 Next do the upgrade, as usual. Then make sure `/usr/bin/fvctl` points to `fvctl-xml`: 135 136 {{{ 137 sudo rm /usr/bin/fvctl 138 sudo ln -s fvctl-xml /usr/bin/fvctl 156 Next do the upgrade, as usual. For simple upgrades, on systems that use dpkg type packages: 157 158 {{{ 159 sudo apt-get update 160 sudo service flowvisor stop 161 sudo apt-get -y install flowvisor=1.0.8-1 162 sudo service flowvisor start 163 }}} 164 165 On systems that use RPM type packages: 166 167 {{{ 168 sudo service flowvisor stop 169 sudo yum -y install flowvisor-1.0.8-1 170 sudo service flowvisor start 171 }}} 172 173 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. 174 175 Then make sure `/usr/bin/fvctl` points to `fvctl-xml`: 176 177 {{{ 178 sudo ln -f -s fvctl-xml /usr/bin/fvctl 139 179 sudo sed -i -e 's/echo "Warning: The XMLRPC interface is deprecated/#echo "Warning: The XMLRPC interface is deprecated/' /usr/bin/fvctl-xml 140 180 }}}