Changes between Version 6 and Version 7 of Layer1Transport/Install


Ignore:
Timestamp:
07/31/13 15:46:14 (11 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Layer1Transport/Install

    v6 v7  
    2222These are instructions to install the layer1transport service.  These instructions were created and tested using an Ubuntu 10.04 system.
    2323
    24 == 2. Obtain the software ==
     24== 1. Obtain the software ==
    2525The 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.
    2626
    27 == 3. Unpack the tarball ==
     27== 2. Unpack the tarball ==
    2828Unpack the tarball and rename the top level directory
    2929{{{
     
    3333}}}
    3434
    35 == 4. Install curl ==
     35== 3. Install curl ==
    3636Make sure that the system has curl installed on it.
    3737
    38 == 5. Drop a floodlight jar file in place ==
     38== 4. Drop a floodlight jar file in place ==
    3939Take the Floodlight 0.9 jar file that you created in the prerequisites section and do the following:
    4040{{{
     
    4343}}}
    4444
    45 == 6. (optional) Update properties file ==
     45== 5. (optional) Update properties file ==
    4646If 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`:
    4747{{{
     
    5050}}}
    5151
    52 == 7. (optional) Update logback config ==
     52== 6. (optional) Update logback config ==
    5353There are three reference logback configurations distributed with this software:
    5454 * `/home/openflow/floodlight/conf/logback_file.xml`: logs floodlight messages to `/var/log/floodlight.log`
     
    5858The 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.
    5959
    60 == 8. Create flows files ==
     60== 7. Create flows files ==
    6161You 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.
    6262
     
    6767}}}
    6868
    69 == 9. Install init.d script ==
     69== 8. Install init.d script ==
    7070Move the init.d script into place and set the appropriate permissions:
    7171{{{
     
    7979}}}
    8080
    81 == 10. Start the service ==
     81== 9. Start the service ==
    8282Start the script if it isn't running already:
    8383{{{
     
    9090}}}
    9191
    92 == 11. Set the service to start on boot ==
     92== 10. Set the service to start on boot ==
    9393Configure 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.
    9494
    95 == 12. Poke holes in firewalls as needed ==
     95== 11. Poke holes in firewalls as needed ==
    9696If 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.
    9797
    98 == 13. Point switch instances at new controller ==
     98== 12. Point switch instances at new controller ==
    9999For 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>.