Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As of right now, we only have binary support for 32-bit Debian and Ubuntu based distributions. If you have a distribution you want supported, or better yet, want to support a new distribution, please send us mail. Note: User flowvisor must exist.

Debian/Ubuntu
Code Block

# Add deb http://updates.flowvisor.org/openflow/downloads/GENI/DEB unstable/binary-$(ARCH)/ to your /etc/apt/sources.list
# sudo apt-get update
# sudo apt-get install flowvisor

...

Fetch the source:

Code Block

hg clone https://bitbucket.org/onlab/flowvisor
cd flowvisor
hg update -C 0.8-MAINT

Now, build it:

Code Block

make

(FlowVisor also works with openjdk, but you will have to adjust the commands accordingly)

...

When prompted, set the prefix to /usr/local and the user/group to the user/group you want the flowvisor to run as. Next, generate a default configuration file with:

Code Block

fvconfig generate /usr/local/etc/flowvisor/flowvisor-config.json
# (optionally) store the root password in /root/.fvp

...

Now and then, fixes will be applied to the mercurial repository, and we will want to install them. In order to get the latest and greatest, do the following:

Code Block

cd $flowvisor_src_dir
make clean
hg pull 
hg update
make

If the build ends with BUILD SUCCESSFUL then install flowvisor again. If you would like to keep your config then simply run:

Code Block

make install

This will leave the previous existing config file and database (if any) intact.

If you would like a completely fresh install, run:

Code Block

rm <path_to_fv_install>/etc/flowvisor/config.json
make install

...

To run flowvisor 0.8.3 and above you will need to convert your config file from xml to json. Luckily, we have made this easy for you. Once FlowVisor is installed, simply run:

Code Block

fvconfig convert config.xml

...

Then, give the following commands (deleting slices implicitly deletes the rules associated with them):

Code Block

fvctl --passwd-file=/root/.fvp  deleteSlice alice
fvctl --passwd-file=/root/.fvp  deleteSlice bob

You can now define a fall-back "production" slice that will catch all flows from all switches that are not handled by higher-priority flowspace definitions. Again, in the second window on the flowvisor machine, give the following commands:

Code Block

fvctl --passwd-file=/root/.fvp createSlice production tcp:yourhost.com:6633 slice-email@yourhost.com
fvctl --passwd-file=/root/.fvp addFlowSpace any 10 any "Slice:production=4"

...

The Expedient aggregate manager needs a correctly built mySSLKeyStore file in the flowvisor configuration directory. To build this file, do the following:

Code Block

cd /usr/local/etc/flowvisor
fvconfig generateCert

...