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


Ignore:
Timestamp:
05/11/15 13:25:19 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v5 v6  
    11[[PageOutline]]
    22
    3 = !VirginiaTech InstaGENI Confirmation Tests  =
     3= !VirginiaTech InstaGENI Confirmation Tests =
    44
    55For details about the tests in this page, see the '''[wiki:GENIRacksHome/InstageniRacks/SiteConfirmationTests InstaGENI Confirmation Tests]''' page.[[BR]]
    66For site status see the '''[wiki:GENIRacksHome/InstageniRacks/ConfirmationTestStatus InstaGENI New Site Confirmation Tests Status]''' page.
    77
    8 Mid-Atlantic Research and Education Exchange (MREX), operated by Virginia Tech
     8__Note:__ Omni nick_names for site aggregate used for these tests are:
     9{{{
     10vt-ig=urn:publicid:IDN+instageni.arc.vt.edu+authority+cm,https://instageni.arc.vt.edu:12369/protogeni/xmlrpc/am
     11vt-ig-of-=urn:publicid:IDN+openflow:foam:foam.instageni.arc.vt.edu+authority+am,https://foam.instageni.arc.vt.edu:3626/foam/gapi/2
     12}}}
     13
    914
    1015== IG-CT-1 - Access to New Site VM resources ==
     16Got Aggregate version, which showed AM API V1, V2, and V3 are supported and V2 is default:
     17{{{
     18$ omni.py getversion -a vt-ig
     19}}}
     20
     21The InstaGENI version in" 'code_tag':'99a2b1f03656cb665918eebd2b95434a6d3e50f9'" is the same as the other two available InstaGENI site (GPO and Utah):
     22{{{
     23IG GPO:         {   'code_tag': '99a2b1f03656cb665918eebd2b95434a6d3e50f9'
     24IG VirginiaTech:       {   'code_tag': '99a2b1f03656cb665918eebd2b95434a6d3e50f9',
     25IG Utah:        {   'code_tag': '99a2b1f03656cb665918eebd2b95434a6d3e50f9'
     26}}}
     27
     28Get list of "available" compute resources:
     29{{{
     30$ omni.py -a vt-ig listresources --available -o
     31}}}
     32
     33Verified that Advertisement RSpec only includes available resources, as requested:
     34{{{
     35$ egrep "node comp|available now" rspec-xxx
     36}}}
     37
     38Created a slice:
     39{{{
     40$ omni.py createslice IG-CT-1
     41}}}
     42
     43Created a 4 VMs sliver using the RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/VirginiaTech/IG-CT-1-gatech.rspec IG-CT-1-gatech.rspec]:
     44{{{
     45$ omni.py createsliver -a vt-ig IG-CT-1 IG-CT-1-gatech.rspec
     46}}}
     47The following is login information for the sliver:
     48{{{
     49$ readyToLogin.py -a vt-ig IG-CT-1
     50<...>
     51
     52}}}
     53
     54=== Measurements ===
     55
     56Log into specified host and collect iperf and ping statistics. All measurements are collected over 60 seconds, using default images and default link bandwidth:
     57
     58'''Iperf InstaGENI VirginiaTech VM-2 to VM-1 (TCP) - TCP window size: 16.0 KB '''
     59
     60''Collected: 2015-05-XX''
     61
     62__One Client_
     63{{{
     64
     65}}}
     66
     67__Five Clients__
     68{{{
     69
     70}}}
     71
     72__Ten Clients__
     73{{{
     74
     75}}}
     76
     77'''Iperf InstaGENI VirginiaTech VM-2 to the VM-1 (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     78{{{
     79
     80}}}
     81
     82'''Ping from InstaGENI VirginiaTech VM-2 to the VM-1 '''
     83{{{
     84
     85}}}
     86
    1187== IG-CT-2 - Access to New Site bare metal and VM resources ==
     88Create a slice:
     89{{{
     90$ omni.py createslice IG-CT-2
     91}}}
     92
     93Created a sliver with one VM and one Raw PC using RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/VirginiaTech/IG-CT-2-gatech.rspec IG-CT-2-gatech.rspec]
     94{{{
     95$ omni.py createsliver -a vt-ig IG-CT-2 IG-CT-2-gatech.rspec
     96
     97
     98}}}
     99
     100Determined login information:
     101{{{
     102$ readyToLogin.py -a vt-ig IG-CT-2
     103<...>
     104
     105}}}
     106
     107
     108=== Measurements ===
     109
     110Log into specified host and collect iperf and ping statistics. All measurements are collected over 60 seconds, using default images and default link bandwidth:
     111
     112'''Iperf InstaGENI VirginiaTech PC to VM (TCP) - TCP window size: 16.0 KB '''
     113
     114''Collected: 2015-05-XX''
     115
     116__One Client_
     117{{{
     118
     119}}}
     120
     121__Five Clients__
     122{{{
     123
     124}}}
     125
     126__Ten Clients__
     127{{{
     128
     129}}}
     130
     131'''Iperf InstaGENI VirginiaTech PC to the VM (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     132{{{
     133
     134}}}
     135
     136'''Ping from InstaGENI VirginiaTech PC to VM '''
     137{{{
     138
     139}}}
     140
     141
     142
     143'''Iperf InstaGENI VirginiaTech PC to PC (TCP) - TCP window size: 16.0 KB '''
     144
     145Even though not part of this test, ran an experiment with 2 raw pcs to capture performance between dedicated devices.
     146
     147
     148''Collected: 2013-02-20''
     149
     150__One Client__
     151{{{
     152
     153}}}
     154
     155__Five Clients__
     156{{{
     157
     158}}}
     159
     160__Ten Clients__
     161{{{
     162
     163}}}
     164
     165'''Iperf InstaGENI VirginiaTech PC to the PC (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     166{{{
     167
     168}}}
     169
     170'''Ping from InstaGENI VirginiaTech PC to PC '''
     171{{{
     172
     173}}}
     174
     175
    12176== IG-CT-3 - Multiple sites experiment  ==
     177
     178Create a slice:
     179{{{
     180$ omni.py createslice IG-CT-3
     181
     182}}}
     183
     184Create a sliver with one VM at VirginiaTech and one VM at GPO using RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/VirginiaTech/IG-CT-3-gatech.rspec IG-CT-3-gatech.rspec].
     185First created the InstaGENI VirginiaTech sliver:
     186{{{
     187$ omni.py createsliver IG-CT-3 -a vt-ig IG-CT-3-gatech.rspec
     188
     189}}}
     190Then creates the InstaGENI GPO sliver:
     191{{{
     192$ omni.py createsliver IG-CT-3 -a ig-gpo IG-CT-3-gatech.rspec
     193
     194}}}
     195
     196Determined login information at each VirginiaTech and GPO aggregate:
     197{{{
     198$ readyToLogin.py IG-CT-3 -a vt-ig
     199  ....
     200
     201$ readyToLogin.py IG-CT-3 -a ig-gpo
     202  ....
     203}}}
     204
     205=== Measurements ===
     206
     207'''Iperf InstaGENI GPO VM-2 to VirginiaTech VM-1 (TCP) - TCP window size: 16.0 KB '''
     208
     209''Collected: 2015-05-XX''
     210
     211__One Client_
     212{{{
     213
     214}}}
     215
     216__Five Clients__
     217{{{
     218
     219}}}
     220
     221__Ten Clients__
     222{{{
     223
     224}}}
     225
     226'''Iperf InstaGENI GPO VM-2 to GPO VM-1 (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     227{{{
     228
     229}}}
     230
     231'''Ping from InstaGENI GPO VM-2 to the GPO VM-1 '''
     232{{{
     233
     234}}}
     235
     236
     237'''Iperf InstaGENI VirginiaTech VM-1 to GPO VM-2 (TCP) - TCP window size: 16.0 KB '''
     238
     239''Collected: 2015-05-XX''
     240
     241__One Client_
     242{{{
     243
     244}}}
     245
     246__Five Clients__
     247{{{
     248
     249}}}
     250
     251__Ten Clients__
     252{{{
     253
     254}}}
     255
     256'''Iperf InstaGENI VirginiaTech VM-1 to GPO VM-2 (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     257{{{
     258
     259}}}
     260
     261'''Ping from InstaGENI VirginiaTech VM-1 to GPO VM-2 '''
     262{{{
     263
     264}}}
     265
    13266== IG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
     267
     268First create a slice:
     269{{{
     270$ omni.py createslice IG-CT-4
     271}}}
     272Then 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/VirginiaTech here].
     273{{{
     274$ omni.py createsliver -a of-nlr IG-CT-4 IG-CT-4-openflow-nlr.rspec
     275$ omni.py createsliver -a of-rutgers IG-CT-4  IG-CT-4-openflow-rutgers.rspec
     276$ omni.py createsliver -a of-i2 IG-CT-4 IG-CT-4-openflow-i2.rspec
     277$ omni.py createsliver -a of-gpo IG-CT-4 IG-CT-4-openflow-gpo.rspec
     278$ omni.py createsliver -a eg-of-gpo IG-CT-4 IG-CT-4-openflow-eg-gpo.rspec
     279$ omni.py createsliver -a of-uen IG-CT-4 ./IG-CT-4-openflow-uen.rspec
     280$ omni.py createsliver -a ig-of-gatech IG-CT-4 IG-CT-4-openflow-vt-ig.rspec
     281$ omni.py createsliver -a ig-of-gpo IG-CT-4 IG-CT-4-openflow-ig-gpo.rspec
     282$ omni.py createsliver -a ig-of-utah IG-CT-4 ./IG-CT-4-openflow-ig-utah.rspec
     283 
     284}}}
     285Then 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/VirginiaTech here].
     286
     287{{{
     288$ omni.py createsliver -a pg-utah IG-CT-4 IG-CT-4-rutgers-wapg-pg-utah.rspec
     289$ omni.py createsliver -a ig-utah IG-CT-4 IG-CT-4-ig-utah.rspec
     290$ omni.py createsliver -a ig-gpo IG-CT-4 IG-CT-4-ig-gpo.rspec
     291$ omni.py createsliver -a eg-gpo IG-CT-4 IG-CT-4-eg-gpo.rspec
     292$ omni.py createsliver -a vt-ig IG-CT-4 IG-CT-4-vt-ig.rspec
     293}}}
     294
     295Determine login for each of compute resources:
     296{{{
     297$ readyToLogin.py -a vt-ig IG-CT-4
     298<...>
     299
     300$ readyToLogin.py -a ig-gpo IG-CT-4
     301<...>
     302
     303$ readyToLogin.py -a pg-utah IG-CT-4
     304<...>
     305
     306$ readyToLogin.py -a ig-utah IG-CT-4
     307<...>
     308
     309$ readyToLogin.py -a eg-gpo IG-CT-4
     310<...>
     311
     312}}}
     313
     314=== Measurements ===
     315This section captures measurements collected between the following endpoints:
     316{{{
     317 1. InstaGENI VirginiaTech VM and InstaGENI VirginiaTech VM
     318 2. InstaGENI VirginiaTech VM and InstaGENI GPO VM
     319 3. InstaGENI VirginiaTech VM and the PG Utah VM
     320 4. InstaGENI VirginiaTech VM and ExoGENI GPO VM
     321 5. InstaGENI VirginiaTech VM and the WAPG node at Rutgers
     322}}}
     323
     3241. The measurements collected for InstaGENI VirginiaTech VM to the InstaGENI VirginiaTech VM:
     325
     326'''Iperf VirginiaTech GPO VM to the VirginiaTech GPO VM (TCP) - TCP window size: 16.0 KB '''
     327
     328''Collected: 2015-05-XX''
     329
     330__One Client_
     331{{{
     332
     333}}}
     334
     335__Five Clients__
     336{{{
     337
     338}}}
     339
     340__Ten Clients__
     341
     342{{{
     343
     344}}}
     345
     346'''Iperf InstaGENI VirginiaTech VM to the InstaGENI VirginiaTech VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     347{{{
     348
     349}}}
     350
     351'''Ping from InstaGENI VirginiaTech VM to the InstaGENI VirginiaTech VM'''
     352{{{
     353
     354}}}
     355
     356
     3572. The measurements collected for InstaGENI VirginiaTech VM to the InstaGENI GPO VM:
     358
     359'''Iperf InstaGENI VirginiaTech VM to the InstaGENI GPO VM (TCP) - TCP window size: 16.0 KB '''
     360
     361''Collected: 2015-05-XX''
     362
     363__One Client_
     364{{{
     365
     366}}}
     367
     368__Five Clients__
     369{{{
     370
     371}}}
     372
     373__Ten Clients__
     374
     375{{{
     376
     377}}}
     378
     379'''Iperf InstaGENI VirginiaTech VM to the InstaGENI GPO VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     380{{{
     381
     382}}}
     383
     384'''Ping from InstaGENI VirginiaTech VM to the InstaGENI GPO VM'''
     385{{{
     386
     387}}}
     388
     3893. The measurements collected for InstaGENI VirginiaTech VM to the PG Utah VM
     390
     391''Collected: 2015-05-XX''
     392
     393'''Iperf InstaGENI VirginiaTech VM to the PG Utah VM (TCP) - TCP window size: 16.0 KB '''
     394
     395__One Client_
     396{{{
     397
     398}}}
     399
     400__Five Clients__
     401{{{
     402
     403}}}
     404
     405__Ten Clients__
     406
     407{{{
     408
     409
     410}}}
     411
     412'''Iperf InstaGENI VirginiaTech VM to the PG Utah VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     413{{{
     414
     415}}}
     416
     417'''Ping from InstaGENI VirginiaTech VM to the PG Utah VM'''
     418{{{
     419
     420}}}
     421
     4224. The measurements collected for InstaGENI VirginiaTech VM to the ExoGENI GPO VM:
     423
     424'''Iperf InstaGENI VirginiaTech VM to the ExoGENI RENCI VM (TCP) - TCP window size: 16.0 KB '''
     425
     426''Collected: 2015-05-XX''
     427
     428__One Client_
     429{{{
     430
     431}}}
     432
     433__Five Clients__
     434{{{
     435
     436}}}
     437
     438__Ten Clients__
     439
     440{{{
     441
     442}}}
     443
     444'''Iperf InstaGENI VirginiaTech VM to the ExoGENI RENCI VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     445{{{
     446
     447}}}
     448
     449'''Ping from InstaGENI VirginiaTech VM to the ExoGENI GPO VM'''
     450{{{
     451
     452}}}
     453
     4546. The measurements collected for InstaGENI VirginiaTech VM to the WAPG Rutgers:
     455
     456''Collected: 2015-05-XX''
     457
     458'''Iperf InstaGENI VirginiaTech VM to the WAPG Rutgers (TCP) - TCP window size: 16.0 KB '''
     459
     460__One Client_
     461{{{
     462
     463}}}
     464
     465__Five Clients__
     466{{{
     467
     468}}}
     469
     470__Ten Clients__
     471{{{
     472
     473}}}
     474
     475'''Iperf InstaGENI VirginiaTech VM to the WAPG Rutgers (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     476{{{
     477
     478}}}
     479
     480'''Ping from InstaGENI VirginiaTech VM to the WAPG Rutgers'''
     481{{{
     482
     483}}}
     484
     485
     486
     487
    14488== IG-CT-5 - Experiment Monitoring ==
     489Reviewed 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.
     490
     491[[Image(VirginiaTech-aggregate.jpg)]]
     492
     493Verified that the FIU compute resources aggregate shows up in the list of aggregates and provides Aggregate Name, Type, Last Update, Version, POP, and Organization:
     494
     495[[Image(VirginiaTech-aggregate-detail.jpg)]]
     496
     497Active slivers:
     498
     499[[Image(VirginiaTech-sliver.jpg)]]
     500
     501List of resources:
     502
     503[[Image(VirginiaTech-resources.jpg)]]
     504Aggregate measurements:
     505
     506[[Image(VirginiaTech-measure.jpg)]]
     507
     508The VirginiaTech InstaGENI FOAM resources aggregate details:
     509
     510[[Image(VirginiaTech-FOAMAggregate.jpg)]]
     511
     512Active !OpenFlow Slivers:
     513
     514[[Image(VirginiaTech-OFSlivers.jpg)]]
     515
     516List of !OpenFlow Resources in use:
     517
     518[[Image(VirginiaTech-OFResources.jpg)]]
     519
     520Monitoring should show Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics and OF Datapath and Sliver Statistics. At the time of this test these measurements were not available.
     521
     522[[Image(VirginiaTech-OFMonitoring.jpg)]]
     523
     524
     525
    15526== IG-CT-6 - Administrative Tests ==
     527
     528Sent request for administrative account to site contact from the [http://groups.geni.net/geni/wiki/GeniAggregate/VirginiaTechInstaGENI VirginiaTech InstaGENI] aggregate page.  Followed instructions at [https://users.emulab.net/trac/protogeni/wiki/RackAdminAccounts Admin Accounts on InstaGeni Racks] page for account request. A local admin account was create and also had to join the ''emulab-ops'' group at https://www.instageni.arc.vt.edu/joinproject.php3?target_pid=emulab-ops.   Once account was create and membership to emulab-ops was approved proceeded to execute administrative tests. 
     529
     530
     531{{{
     532LNM:~$ ssh lnevers@control.instageni.arc.vt.edu
     533
     534}}}
     535
     536Also access the node via the PG Boss alias:
     537{{{
     538LNM:~$ ssh boss.instageni.arc.vt.edu
     539}}}
     540
     541Further verified access by ssh from ops.instageni.gpolab.bbn.com to boss.instageni.gpolab.bbn.com, which is usually restricted for non-admin users:
     542{{{
     543LNM:~$ ssh ops.instageni.arc.vt.edu
     544
     545}}}
     546From boss node accessed each of the experiment nodes that support VMs:
     547{{{
     548[lnevers@boss ~]$ for i in pc1 pc2; do ssh $i "echo -n '===> Host: ';hostname;sudo whoami;uname -a;echo"; done
     549
     550}}}
     551
     552In order to access Dedicated Nodes some experiment must be running on the raw-pc device. At the time of this capture two raw-pc nodes were in use (pcX and pcY):
     553{{{
     554[lnevers@boss ~]$ sudo ssh pcX
     555[root@pcX ~]# sudo whoami
     556root
     557[root@pcX ~]# exit
     558logout
     559Connection to pcX.instageni.arc.vt.edu
     560[lnevers@boss ~]$ sudo ssh pcY
     561[root@pc ~]# sudo whoami
     562root
     563[root@pc ~]#
     564}}}
     565
     566Access infrastructure Switches using documented password. First connect to the switch named procurve1 the control network switch:
     567{{{
     568[lnevers@boss ~]$ sudo more /usr/testbed/etc/switch.pswd
     569XXXXXXXXX
     570[lnevers@boss ~]$ telnet procurve1
     571
     572
     573}}}
     574
     575Connect to the switch named procurve2 the dataplane network switch via ssh using the documented password:
     576{{{
     577[lnevers@boss ~]$ sudo more /usr/testbed/etc/switch.pswd
     578xxxxxxx
     579[lnevers@boss ~]$ ssh manager@procurve2
     580}}}
     581
     582Access the FOAM VM and gather information for version
     583{{{
     584LNM:~$ ssh lnevers@foam.instageni.arc.vt.edu
     585
     586sudo foamctl admin:get-version  --passwd-file=/etc/foam.passwd
     587
     588}}}
     589Check FOAM configuration for  site.admin.email, geni.site-tag, email.from settings:
     590{{{
     591foamctl config:get-value --key="site.admin.email"  --passwd-file=/etc/foam.passwd
     592
     593foamctl config:get-value --key="geni.site-tag"  --passwd-file=/etc/foam.passwd
     594
     595foamctl config:get-value --key="email.from"  --passwd-file=/etc/foam.passwd
     596
     597# check if FOAM auto-approve is on. Value 2 = auto-approve is on.
     598
     599foamctl config:get-value --key="geni.approval.approve-on-creation"  --passwd-file=/etc/foam.passwd
     600
     601}}}
     602
     603Show FOAM slivers and details for one sliver:
     604
     605{{{
     606foamctl geni:list-slivers --passwd-file=/etc/foam.passwd
     607
     608}}}
     609Access the FlowVisor VM and gather version information:
     610{{{
     611
     612ssh lnevers@flowvisor.instageni.arc.vt.edu
     613}}}
     614Check the !FlowVisor version, list of devices, get details for a device, list of active slices, and details for one of the slices:
     615{{{     
     616
     617fvctl --passwd-file=/etc/flowvisor.passwd ping hello
     618
     619# Devices
     620fvctl --passwd-file=/etc/flowvisor.passwd listDevices
     621
     622fvctl --passwd-file=/etc/flowvisor.passwd getDeviceInfo 06:d6:6c:3b:e5:68:00:00
     623
     624#Slices
     625fvctl --passwd-file=/etc/flowvisor.passwd listSlices
     626
     627fvctl --passwd-file=/etc/flowvisor.passwd getSliceInfo 5c956f94-5e05-40b5-948f-34d0149d9182
     628
     629}}}
     630
     631Check the FlowVisor setting:
     632{{{
     633fvctl --passwd-file=/etc/flowvisor.passwd dumpConfig /tmp/flowvisor-config
     634more /tmp/flowvisor-config
     635
     636}}}
     637
     638
     639Verify 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 all alerts have status OK.
     640
     641
     642[[Image(VirginiaTech-nagios.jpg)]]
     643
     644Verify 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 all alerts have status OK.
     645
     646[[Image(VirginiaTech-OF-nagios.jpg)]]
     647
     648
    16649
    17650----