Changes between Version 24 and Version 25 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3
- Timestamp:
- 12/06/12 14:39:45 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3
v24 v25 23 23 || Step 3 ||[[Color(yellow,Complete)]]|| || || 24 24 || Step 4 ||[[Color(yellow,Complete)]]|| || || 25 || Step 5 ||[[Color( orange,Blocked)]] || || ||26 || Step 6 || 25 || Step 5 ||[[Color(#63B8FF,In Progress)]] || || || 26 || Step 6 ||[[Color(yellow,Complete)]]|| || || 27 27 || Step 7 || || || || 28 || Step 8 || || || || 29 || Step 9 || || || || 30 || Step 10 || || || || 31 || Step 11 || || || || 32 28 || Step 8 ||[[Color(yellow,Complete)]]|| || || 29 || Step 9 ||[[Color(yellow,Complete)]]|| || || 30 || Step 10 ||[[Color(#63B8FF,In Progress)]]|| ||Not executed in initial test runs|| 31 || Step 11 ||[[Color(#63B8FF,In Progress)]]|| ||Not executed in initial test runs|| 32 || Step 12 ||[[Color(#63B8FF,In Progress)]]|| ||exoticket:134|| 33 || Step 13 ||[[Color(#63B8FF,In Progress)]]|| ||exoticket:134|| 34 || Step 14 ||[[Color(#63B8FF,In Progress)]]|| ||exoticket:134|| 35 || Step 15 || || ||100 VMs in one sliver from one aggregate not supported|| 36 || Step 16 || || || || 33 37 34 38 [[BR]] … … 102 106 This step cannot be executed for 100 VM in one sliver, due to the resource allocation which is 50/50 between the local BBN SM and the global ExoSM. Based on the allocation, the test case description was modified to create two slivers, where each has 50 VMs in the BBN Rack, with one request to the BBN SM and one request to the ExoSM. 103 107 104 '''NOTE:''' Rspecs with 50 VMs have not been tests, but other scenarios have been tested and are covered in this page.108 '''NOTE:''' Rspecs with 50 VMs have not yes been tested, but other scenarios have been tested and are covered in this page. 105 109 106 110 To set up a sliver in the BBN rack that is created via the ExoSM, this type of command is used: … … 124 128 == Step 9. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts. == 125 129 126 == Step 8. Verify that several VMs running on the same worker node have a distinct MAC address for their interface. ==130 == Step 10. Verify that several VMs running on the same worker node have a distinct MAC address for their interface. == 127 131 Allocated VMs have unique MAC addresses. 128 132 129 == Step 9. Verify for several VMs running on the same worker node, that their MAC addresses are learned on the data plane switch. ==133 == Step 11. Verify for several VMs running on the same worker node, that their MAC addresses are learned on the data plane switch. == 130 134 131 135 The successful exchange of traffic on the dataplane interface shows that are learned on data plane switch. 132 136 133 == Step 1 0. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts. ==137 == Step 12. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts. == 134 138 This step is replaced by iperf for ExoGENI test cases. Not yet completed during scalability tests. 135 139 136 == Step 1 1. Stop traffic and delete sliver. ==140 == Step 13. Stop traffic and delete sliver. == 137 141 Slivers are deleted as follows throughout testing: 138 142 {{{ … … 141 145 }}} 142 146 143 == Step 1 2. Re-execute procedure in steps 1-11with changes required for Test 1: 10 slivers with 10 VMs each ==147 == Step 14. Re-execute procedure in steps 1-13 with changes required for Test 1: 10 slivers with 10 VMs each == 144 148 145 149 This experiment was setup at the RENCI ExoGENI rack using the RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/ExoGENI/Spiral4/Rspecs/AcceptanceTests/EG-EXP-3/exo-10vm-rci.rspec exo-10vm-rci.rspec] for both RENCI SM and ExoSM. The following slices were created: … … 179 183 Slivers were deleted upon completion. 180 184 181 == Step 13. Re-execute procedure in steps 1-1 1with changes required for Test 2: 4 slivers w/20VMS +2 slivers w/10 VMs ==182 183 184 == Step 14. Re-execute procedure in steps 1-1 1with changes required for Test 3: 20 slivers with 5 VMs each ==185 == Step 13. Re-execute procedure in steps 1-13 with changes required for Test 2: 4 slivers w/20VMS +2 slivers w/10 VMs == 186 187 188 == Step 14. Re-execute procedure in steps 1-13 with changes required for Test 3: 20 slivers with 5 VMs each == 185 189 186 190 In initial run no traffic was exchanged, and logins were only tried on a few nodes. … … 189 193 190 194 191 == Step 15. Re-execute procedure in steps 1-11 with changes required for Test 4: 100 Sliver with 1 VM == 192 193 == Step 14. Re-execute procedure in steps 1-11 with changes required for Test 5: 1 slivers with 100 VMs == 194 195 == Step 14. Re-execute procedure in steps 1-11 with changes required for Test 6: 2 slivers with 50 VMs each == 196 195 == Step 15. Re-execute procedure in steps 1-13 with changes required for Test 4: 100 Sliver with 1 VM == 196 197 == Step 16. Re-execute procedure in steps 1-13 with changes required for Test 5: 1 slivers with 100 VMs == 198 199 Not supported due to current allocation 200 201 == Step 17. Re-execute procedure in steps 1-13 with changes required for Test 6: 2 slivers with 50 VMs each == 202
