Changes between Version 21 and Version 22 of GENIExperimenter/ExperimentExample-stitching


Ignore:
Timestamp:
07/16/13 14:32:37 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample-stitching

    v21 v22  
    7272
    7373We will now use the new Omni tool named ''stitcher.py'' to set up a stitched topology between the two nodes. The ''stitcher.py'' tool deliver:
    74  - Simpler experiment set-up. ''Stitcher.py creates slivers at all aggregates including network stitching path.
     74 - Simpler experiment set-up. ''Stitcher.py'' creates slivers at all aggregates including network stitching path.
    7575 - Stitcher.py parses RSpec to determine all compute resource aggregates from your RSpec. No longer need to specify “-a aggregateName”.
    7676 - ''Stitcher.py'' uses the MAX Stitching Computation Service (SCS) to determine VLAN path needed for your experiment.
     
    9797}}}
    9898
    99 A sliver that included a stitched VLAN path can be created using the ''stitcher.py'' script. There is no need to specify the ''-a'' aggregate option, aggregates are determined from the RSpec and need not be specified. Also note that a file is created in the directory where the sliver is created that capture the aggregates associated with the slice.  Following is the stitcher operation that setup up all slivers:
     99Now, we create slivers using the ''stitcher.py'' script. 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 sliver is created that capture the aggregates associated with the slice.  Following is the stitcher operation that setup up all slivers:
    100100{{{
    101101$ stitcher.py createsliver ig-gpo-ig-utah stitch-ig-gpo-ig-utah.rspec -o
     
    140140 (4) Request at Internet2/ION waits for DCN circuits. If this request fails, stitcher.py will try again after 600 seconds. [[BR]]
    141141 (5) A combined manifest rspec is assembled by the stitcher.py to show all aggregates and VLANs used in the sliver.
     142
     143The above stitched scenario sliver creation brings together various areas that are normally involved in the manual setup of an equivalent circuit:
     144 - Switch configuration at rack endpoints.
     145 - Static circuit to get to ION
     146 - ION/OSCARS creation of a dynamic circuit with VLAN translation
     147 - A static connection over UEN
     148 - A routed connection across PG Utah
     149 - A dynamic circuit and then a fixed circuit to Utah InstaGENI.
    142150
    143151The combined manifest [http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/ExperimentExample-stitching/ig-gpo-ig-utah-manifest-rspec-stitching-combined.xml ig-gpo-ig-utah-manifest-rspec-stitching-combined.xml] is attached. Below is part of the ig-gpo-ig-utah-manifest-rspec-stitching-combined.xml file showing the stitching manifest that includes all hops hops along the stitched VLAN path:
     
    315323  - <hop id="6"> is for the Utah InstaGENI switch (procurve2:1.19) and uses VLAN 874
    316324
     325
    317326At this point the experiment has been set up and you may determine the login information at each compute aggregate:
    318327{{{