Changes between Version 20 and Version 21 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-5


Ignore:
Timestamp:
08/24/12 10:35:54 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-5

    v20 v21  
    7474}}}
    7575
    76 == 1. As Experimenter1, Determine BBN compute resources and define RSpec ==
     76== 1. As Experimenter1 (lnevers@bbn.com), determine PG site compute resources and define RSpec ==
    7777
    7878Collect list resources from InstaGENI compute and network aggregate managers.
    … …  
    8484}}}
    8585
     86Defined the [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-pg-site.rspec IG-EXP-5-exp1-pg-site.rspec] file to request the ProtoGENI site compute resources request.
     87
     88
    8689== 2. Determine remote meso-scale compute resources and define RSpec ==
    8790
    88 The Rspecs defined for the 3 meso-scale sites:
    89 
    90    - 1 WAPG node (pg51) at Rutgers Site via Internet2
    91    - 1 MyPLC node (planetlab4.clemson.edu) at Clemson Site via NLR
    92    - 1 MyPLC node (navis.gpolab.bbn.com) at BBN Site Via NLR
    93 
    94 == 3. Define a request RSpec for !OpenFlow network resources at the BBN InstaGENI AM ==
    95 
    96 Defined the RSpec for the Utah !OpenFlow switch in the ExoGENI rack to the core VLAN 3716. The following RSPecx were used:
    97 
    98  * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-openflow-ig.rspec IG-EXP-5-openflow-ig.rspec] - Utah InstaGENI Rack FOAM Aggregate network resource request RSpec.
    99  * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-compute-ig.rspec IG-EXP-5-compute-ig.rspec] - Utah InstaGENI Rack FOAM Aggregate Network resources request Rspec.
    100  * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-compute-pg.rspec IG-EXP-5-compute-pg.rspec] - Utah ProtoGENI FOAM Aggregate Network resources request Rspec.
     91The RSpecs for experiment 1 are defined for the meso-scale sites at Rutgers, where one WAPG node (pg51) is used via Internet2
     92
     93
     94== 3. Define a request RSpec for !OpenFlow network resources at the InstaGENI AM ==
     95
     96Defined the RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-ig.rspec IG-EXP-5-exp1-openflow-ig.rspec] for the Utah InstaGENI FOAM Aggregate to allow the site PG site compute resources to access the core VLAN 3716.
    10197
    10298== 4. Define a request RSpec for !OpenFlow network resources at the remote I2 Meso-scale site ==
    10399
    104 An RSpec was defined for each site FOAM aggregate and compute resources aggregate.  The following RSpec were used for the meso-scale sites:
    105   * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-wapg-rutgers.rspec IG-EXP-5-wapg-rutgers.rspec] - Rutgers WAPG nodes pg51 compute resource request RSpec.
    106   * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-openflow-rutgers.rspec IG-EXP-5-openflow-rutgers.rspec] - Rutgers FOAM Aggregate network resource request RSpec.
    107   * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-myplc-clemson.rspec IG-EXP-5-myplc-clemson.rspec] - Clemson MyPLC node planetlab4 compute resource request RSpec.
    108   * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-openflow-clemson.rspec IG-EXP-5-openflow-clemson.rspec] - Clemson FOAM Aggregate network resource request RSpec.
    109   * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-myplc-bbn.rspec IG-EXP-5-myplc-bbn.rspec] - BBN MyPLC node navis compute resource request RSpec.
    110   * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-openflow-bbn.rspec IG-EXP-5-openflow-bbn.rspec] - BBN FOAM Aggregate network resource request RSpec.
     100RSpecs were defined for Rutgers FOAM aggregate and WAPG compute resource.  The following RSpecs were used for the meso-scale site:
     101
     102  * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-pg-site.rspec IG-EXP-5-exp1-XXXX.rspec] - Rutgers WAPG nodes pg51 compute resource request RSpec.
     103
     104  * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-rutgers.rspec IG-EXP-5-exp1-openflow-rutgers.rspec] - Rutgers FOAM Aggregate network resource request RSpec.
    111105
    112106== 5. Define a request RSpec for the !OpenFlow Core resources ==
    113107
    114 The OF core resources for VLAN 3716 were defined as follows:
    115  
    116  * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-openflow-i2.rspec IG-EXP-5-openflow-i2.rspec] - Internet2 Core FOAM Aggregate network resources request RSpec.
    117  * [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-openflow-nlr.rspec IG-EXP-5-openflow-nlr.rspec] - NLR Core FOAM Aggregate network resources request RSpec.
     108The file [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp1-openflow-i2.rspec IG-EXP-5-exp1-openflow-i2.rspec] defines the  Internet2 Core FOAM Aggregate network resources request RSpec.
    118109
    119110== 6. Create the first slice ==
    … …  
    121112Created the first slice as with GPO ProtoGENI credentials:
    122113{{{
    123 omni.py createslice IG-EXP-5
     114 $ omni.py createslice IG-EXP-5-exp1
    124115}}}
    125116== 7. Create a sliver for the BBN compute resources ==
    … …  
    128119 
    129120{{{
    130 omni.py -a pg createsliver IG-EXP-5 IG-EXP-5-compute-pg.rspec
    131 }}}
     121 $ omni.py -a pg createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-pg-site.rspec
     122}}}
     123
    132124== 8. Create a sliver at the I2 meso-scale site using FOAM at site ==
    133125Created a sliver at the Rutgers FOAM for VLAN 3716:
    134126{{{
    135  ./src/omni.py -a of-rutgers createsliver IG-EXP-5-scenario1 IG-EXP-5-openflow-rutgers.rspec
    136 
    137 }}}
    138 == 9. Create a sliver at of the BBN InstaGENI AM ==
    139 Created slivers at:
    140  - InstaGENI rack compute resource aggregate
    141  - InstaGENI rack FOAM network resource aggregate
     127 $ omni.py -a of-rutgers createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-openflow-rutgers.rspec
     128}}}
     129
     130== 9. Create a sliver at of the Utah InstaGENI AM ==
     131
     132Created slivers at the InstaGENI rack FOAM network resource aggregate
    142133 
    143134{{{
    144 omni.py -a ig createsliver IG-EXP-5 IG-EXP-5-compute-ig.rspec
    145 omni.py -a of-ig createsliver IG-EXP-5 IG-EXP-5-openflow-ig.rspec
    146 }}}
    147 
    148 To login to the compute resources above determine the following:
    149 {{{
    150 omni.py -a ig sliverstatus IG-EXP-5 -o
    151 egrep "hostname|port" IG-EXP-5-sliverstatus-utah-geniracks-net-protogeni.json
     135 $ omni.py -a of-ig createsliver IG-EXP-5-exp1 IG-EXP-5-exp1-openflow-ig.rspec
    152136}}}
    153137
    … …  
    156140Created slivers at Internet2 and NLR FOAM network resource aggregate:
    157141{{{
    158 omni.py -a of-i2 createsliver IG-EXP-5 IG-EXP-5-openflow-i2.rspec
    159 omni.py -a of-nlr createsliver IG-EXP-5 IG-EXP-5-openflow-nlr.rspec
     142 $ omni.py -a of-i2 createsliver IG-EXP-5-exp1 G-EXP-5-exp1-openflow-i2.rspec
    160143}}}
    161144
    162145== 10a. Create a sliver for all remaining Meso-scale compute and network resources ==
    163 The following slivers were created:
    164 {{{
    165 omni.py -a pg2 createsliver IG-EXP-5 --api-version 2 -t GENI 3 IG-EXP-5-wapg-rutgers.rspec
    166 omni.py -a of-rutgers createsliver IG-EXP-5 IG-EXP-5-openflow-rutgers.rspec
    167 omni.py -a plc-clemson createsliver IG-EXP-5 IG-EXP-5-myplc-clemson.rspec
    168 omni.py -a of-clemson createsliver IG-EXP-5 IG-EXP-5-openflow-clemson.rspec
    169 omni.py -a plc-bbn createsliver IG-EXP-5 IG-EXP-5-myplc-bbn.rspec
    170 omni.py -a of-bbn createsliver IG-EXP-5 IG-EXP-5-openflow-bbn.rspec
     146
     147WAPG nodes are part of the Utah PG aggregate, therefore a second request to add a resource does not work. Also modify sliver is not an available feature at this time, so this step is modified to create a second slice for experiment1. In order to create a second request at the PG site the following slice and sliver were created for the Rutgers WAPG node:
     148{{{
     149 $ omni.py createslice IG-EXP-5-exp1a
     150 $ omni.py -a pg2 createsliver IG-EXP-5-exp1a --api-version 2 -t GENI 3 IG-EXP-5-exp1-rutgers-wapg.rspec
    171151}}}
    172152
    173153== 11. Log in to each of the compute resources and send traffic to the other end-point ==
     154
    174155The nodes assigned for compute resources were determined as follows:
    175156{{{
    176 omni.py -a ig sliverstatus IG-EXP-5 -o
    177 omni.py -a of-ig sliverstatus IG-EXP-5 -o
    178 omni.py -a of-i2 sliverstatus IG-EXP-5 -o
    179 omni.py -a pg2  sliverstatus IG-EXP-5 -o
    180 omni.py -a plc-clemson  sliverstatus IG-EXP-5 -o
    181 omni.py -a plc-bbn  sliverstatus IG-EXP-5 -o
    182 }}}
    183 The above created output files named IG-EXP-5-sliverstatus-SITENAME.json from which the assigned hosts can be determined:
    184 {{{
    185 egrep "hostname" IG-EXP-5-sliverstatus-SITENAME.json
    186 }}}
    187 
    188 For this experiment, local PG resources were also configured to be allowed on VLAN 1750 thorough the InstaGENI rack, the following sliver was created:
    189 {{{
    190 omni.py -a pg createsliver IG-EXP-5 IG-EXP-5-compute-pg.rspec
    191 }}}
    192 To login to this resource, determined access details as follows:
    193 {{{
    194 omni.py -a pg sliverstatus IG-EXP-5 -o
    195 egrep "hostname|port" IG-EXP-5-sliverstatus-utah-geniracks-net-protogeni.json
     157$ omni.py -a pg2  sliverstatus IG-EXP-5-exp1 --api-version 2 -t GENI 3 -o
     158$ omni.py -a pg  sliverstatus IG-EXP-5-exp1a -o
     159}}}
     160The above created output files from which the assigned hosts can be determined:
     161{{{
     162 $ egrep "hostname" IG-EXP-5-sliverstatus-SITENAME.json
     163}}}
     164Or you me also use the gcf/examples/readyToLogin.py script:
     165{{{
     166$ ./examples/readyToLogin.py -a pg  IG-EXP-5-exp1 -o
     167INFO:omni:Loading config file omni_config
     168INFO:omni:Using control framework pgeni
     169INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+IG-EXP-5-exp1 expires on 2012-08-25 14:09:56 UTC
     170INFO:omni:Substituting AM nickname pg with URL http://www.emulab.net/protogeni/xmlrpc/am, URN unspecified_AM_URN
     171INFO:omni:Status of Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+IG-EXP-5-exp1:
     172INFO:omni:Writing to 'IG-EXP-5-exp1-sliverstatus-www-emulab-net-protogeni.json'
     173INFO:omni:Sliver status for Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+IG-EXP-5-exp1 at AM URL http://www.emulab.net/protogeni/xmlrpc/am
     174INFO:omni:Loading config file omni_config
     175INFO:omni:Using control framework pgeni
     176================================================================================
     177Aggregate [http://www.emulab.net/protogeni/xmlrpc/am] has a ProtoGENI sliver.
     178
     179pc535.emulab.net's geni_status is: ready
     180Login using:
     181        xterm -e ssh -i ~/.ssh/id_rsa lnevers@pc535.emulab.net -p 35642 &
     182================================================================================
    196183}}}
    197184
    198185== 12. Verify that traffic is delivered to target ==
    199 Ping traffic was successfully exchange between each compute resource reserved,
     186Logged in with the following:
     187{{{
     188$ xterm -e ssh -i ~/.ssh/id_rsa lnevers@pc535.emulab.net -p 35642 &
     189}}}
     190
     191Exchanged traffic with the remote meso-scale resource at Rutgers:
     192{{{
     193
     194}}}
    200195
    201196== 13. Review baseline, GMOC, and meso-scale monitoring statistics  ==
    202 No monitoring data available for InstaGENI rack at this time.  Will revisit after GEC14.
    203 
    204 == 14. As Experimenter2, determine BBN compute resources and define RSpec ==
    205 Note: for initial run through of this test only one set of credentials were used
    206 
     197
     198Monitoring status is replaced by iperf tests.
     199
     200== 14. As Experimenter2, determine Utah site compute resources and define RSpec ==
     201
     202As Experimenter2 (lnevers2@bbn.com) defined  XXXX
     203
     204   
    207205== 15. Determine remote meso-scale NLR compute resources and define RSpec ==
    208206
    209 NLR OpenFlow Rspec was defined in step 5.
    210 
    211 == 16. Define a request RSpec for !OpenFlow network resources at the BBN InstaGENI AM ==
    212 
    213 For the initial run which combined the two experiments, these steps were completed above
    214 in step 9.
     207The Clemson site was used as a remote meso-scale site and the file [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-myplc-clemson.rspec IG-EXP-5-myplc-clemson.rspec] captures the Clemson MyPLC node planetlab4 compute resource request.
     208
     209== 16. Define a request RSpec for !OpenFlow network resources at the Utah InstaGENI AM ==
     210
     211Defined the [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-exp2-pg-site.rspec IG-EXP-5-exp2-pg-site.rspec] file to request the ProtoGENI site compute resources request for experiment2.
    215212
    216213== 17. Define a request RSpec for !OpenFlow network resources at the remote NLR Meso-scale site ==
    217214
     215Defined the file [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-openflow-clemson.rspec IG-EXP-5-openflow-clemson.rspec] to capture the Clemson FOAM Aggregate network resource request needed to allow the MyPLC node (planetlab4.clemson.edu) access to the !OpenFlow network core.
     216
    218217== 18. Define a request RSpec for the !OpenFlow Core resources ==
    219 Created sliver at NLR and Internet2 FOAM network resource aggregates:
     218
     219Defined [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-5/IG-EXP-5-openflow-nlr.rspec IG-EXP-5-openflow-nlr.rspec] to capture the NLR Core FOAM Aggregate network resources request.
     220
     221
     222== 19. Create the second slice ==
     223
     224As experimenter2 (lnevers2@bbn.com) created a slice:
     225{{{
     226$ ./src/omni.py createslice IG-EXP-5-exp2
     227}}}
     228
     229== 20. Create a sliver for the Utah compute resources ==
     230Created a sliver for the site resources at the Utah PG as follows:
     231{{{
     232$ omni.py -a pg createsliver IG-EXP-5-exp2 IG-EXP-5-exp2-pg-site.rspec
     233}}}
     234
     235== 21. Create a sliver at the meso-scale site using FOAM at site ==
     236Created a sliver at the Clemson FOAM aggregate requesting the network resources required to allow the MyPLC host to access the !OpenFlow Backbone VLAN 3716:
     237{{{
     238$ ./src/omni.py -a of-clemson createsliver IG-EXP-5-exp2 IG-EXP-5-exp2-openflow-clemson.rspec
     239}}}
     240
     241== 22. Create a sliver at of the Utah InstaGENI AM ==
     242
     243Created slivers at the InstaGENI rack FOAM network resource aggregate to allow the PG site resources to access the !OpenFlow backbone:
     244 
     245{{{
     246 $ omni.py -a of-ig createsliver IG-EXP-5-exp2 IG-EXP-5-exp2-openflow-ig.rspec
     247}}}
     248
     249== 23. Create a sliver for the !OpenFlow resources in the core ==
     250
     251Created sliver at NLR FOAM network resource aggregates:
    220252{{{
    221 omni.py -a of-i2 createsliver IG-EXP-5 IG-EXP-5-openflow-i2.rspec
    222 omni.py -a of-nlr createsliver IG-EXP-5 IG-EXP-5-openflow-nlr.rspec
    223 }}}
    224 
    225 == 19. Create the second slice ==
    226 For the initial run which combined the two experiments, there is no second slice.
    227 
    228 == 20. Create a sliver for the BBN compute resources ==
    229 See step 10a.
    230 
    231 == 21. Create a sliver at the meso-scale site using FOAM at site ==
    232 See step 10a.
    233 
    234 == 22. Create a sliver at of the BBN InstaGENI AM ==
    235 
    236 See step 9.
    237 
    238 == 23. Create a sliver for the !OpenFlow resources in the core ==
    239 
    240 See step 10.
     253 $ omni.py -a of-nlr createsliver IG-EXP-5-exp2 IG-EXP-5-exp2-openflow-nlr.rspec 
     254}}}
    241255
    242256== 24. Create a sliver for the meso-scale compute resources ==
    243 
    244 See step 10a.
     257Requested the MyPLC node xXX at the Clemson resource aggregate:
     258
     259{{{
     260$ $ ./src/omni.py -a plc-clemson createsliver IG-EXP-5-exp2 IG-EXP-5-exp2-myplc-clemson.rspec 
     261}}}
    245262
    246263== 25. Log in to each of the compute resources and send traffic to the other endpoint ==
    247264
     265Verify the status for each compute resource sliver, and use login information when ready:
     266{{{
     267$ omni.py -a plc-clemson  sliverstatus IG-EXP-5-exp1 -o
     268$ omni.py -a pg sliverstatus IG-EXP-5-exp1 -o
     269}}}
     270Used the readToLogin.py script to determine state and login:
     271{{{
     272$ ./examples/readyToLogin.py -a pg IG-EXP-5-exp2
     273....
     274================================================================================
     275Aggregate [http://www.emulab.net/protogeni/xmlrpc/am] has a ProtoGENI sliver.
     276
     277
     278pc496.emulab.net's geni_status is: notready
     279Login using:
     280        xterm -e ssh -i /home/lnevers2/.ssh/geni_key lnevers2@pc496.emulab.net -p 35898 &
     281
     282================================================================================
     283$ ./examples/readyToLogin.py -a plc-clemson IG-EXP-5-exp2
     284...
     285================================================================================
     286Aggregate [http://myplc.clemson.edu:12346/] has a PlanetLab sliver.
     287
     288planetlab4.clemson.edu's geni_status is: ready (pl_boot_state:boot)
     289Login using:
     290        xterm -e ssh -i /home/lnevers2/.ssh/geni_key pgenigpolabbbncom_IGEXP5exp2@planetlab4.clemson.edu &
     291
     292================================================================================
     293}}}
     294
    248295Was able to exchange ping traffic between each of the compute resources.
     296
     297At PG site resource:
     298{{{
     299[lnevers2@utah-pg ~]$ ping 10.42.11.104
     300}}}
     301
     302At Clemson MyPLC site:
     303{{{
     304[lnevers2@utah-pg ~]$ ping 10.42.11.104
     305}}}
     306
    249307
    250308== 26. As Experimenter2, insert flowmods and send packet-outs only for traffic assigned to the slivers ==