Changes between Version 7 and Version 8 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-3
- Timestamp:
- 05/22/12 19:03:28 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-3
v7 v8 8 8 This section captures the status for each step in the acceptance test plan. 9 9 10 || '''Step''' || '''State''' || '''Date completed''' ||''' Ticket ''' || '''Comments''' ||11 || Step 1 ||[[Color( orange,Blocked)]] || || || Blocked on prerequisite tests completion.||12 || Step 2 || || || || ||13 || Step 3 || || || ||Initial scenario will determine max on 1 Worker Node||14 || Step 4 || || || || ||15 || Step 5 || || |||| ||16 || Step 6 || || || || ||10 || '''Step''' || '''State''' || '''Date completed''' ||''' Ticket ''' || '''Comments''' || 11 || Step 1 ||[[Color(yellow,Complete)]] || || || || 12 || Step 2 || || || || || 13 || Step 3 || || || || || 14 || Step 4 || || || || || 15 || Step 5 ||[[Color(red,Fail)]] || || instaticket:32|| || 16 || Step 6 || || || || || 17 17 || Step 7 || || || || || 18 18 || Step 8 || || || || || … … 25 25 || Step 15 || || || || || 26 26 || Step 16 || || || || || 27 28 To better capture the findings of each 100VM scenario, the following table is added for each scenario tested: 29 30 || ''' Test Scenario''' || '''Results''' || 31 || Scenario 1: 1 Slice with 100 VMs || FAILED || 32 || Scenario 2: 2 Slices with 50 VMs each || FAILED || 33 || Scenario 3: 4 Slices with 25 VMS each || 34 || Scenario 4: 50 Slices with 2 VMs each || 35 || Scenario 5: 100 Slices with 1 VM each || 36 || Scenario 6: 10 Slices with 10 VMs each || 27 37 28 38 [[BR]] … … 61 71 62 72 == Step 1. As Experimenter1, request !ListResources from Utah InstaGENI == 73 Issue the following: 74 {{{ 75 $ ./src/omni.py -a insta-utah listresources --api-version 2 -t GENI 3 -available -o 76 }}} 77 78 Note: "insta-utah is a nick_name for the https://boss.utah.geniracks.net/protogeni/xmlrpc/am/2.0 aggregate 79 63 80 == Step 2. Review !ListResources output, and identify available resources == 81 82 RSpec does not provide insight into what is available. 83 64 84 == Step 3. Write the Scenario 1 RSpec that requests 100 VMs evenly distributed across the experiment nodes using the default image == 85 Created a 100 VM grid scenario. 86 65 87 == Step 4. Create a slice == 88 {{{ 89 $ ./src/omni.py -a insta-utah createslice 100vmgrid 90 }}} 91 66 92 == Step 5. Create a sliver in the slice, using the RSpec defined in step 3 == 93 Used the following; 94 {{{ 95 $ ./src/omni.py -a insta-utah createsliver 100vmgrid ./instarspec/insta-100vm-grid.rspec --api-version 2 -t GENI 3 96 }}} 97 FAILED: See instaticket:32 98 67 99 == Step 6. Log into several of the VMs, and send traffic to several other systems == 100 FAILED: See instaticket:32 101 68 102 == Step 7. Step up traffic rates to verify VMs continue to operate with realistic traffic loads == 103 FAILED: See instaticket:32 104 69 105 == Step 8. Review system statistics and VM isolation (does not include network isolation) == 106 FAILED: See instaticket:32 107 70 108 == Step 9. Verify that several VMs running on the same experiment node have a distinct MAC address for their interface == 109 FAILED: See instaticket:32 110 71 111 == Step 10. Verify for several VMs running on the same experiment node, that their MAC addresses are learned on the data plane switch == 112 FAILED: See instaticket:32 113 72 114 == Step 11. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts == 73 115 == Step 12. Stop traffic and delete sliver ==
