Changes between Version 32 and Version 33 of GENIExperimenter/ExperimentExample-stitching
- Timestamp:
- 07/20/13 23:14:48 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/ExperimentExample-stitching
v32 v33 58 58 </rspec> 59 59 }}} 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.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. 61 61 62 62 … … 130 130 }}} 131 131 132 (1) Sticher.py gets your slice credentials to make sure you have named a valid slice in which to create your circuitand 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 tothe Internet2/ION aggregate.[[BR]]134 (3) Stitcher.pygenerates 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.pywill 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. 138 138 139 139 The above stitched scenario sliver creation brings together various areas that are normally involved in the manual setup of an equivalent circuit: 140 140 - Switch configuration at rack endpoints 141 - Static circuit to get to ION141 - Static circuit configuration to reach ION in the aggregate 142 142 - ION/OSCARS creation of a dynamic circuit with VLAN translation 143 143 - A static connection over UEN … … 149 149 [[Image(IG-GPO-IG-Utah-tags.jpg)]] 150 150 151 Below is part of the ig-gpo-ig-utah-manifest-rspec-stitching-combined.xml file showing the stitching manifest that includes all hops hopsalong the stitched VLAN path:151 Below 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: 152 152 153 153 {{{ … … 325 325 326 326 327 At this point the experiment has been set up and you may determine the login information at each compute aggregate:327 At this point the experiment has been set up, and you may determine the login information at each compute aggregate: 328 328 {{{ 329 329 $ readyToLogin.py gpo2utah -a ig-gpo … … 367 367 (a) publically routable IP address is 192.1.242.150 368 368 369 We can now connect ed to the web server to verify that iperf tests were run and thatclient completed wget operations:369 We can now connect to the web server to verify that iperf tests were run and that the client completed wget operations: 370 370 371 371 [[Image(web-server.jpg)]] … … 373 373 [[BR]] 374 374 375 Select the ''' ''Web Server Statistics'' ''' link and verify that wget was sucessfull for images:375 Select the ''' ''Web Server Statistics'' ''' link, and verify that wget was sucessfull for images: 376 376 377 377 [[Image(web-server-stats.jpg)]] … … 385 385 Before starting the !PingPlus portion of the experiment, verify that no information existing for !PingPlus by selecting the link ''' ''Layer 2 !PingPlus Statistics'' '''. 386 386 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:387 Now 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: 388 388 {{{ 389 389 $ ssh -p 30010 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.utah.geniracks.net … … 416 416 }}} 417 417 418 Now go back to the web server and select the ''' ''Layer 2 !PingPlus Statistics'' ''' link and you will findstatistics:418 Now, we go back to the web server and select the ''' ''Layer 2 !PingPlus Statistics'' ''' link. You will find new statistics: 419 419 420 420 [[Image(web-server-pingplus.jpg)]] … … 456 456 == Additional Stitching Scenarios == 457 457 458 Additional stitching scenarios have been tested and some example request RSpec can be used as a reference at458 Additional stitching scenarios have been tested and some example request RSpecs can be used as a reference at 459 459 this [http://groups.geni.net/geni/browser/trunk/stitch-examples location]: 460 460