wiki:GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3

Version 10 (modified by lnevers@bbn.com, 7 years ago) (diff)

--

EG-EXP-3: ExoGENI 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 ExoGENI Acceptance Test Status page.

Test Status

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

Step State Tickets Comments
Step 1 Color(orange,Blocked)? Current rack configuration allows only 36
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11


State Legend Description
Color(green,Pass)? Test completed and met all criteria
Color(#98FB98,Pass: most criteria)? Test completed and met most criteria. Exceptions documented
Color(red,Fail)? Test completed and failed to meet criteria.
Color(yellow,Complete)? Test completed but will require re-execution due to expected changes
Color(orange,Blocked)? Blocked by ticketed issue(s).
Color(#63B8FF,In Progress)? Currently under test.


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 GPO rack.

Status: Done

Prereq: GENI Experimenter1 account exists.

Status: Done

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

Status: Blocked on prerequisite tests completion.

Test Plan Steps

Step 1. Request ListResources from BBN ExoGENI.

Step 2. Review ListResources output, and identify available resources.

Step 3. Write a RSpec that requests 100 VMs evenly distributed across the worker 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. Review monitoring statistics and check for resource status for CPU, disk, memory utilization, interface counters, uptime, process counts, and active user counts.

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

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

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

Step 11. Stop traffic and delete sliver.