Changes between Version 5 and Version 6 of GENIRacksHome/InstageniRacks/ConfirmationTestStatus/MAX


Ignore:
Timestamp:
09/17/13 16:46:51 (11 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v5 v6  
    772772
    773773== IG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
     774First create a slice:
     775{{{
     776$  omni.py createslice IG-CT-4
     77716:13:56 INFO     omni: Loading agg_nick_cache file '/home/lnevers/.gcf/agg_nick_cache'
     77816:13:56 INFO     omni: Loading config file /home/lnevers/.gcf/omni_config
     77916:13:56 INFO     omni: Using control framework portal
     78016:13:57 INFO     omni: Created slice with Name IG-CT-4, URN urn:publicid:IDN+ch.geni.net:ln-prj+slice+IG-CT-4, Expiration 2013-09-23 13:34:40
     78116:13:57 INFO     omni:  ------------------------------------------------------------
     78216:13:57 INFO     omni:  Completed createslice:
     783Args: createslice IG-CT-4
     784
     785  Result Summary: Created slice with Name IG-CT-4, URN urn:publicid:IDN+ch.geni.net:ln-prj+slice+IG-CT-4, Expiration 2013-09-23 13:34:40
     786 
     78716:13:57 INFO     omni:  ============================================================
     788}}}
     789
     790Then create slivers at all OpenFlow aggregates.  This confirmation test creates a sliver at each of the following aggregates using the RSpec specified.  RSpecs can be found [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/NYSERNet here].
     791{{{
     792$ omni.py createsliver -a of-nlr IG-CT-4 IG-CT-4-openflow-nlr.rspec -V1
     793$ omni.py createsliver -a of-i2 IG-CT-4 IG-CT-4-openflow-internet2.rspec -V1
     794$ omni.py createsliver -a of-gpo IG-CT-4 IG-CT-4-openflow-gpo.rspec -V1
     795$ omni.py createsliver -a eg-of-gpo IG-CT-4 IG-CT-4-openflow-eg-gpo.rspec -V1
     796$ omni.py createsliver -a of-uen IG-CT-4 IG-CT-4-openflow-uen.rspec -V1
     797$ omni.py createsliver -a ig-of-max IG-CT-4 IG-CT-4-openflow-ig-max.rspec -V1
     798$ omni.py createsliver -a ig-of-gpo IG-CT-4 IG-CT-4-openflow-ig-gpo.rspec -V1
     799
     800 
     801}}}
     802Then create a sliver at each of the compute resource aggregates, RSpecs used can be found RSpecs can be found [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/NYSERNet here].
     803
     804{{{
     805$ omni.py createsliver -a pg-utah IG-CT-4 IG-CT-4-pg-utah.rspec
     806$ omni.py createsliver -a ig-gpo IG-CT-4 IG-CT-4-ig-gpo.rspec
     807$ omni.py createsliver -a eg-gpo IG-CT-4 IG-CT-4-eg-gpo.rspec
     808$ omni.py createsliver -a ig-max IG-CT-4 IG-CT-4-ig-max.rspec
     809}}}
     810
     811{{{
     812$ readyToLogin.py -a ig-max IG-CT-4
     813<...>
     814================================================================================
     815LOGIN INFO for AM: https://instageni.maxgigapop.net:12369/protogeni/xmlrpc/am
     816================================================================================
     817
     818For more login info, see the section entitled:
     819         'Providing a private key to ssh' in 'readyToLogin.py -h'
     820
     821max-ig2's geni_status is: changing (am_status:changing)
     822User lnevers logs in to max-ig2 using:
     823        ssh -p 31291  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.maxgigapop.net
     824
     825max-ig's geni_status is: changing (am_status:changing)
     826User lnevers logs in to max-ig using:
     827        ssh -p 31290  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.maxgigapop.net
     828
     829$ readyToLogin.py -a ig-gpo IG-CT-4
     830<...>
     831gpo-ig2's geni_status is: ready (am_status:ready)
     832User lnevers logs in to gpo-ig2 using:
     833        ssh -p 35643  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.gpolab.bbn.com
     834
     835gpo-ig's geni_status is: ready (am_status:ready)
     836User lnevers logs in to gpo-ig using:
     837        ssh -p 35642  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.gpolab.bbn.com
     838
     839$ readyToLogin.py -a pg-utah IG-CT-4
     840<...>
     841================================================================================
     842LOGIN INFO for AM: https://www.emulab.net:12369/protogeni/xmlrpc/am/2.0
     843================================================================================
     844
     845For more login info, see the section entitled:
     846         'Providing a private key to ssh' in 'readyToLogin.py -h'
     847
     848utah-pg's geni_status is: ready (am_status:ready)
     849User lnevers logs in to utah-pg using:
     850        ssh -p 36154  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc403.emulab.net
     851
     852$ readyToLogin.py -a eg-gpo IG-CT-4
     853<...>
     854================================================================================
     855LOGIN INFO for AM: https://bbn-hn.exogeni.net:11443/orca/xmlrpc
     856================================================================================
     857
     858For more login info, see the section entitled:
     859         'Providing a private key to ssh' in 'readyToLogin.py -h'
     860
     861VM's geni_status is: ready (am_status:ready)
     862User lnevers logs in to VM using:
     863        ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@192.1.242.9
     864}}}
     865
     866=== Measurements ===
     867This section captures measurements collected between the following endpoints:
     868{{{
     869 1. InstaGENI MAX VM and InstaGENI MAX VM
     870 2. InstaGENI MAX VM and InstaGENI GPO VM
     871 3. InstaGENI MAX VM and the PG Utah VM
     872 4. InstaGENI MAX VM and ExoGENI GPO VM
     873}}}
     874
     8751. The measurements collected for InstaGENI MAX VM to the InstaGENI MAX VM:
     876
     877'''Iperf MAX GPO VM to the MAX GPO VM (TCP)
     878
     879''Collected: 2013-XX-XX''
     880
     881__One Client_
     882{{{
     883[ ID] Interval       Transfer     Bandwidth
     884[  3]  0.0-60.0 sec  8.77 GBytes  1.26 Gbits/sec
     885}}}
     886
     887__Five Clients__
     888{{{
     889[ ID] Interval       Transfer     Bandwidth
     890[  7]  0.0-60.0 sec  7.08 GBytes  1.01 Gbits/sec
     891[  3]  0.0-60.0 sec  7.03 GBytes  1.01 Gbits/sec
     892[  5]  0.0-60.0 sec  7.05 GBytes  1.01 Gbits/sec
     893[  4]  0.0-60.0 sec  7.07 GBytes  1.01 Gbits/sec
     894[  6]  0.0-60.0 sec  7.15 GBytes  1.02 Gbits/sec
     895[SUM]  0.0-60.0 sec  35.4 GBytes  5.06 Gbits/sec
     896}}}
     897
     898__Ten Clients__
     899
     900{{{
     901[ ID] Interval       Transfer     Bandwidth
     902[ 12]  0.0-60.0 sec  5.88 GBytes   842 Mbits/sec
     903[  3]  0.0-60.0 sec  5.74 GBytes   822 Mbits/sec
     904[  6]  0.0-60.0 sec  6.02 GBytes   862 Mbits/sec
     905[  4]  0.0-60.0 sec  6.08 GBytes   870 Mbits/sec
     906[  8]  0.0-60.0 sec  6.09 GBytes   871 Mbits/sec
     907[  5]  0.0-60.0 sec  6.03 GBytes   863 Mbits/sec
     908[  9]  0.0-60.0 sec  6.06 GBytes   868 Mbits/sec
     909[  7]  0.0-60.0 sec  5.87 GBytes   840 Mbits/sec
     910[ 10]  0.0-60.0 sec  5.94 GBytes   850 Mbits/sec
     911[ 11]  0.0-60.0 sec  6.08 GBytes   870 Mbits/sec
     912[SUM]  0.0-60.0 sec  59.8 GBytes  8.56 Gbits/sec
     913}}}
     914
     915'''Iperf InstaGENI MAX VM to the InstaGENI MAX VM  (UDP)
     916{{{
     917[ ID] Interval       Transfer     Bandwidth
     918[  3]  0.0-60.0 sec   719 MBytes   101 Mbits/sec
     919[  3] Sent 512821 datagrams
     920[  3] Server Report:
     921[  3]  0.0-60.0 sec   719 MBytes   101 Mbits/sec   0.001 ms    0/512820 (0%)
     922[  3]  0.0-60.0 sec  1 datagrams received out-of-order
     923}}}
     924
     925'''Ping from InstaGENI MAX VM to the InstaGENI MAX VM'''
     926{{{
     92760 packets transmitted, 60 received, 0% packet loss, time 59000ms
     928rtt min/avg/max/mdev = 0.037/0.048/0.071/0.005 ms
     929}}}
     930
     931
     9322. The measurements collected for InstaGENI MAX VM to the InstaGENI GPO VM:
     933
     934'''Iperf InstaGENI MAX VM to the InstaGENI GPO VM (TCP)
     935
     936''Collected: 2013-09-19''
     937
     938__One Client_
     939{{{
     940
     941}}}
     942
     943__Five Clients__
     944{{{
     945
     946}}}
     947
     948__Ten Clients__
     949
     950{{{
     951
     952}}}
     953
     954'''Iperf InstaGENI MAX VM to the InstaGENI GPO VM  (UDP)
     955{{{
     956
     957}}}
     958
     959'''Ping from InstaGENI MAX VM to the InstaGENI GPO VM'''
     960{{{
     961
     962}}}
     963
     9643. The measurements collected for InstaGENI MAX VM to the PG Utah VM
     965
     966''Collected: 2013-XX-XX''
     967
     968'''Iperf InstaGENI MAX VM to the PG Utah VM (TCP)
     969
     970__One Client_
     971{{{
     972
     973}}}
     974
     975__Five Clients__
     976{{{
     977
     978}}}
     979
     980__Ten Clients__
     981
     982{{{
     983
     984
     985}}}
     986
     987'''Iperf InstaGENI MAX VM to the PG Utah VM  (UDP)
     988{{{
     989
     990}}}
     991
     992'''Ping from InstaGENI MAX VM to the PG Utah VM'''
     993{{{
     994
     995}}}
     996
     9974. The measurements collected for InstaGENI MAX VM to the ExoGENI GPO VM:
     998
     999'''Iperf InstaGENI MAX VM to the ExoGENI RENCI VM (TCP)
     1000
     1001''Collected: 2013-XX-XX''
     1002
     1003__One Client_
     1004{{{
     1005
     1006}}}
     1007
     1008__Five Clients__
     1009{{{
     1010
     1011}}}
     1012
     1013__Ten Clients__
     1014
     1015{{{
     1016
     1017}}}
     1018
     1019'''Iperf InstaGENI MAX VM to the ExoGENI RENCI VM  (UDP)
     1020{{{
     1021
     1022}}}
     1023
     1024'''Ping from InstaGENI MAX VM to the ExoGENI GPO VM'''
     1025{{{
     1026
     1027}}}
    7741028
    7751029== IG-CT-5 - Experiment Monitoring ==