Changes between Version 4 and Version 5 of GENIExperimenter/ExperimentExample-stitching


Ignore:
Timestamp:
07/15/13 22:11:18 (11 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/ExperimentExample-stitching

    v4 v5  
    11= GENI Network Stitching Example =
    22
    3 
    4 This page used gcf 2.4 preview 7 to show an example experiment that creates a network stitching path between the GPO InstaGENI and the Utah InstaGENI racks. The experiment uses [http://groups.geni.net/geni/wiki/GeniClearinghouse GENI Clearinghouse] credentials with the 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].
     3This page used gcf 2.4 preview 7 to show an example experiment that creates a network stitching path between the GPO InstaGENI and the Utah InstaGENI racks.
     4
     5
     6<<Insert Image>>
     7
     8The experiment uses [http://groups.geni.net/geni/wiki/GeniClearinghouse GENI Clearinghouse] credentials with the 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].
    59
    610== Design Experiment ==
    … …  
    1115}}}
    1216
    13 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, captured in the following Request RSpec:
    14 
    15 <<Insert Image>>
     17At 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 both a Web Server and an Iperf server, also a routable IP address is requested to access the web server. All this is captured in the request RSpec used for this experiment:
    1618
    1719Assemble a Request Rspec that includes one VM at each rack site:
    … …  
    10110321:29:34 WARNING  stitch.Aggregate: Slivers at PG Utah may not be requested initially for > 5 days. PG Utah slivers will expire earlier than at other aggregates - requested expiration being reset from 2013-07-25T00:00:00Z to 2013-07-21T01:09:34Z
    10210421:30:12 INFO     stitch.Aggregate: Allocation at <Aggregate urn:publicid:IDN+emulab.net+authority+cm> complete.
    103 21:30:12 INFO     stitch.Aggregate: Writing to '/tmp/ig-gpo-ig-utah-createsliver-request-11-utah-geniracks-net.xml'
     10521:30:12 INFO     stitch.Aggregate: Writing to '/tmp/ig-gpo-ig-utah-createsliver-request-11-utah-geniracks-net.xml'       <==(3)
    10410621:30:12 INFO     stitch.Aggregate:
    105107        Stitcher doing createsliver at https://boss.utah.geniracks.net:12369/protogeni/xmlrpc/am
    … …  
    11011221:30:56 ERROR    omni:  {'output': 'vlan tag for link not available', 'code': {'protogeni_error_log': 'urn:publicid:IDN+instageni.gpolab.bbn.com+log+f90141724ac70ca40144bd5b8775e40f', 'am_type': 'protogeni', 'geni_code': 1, 'am_code': 1, 'protogeni_error_url': 'https://boss.instageni.gpolab.bbn.com/spewlogfile.php3?logfile=f90141724ac70ca40144bd5b8775e40f'}, 'value': 0}
    11111321:31:41 INFO     stitch.Aggregate: Allocation at <Aggregate urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm> complete.
    112 21:31:41 INFO     stitch.Aggregate: Writing to '/tmp/ig-gpo-ig-utah-createsliver-request-11-ion-internet2-edu.xml'       <==(3)
     11421:31:41 INFO     stitch.Aggregate: Writing to '/tmp/ig-gpo-ig-utah-createsliver-request-11-ion-internet2-edu.xml'       <==(5)
    11311521:31:41 INFO     stitch.Aggregate:
    114         Stitcher doing createsliver at http://geni-am.net.internet2.edu:12346
     116        Stitcher doing createsliver at http://geni-am.net.internet2.edu:12346    <==(6)
    11511721:32:25 INFO     stitch.Aggregate: DCN AM <Aggregate urn:publicid:IDN+ion.internet2.edu+authority+am>: must wait for status ready....
    11611821:32:25 INFO     stitch.Aggregate: Pause to let circuit become ready...
    … …  
    123125}}}
    124126
    125  (1) Sticher.py run rspeclint on the  stitch-ig-gpo-ig-utah.rspec file. [[BR]]
    126  (2) Sticher.py contact the Stitching Computation Service (SCS) and returns the list of AMs that are needed to stitch a path. [[BR]]
    127  (3) Stitcher.py generates a request RSpec for each of the aggregates in the path. [[BR]]
     127 (1) Sticher.py runs rspeclint on the  stitch-ig-gpo-ig-utah.rspec file. [[BR]]
     128 (2) Sticher.py contacts the Stitching Computation Service (SCS) and returns the list of AMs that are needed to establish the stitching path.[[BR]]
     129 (3) Stitcher.py generates a request RSpec for each of the aggregates in the path including ION/Internet2. [[BR]]
    128130 (4) Second attempt at GPO InstaGENI, initial request failed because the requested VLAN was not available. [[BR]]
    129 
    130 
    131 
    132 = Finish Experiment ==
     131 (5) Request at Internet2/ION waits for DCN circuits. If this request fails, stitcher.py will try again after 600 seconds. [[BR]]
     132
     133At this point the experiment has been set up and you may determine the login information at each compute aggregate:
     134{{{
     135$ readyToLogin.py ig-gpo-ig-utah -a ig-gpo       
     136...
     137server-gpo's geni_status is: ready (am_status:ready)
     138User lnevers logs in to server-gpo using:
     139
     140        ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pcvm2-14.instageni.gpolab.bbn.com
     141
     142$ readyToLogin.py ig-gpo-ig-utah -a ig-utah
     143
     144client-utah's geni_status is: ready (am_status:ready)
     145User lnevers logs in to client-utah using:
     146        ssh -p 30522  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc5.utah.geniracks.net
     147}}}
     148
     149We will use the ''server-gpo'' login to determine the routable IP address that was requested for the Web Server:
     150{{{
     151$ ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pcvm2-14.instageni.gpolab.bbn.com
     152Warning: Permanently added 'pcvm2-14.instageni.gpolab.bbn.com,192.1.242.151' (RSA) to the list of known hosts.
     153[lnevers@server-gpo ~]$ /sbin/ifconfig
     154eth999    Link encap:Ethernet  HWaddr 02:94:6D:BC:36:DC 
     155          inet addr:192.1.242.151  Bcast:192.1.242.255  Mask:255.255.255.128
     156          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     157          RX packets:16760 errors:0 dropped:0 overruns:0 frame:0
     158          TX packets:8485 errors:0 dropped:0 overruns:0 carrier:0
     159          collisions:0 txqueuelen:0
     160          RX bytes:22877000 (21.8 MiB)  TX bytes:460760 (449.9 KiB)
     161
     162eth3747   Link encap:Ethernet  HWaddr 02:50:1E:B4:3D:52 
     163          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
     164          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     165          RX packets:63 errors:0 dropped:0 overruns:0 frame:0
     166          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
     167          collisions:0 txqueuelen:0
     168          RX bytes:3064 (2.9 KiB)  TX bytes:476 (476.0 b)
     169}}}
     170
     171
     172You may also use the ''client-utah'' login to verify connectivity between to the ''server-gpo'':
     173
     174$ ssh -p 30522  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc5.utah.geniracks.net
     175[lnevers@client-utah ~]$ /sbin/ifconfig
     176eth923    Link encap:Ethernet  HWaddr 02:FC:D2:8D:7C:FF 
     177          inet addr:192.168.4.2  Bcast:192.168.4.255  Mask:255.255.255.0
     178          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     179          RX packets:54 errors:0 dropped:0 overruns:0 frame:0
     180          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     181          collisions:0 txqueuelen:0
     182          RX bytes:2408 (2.3 KiB)  TX bytes:0 (0.0 b)
     183
     184eth999    Link encap:Ethernet  HWaddr 02:CD:95:2D:16:C5 
     185          inet addr:172.17.5.7  Bcast:172.31.255.255  Mask:255.240.0.0
     186          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     187          RX packets:17003 errors:0 dropped:0 overruns:0 frame:0
     188          TX packets:8062 errors:0 dropped:0 overruns:0 carrier:0
     189          collisions:0 txqueuelen:0
     190          RX bytes:22951047 (21.8 MiB)  TX bytes:432534 (422.3 KiB)
     191[lnevers@client-utah ~]$ ping -c 5 192.168.4.1
     192PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
     19364 bytes from 192.168.4.1: icmp_req=1 ttl=64 time=161 ms
     19464 bytes from 192.168.4.1: icmp_req=2 ttl=64 time=80.3 ms
     19564 bytes from 192.168.4.1: icmp_req=3 ttl=64 time=80.4 ms
     19664 bytes from 192.168.4.1: icmp_req=4 ttl=64 time=80.4 ms
     19764 bytes from 192.168.4.1: icmp_req=5 ttl=64 time=80.4 ms
     198
     199--- 192.168.4.1 ping statistics ---
     2005 packets transmitted, 5 received, 0% packet loss, time 4005ms
     201rtt min/avg/max/mdev = 80.388/96.667/161.683/32.508 ms
     202}}}
     203
     204}}}
     205
     206
     207== Finish Experiment ==
    133208{{{
    134209#!html