Changes between Version 7 and Version 8 of Layer1Transport/Install


Ignore:
Timestamp:
07/31/13 16:07:53 (6 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Layer1Transport/Install

    v7 v8  
    11[[PageOutline]]
    22
    3 = Introduction =
     3= GENI layer1transport service installation =
     4
     5== Introduction ==
    46This page describes how to install the layer1transport service.
    57
    6 = Variables =
     8== Variables ==
    79|| '''Name'''                || '''Description'''             || '''Default Values''' || '''Files that use these values''' ||
    810|| <version>                 || Version of layer1transport    ||                      ||                                   ||
     
    1113|| <of_port>                 || OF controller port for FL     || 11750                || properties file                   ||
    1214
    13 = Prerequisites =
     15== Prerequisites ==
    1416
    15 == 1. Create openflow user ==
     17=== 1. Create openflow user ===
    1618Create a user named openflow on the system to run this service. 
    1719
    18 == 2. Install Floodlight 0.90 ==
     20=== 2. Install Floodlight 0.90 ===
    1921Floodlight installation instructions can be found at http://docs.projectfloodlight.org/display/floodlightcontroller/Installation+Guide, and instructions for obtaining the source code can be obtained at http://www.projectfloodlight.org/download/.
    2022
    21 = Installation Instructions =
     23== Installation Instructions ==
    2224These are instructions to install the layer1transport service.  These instructions were created and tested using an Ubuntu 10.04 system.
    2325
    24 == 1. Obtain the software ==
     26=== 1. Obtain the software ===
    2527The software for the layer1transport service can be downloaded at http://www.gpolab.bbn.com/local-sw/.  Download the tarball, and place it in the openflow user's home directory.
    2628
    27 == 2. Unpack the tarball ==
     29=== 2. Unpack the tarball ===
    2830Unpack the tarball and rename the top level directory
    2931{{{
     
    3335}}}
    3436
    35 == 3. Install curl ==
     37=== 3. Install curl ===
    3638Make sure that the system has curl installed on it.
    3739
    38 == 4. Drop a floodlight jar file in place ==
     40=== 4. Drop a floodlight jar file in place ===
    3941Take the Floodlight 0.9 jar file that you created in the prerequisites section and do the following:
    4042{{{
     
    4345}}}
    4446
    45 == 5. (optional) Update properties file ==
     47=== 5. (optional) Update properties file ===
    4648If you need to change the <of_port> and/or the <rest_port> that the Floodlight instance binds to, then the modify following lines in `/home/openflow/floodlight/config/layer1transport.properties`:
    4749{{{
     
    5052}}}
    5153
    52 == 6. (optional) Update logback config ==
     54=== 6. (optional) Update logback config ===
    5355There are three reference logback configurations distributed with this software:
    5456 * `/home/openflow/floodlight/conf/logback_file.xml`: logs floodlight messages to `/var/log/floodlight.log`
     
    5860The layer1transport service uses the file `/home/openflow/floodlight/conf/logback.xml`, which by default is a symlink that points to `logback_file.xml`.  If you want to change which configuration you use, or if you want to use an alternate configuration, make modifications now.
    5961
    60 == 7. Create flows files ==
     62=== 7. Create flows files ===
    6163You will need to create files that define that flows that should be managed by the SFP module in floodlight.  The flows files '''must''' have a `.json` file extension in order to work with this service.  The API and the data format are defined in [http://docs.projectfloodlight.org/display/floodlightcontroller/Static+Flow+Pusher+API+%28New%29 the SFP documentation].  Defining the proper flows requires an understanding of your switch platforms, and where administrative flows are needed within the network.  Please coordinate with us if you would like help defining these, or if you would like us to sanity check.  One you have defined the flows in a set of files, place the files under `/home/openflow/floodlight/flows.d/`.  Two files are provided as a reference.
    6264
     
    6769}}}
    6870
    69 == 8. Install init.d script ==
     71=== 8. Install init.d script ===
    7072Move the init.d script into place and set the appropriate permissions:
    7173{{{
     
    7981}}}
    8082
    81 == 9. Start the service ==
     83=== 9. Start the service ===
    8284Start the script if it isn't running already:
    8385{{{
     
    9092}}}
    9193
    92 == 10. Set the service to start on boot ==
     94=== 10. Set the service to start on boot ===
    9395Configure the host, either through an OS-specific tool or through a configuration management system, to have the layer1transport service to start up at boot time.
    9496
    95 == 11. Poke holes in firewalls as needed ==
     97=== 11. Poke holes in firewalls as needed ===
    9698If you need to poke a hole in the firewall (either in the network or on the controller host itself) for the switch to reach <of_port> on the controller, do this now.
    9799
    98 == 12. Point switch instances at new controller ==
     100=== 12. Point switch instances at new controller ===
    99101For each OF instance that needs to have flows installed, point the instance at administrative Floodlight instance that you stood up.  How this gets done will depend on the switch platform.  You will point the switch at the <of_port>.