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


Ignore:
Timestamp:
07/20/13 23:14:48 (6 years ago)
Author:
hdempsey@bbn.com
Comment:

more typos and wording

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample-stitching

    v32 v33  
    5858</rspec>
    5959}}}
    60 In 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.
     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
     
    130130}}}
    131131
    132  (1) Sticher.py gets your slice credentials to make sure you have named a valid slice in which to create your circuit and then it runs rspeclint on the ''stitch-ig-gpo-ig-utah.rspec '' file, if rspeclint is found in your search path. [[BR]]
    133  (2) Sticher.py contacts the Stitching Computation Service (SCS) and returns the list of AMs that are needed to establish the stitching path in addition to the Internet2/ION aggregate.[[BR]]
    134  (3) Stitcher.py generates a request RSpec for each of the aggregates in the path to request both network and compute resources. [[BR]]
    135  (4) Creates sliver at each aggregate (path & end-points) [[BR]]
    136  (5) Request at Internet2/ION waits for DCN circuits. If this request fails, stitcher.py will try again after 600 seconds. [[BR]]
    137  (6) A combined manifest rspec is assembled by the stitcher.py to show all aggregates and VLANs used in the sliver.
     132 (1) ''Sticher.py'' gets your slice credentials to make sure you have named a valid slice in which to create your circuit, and then it runs rspeclint on the ''stitch-ig-gpo-ig-utah.rspec '' file, if rspeclint is found in your search path. [[BR]]
     133 (2) ''Sticher.py'' contacts the Stitching Computation Service (SCS) and returns the list of AMs that are needed to establish the stitching path, including the Internet2/ION aggregate.[[BR]]
     134 (3) ''Stitcher.py'' generates a request RSpec for each of the aggregates in the path to request both network and compute resources. [[BR]]
     135 (4) ''Stitcher.py'' creates sliver at each aggregate (path & end-points) [[BR]]
     136 (5) The request to Internet2/ION waits for DCN circuits to be created. If this request fails, ''stitcher.py'' will try again after 600 seconds. [[BR]]
     137 (6) A combined manifest Rspec is assembled by ''stitcher.py'' to show all aggregates and VLANs used in the slice.
    138138
    139139The above stitched scenario sliver creation brings together various areas that are normally involved in the manual setup of an equivalent circuit:
    140140 - Switch configuration at rack endpoints
    141  - Static circuit to get to ION
     141 - Static circuit configuration to reach ION in the aggregate
    142142 - ION/OSCARS creation of a dynamic circuit with VLAN translation
    143143 - A static connection over UEN
     
    149149[[Image(IG-GPO-IG-Utah-tags.jpg)]]
    150150
    151 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:
     151Below is part of the ig-gpo-ig-utah-manifest-rspec-stitching-combined.xml file showing the stitching manifest that includes all hops along the stitched VLAN path:
    152152
    153153{{{
     
    325325
    326326
    327 At this point the experiment has been set up and you may determine the login information at each compute aggregate:
     327At this point the experiment has been set up, and you may determine the login information at each compute aggregate:
    328328{{{
    329329$ readyToLogin.py gpo2utah -a ig-gpo
     
    367367 (a) publically routable IP address is 192.1.242.150
    368368
    369 We can now connected to the web server to verify that iperf tests were run and that client completed wget operations:
     369We can now connect to the web server to verify that iperf tests were run and that the client completed wget operations:
    370370
    371371[[Image(web-server.jpg)]]
     
    373373[[BR]]
    374374
    375 Select the ''' ''Web Server Statistics'' ''' link and verify that wget was sucessfull for images:
     375Select the ''' ''Web Server Statistics'' ''' link, and verify that wget was sucessfull for images:
    376376
    377377[[Image(web-server-stats.jpg)]]
     
    385385Before starting the !PingPlus portion of the experiment, verify that no information existing for !PingPlus by selecting the link ''' ''Layer 2 !PingPlus Statistics'' '''.
    386386
    387 Now we start the Layer 2 !PingPlus experiment, by logging into the ''client-utah'' determining its dataplane MAC address and then shutting down IP on that interface:
     387Now we start the Layer 2 !PingPlus experiment, by logging into ''client-utah,'' determining its dataplane MAC address and then shutting down IP on that interface:
    388388{{{
    389389$ ssh -p 30010  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.utah.geniracks.net
     
    416416}}}
    417417
    418 Now go back to the web server and select the ''' ''Layer 2 !PingPlus Statistics'' ''' link and you will find statistics:
     418Now, we go back to the web server and select the ''' ''Layer 2 !PingPlus Statistics'' ''' link.  You will find new statistics:
    419419
    420420[[Image(web-server-pingplus.jpg)]]
     
    456456== Additional Stitching Scenarios ==
    457457
    458 Additional stitching scenarios have been tested and some example request RSpec can be used as a reference at
     458Additional stitching scenarios have been tested and some example request RSpecs can be used as a reference at
    459459this [http://groups.geni.net/geni/browser/trunk/stitch-examples location]:
    460460