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

Version 9 (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


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 traffic.
  • IG-MON-4-exp2: IG GPO non-OpenFlow experiment with 1 VM and one dedicated raw-pc, both exchanging traffic.
  • 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 [insert_link_here]. Also traffic levels and types will be captured when this test is run.

In addition to the 4 experiment listed above the following experiments were running on the GPO IG rack: [Insert_capture for https://boss.instageni.gpolab.bbn.com/showexp_list.php3]

Scenario 1: Mix of experiments

The first head node monitoring scenario was captured while the rack had 27 nodes allocated:

No image "XXX.jpg" attached to GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-MON-4

On the Head node the system was mostly idle:

[lnevers@boss ~]$ top
last pid:  6455;  load averages:  0.05,  0.11,  0.13                                               up 48+22:16:24  15:19:20
140 processes: 1 running, 138 sleeping, 1 zombie
CPU:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
Mem: 384M Active, 1241M Inact, 187M Wired, 25M Cache, 93M Buf, 162M Free
Swap: 2047M Total, 2420K Used, 2045M Free

[lnevers@boss ~]$ ps -eao pcpu,pid,user,args | sort -r -k1   
 %CPU   PID USER    COMMAND
  0.0 95092 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 95089 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 95086 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 95084 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 95083 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 95045 elabman dbus-launch --autolaunch=05f048b1db6b246dc4dcc41b00014cac --binary-syntax --close-stderr
  0.0 95028 elabman emacs
  0.0 94997 elabman bash -login
  0.0 91498 elabman bash -login
  0.0 90045 elabman bash -login
  0.0 84248 elabman ssh pc1
  0.0 83886 elabman bash -login
  0.0 68989 elabman mysql geni-cm
  0.0 55878 elabman emacs
  0.0 49903 root    tcppd (perl5.12.4)
  0.0 39666 elabman mysql tbdb
  0.0 38352 elabman mysql tbdb
  0.0 33963 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 33959 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 33956 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 33954 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 33953 elabman /usr/X11R6/bin/bash --noediting -i
  0.0 25286 elabman emacs -nw GeniCM.pm.in
  0.0 16663 elabman bash -login
  0.0  7518 lnevers sort -r -k1
  0.0  7517 lnevers ps -eao pcpu,pid,user,args
  0.0  6453 lnevers bash
  0.0  6448 lnevers -tcsh (tcsh)
  0.0  1709 root    /usr/libexec/getty std.115200 console
[lnevers@boss ~]$ iostat
       tty             da4              da1              da2             cpu
 tin  tout  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s  us ni sy in id
   0     3 26.01   0  0.01  20.72   0  0.00   7.91   1  0.01   1  0  1  0 98
[lnevers@boss ~]$ 
[lnevers@boss ~]$ uptime
 3:27PM  up 48 days, 22:25, 6 users, load averages: 0.17, 0.18, 0.15
[lnevers@boss ~]$ iostat
       tty             da4              da1              da2             cpu
 tin  tout  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s  us ni sy in id
   0     3 26.01   0  0.01  20.72   0  0.00   7.91   1  0.01   1  0  1  0 98

Similar results on the OPS node:

last pid: 22804;  load averages:  0.10,  0.06,  0.01                                               up 48+22:20:45  15:23:31
107 processes: 1 running, 106 sleeping
CPU:  0.8% user,  0.0% nice,  0.4% system,  0.0% interrupt, 98.8% idle
Mem: 166M Active, 871M Inact, 147M Wired, 8460K Cache, 95M Buf, 808M Free
Swap: 2047M Total, 852K Used, 2046M Free

[lnevers@ops ~]$ ps -eao pcpu,pid,user,args | sort -r -k1        
 %CPU   PID USER    COMMAND
  0.0 98491 elabman bash -login
  0.0 23097 lnevers sort -r -k1
  0.0 23096 lnevers ps -eao pcpu,pid,user,args
  0.0 23059 lnevers bash
  0.0 23054 lnevers -tcsh (tcsh)
  0.0   779 root    /usr/libexec/getty std.115200 console
  0.0   597 mysql   /usr/local/libexec/mysqld --basedir=/usr/local --datadir=/var/db/mysql --user=mysql --pid-file=/var/db/
  0.0   530 root    /bin/sh /usr/local/bin/mysqld_safe --pid-file=/var/db/mysql/mysqld.pid --user=mysql --log-long-format -
[lnevers@ops ~]$ uptime
 3:29PM  up 48 days, 22:27, 2 users, load averages: 0.28, 0.13, 0.04
[lnevers@ops ~]$ iostat
       tty             da3              da0              da4             cpu
 tin  tout  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s  us ni sy in id
   0     1 20.32   0  0.00  11.07   0  0.01  11.09   0  0.00   0  0  0  0 100

While the 4 experiments involving OpenFlow 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