wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-MON-4

Version 2 (modified by lnevers@bbn.com, 11 years ago) (diff)

--

IG-MON-4: Infrastructure Device Performance Test

This page captures status for the test case IG-MON-4, which verifies that the rack head node performs well enough to run all the services it needs to run while OpenFlow and non-OpenFlow experiments are running. For overall status see the InstaGENI Acceptance Test Status page.

Last update: 2013/01/29

Test Status

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

StepState Ticket Notes
Step 1
Step 2
Step 3

[BR]]

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.


Test Plan Steps

This test cases sets up several experiments to generate resource usage for both compute and network resources in an InstaGENI Rack. The rack used is the GPO rack and the following experiments are set up before head node device performance is reviewed:

  • IG-MON-4-exp1: IG GPO non-OpenFlow experiment with 10 VM nodes, all nodes exchanging TCP traffic.
  • IG-MON-4-exp2: IG GPO non-OpenFlow experimetn with 1 VM and one dedicated raw-pc, both exchanging traffic with iperf
  • IG-MON-4-exp3: IG GPO OpenFlow experiment with 2 nodes in rack exchanging traffic with 2 site GPO OpenFlow campus resources.
  • IG-MON-4-exp4: IG GPO OpenFlow experiment with 2 nodes exchanging traffic with 2 remote IG Utah OpenFlow nodes.

The setup of the experiments above is not captured in this test case, but the Rspec are available [here]. While the 4 experiments involving FOAM-controlled OpenFlow slivers and compute slivers are running, execute the steps below.

1. View OpenFlow control monitoring at GMOC and verify that no monitoring data is missing

2. View VLAN 1750 data plane monitoring

Verify the VLAN 1750 data plane monitoring which pings the rack's interface on VLAN 1750, and verify that packets are not being dropped

3. Verify CPU idle percentage on the server host and the FOAM VM are both nonzero

Attachments (1)

Download all attachments as: .zip