== InstaGENI Acceptance Tests Open Topic ==

== Open Topics: 2013-02-27 ==

=== Experimenter Tests ===

__IG-EXP-7: Click Router Experiment Acceptance Test__   --->   Expected Date: March 01  [[BR]]
Niky is modifying click router setup to run in two racks scenario. On 02/26 she was implementing click router environment workarounds.  Expect to be able to run test by Friday March 1.

=== Administrative Tests ===

__IG-ADM-1: Rack Receipt and Inventory Test__   --->   Expected Date: March 13  [[BR]]
Only remaining blocker is government property tracking (specifically tags at BBN).

__IG-ADM-3: Full Rack Reboot Test__  --->   Expected Date: March 11 [[BR]]
Need documentation by March 8th, would like to execute on March 11 [[BR]]

__IG-ADM-4: Emergency Stop Test__   --->   Expected Date: March 4 (March 5th alternate) [[BR]]
An Emergency Stop Procedure detailed test outline is being defined.  The preparation steps are currently being executed and coordination is taking place with ES teams. Provided feedback on the InstaGENI documents, which have been addressed. Trying to schedule IG-ADM-4 with the InstaGENI team for March 4th, with the 5th as an alternate or a re-test date. These dates should work for Eldar and the GMOC. There are no blocking issues at this time.

__IG-ADM-5: Software Update Test__   --->   Expected Date:  March 5 (March 11 alternate) [[BR]]

Nick to complete tests the current GENI-recommended versions of FV and FOAM by Friday March 1.  Once Nick completes testing and InstaGENI Team requests site admins to upgrade, expect to run upgrade tests on March 4th. If we miss that date, March 11th is the last chance before GEC.

__IG-ADM-6: Control Network Disconnection Test__   --->   Expected Date: March 7 or 8 [[BR]]
Expect to execute full procedure on March 7th or 8th.
 

__IG-ADM-7: Documentation Review Test__   --->   Expected Date: ??? [[BR]]

Prioritized outstanding documentation email on 01/31/2013. Waiting on responses from InstaGENI team.

=== Monitoring Tests ===

__IG-MON-1: Control Network Software and VLAN Inspection Test__   --->   Expected Date: ???  [[BR]]
 * Blocking question in email discussion about source code availability on racks. 
 * GPO is blocking and needs to capture questions about control network setup, which will be collected as part of IG-MON-2.

__IG-MON-2: GENI Software Configuration Inspection Test__    Expected Date: ???  [[BR]]
GPO is blocking and needs to capture questions about control network setup. 

__IG-MON-3: GENI Active Experiment Inspection Test__ --->  Expected Date: ???  [[BR]]


__IG-MON-5: GMOC Data Collection Test__ --->   Expected Date: ???  [[BR]]

Working on a consolidated debian package of tango-monitor-instageni to be run on control nodes. Package is to be initially tested on BBN head node.
Software to be delivered will include:
 * Code to run on one or more head nodes (and configuration of the credentials which that code needs to speak AM API and ProtoGENI data collection API)
 * Update of the tango-monitor-pgenishared package which runs on shared workers.


== InstaGENI Site Confirmation Tests Open Topic ==

Performance Issues:

 - Leigh investigating PC to VM results which did not meet his expectations for bandwidth shaping. In a scenario where no bandwidth is specified in RSpec, nodes will get a  1 GB interface whose traffic is shaped to 100 Mb/s for a VM, but not for a PC.  But performance recorded from PC show unexpected traffic levels:
 
|| End Points                 || One Client         || Five Clients        ||   Ten Clients      ||
|| PC to VM                   || 101 Mbits/sec      || 101 Mbits/sec       || 101 Mbits/sec      ||
|| VM to PC                   || 101 Mbits/sec      ||  101 Mbits/sec      || 101 Mbits/sec      || 

 - Potential Site to Site VM over !OpenFlow performance issue for Utah sites.  Sent email to Rob. but not sure if he has access to page yet. Performance results captured show the following iperf TCP throughput: 

|| End points                              ||  One Client        ||    5 Clients           ||   10 Clients(tcp)    ||
||GPO IG VM to Utah IG   VM ||  11.2 Mbits/sec ||  21.7 Mbits/sec ||   41.5 Mbits/sec   ||
|| GPO IG VM to Utah PG VM ||  10.7 Mbits/sec ||  25.2 Mbits/sec ||   36.7 Mbits/sec   ||

According to Rob, the only limitation is between the Utah campus switch on campus and the switch in the SALT I2 POP, which are limited to 4Gbps between them.  The results we go were substantially lower.

Several fixes have been put in place since the measurements were collected in mid-February. Need to re-ran to re-run experiment to verify that results are unchanged.