Changes between Initial Version and Version 1 of GENIRacksHome/CiscoGENIRacks/AcceptanceTestPlan


Ignore:
Timestamp:
04/10/15 15:26:02 (9 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/CiscoGENIRacks/AcceptanceTestPlan

    v1 v1  
     1= Cisco GENI Racks Interoperability and OpenFlow Acceptance Test Plan =
     2
     3The '''[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
     4[ http://groups.geni.net/geni/wiki/GeniRacks GENI Rack Requirements.
     5
     6This 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.
     7
     8
     9== Assumptions and Dependencies ==
     10
     11The following assumptions are made for all tests described in this plan:
     12
     13 * GENI Clearinghouse credentials  are used for all tests.
     14 * GPO Clearinghouse is the Slice Authority for all tests.
     15 * Resources for each test will be requested from the local broker whenever possible.
     16 * Compute resources are VMs unless otherwise stated.
     17 * All Service Manager (SM) requests MUST be made via the  GENI AM API.
     18 * In all scenarios, one experiment is always equal to one slice.
     19 * FOAM will be used as the !OpenFlow aggregate manager for Meso-scale resources in the !OpenFlow test cases.
     20
     21The following technical dependencies will be verified before test cases are executed:
     22
     23 * ORCA RSpec/NDL conversion service is available to convert GENI requests.
     24
     25Test Traffic Profile:
     26
     27 * Experiment traffic includes UDP and TCP data streams that run for 60 seconds
     28 * Traffic exchange is used to verify that the appropriate data paths are used and that traffic is delivered successfully for each test described.
     29 * Performance measurement is not a goal of these acceptance tests.
     30
     31= Acceptance Tests Descriptions =
     32
     33This 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.
     34
     35== CG-EXP-1: GENI AM API Compliance ==
     36
     37This tests will validate compliance to GENI AM API by:
     38 - Running the [http://trac.gpolab.bbn.com/gcf/wiki/AmApiAcceptanceTests GENI AM API Acceptance tests]. 
     39 - Validating Advertisement RSPecs.
     40 - Validating Manifest RSpecs.
     41 - and Request RSpec Support.
     42
     43== CG-EXP-2: Resource Allocation ==
     44
     45This test validate ability to allocate all resource types specified in the [http://groups.geni.net/geni/wiki/GeniRacks GENI Rack Requirements] including:
     46  - Request VMs and exchange traffic between allocated end-points
     47  - Request bare Metal and exchange traffic between allocated end-points
     48
     49== CG-EXP-2: ExoGENI Stitching Support ==
     50This test case validate the ability to use ExoGENI Stitching to other ExoGENI racks. Attempts will be made to connect resources at:
     51 - co-located Cisco rack - NCSU to NCSU2
     52 - remote ExoGENI racks:
     53   - NCSU2 to WVN
     54   - NCSU to WVN
     55   - NCSU2 to WVN
     56   - NCSU to GPO EG
     57
     58== CG-EXP-4: GENI Stitching Support ==
     59   - NCSU2 to GPO EG
     60 
     61
     62==