Changes between Version 13 and Version 14 of GENIRacksHome/AcceptanceTests/InstageniAcceptanceTestsPlan


Ignore:
Timestamp:
04/13/12 16:08:18 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/AcceptanceTests/InstageniAcceptanceTestsPlan

    v13 v14  
    182182=== IG-EXP-3: InstaGENI Single Site 100 VM Test ===
    183183
    184 This one site test runs on the Utah InstaGENI rack and includes one experiment to validate compute resource requirements for VMs. The goal of this test is not to validate the InstaGENI limits, but simply to verify that the InstaGENI rack can provide 100 VMs with its experiment nodes.  This test will evenly distribute the VM requests across the available experiment nodes.
     184This one site test runs on the Utah InstaGENI rack and includes various scenarios to validate compute resource requirements for VMs. The goal of this test is not to validate the InstaGENI limits, but simply to verify that the InstaGENI rack can provide 100 VMs with its experiment nodes under various scenarios, including:
     185 * Scenario 1: 1 Slice with 100 VMs
     186 * Scenario 2: 2 Slices with 50 VMs each
     187 * Scenario 3: 4 Slices with 25 VMS each
     188 * Scenario 4: 50 Slices with 2 VMs each
     189 * Scenario 5: 100 Slices with 1 VM each
     190
     191If Scenario 1 does not work, tests will be run to determine the maximum number of VMs allowed in one slice. In the event that the  maximum number of VMs allowed in one slice is less than 50 VMs, than scenario 2 will not be executed. This test will evenly distribute the VM requests across the available experiment nodes for each scenario.
    185192
    186193==== Test Topology ====
     
    194201
    195202 * Traffic generation tools may be part of image or installed at experiment runtime.
    196  * Administrative accounts exist for GPO staff on the Utah InstGENI rack.
     203 * Administrative accounts exist for GPO staff on the Utah InstaGENI rack.
    197204 * GENI Experimenter1 account exists. 
    198205 * Baseline Monitoring is in place for the entire Utah site, to ensure that any problems are quickly identified.
     
    202209Do the following:
    203210
    204  1. Request !ListResources from Utah InstaGENI.
     211 1. As Experimenter1, request !ListResources from Utah InstaGENI.
    205212 2. Review !ListResources output, and identify available resources.
    206  3. Write a RSpec that requests 100 VMs evenly distributed across the experiment nodes using the default image.
     213 3. Write the Scenario 1 RSpec that requests 100 VMs evenly distributed across the experiment nodes using the default image.
    207214 4. Create a slice.
    208215 5. Create a sliver in the slice, using the RSpec defined in step 3.
     
    214221 11. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts.
    215222 12. Stop traffic and delete sliver.
     223 13. Re-execute the procedure described in steps 1-12 with changes required for Scenario 2 (2 Slices with 50 VMs each).
     224 14. Re-execute the procedure described in steps 1-12 with changes required for Scenario 3 (4 Slices with 25 VMS each).
     225 15. Re-execute the procedure described in steps 1-12 with changes required for Scenario 4 (50 Slices with 2 VMs each).
     226 16. Re-execute the procedure described in steps 1-12 with changes required for Scenario 5 (100 Slices with 1 VM each).
    216227
    217228