Changes between Version 13 and Version 14 of GEC21Agenda/ChoiceNet/gt_tool


Ignore:
Timestamp:
10/16/14 22:08:23 (4 years ago)
Author:
griff@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC21Agenda/ChoiceNet/gt_tool

    v13 v14  
    22
    33
    4 At this point we will start configure and Installing Choicenet code onto the nodes in your slice.
     4At this point we will installing the !ChoiceNet software onto the nodes in your slice, configure the software, and start it
     5running.  Execute the list of commands below on your global node GN0:
    56
    6 Follow the list of commands below to set up the CHOICENET FRAMEWORK
     7 - '''Replace the <MANIFEST_FILENAME> and <GENI USERNAME> with the values shown to you during the pre-setup phase'''
    78
    8 '''Replace the <MANIFEST_FILENAME> and <GENI USERNAME> with the values shown to you during the pre-setup phase'''
    9 
    10 If you forgot to write down the MANIFEST_FILENAME, it will be ~/SLICENAME_manifest.xml (where SLICENAME is the name of your slice).
     9    * If you forgot to write down the MANIFEST_FILENAME, it will be ~/SLICENAME_manifest.xml (where SLICENAME is the name of your slice).
    1110
    1211
    13 Change into the choicenet bin directory
     12 1. Change into the choicenet bin directory where the !ChoiceNet software is located:
    1413{{{
    1514#!sh
     
    1817
    1918
    20 Run the configure to setup the necessary interfaces, routes and bridges
     19 1. Use the ''configure'' command to the getool to configure the slice with the addresses, interface, bridges, etc needed by
     20the !ChoiceNet services:
     21
    2122{{{
    2223#!sh
     
    2425}}}
    2526
    26 Now install the Choicenet code which includes Choicenet CLICK Implementation and the Choicenet SDN Implementation
     27 1. Now use the getool ''install'' command to install the !ChoiceNet software.
     28 which includes Choicenet CLICK Implementation and the Choicenet SDN Implementation
    2729{{{
    2830#!sh
    2931./getool -f <MANIFEST FILENAME> -l <GENI USERNAME> -i ~/.ssh/id_rsa install
    3032}}}
     33This command will take several minutes to run (10-15 minutes).  This is installing two different
     34network layer !ChoiceNet routing and forwarding services.  The following describes the two services
     35being installed:
     36   1. Source-routed Forwarding:
     37This !ChoiceNet forwarding service forwards packets based on the source-route contained in
     38the packet header.  Unlike existing IP source routing techniques, this forwarding service will
     39not forward a packet unless the packet also contains proof that the sender ''paid'' for the forwarding
     40service.  Each entry in the source-route not only identifies the next hop, but also provides a ''proof of purchase''
     41indicating that the sender paid for use of the next hop.  This proof will be checked at the next hop before the
     42packet is allowed to proceed forward.  Packets without proof are automatically dropped.
     43
     44Senders in this model contact a ''Path Service (PS)'' that discovers multiple paths between any two nodes.
     45The send application tells the PS what type of path is desired -- for example
     46a High Bandwidth (and presumably expensive) path, or a Low Bandwidth path (that may be substantially cheaper).
     47The sender also includes some form of payment in the request to the PS, who in turn formulates the best path
     48for the sender, and then returns the best path along with the ''proof of purchase'' needed to get packets through
     49each hop along the path.  Senders then include the path and proof of purchases for each router along the path
     50in the packet header which is examined by every router along the path.
     51
     52To implement this service, we install a '''Click Router'' in the linux kernel along with a click module that implements
     53our forwarding service.  As packets enter the router they are passed to our Click module to examine them and decide
     54whether to forward them or not.  We also need to install a '''Path Service (PS)'' that sending applications contact to
     55purchase paths.  The Click routers advertise their forwarding service to the PS which in turn computes the best
     56path (e.g., high bandwidth or low latency) and sells it to the sending application.  To avoid the need to write
     57an entirely new set of applications that are !ChoiceNet-aware, we instead wrote a '''wrapper library''' that  we can load
     58with existing IPv6 applications.  The wrapper library intercepts socket library calls from the application, consults a
     59local config file to determine what type of path is needed, purchases the appropriate path from the PS, and then begins
     60sending packets using the newly purchased path.
     61
     62
     63   1. Openflow-based Forwarding:
     64One forwarding service offers something akin to a
     65''source routed'' forwarding. 
    3166
    3267