Changes between Version 14 and Version 15 of PhoebusExperimentGEMINI


Ignore:
Timestamp:
03/20/13 17:47:52 (7 years ago)
Author:
kissel@cis.udel.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PhoebusExperimentGEMINI

    v14 v15  
    22
    33== 1. Goals ==
    4 
     4 * Configure the "User Workspace" VM
     5 * Start an InstaGENI slice
     6 * Modify the request RSpec to include experiment-specific functions
     7 * Use Omni to create slivers at the chosen aggregates
     8 * Use Flack to view and modify the experiment properties as well as view slice status
     9 * Instrument the slice with GEMINI and configure some measurements using the GENI Desktop
     10 * Configure nodes using the command line to setup the experiment
     11 * Run an experiment using scripts to control the node interface properties
     12 * View results and explore the GEMINI services
     13 
    514== 2. Experiment Overview ==
    615
     16This custom experiment will make use of a WAN accelerator service called Phoebus.  Phoebus can help transfer performance of TCP flows over long-distance, or "challeneged", network environments through path segmentation, protocol adaptation, and automatic protocol tuning. Phoebus Gateways (PGs) are typically installed on nodes bordering WAN link(s), segmenting the WAN path from the edge networks (e.g., campus or data centers).  This experiment will create a simple 4-node topology over which to test the operation of Phoebus when used with a common network benchmark.  To simulate WAN latencies and edge loss, we will use the netem (Network Emulator) module in Linux to modify how packates are handled across the experimental topology.  GEMINI will be used to verify connectivity and to collect some performance data.
     17
    718[[Image(phoebus_exp.PNG)]]
     19
     20The image above shows the topology we will create on InstaGENI.  We will make some assumptions about addresses assigned to each interface to help with the consistency of this tutorial.
     21
     22client0  : 10.10.1.1
     23gateway0 : 10.10.1.2 and 192.168.1.1
     24gateway1 : 192.168.1.2 and 10.10.2.2
     25client0  : 10.10.2.1
     26
     27This IP assignment will give us 3 distinct subnets over which to send traffic.  10.10.1.0/24 (edge 0), 192.168.1.0/24 (WAN), and 10.10.2.0/24 (edge 1)  Host routing will be necessary to allow IP fowarding across each subnet.
    828
    929== 3. Setting up your user environment ==