Changes between Version 31 and Version 32 of GENIExperimenter/ExperimentExample-stitching


Ignore:
Timestamp:
07/20/13 22:58:25 (6 years ago)
Author:
hdempsey@bbn.com
Comment:

typos/wording fixes

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample-stitching

    v31 v32  
    77
    88
    9 The experiment uses [http://groups.geni.net/geni/wiki/GeniClearinghouse GENI Clearinghouse] credentials with the new omni tool named ''stitcher.py''.  GENI network stitching does not require any special configuration. If you haven't already configured Omni, please follow [http://trac.gpolab.bbn.com/gcf/wiki/OmniConfigure/Automatic these configuration instructions]. If you need further assistance, please contact [mailto:help@geni.net].
     9The experiment uses [http://groups.geni.net/geni/wiki/GeniClearinghouse GENI Clearinghouse] credentials with the new Omni tool named ''stitcher.py''.  GENI network stitching does not require any special configuration. If you haven't already configured Omni, please follow [http://trac.gpolab.bbn.com/gcf/wiki/OmniConfigure/Automatic these configuration instructions]. If you need further assistance, please contact [mailto:help@geni.net].
    1010
    1111== 1. Design the Stitching Experiment ==
     
    1414<img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/design.png?format=raw" alt="Design/Setup"></a>
    1515}}}
    16 At this time GENI network stitching is supported by several aggregates. This example shows a simple stitching scenario with one server VM in the GPO InstaGENI rack and one client VM in the Utah InstaGENI rack.  The server-gpo host is configured as a Web, Iperf and !PingPlus server; it also has a routable IP address that is used to access the web server and display results for all traffic types.
     16At this time, GENI network stitching is supported by several aggregates. This example shows a simple stitching scenario with one server VM in the GPO InstaGENI rack and one client VM in the Utah InstaGENI rack.  The server-gpo host is configured as a Web, Iperf and !PingPlus server; it also has a routable IP address that is used to access the web server and display results for all traffic types.
    1717
    1818We define an RSpec with 2 nodes and one link between them. The link ''' ''must'' ''' specify the 2 aggregates that are the
     
    5858</rspec>
    5959}}}
    60 In the above RSpec, the link information in the ''component_manager name'' is used by the ''stitcher.py'' to contact the GENI Stitching Computation Service and determine a path between the end-point hosts.
     60In the above RSpec, ''stitcher.py''uses the link information in the ''component_manager name'' to contact the GENI Stitching Computation Service (SCS) and determine a path between the end-point hosts.
    6161
    6262
     
    6767}}}
    6868
    69 We now use the ''stitcher.py'' to set up a stitched topology between the two nodes. The ''stitcher.py'' tool deliver:
    70  - Simpler experiment set-up, it creates slivers at all aggregates including network stitching path.
    71  - Stitcher.py parses RSpec to determine all compute resource aggregates from your RSpec. No longer need to specify “-a aggregateName”.
    72  - ''Stitcher.py'' uses the MAX Stitching Computation Service (SCS) to determine VLAN path needed for your experiment.
    73  - VLANs are a scarce commodity, and failures can happen. ''Stitcher.py'' will re-try to create sliver when failures occur.
    74 
    75 First create a slice for this experiment:
     69We now use ''stitcher.py'' to set up a stitched topology between the two nodes.
     70 - ''Stitcher.py'' simplifies experiment set-up because it creates slivers at all aggregates, including the network stitching path.
     71 - ''Stitcher.py'' determines all your experiment compute resource aggregates from your RSpec. (You no longer need to enter “-a aggregateName”.)
     72 - ''Stitcher.py'' uses the MAX Stitching Computation Service (SCS) to determine VLAN paths needed for your experiment.
     73 - VLANs are a scarce commodity, and failures can happen. ''Stitcher.py'' will retry if it fails to create a sliver at an aggregate.
     74
     75We first create a slice for this experiment:
    7676{{{
    7777$ omni.py createslice gpo2utah
     
    9393}}}
    9494
    95 Now, we create all slivers using the ''stitcher.py''. Remember there is no need to specify the ''-a'' aggregate option, aggregates are determined from the RSpec and need not be specified. Note that a file is created in the directory where the slivers are created that capture the aggregates associated with the slice.  Following is the stitcher command used:
     95Next, we create all necessary slivers using ''stitcher.py''. (Remember there is no need to specify the ''-a'' aggregate option.)  The "stitcher.py'' tool records the aggregates associated with the slice in a file that it creates in the directory where you run the tool.  We type this command:
     96
    9697{{{
    9798$ stitcher.py createsliver gpo2utah stitch-ig-gpo-ig-utah.rspec -o