IG-EXP-3: InstaGENI Single Site 100 VM Test

This page captures status for the test case EG-EXP-3, which verifies the ability to support 100 VM in one rack. For overall status see the InstaGENI Acceptance Test Status page.

Test Status

This section captures the status for each step in the acceptance test plan.

Step	State	Date completed	Ticket	Comments
Step 1	Color(#63B8FF,In Progress)?			Requested dedicated node access for 05/15/2012
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16

State Legend	Description
Color(green,Pass)?	Test completed and met all criteria
Color( #98FB98, #100000 , Pass)?	Test completed and met most criteria. Exceptions documented
Color( #F0FFF0, #100000 , Complete)?	Test completed but requiring re-execution due to expected changes
Color( #B0E0E6, #100000 , Complete)?	Test completed with workaround for ticketed issue(s)
Color(#CAE1FF,Workaround)?	Test in progress with workaround for ticketed issue(s).
Color(#63B8FF,In Progress)?	Currently under test.
Color(red,Fail)?	Test completed and failed to meet criteria.
Color(orange,Blocked)?	Blocked by ticketed issue(s).

Prerequisites

Status for test prerequisites:

Prereq: Traffic generation tools may be part of image or installed at experiment runtime.

Status: Done: Only using ping with mixed sizes and rates for now.

Prereq: Administrative accounts exist for GPO staff on the Utah InstaGENI rack.

Status: GPO as administrative account on InstaGENI Rack.

Prereq: GENI Experimenter1 account exists.

Status: DONE, will use credentials for ​lnevers@bbn.com.

Prereq: Baseline Monitoring is in place for the entire Utah site, to ensure that any problems are quickly identified.

Status: Blocked on prerequisite tests completion.

Test Plan Steps

Step 1. As Experimenter1, request ListResources from Utah InstaGENI

Step 2. Review ListResources output, and identify available resources

Step 3. Write the Scenario 1 RSpec that requests 100 VMs evenly distributed across the experiment nodes using the default image

Step 4. Create a slice

Step 5. Create a sliver in the slice, using the RSpec defined in step 3

Step 6. Log into several of the VMs, and send traffic to several other systems

Step 7. Step up traffic rates to verify VMs continue to operate with realistic traffic loads

Step 8. Review system statistics and VM isolation (does not include network isolation)

Step 9. Verify that several VMs running on the same experiment node have a distinct MAC address for their interface

Step 10. Verify for several VMs running on the same experiment node, that their MAC addresses are learned on the data plane switch

Step 11. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts

Step 12. Stop traffic and delete sliver

Step 13. Re-execute the procedure described in steps 1-12 with changes required for Scenario 2 (2 Slices with 50 VMs each)

Step 14. Re-execute the procedure described in steps 1-12 with changes required for Scenario 3 (4 Slices with 25 VMS each)

Step 15. Re-execute the procedure described in steps 1-12 with changes required for Scenario 4 (50 Slices with 2 VMs each)

Step 16. Re-execute the procedure described in steps 1-12 with changes required for Scenario 5 (100 Slices with 1 VM each)