Changes between Version 6 and Version 7 of GENIRacksHome/InstageniRacks/ConfirmationTestStatus/UWisconsin


Ignore:
Timestamp:
10/24/13 09:54:45 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v6 v7  
    768768}}}
    769769== IG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
     770
     771First created a slice:
     772{{{
     773$ omni.py createslice IG-CT-4
     774}}}
     775Then created 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/Wisconsin here].
     776{{{
     777$ omni.py createsliver -a nlr-of IG-CT-4 IG-CT-4-openflow-nlr.rspec
     778$ omni.py createsliver -a i2-of IG-CT-4 IG-CT-4-openflow-internet2.rspec
     779$ omni.py createsliver -a gpo-of IG-CT-4 IG-CT-4-openflow-gpo.rspec
     780$ omni.py createsliver -a gpo-eg-of IG-CT-4 IG-CT-4-openflow-eg-gpo.rspec
     781$ omni.py createsliver -a uen-of IG-CT-4 IG-CT-4-openflow-uen.rspec
     782$ omni.py createsliver -a wisconsin-ig-of IG-CT-4 IG-CT-4-openflow-ig-wisconsin.rspec
     783$ omni.py createsliver -a gpo-ig-of IG-CT-4 IG-CT-4-openflow-ig-gpo.rspec
     784$ omni.py createsliver -a moxi-of IG-CT-4 IG-CT-4-openflow-moxi.rspec  -V1
     785}}}
     786
     787Then created 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/Wisconsin here].
     788
     789{{{
     790$ omni.py createsliver -a pg-utah IG-CT-4 IG-CT-4-pg-utah.rspec
     791$ omni.py createsliver -a gpo-ig IG-CT-4 IG-CT-4-ig-gpo.rspec
     792$ omni.py createsliver -a gpo-eg IG-CT-4 IG-CT-4-eg-gpo.rspec
     793$ omni.py createsliver -a wisconsin-ig IG-CT-4 IG-CT-4-ig-wisconsin.rspec
     794}}}
     795
     796Determined login for each of compute resources:
     797{{{
     798$ readyToLogin.py -a wisconsin-ig IG-CT-4
     799<...>
     800================================================================================
     801LOGIN INFO for AM: https://instageni.wisc.edu:12369/protogeni/xmlrpc/am
     802================================================================================
     803
     804For more login info, see the section entitled:
     805         'Providing a private key to ssh' in 'readyToLogin.py -h'
     806
     807wisc-ig2's geni_status is: ready (am_status:ready)
     808User lnevers logs in to wisc-ig2 using:
     809        ssh -p 33083  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.wisc.edu
     810
     811wisc-ig's geni_status is: ready (am_status:ready)
     812User lnevers logs in to wisc-ig using:
     813        ssh -p 33082  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.wisc.edu
     814
     815$ readyToLogin.py -a gpo-ig IG-CT-4
     816<...>
     817================================================================================
     818LOGIN INFO for AM: https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am/2.0
     819================================================================================
     820
     821For more login info, see the section entitled:
     822         'Providing a private key to ssh' in 'readyToLogin.py -h'
     823
     824gpo-ig2's geni_status is: ready (am_status:ready)
     825User lnevers logs in to gpo-ig2 using:
     826        ssh -p 37691  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.gpolab.bbn.com
     827
     828gpo-ig's geni_status is: ready (am_status:ready)
     829User lnevers logs in to gpo-ig using:
     830        ssh -p 37690  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.gpolab.bbn.com
     831
     832$ readyToLogin.py -a pg-utah IG-CT-4
     833<...>
     834================================================================================
     835LOGIN INFO for AM: https://www.emulab.net:12369/protogeni/xmlrpc/am/2.0
     836================================================================================
     837
     838For more login info, see the section entitled:
     839         'Providing a private key to ssh' in 'readyToLogin.py -h'
     840
     841utah-pg's geni_status is: ready (am_status:ready)
     842User lnevers logs in to utah-pg using:
     843        ssh -p 35386  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc522.emulab.net
     844
     845$ readyToLogin.py -a gpo-eg IG-CT-4
     846<...>
     847================================================================================
     848LOGIN INFO for AM: https://bbn-hn.exogeni.net:11443/orca/xmlrpc
     849================================================================================
     850
     851For more login info, see the section entitled:
     852         'Providing a private key to ssh' in 'readyToLogin.py -h'
     853
     854VM's geni_status is: ready (am_status:ready)
     855User lnevers logs in to VM using:
     856        ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@192.1.242.5
     857}}}
     858
     859=== Measurements ===
     860
     861This section captures measurements collected between the following endpoints:
     862{{{
     863 1. InstaGENI Wisconsin VM and InstaGENI Wisconsin VM
     864 2. InstaGENI Wisconsin VM and InstaGENI GPO VM
     865 3. InstaGENI Wisconsin VM and the PG Utah VM
     866 4. InstaGENI Wisconsin VM and ExoGENI GPO VM
     867}}}
     868
     8691. The measurements collected for InstaGENI Wisconsin VM to the InstaGENI Wisconsin VM:
     870
     871'''Iperf InstaGENI Wisconsin VM to InstaGENI Wisconsin VM (TCP)
     872
     873''Collected: 2013-10-24''
     874
     875__One Client_
     876{{{
     877[ ID] Interval       Transfer     Bandwidth
     878[  3]  0.0-60.0 sec  8.88 GBytes  1.27 Gbits/sec
     879}}}
     880
     881__Five Clients__
     882{{{
     883[ ID] Interval       Transfer     Bandwidth
     884[  7]  0.0-60.0 sec  6.93 GBytes   992 Mbits/sec
     885[  4]  0.0-60.0 sec  6.88 GBytes   984 Mbits/sec
     886[  5]  0.0-60.0 sec  6.97 GBytes   998 Mbits/sec
     887[  3]  0.0-60.0 sec  6.97 GBytes   997 Mbits/sec
     888[  6]  0.0-60.0 sec  6.94 GBytes   994 Mbits/sec
     889[SUM]  0.0-60.0 sec  34.7 GBytes  4.97 Gbits/sec
     890}}}
     891
     892__Ten Clients__
     893
     894{{{
     895[ ID] Interval       Transfer     Bandwidth
     896[ 12]  0.0-60.0 sec  6.67 GBytes   955 Mbits/sec
     897[  4]  0.0-60.0 sec  6.19 GBytes   886 Mbits/sec
     898[  3]  0.0-60.0 sec  5.64 GBytes   807 Mbits/sec
     899[  5]  0.0-60.0 sec  6.06 GBytes   867 Mbits/sec
     900[  7]  0.0-60.0 sec  5.59 GBytes   801 Mbits/sec
     901[  6]  0.0-60.0 sec  6.04 GBytes   865 Mbits/sec
     902[  9]  0.0-60.0 sec  6.21 GBytes   889 Mbits/sec
     903[ 10]  0.0-60.0 sec  5.63 GBytes   806 Mbits/sec
     904[  8]  0.0-60.0 sec  5.46 GBytes   781 Mbits/sec
     905[ 11]  0.0-60.0 sec  5.90 GBytes   845 Mbits/sec
     906[SUM]  0.0-60.0 sec  59.4 GBytes  8.50 Gbits/sec
     907}}}
     908
     909'''Iperf InstaGENI Wisconsin VM to the InstaGENI Wisconsin VM  (UDP)
     910{{{
     911
     912}}}
     913
     914'''Ping from InstaGENI Wisconsin VM to the InstaGENI Wisconsin VM'''
     915{{{
     916
     917}}}
     918
     919
     9202. The measurements collected for InstaGENI Wisconsin VM to the InstaGENI GPO VM:
     921
     922'''Iperf InstaGENI Wisconsin VM to the InstaGENI GPO VM (TCP)
     923
     924''Collected: 2013-10-24''
     925
     926__One Client_
     927{{{
     928
     929}}}
     930
     931__Five Clients__
     932{{{
     933
     934}}}
     935
     936__Ten Clients__
     937
     938{{{
     939
     940}}}
     941
     942'''Iperf InstaGENI Wisconsin VM to the InstaGENI GPO VM  (UDP)
     943{{{
     944
     945}}}
     946
     947'''Ping from InstaGENI Wisconsin VM to the InstaGENI GPO VM'''
     948{{{
     949
     950}}}
     951
     9523. The measurements collected for InstaGENI Wisconsin VM to the PG Utah VM
     953
     954''Collected: 2013-10-24''
     955
     956'''Iperf InstaGENI Wisconsin VM to the PG Utah VM (TCP)
     957
     958__One Client_
     959{{{
     960
     961}}}
     962
     963__Five Clients__
     964{{{
     965
     966}}}
     967
     968__Ten Clients__
     969
     970{{{
     971
     972
     973}}}
     974
     975'''Iperf InstaGENI Wisconsin VM to the PG Utah VM  (UDP)
     976{{{
     977
     978}}}
     979
     980'''Ping from InstaGENI Wisconsin VM to the PG Utah VM'''
     981{{{
     982
     983}}}
     984
     9854. The measurements collected for InstaGENI Wisconsin VM to the ExoGENI GPO VM:
     986
     987'''Iperf InstaGENI Wisconsin VM to the ExoGENI GPO VM (TCP)
     988
     989''Collected: 2013-10-24''
     990
     991__One Client_
     992{{{
     993
     994}}}
     995
     996__Five Clients__
     997{{{
     998
     999}}}
     1000
     1001__Ten Clients__
     1002
     1003{{{
     1004
     1005}}}
     1006
     1007'''Iperf InstaGENI Wisconsin VM to the ExoGENI GPO VM  (UDP)
     1008{{{
     1009
     1010}}}
     1011
     1012'''Ping from InstaGENI Wisconsin VM to the ExoGENI GPO VM'''
     1013{{{
     1014
     1015}}}
     1016
    7701017== IG-CT-5 - Experiment Monitoring ==
     1018Reviewed content of the GMOC Monitoring page for [https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregates aggregates], and found/not found both Compute Resources and FOAM aggregates.
     1019
     1020[[Image(Wisconsin-aggregate.jpg)]]
     1021
     1022Verified that the Wisconsin compute resources aggregate shows up in the list of aggregates and provides Aggregate Name, Type, Last Update, Version, POP, and Organization:
     1023
     1024[[Image(Wisconsin-aggregate-detail.jpg)]]
     1025
     1026Active slivers:
     1027
     1028[[Image(Wisconsin-sliver.jpg)]]
     1029
     1030List of resources:
     1031
     1032[[Image(Wisconsin-resources.jpg)]]
     1033Aggregate measurements:
     1034
     1035[[Image(Wisconsin-measure.jpg)]]
     1036
     1037The Wisconsin InstaGENI FOAM resources aggregate details:
     1038
     1039[[Image(Wisconsin-FOAMAggregate.jpg)]]
     1040
     1041Active !OpenFlow Slivers:
     1042
     1043[[Image(Wisconsin-OFSlivers.jpg)]]
     1044
     1045List of !OpenFlow Resources in use:
     1046
     1047[[Image(Wisconsin-OFResources.jpg)]]
     1048
     1049Monitoring shows Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics and OF Datapath and Sliver Statistics:
     1050
     1051[[Image(Wisconsin-OFMonitoring.jpg)]]
     1052
    7711053== IG-CT-6 - Administrative Tests ==
    7721054
     1055
     1056
     1057Verify alerts for the compute resource Aggregate Manager are being reported to the [http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi GPO Tango GENI Nagios monitoring] and that the majority of alerts have a status of "OK". Other statuses may be encountered and are verified with activities, outages or known issues for the site.
     1058
     1059
     1060[[Image(Wisconsin-nagios.jpg)]]
     1061
     1062Verify alerts for the FOAM Aggregate Manager are being reported to the [http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi GPO Tango GENI Nagios monitoring] and that the majority of alerts have a status of "OK". Other statuses may be encountered and are verified with activities, outages or known issues for the site.
     1063
     1064[[Image(Wisconsin-OF-nagios.jpg)]]
    7731065----
    7741066{{{