Changes between Version 28 and Version 29 of GENIExperimenter/ExperimentExample-stitching


Ignore:
Timestamp:
07/18/13 14:10:49 (11 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/ExperimentExample-stitching

    v28 v29  
    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 aggregate, this example shows a simple stitching scenario with one server VM in the GPO InstaGENI rack and one VM client in the Utah InstaGENI rack that are connected with a link.  The server-gpo host is configured to be 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 aggregate, this example shows a simple stitching scenario with one server VM in the GPO InstaGENI rack and one VM client in the Utah InstaGENI rack that are connected with a link.  The server-gpo host is configured to be 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
    … …  
    383383[[Image(web-server-iperf.jpg)]]
    384384
    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 
    387 Now we start the PingPlus experiment, by logging into the ''client-utah'' determining its dataplane MAC address and then shutting down IP on that interface:
     385Before starting the !PingPlus portion of the experiment, verify that no information existing for !PingPlus by selecting the link ''' ''Layer 2 !PingPlus Statistics'' '''.
     386
     387Now 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:
    388388{{{
    389389$ ssh -p 30010  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.utah.geniracks.net
    … …  
    409409}}}
    410410
    411 Now on the server, shutdown IP on the dataplane interface and run PingPLus:
     411Now on the server, shutdown IP on the dataplane interface and run Layer 2 !PingPLus:
    412412{{{
    413413[lnevers@server-gpo ~]$ sudo /sbin/ifconfig eth3748 0
    … …  
    416416}}}
    417417
    418 Now go back to the web server and select the ''' ''Layer 2 PingPlus Statistics'' ''' link and you will find statistics:
     418Now go back to the web server and select the ''' ''Layer 2 !PingPlus Statistics'' ''' link and you will find statistics:
    419419
    420420[[Image(web-server-pingplus.jpg)]]
    … …  
    430430Now that the experiment is completed, we release all resources:
    431431{{{
    432 $ stitcher.py deletesliver ig-gpo-ig-utah                               
    433 08:33:23 INFO     stitcher: Loading config file /home/lnevers/.gcf/omni_config
    434 08:33:23 INFO     stitcher: Using control framework portal
    435 08:33:23 INFO     stitcher: Reading stitching slice ig-gpo-ig-utah aggregates from file ch\.geni\.net.ln-prj.ig-gpo-ig-utah-amlist.txt  <==(1)
    436 08:33:23 INFO     stitcher: Adding aggregate option https://boss.utah.geniracks.net:12369/protogeni/xmlrpc/am (urn:publicid:IDN+utah.geniracks.net+authority+cm) <==(2)
    437 08:33:23 INFO     stitcher: Adding aggregate option https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am (urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm)<==(2)
    438 08:33:23 INFO     stitcher: Adding aggregate option https://www.emulab.net:12369/protogeni/xmlrpc/am (urn:publicid:IDN+emulab.net+authority+cm)                 <==(2)
    439 08:33:23 INFO     stitcher: Adding aggregate option http://geni-am.net.internet2.edu:12346 (urn:publicid:IDN+ion.internet2.edu+authority+am)                    <==(2)
    440 08:33:23 INFO     omni: Loading config file /home/lnevers/.gcf/omni_config
    441 08:33:23 INFO     omni: Using control framework portal
    442 08:33:24 INFO     omni: Slice urn:publicid:IDN+ch.geni.net:ln-prj+slice+ig-gpo-ig-utah expires on 2013-07-25 00:00:00 UTC
    443 08:34:20 INFO     omni:  (PG log url - look here for details on any failures: https://boss.utah.geniracks.net/spewlogfile.php3?logfile=639d88975aaa36cc97fe2a95a9e359f1)
    444 08:34:20 INFO     omni: Deleted sliver urn:publicid:IDN+ch.geni.net:ln-prj+slice+ig-gpo-ig-utah on unspecified_AM_URN at https://boss.utah.geniracks.net:12369/protogeni/xmlrpc/am
    445 08:35:04 INFO     omni:  (PG log url - look here for details on any failures: https://www.emulab.net/spewlogfile.php3?logfile=d87f3ca663ce1c55aae1537de2563458)
    446 08:35:04 INFO     omni: Deleted sliver urn:publicid:IDN+ch.geni.net:ln-prj+slice+ig-gpo-ig-utah on unspecified_AM_URN++ at https://www.emulab.net:12369/protogeni/xmlrpc/am
    447 08:35:09 INFO     omni: Deleted sliver urn:publicid:IDN+ch.geni.net:ln-prj+slice+ig-gpo-ig-utah on unspecified_AM_URN+++ at http://geni-am.net.internet2.edu:12346
    448 08:36:00 INFO     omni:  (PG log url - look here for details on any failures: https://boss.instageni.gpolab.bbn.com/spewlogfile.php3?logfile=aa5267b3bd8b1bff2a67f4354efdce38)
    449 08:36:00 INFO     omni: Deleted sliver urn:publicid:IDN+ch.geni.net:ln-prj+slice+ig-gpo-ig-utah on unspecified_AM_URN+ at https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am
    450 Deleted slivers on 4 out of a possible 4 aggregates  <==(3)
    451 }}}
    452 
    453  (1) Stitcher.py uses the files '' ch\.geni\.net.ln-prj.ig-gpo-ig-utah-amlist.txt'' which has the AM list associated with the slice. Note, that is this file does not exist in the current working directory, stitcher.py will try to delete the sliver at all know aggregates, but you will still have to delete the sliver manually at the Internet2/ION aggregate (http://geni-am.net.internet2.edu:12346) [[BR]]
    454  (2) List of aggregates where the sliver will be deleted. [[BR]]
    455  (3) Sliver has been deletes and compute and network resources are released at all aggregates. [[BR]]
     432$ stitcher.py deletesliver gpo2utah
     43314:06:49 INFO     stitcher: Loading config file /home/lnevers/.gcf/omni_config
     43414:06:49 INFO     stitcher: Using control framework portal
     43514:06:49 INFO     stitcher: Reading stitching slice gpo2utah aggregates from file ch\.geni\.net.ln-prj.gpo2utah-amlist.txt
     43614:06:49 INFO     stitcher: Adding aggregate option https://boss.utah.geniracks.net:12369/protogeni/xmlrpc/am (urn:publicid:IDN+utah.geniracks.net+authority+cm)
     43714:06:49 INFO     stitcher: Adding aggregate option https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am (urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm)
     43814:06:49 INFO     stitcher: Adding aggregate option https://www.emulab.net:12369/protogeni/xmlrpc/am (urn:publicid:IDN+emulab.net+authority+cm)
     43914:06:49 INFO     stitcher: Adding aggregate option http://geni-am.net.internet2.edu:12346 (urn:publicid:IDN+ion.internet2.edu+authority+am)
     44014:06:49 INFO     omni: Loading config file /home/lnevers/.gcf/omni_config
     44114:06:49 INFO     omni: Using control framework portal
     44214:06:50 INFO     omni: Slice urn:publicid:IDN+ch.geni.net:ln-prj+slice+gpo2utah expires on 2013-07-25 14:41:19 UTC
     44314:07:42 INFO     omni:  (PG log url - look here for details on any failures: https://boss.utah.geniracks.net/spewlogfile.php3?logfile=e3d387c4d5ad58f9b889a2c7790b0ed0)
     44414:07:42 INFO     omni: Deleted sliver urn:publicid:IDN+ch.geni.net:ln-prj+slice+gpo2utah on unspecified_AM_URN at https://boss.utah.geniracks.net:12369/protogeni/xmlrpc/am
     44514:09:20 INFO     omni:  (PG log url - look here for details on any failures: https://www.emulab.net/spewlogfile.php3?logfile=1bb4c8c04af55227d54b5e21419ccdd3)
     44614:09:20 INFO     omni: Deleted sliver urn:publicid:IDN+ch.geni.net:ln-prj+slice+gpo2utah on unspecified_AM_URN++ at https://www.emulab.net:12369/protogeni/xmlrpc/am
     44714:09:25 INFO     omni: Deleted sliver urn:publicid:IDN+ch.geni.net:ln-prj+slice+gpo2utah on unspecified_AM_URN+++ at http://geni-am.net.internet2.edu:12346
     44814:10:21 INFO     omni:  (PG log url - look here for details on any failures: https://boss.instageni.gpolab.bbn.com/spewlogfile.php3?logfile=65c7e0135a681d30e9f4ac46c088a5d8)
     44914:10:21 INFO     omni: Deleted sliver urn:publicid:IDN+ch.geni.net:ln-prj+slice+gpo2utah on unspecified_AM_URN+ at https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am
     450Deleted slivers on 4 out of a possible 4 aggregates
     451$
     452}}}
     453
     454Stitcher.py uses the files '' ch\.geni\.net.ln-prj.gpo2utah-amlist.txt'' which has the AM list associated with the slice. Note, that is this file does not exist in the current working directory, stitcher.py will try to delete the sliver at all know aggregates, but you will still have to delete the sliver manually at the Internet2/ION aggregate (http://geni-am.net.internet2.edu:12346).   Now the sliver has been deleted and compute and network resources are released at all aggregates.
    456455
    457456== Additional Stitching Scenarios ==
    … …  
    472471  - stitch-triangle.rspec - triangle topology (Utah PG<=>Utah KY<=> GPO IG <==> Utah PG)
    473472
    474 
    475 If additional help is needed please contact [mailto:help@geni.net]
     473If additional help is needed please contact [mailto:help@geni.net].
    476474