= Cisco GENI Racks Interoperability and OpenFlow Acceptance Test Plan =

The '''[wiki:GENIRacksHome/CiscoGENIRacks/AcceptanceTestPlan Cisco GENI Racks Interoperability and OpenFlow Acceptance Test Plan]''' is based on the [wiki:GENIRacksHome/AcceptanceTests/ExogeniAcceptanceTestsPlan ExoGENI System Acceptance Test Plan] test cases.  Test cases have been renamed for the Cisco rack and some have been combined to generate a more efficient test effort. The goal of this plan is to validate the 
[ http://groups.geni.net/geni/wiki/GeniRacks GENI Rack Requirements. 

This plan defines tests that cover the following types of requirements: Integration (C), Monitoring(D), Experimenter(G) and Local Aggregate (F) requirements.  The [http://trac.gpolab.bbn.com/gcf/wiki/AmApiAcceptanceTests GENI AM API Acceptance tests] suite covers Software (A and B) requirements that are not covered in this plan.  This plan covers high-priority functional tests; ExoGENI racks support more functions than those highlighted here.   Issues from acceptance testing will be tracked in [http://groups.geni.net/exogeni ExoGENI trac tickets] system.  Test Status can be found in the  '''[wiki:GENIRacksHome/CiscoGENIRacks/AcceptanceTestStatus Cisco GENI Acceptance Test Status]''' page. 


== Assumptions and Dependencies ==

The following assumptions are made for all tests described in this plan:

 * GENI Clearinghouse credentials  are used for all tests.
 * GPO Clearinghouse is the Slice Authority for all tests.
 * Resources for each test will be requested from the local broker whenever possible.
 * Compute resources are VMs unless otherwise stated.
 * All Service Manager (SM) requests MUST be made via the  GENI AM API.
 * In all scenarios, one experiment is always equal to one slice.
 * FOAM will be used as the !OpenFlow aggregate manager for Meso-scale resources in the !OpenFlow test cases.

The following technical dependencies will be verified before test cases are executed:

 * ORCA RSpec/NDL conversion service is available to convert GENI requests.

Test Traffic Profile:

 * Experiment traffic includes UDP and TCP data streams that run for 60 seconds 
 * Traffic exchange is used to verify that the appropriate data paths are used and that traffic is delivered successfully for each test described.
 * Performance measurement is not a goal of these acceptance tests.

= Acceptance Tests Descriptions = 

This section describes each acceptance test by defining its goals, topology, and outline test procedure.  Main area of acceptance include: GENI AM API compliance, Resource Allocation, ExoGENI Stitching Support, GENI Stitching Support, OpenFlow Support, Administrative functions and Monitoring.  Attempts will also be made at characterizing rack performance.

== CG-EXP-1: GENI AM API Compliance == 

This tests will validate compliance to GENI AM API by: 
 - Running the [http://trac.gpolab.bbn.com/gcf/wiki/AmApiAcceptanceTests GENI AM API Acceptance tests].  
 - Validating Advertisement RSPecs.
 - Validating Manifest RSpecs.
 - and Request RSpec Support.

== CG-EXP-2: Resource Allocation ==

This test validate ability to allocate all resource types specified in the [http://groups.geni.net/geni/wiki/GeniRacks GENI Rack Requirements] including:
  - Request VMs and exchange traffic between allocated end-points
  - Request bare Metal and exchange traffic between allocated end-points

== CG-EXP-2: ExoGENI Stitching Support ==
This test case validate the ability to use ExoGENI Stitching to other ExoGENI racks. Attempts will be made to connect resources at:
 - co-located Cisco rack - NCSU to NCSU2
 - remote ExoGENI racks:
   - NCSU2 to WVN
   - NCSU to WVN
   - NCSU2 to WVN
   - NCSU to GPO EG

== CG-EXP-4: GENI Stitching Support ==
   - NCSU2 to GPO EG
 

==