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


Ignore:
Timestamp:
05/14/12 17:00:22 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v2 v3  
    99
    1010|| '''Step''' || '''State'''           || '''Date completed'''    ||''' Ticket ''' || '''Comments''' ||
    11 || Step 1     ||                       ||                         ||               ||                ||
     11|| Step 1     ||[[Color(#63B8FF,In Progress)]]||                         ||               || Requested dedicated node access for 05/15/2012  ||
    1212|| Step 2     ||                       ||                         ||               ||                ||
    1313|| Step 3     ||                       ||                         ||               ||                ||
     
    4040
    4141
     42= Prerequisites =
     43
     44Status for test prerequisites:
     45
     46__Prereq:__ Traffic generation tools may be part of image or installed at experiment runtime.
     47
     48__Status:__ Done: Only using ping with mixed sizes and rates for now.
     49
     50__Prereq:__ Administrative accounts exist for GPO staff on the Utah InstaGENI rack.
     51
     52__Status:__ GPO as administrative account on InstaGENI Rack.
     53
     54__Prereq:__ GENI Experimenter1 account exists. 
     55
     56__Status:__ DONE, will use credentials for lnevers@bbn.com.
     57
     58__Prereq:__ Baseline Monitoring is in place for the entire Utah site, to ensure that any problems are quickly identified.
     59
     60__Status:__ Blocked on prerequisite tests completion.
     61
    4262
    4363= Test Plan Steps =
    4464
    45  1. As Experimenter1, request !ListResources from Utah InstaGENI.
    46  2. Review !ListResources output, and identify available resources.
    47  3. Write the Scenario 1 RSpec that requests 100 VMs evenly distributed across the experiment nodes using the default image.
    48  4. Create a slice.
    49  5. Create a sliver in the slice, using the RSpec defined in step 3.
    50  6. Log into several of the VMs, and send traffic to several other systems.
    51  7. Step up traffic rates to verify VMs continue to operate with realistic traffic loads.
    52  8. Review system statistics and VM isolation (does not include network isolation)
    53  9. Verify that several VMs running on the same experiment node have a distinct MAC address for their interface.
    54  10. Verify for several VMs running on the same experiment node, that their MAC addresses are learned on the data plane switch.
    55  11. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts.
    56  12. Stop traffic and delete sliver.
    57  13. Re-execute the procedure described in steps 1-12 with changes required for Scenario 2 (2 Slices with 50 VMs each).
    58  14. Re-execute the procedure described in steps 1-12 with changes required for Scenario 3 (4 Slices with 25 VMS each).
    59  15. Re-execute the procedure described in steps 1-12 with changes required for Scenario 4 (50 Slices with 2 VMs each).
    60  16. Re-execute the procedure described in steps 1-12 with changes required for Scenario 5 (100 Slices with 1 VM each).
     65== Step 1. As Experimenter1, request !ListResources from Utah InstaGENI ==
     66== Step 2. Review !ListResources output, and identify available resources ==
     67== Step 3. Write the Scenario 1 RSpec that requests 100 VMs evenly distributed across the experiment nodes using the default image ==
     68== Step 4. Create a slice ==
     69== Step 5. Create a sliver in the slice, using the RSpec defined in step 3 ==
     70== Step 6. Log into several of the VMs, and send traffic to several other systems ==
     71== Step 7. Step up traffic rates to verify VMs continue to operate with realistic traffic loads ==
     72== Step 8. Review system statistics and VM isolation (does not include network isolation) ==
     73== Step 9. Verify that several VMs running on the same experiment node have a distinct MAC address for their interface ==
     74== Step 10. Verify for several VMs running on the same experiment node, that their MAC addresses are learned on the data plane switch ==
     75== Step 11. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts ==
     76== Step 12. Stop traffic and delete sliver ==
     77== Step 13. Re-execute the procedure described in steps 1-12 with changes required for Scenario 2 (2 Slices with 50 VMs each) ==
     78== Step 14. Re-execute the procedure described in steps 1-12 with changes required for Scenario 3 (4 Slices with 25 VMS each) ==
     79== Step 15. Re-execute the procedure described in steps 1-12 with changes required for Scenario 4 (50 Slices with 2 VMs each) ==
     80== Step 16. Re-execute the procedure described in steps 1-12 with changes required for Scenario 5 (100 Slices with 1 VM each) ==
    6181