Changes between Version 3 and Version 4 of GENIRacksHome/InstageniRacks/ConfirmationTestStatus/GPO


Ignore:
Timestamp:
12/20/12 13:44:52 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniRacks/ConfirmationTestStatus/GPO

    v3 v4  
    582582
    583583== IG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
     584
     585This confirmation test creates a sliver at each of the following Aggregates:
     586 * Utah InstaGENI with two VM on shared VLAN 1750 using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/GPO/IG-CT-4-ig-utah.rspec IG-CT-4-ig-utah.rspec].
     587 * GPO InstaGENI with two VMs on shared VLAN 1750 using [TBD] RSPEC.
     588 * ProtoGENI Utah  with one VM on shared VLAN 1750 using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/GPO/IG-CT-4-pg-utah.rspec IG-CT-4-pg-utah.rspec].
     589 * ProtoGENI Utah with 1 WAPG nodes located at Indiana using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Utah/IG-CT-4-openflow-indiana-wapg.rspec IG-CT-4-openflow-indiana-wapg.rspec].
     590 * !OpenFlow datapaths at:
     591   - NLR using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/GPO/IG-CT-4-openflow-nlr.rspec IG-CT-4-openflow-nlr.rspec].
     592   - Internet2 using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/GPO/IG-CT-4-openflow-internet2.rspec IG-CT-4-openflow-internet2.rspec].
     593   - UEN using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/GPO/IG-CT-4-openflow-uen.rspec IG-CT-4-openflow-uen.rspec].
     594   - Indian FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/GPo/IG-CT-4-openflow-indiana-wapg.rspec IG-CT-4-openflow-indiana-wapg.rspec].
     595   - Utah InstaGENI FOAM using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/GPO/IG-CT-4-openflow-instageni.rspec IG-CT-4-openflow-instageni.rspec].
     596   - GPO ExoGENI using [TBD] RSpec.
     597''__Note__'': To avoid multiple resource requests to the PG Utah aggregate, and thus multiple slices, one can combine the RSpec for the PG Utah VMs on shared VLAN 1750 and the request for the Indiana WAPG nodes into one RSpec. An example of the combined RSpec is [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/GPO/IG-CT-4-indiana-wapg-pg-utah.rspec IG-CT-4-indiana-wapg-pg-utah.rspec].
     598
     599[[BR]]
     600Following is the command sequence that is executed to setup the topology for this confirmation test:
     601{{{
     602# Create the slice to be used for this confirmation test:
     603$ omni.py createslice IG-CT-4
     604
     605# Create the FOAM slivers at the Internet and NLR FOAM
     606$ omni.py createsliver -a of-i2 IG-CT-4 IG-CT-4-openflow-internet2.rspec -V1
     607$ omni.py createsliver -a of-nlr IG-CT-4 IG-CT-4-openflow-nlr.rspec -V1
     608
     609# Create FOAM sliver at UEN regional for path to backbone
     610$ omni.py createsliver -a of-uen IG-CT-4  IG-CT-4-openflow-uen.rspec  -V1
     611
     612# Create the sliver at Utah InstaGENI FOAM which will allow the PG Utah FOAM to interoperate with sliver.
     613$ omni.py createsliver -a of-ig IG-CT-4 IG-CT-4-openflow-instageni.rspec  -V1
     614
     615# Create the slivers at InstaGENI Utah to request nodes on shared VLAN 1750
     616omni.py createsliver -a ig-utah IG-CT-4 IG-CT-4-ig-utah.rspec
     617
     618
     619# Create the slivers at InstaGENI GPO to request nodes on shared VLAN 1750
     620omni.py createsliver -a ig-gpo IG-CT-4 IG-CT-4-ig-gpo.rspec
     621
     622# Create the sliver at PG Utah to request one WAPG Node at Indiana and one VM at PG Utah on shared VLAN 1750.
     623$ omni.py createsliver -a pg-utah IG-CT-4  IG-CT-4-indiana-wapg.rspec
     624}}}
     625
     626''__Note__'': To avoid multiple resource requests to the PG Utah aggregate, and thus multiple slices, one can comine the RSPec for the PG Utah VMs on shared VLAN 1750 and the request for the Indiana WAPG nodes into one RSpec. An example of the combined RSpec is [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Utah/IG-CT-4-indiana-wapg-pg-utah.rspec IG-CT-4-indiana-wapg-pg-utah.rspec].
     627
     628Once the slivers were ready, determined login for PG and Indiana hosts on shared VLAN 1750:
     629{{{
     630$ readyToLogin.py -a pg-utah IG-CT-4
     631<...>
     632wapg-indiana-pg58's geni_status is: ready (am_status:ready)
     633User lnevers logins to wapg-indiana-pg58 using:
     634        xterm -e ssh -i /home/lnevers/.ssh/id_rsa lnevers@pg58.emulab.net &
     635
     636utah-pg's geni_status is: ready (am_status:ready)
     637User lnevers logins to utah-pg using:
     638        xterm -e ssh -p 32314  -i /home/lnevers/.ssh/id_rsa lnevers@pc545.emulab.net &
     639}}}
     640
     641Determined login for Utah InstaGENI:
     642{{{
     643$ readyToLogin.py -a ig-utah  IG-CT-4
     644<...>
     645utah-ig's geni_status is: ready (am_status:ready)
     646User lnevers logins to utah-ig using:
     647        xterm -e ssh -p 31034  -i /home/lnevers/.ssh/id_rsa lnevers@pc3.utah.geniracks.net &
     648
     649utah-ig2's geni_status is: ready (am_status:ready)
     650User lnevers logins to utah-ig2 using:
     651        xterm -e ssh -p 31035  -i /home/lnevers/.ssh/id_rsa lnevers@pc3.utah.geniracks.net &
     652
     653}}}
     654Determined login for GPO InstaGENI:
     655{{{
     656$ readyToLogin.py -a ig-gpo IG-CT-4
     657<...>
     658gpo-ig2's geni_status is: ready (am_status:ready)
     659User lnevers logins to gpo-ig2 using:
     660        xterm -e ssh -p 30779  -i /home/lnevers/.ssh/id_rsa lnevers@pc1.instageni.gpolab.bbn.com &
     661
     662gpo-ig's geni_status is: ready (am_status:ready)
     663User lnevers logins to gpo-ig using:
     664        xterm -e ssh -p 30778  -i /home/lnevers/.ssh/id_rsa lnevers@pc1.instageni.gpolab.bbn.com &
     665
     666}}}
     667
     668Determined login for GPO ExoGENI:
     669{{{
     670$ readyToLogin.py -a eg-gpo IG-CT-4
     671<...>
     672User root logins to VM using:
     673        xterm -e ssh -i /home/lnevers/.ssh/id_rsa root@192.1.242.9 &
     674{{{
     675
     676=== Measurements ===
     677This section captures measurements collected between the following endpoints:
     678 - InstaGENI Utah VM and the PG Utah VM
     679 - InstaGENI Utah VM and the WAPG node at Wisconsin
     680
     681The measurements collected for InstaGENI Utah VM to the PG Utah:
     682
     683'''Iperf InstaGENI Utah VM to the PG Utah VM (TCP) - TCP window size: 16.0 KB '''
     684
     685__One Client_
     686{{{
     687[ ID] Interval       Transfer     Bandwidth
     688[  4]  0.0-60.0 sec  6.32 GBytes   904 Mbits/sec
     689}}}
     690
     691__Five Clients__
     692{{{
     693[ ID] Interval       Transfer     Bandwidth
     694[  3]  0.0-59.9 sec  1.20 GBytes   172 Mbits/sec
     695[  4]  0.0-59.9 sec  1.46 GBytes   210 Mbits/sec
     696[  6]  0.0-59.9 sec  1.35 GBytes   194 Mbits/sec
     697[  7]  0.0-59.9 sec  1.16 GBytes   166 Mbits/sec
     698[  5]  0.0-60.0 sec  1.15 GBytes   164 Mbits/sec
     699[SUM]  0.0-60.0 sec  6.32 GBytes   905 Mbits/sec
     700}}}
     701
     702__Ten Clients__
     703
     704{{{
     705[ ID] Interval       Transfer     Bandwidth
     706[  3]  0.0-59.9 sec   580 MBytes  81.2 Mbits/sec
     707[  5]  0.0-59.9 sec   638 MBytes  89.4 Mbits/sec
     708[  4]  0.0-59.9 sec   644 MBytes  90.2 Mbits/sec
     709[  9]  0.0-60.0 sec   600 MBytes  84.0 Mbits/sec
     710[ 12]  0.0-60.0 sec   659 MBytes  92.2 Mbits/sec
     711[  8]  0.0-59.9 sec   763 MBytes   107 Mbits/sec
     712[  7]  0.0-60.0 sec   669 MBytes  93.6 Mbits/sec
     713[  6]  0.0-60.0 sec   607 MBytes  84.9 Mbits/sec
     714[ 10]  0.0-60.0 sec   669 MBytes  93.5 Mbits/sec
     715[ 11]  0.0-60.0 sec   646 MBytes  90.3 Mbits/sec
     716[SUM]  0.0-60.0 sec  6.32 GBytes   905 Mbits/sec
     717}}}
     718
     719'''Iperf InstaGENI Utah VM to the PG Utah VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     720{{{
     721[ ID] Interval       Transfer     Bandwidth
     722[  3]  0.0-60.0 sec  7.50 MBytes  1.05 Mbits/sec
     723[  3] Sent 5351 datagrams
     724[  3] Server Report:
     725[  3]  0.0-59.9 sec  7.50 MBytes  1.05 Mbits/sec   0.016 ms    5/ 5351 (0.093%)
     726[  3]  0.0-59.9 sec  5 datagrams received out-of-order
     727}}}
     728
     729'''Ping from InstaGENI Utah VM to the PG Utah VM'''
     730{{{
     73160 packets transmitted, 60 received, 0% packet loss, time 60999ms
     732rtt min/avg/max/mdev = 0.158/1.287/66.300/8.324 ms
     733}}}
     734
     735The measurements collected for InstaGENI Utah VM to the WAPG Indiana:
     736
     737'''Iperf InstaGENI Utah VM to the WAPG Wisconsin (TCP) - TCP window size: 16.0 KB '''
     738
     739__One Client_
     740{{{
     741
     742}}}
     743
     744__Five Clients__
     745{{{
     746
     747}}}
     748
     749__Ten Clients__
     750
     751'''Iperf InstaGENI Utah VM to the WAPG Wisconsin (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     752{{{
     753
     754}}}
     755
     756'''Ping from InstaGENI Utah VM to the WAPG Wisconsin'''
     757{{{
     75875 packets transmitted, 16 received, 78% packet loss, time 74008ms
     759rtt min/avg/max/mdev = 391.590/1236.949/3158.446/996.015 ms, pipe 4
     760}}}
    584761
    585762== IG-CT-5 - Experiment Monitoring ==