| 1 | |
| 2 | = EG-EXP-3: ExoGENI Single Site 100 VM Test = |
| 3 | |
| 4 | This page captures status for the test case EG-EXP-3, which verifies the ability to support 100 VM in one rack. |
| 5 | |
| 6 | |
| 7 | = Test Status = |
| 8 | This section captures the status for each step in the acceptance test plan. |
| 9 | |
| 10 | || '''Step''' || '''State''' || '''Date completed''' ||''' Ticket ''' || '''Comments''' || |
| 11 | || Step 1 || || || || || |
| 12 | || Step 2 || || || || || |
| 13 | || Step 3 || || || || || |
| 14 | || Step 4 || || || || || |
| 15 | || Step 5 || || || || || |
| 16 | || Step 6 || || || || || |
| 17 | || Step 7 || || || || || |
| 18 | || Step 8 || || || || || |
| 19 | || Step 9 || || || || || |
| 20 | || Step 10 || || || || || |
| 21 | || Step 11 || || || || || |
| 22 | |
| 23 | |
| 24 | || ''Status Legend'' || ''Description '' || |
| 25 | || || |
| 26 | || [[Color(green,Pass)]] || Completed and met criteria || |
| 27 | || [[Color(red,Fail)]] || Completed and failed to meet criteria || |
| 28 | || [[Color(orange,Blocked)]] || Blocked by ticketed issue || |
| 29 | || In progress || Currently under test || |
| 30 | |
| 31 | = Test Plan Steps = |
| 32 | |
| 33 | 1. Request !ListResources from BBN ExoGENI. |
| 34 | 2. Review !ListResources output, and identify available resources. |
| 35 | 3. Write a RSpec that requests 100 VMs evenly distributed across the worker nodes using the default image. |
| 36 | 4. Create a slice. |
| 37 | 5. Create a sliver in the slice, using the RSpec defined in step 3. |
| 38 | 6. Log into several of the VMs, and send traffic to several other systems. |
| 39 | 7. Step up traffic rates to verify VMs continue to operate with realistic traffic loads. |
| 40 | 8. Review system statistics and VM isolation (does not include network isolation) |
| 41 | 9. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts. |
| 42 | 8. Verify that several VMs running on the same worker node have a distinct MAC address for their interface. |
| 43 | 9. Verify for several VMs running on the same worker node, that their MAC addresses are learned on the data plane switch. |
| 44 | 10. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts. |
| 45 | 11. Stop traffic and delete sliver. |