Changes between Version 14 and Version 15 of GeniDesktop/Summer_Camp_2015


Ignore:
Timestamp:
05/21/15 15:55:08 (9 years ago)
Author:
fei@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniDesktop/Summer_Camp_2015

    v14 v15  
    55[[BR]]
    66== 1. Introduction ==
    7 [[BR]]
    87
    98This tutorial consists of three parts:
     
    1312 * Flow Installation and Monitoring in GENI Desktop
    1413
    15 :: === Important URLs ===
     14=== Important URLs ===
    1615
    1716||  To use the GENI Desktop, go to ||   [https://genidesktop.netlab.uky.edu https://genidesktop.netlab.uky.edu] ||
     
    2221[[BR]]
    2322== 2. Basic GENI Desktop Operations ==
    24 [[BR]]
    2523
    2624=== Part I: Setup ===
    2725     *  Follow the instructions of the general GENI Desktop tutorial to create a topology with three Xen nodes as shown below.
    2826
    29 [[Image(basic_topo2.png, 500px)]]
     27[[Image(basic_topo3.png, 500px)]]
    3028
    3129=== Part II: Excute ===
     
    7977
    8078[[BR]]
    81 == 2. Introduction to OpenFlow ==
    82 [[BR]]
     79== 3. Introduction to OpenFlow ==
    8380
    8481A brief introduction to OpenFlow can be found at [   ]
     
    8683
    8784[[BR]]
    88 == 3. Flow Installation and Monitoring ==
    89 [[BR]]
     85== 4. Flow Installation and Monitoring ==
     86
     87To use these functions, go to the new URL at
     88[http://genidesktop.netlab.uy.edu/wild http://genidesktop.netlab.uky.edu/wild]
    9089
    9190=== Part I: Setup ===
     
    9897        * Click on "Site X" where X is a number. Choose any InstaGENI rack from the drop-down menu for Aggregate.
    9998        * Click on "Allocate resources using this RSPEC"
     99
    100100      * Step 2: Create the experiment slice with a topology consisting of of three OVS nodes and two Xen nodes as shown below.
    101101        * Drag "GD OVS" icon node to the canvas for the three OVS nodes.
     
    104104        * Allocate the resources.
    105105
    106 [[Image(aag_topo2.xcf, 500px)]]
    107 
     106[[Image(aag_topo3.png, 500px)]]
    108107
    109108=== Part II: Execute ===
    110109    * Step 1: Figure out the public IP address of the controller after the controller slice is created.
    111     * Step 2: Run an initialization script "  " on all OVS nodes in the experiment.
     110You can do "nslookup full_name_of_the_node" on a linux terminal. Or you can follow these steps.
     111      * Highlight the controller node.
     112      * Click on "Command" module.
     113      * Click on "set selection"
     114      * Type "ifconfig eth0" in the text box and click on "Run Command"
     115      * Write down the IP address of the controller.
     116      * You may test the controller's web GUI by going to http://IP_address:8080/.
     117
     118    * Step 2: Run an initialization script on all OVS nodes in the experiment.
     119      * Open up the slice containing the topology.
     120      * Click on the "Command" module.
     121      * Highlight all OVS nodes and click on the "Set Selection" button.
     122      * Type the following command in the text box "sudo python /local/ovscmd.py -i IP_address", where IP_address is the controller's IP address you found in Step 1.
     123      * Log into the controller's web GUI by going to http://IP_address:8080/ and check all OVS nodes were added.
     124     
    112125    * Step 3: Install, list, and delete flows on the experiment
    113       * Click on "Flow Install". Fill in the IP address of the controller.
    114       * Select a path in the topology and highlight it.
    115       * Fill in the form to set the flow.
    116       * You can also try list and delete flows.
     126      * Click on "Flow Install" Module. Fill in the IP address of the controller.
     127      * Check "Add ARP processing", "Add Subnet Gateways", and "No routing rules", then click on
     128"Initialize"
     129      * Select a path in the topology and highlight both nodes and links on the path.
     130      * Fill in the form to set the flow. You can choose between TCP and UDP, between one-way or two-way
     131paths, and the port numbers at the nodes. The selection between "Src" and "Dst" is only effective for
     132one-way path.
     133      * Click on "Install Flow".
     134      * You can also try "Refresh List" to list the current flows or "Delete Flow" to delete a flow from the list.
     135
    117136    * Step 4: Monitor per-flow performance
    118       * Click on "Flow Monitor".
    119       * Choose a flow to monitor at a selected node.
     137      * Click on "Flow Monitor" module. Fill in the IP address of the controller.
     138      * Check "All Nodes" and click on "Query Statistics".
     139      * Choose a flow to monitor at a selected node by going to a node and finding the flow you want to monitor.
     140Then click on "Packets" or "Bytes". A graph of live measurement will show.
    120141      * Send traffic (ping, iperf, etc) from end host A to end host B in the experiment.
    121142