Changes between Version 37 and Version 38 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-3


Ignore:
Timestamp:
08/21/12 14:18:31 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-3

    v37 v38  
    174174== Step 15. Re-execute the procedure described in steps 1-12 with changes required for Scenario 4 (50 Slices with 2 VMs each) ==
    175175
    176 Successfully execute this scenario and was able to login to several of the VMs and exchange traffic. Final allocation distribution was applied as follows on the two pcshared nodes:
     176Successfully execute this scenario in 06/01/12 and was able to login to several of the VMs and exchange traffic. Final allocation distribution was applied as follows on the two pcshared nodes:
    177177
    178178    * 58 VMs on pc3
     
    181181The Request RSpec for the 2VM slivers can be found [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-3/insta-2vm-v3.rspec here]
    182182
     183''__08/21/12 test run__''
     184
     185Re-executed procedure on 08/21/12 and was once again able to reserve 100 VMS (50 slices with 2 VMs each). Final allocation distribution was applied as follows on the three pcshared nodes:
     186   * 38 VMs on pc5
     187   * 34 VMs on pc3
     188   * 28 VMs on pc1.
     189
     190Extended the test to 150 WMs could be reserved with 75 slivers, and added 25 more slices to the 08/21/12 run. The resulting allocation:
     191   * 42 VMs on pc5
     192   * 50 VMs on pc3
     193   * 58 VMs on pc1.
     194
     195Ran the GCF script ''readyToLogin.py''  to determine access information for the 150 VMs allocated:
     196{{{
     197j=1
     198while [ $j -le 75 ];
     199do
     200./examples/readyToLogin.py 2vmslice$j -a ig-utah
     201sleep 2;
     202j=`expr $j + 1`
     203done
     204}}}
     205
     206The readyToLogin script is part of the GCF examples directory and provides login information for active slivers, which looks as follows:
     207{{{
     208 $ ./examples/readyToLogin.py 2vmslice1 -a ig-utah -q
     209   ================================================================================
     210   Aggregate [http://utah.geniracks.net/protogeni/xmlrpc/am] has a ProtoGENI sliver.
     211
     212
     213   pc3.utah.geniracks.net's geni_status is: ready
     214  Login using:
     215        xterm -e ssh -i ~/.ssh/id_rsa lnevers@pc3.utah.geniracks.net -p 30778 &
     216
     217   pc3.utah.geniracks.net's geni_status is: ready
     218   Login using:
     219        xterm -e ssh -i ~/.ssh/id_rsa lnevers@pc3.utah.geniracks.net -p 30779 &
     220
     221  ================================================================================
     222}}}
     223
    183224== Step 16. Re-execute the procedure described in steps 1-12 with changes required for Scenario 5 (100 Slices with 1 VM each) ==
    184225