Changes between Version 1 and Version 2 of Internal/OpenFlow/FloodlightFVPort/InstallUsage
- Timestamp:
- Aug 19, 2012, 7:53:20 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/OpenFlow/FloodlightFVPort/InstallUsage
v1 v2 1 1 = Installation and Usage = 2 2 3 As of now this project is extremely rough around the edges. 3 As of now this project is extremely rough around the edges. However, the information on the Floodlight [http://floodlight.openflowhub.org/getting-started/ Getting Started] page and [http://floodlight.openflowhub.org/developing-floodlight/ Development tutorial] apply almost exactly to this version of the controller and can be used to troubleshoot installation and module development/loading issues. 4 4 5 === Installation === 5 == Installation == 6 7 On Ubuntu 10.04 and later: 8 9 Install dependencies: 10 {{{ 11 sudo apt-get install build-essential default-jdk ant python-dev eclipse 12 }}} 6 13 7 14 The source code can be fetched using git and built with `ant`: … … 15 22 As with the regular Floodlight, `ant eclipse` allows it to work with eclipse and `ant javadoc` will produce javadocs for the code. 16 23 17 == = running in !FlowVisor mode ===24 == running in !FlowVisor mode == 18 25 19 26 To run: … … 24 31 This brings the controller up in "!FlowVisor mode," with two default slices containing the !LearningSwitch and Forwarding modules. The slice configurations are in config.json, found with the .properties file in [floodlight working directory]/src/main/resources/. 25 32 26 == = running as a regular controller ===33 == running as a regular controller == 27 34 28 35 Alternatively, since none of the original code base was modified, this version of Floodlight can be run as a normal v0.85 controller by replacing … … 36 43 in `src/main/resources/META-INF/services/net.floodlight.core.module.IFloodlightModule` and launching it without the -cf option. 37 44 38 == = creating a custom configuration file ===45 == creating a custom configuration file == 39 46 As of now, !FlowVisor is required to create custom configuration files. This takes four steps: 40 47