User Tools

Site Tools


plugfest:test_plan_proposal

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
plugfest:test_plan_proposal [2016/02/06 18:36]
Bin Hu [Device Under Test (DUT)]
plugfest:test_plan_proposal [2016/02/26 14:23] (current)
Bin Hu [Device Under Test (DUT)]
Line 1: Line 1:
 ===== Test Plan Proposal ===== ===== Test Plan Proposal =====
 +==== About this Page ====
 +The content below is intended as a sandbox / idea-pad for potential plugfest test cases. ​ The final / formal test plans will be captured in the DoveTail repository, allowing for continued development between test events.
  
 ==== Device Under Test (DUT) ==== ==== Device Under Test (DUT) ====
  
-=== DUT #1 ===+=== DUT #1 (Does an OPNFV Brahmaputra scenario deploy on a new set of hardware?​) ​===
  
-Installation Process with SDN Integration on Bare Metal Device+Testing OPNFV (or OPNFV-derived commercial product) ​Installation Process with SDN Integration on Bare Metal Device
  
   * Hardware platforms and configurations:​ TBD after Brahmaputra Release is ready   * Hardware platforms and configurations:​ TBD after Brahmaputra Release is ready
-  * Installers:+  * Installers ​- each DUT can support one or more installers
     * Apex     * Apex
     * Compass     * Compass
     * Fuel     * Fuel
     * Joid     * Joid
-  * Scenarios - TBC after Brahmaputra Release is ready+  * Scenarios - each DUT can support one or more scenarios.
     * os-odl_l2-nofeature-ha     * os-odl_l2-nofeature-ha
     * os-odl_l3-nofeature-ha     * os-odl_l3-nofeature-ha
Line 19: Line 21:
     * os-opencontrail-nofeature-ha     * os-opencontrail-nofeature-ha
  
-=== DUT #2 ===+=== DUT #2 (a new scenario, i.e. a new mix of new components, their configuration and hardware etc.) ===
  
-Device running ​OPNFV (or OPNFV-derived commercial software) for installation tests, VNF integration,​ etc.+Testing interoperability of other network elements against ​OPNFV platform:
  
-=== DUT#2 ===+  * All about control plane 
 +  * Baseline with well known/​proven equipment (a switch, a router, ???)
  
-network equipment interfacing with OPNFV (e.g., switches, routers, firewalls, etc.)+=== DUT #3 (a use case on top of a new mix of new componentstheir configuration and hardware ​etc.) ===
  
-==== Target ​Specific Use Cases ====+Testing interoperability of Specific Use Cases and Capabilities
  
-  * L3 VPN +=== DUT #4 (Does my VNF XYZ run on a specific scenario?) ===
-  * L2 VPN +
-  * vRouter +
-  * vCPE+
  
-==== Other Capabilities ====+  * Testing the ability of bringing up one or a set of VNFs against one or more Scenarios of OPNFV platform 
 +  * Testing the ability of shutting down one or a set of VNFs against one or more Scenarios of OPNFV platform 
 +  * Testing the ability of state transition of one VNF against one or more Scenarios of OPNFV platform
  
-  ​Fault management +**Note**: testing of VNF itself is out of scope
-  ​Performance management +
-  ​Service Creation and Lifecycle Management +
-  ​Failover +
-  * SFC+
  
 +
 +==== Targeted Specific Use Cases ====
 +
 +=== Test Procedure for SFC over L3 VPN ===
 +
 +TBD
 +
 +=== Test Procedure for L3 VPN Other Use Cases ===
 +
 +TBD
 +
 +=== Test Procedure for vRouter ===
 +
 +TBD
 +
 +=== Test Procedure for vCPE ===
 +
 +TBD
 +
 +=== Test Procedure for L2 VPN ===
 +
 +TBD
 +
 +=== Test Procedure for Fault management ===
 +
 +TBD
 +
 +=== Test Procedure for Performance management ===
 +
 +TBD
 +
 +=== Test Procedure for Service Creation and Lifecycle Management ===
 +
 +TBD
 +
 +=== Test Procedure for Failover ===
 +
 +TBD
 +
 +==== Template of Test Case Definition ====
 +
 +Click {{:​plugfest:​test_case_formatting.docx|here}} to download the template of test case definition.
plugfest/test_plan_proposal.1454783763.txt.gz · Last modified: 2016/02/06 18:36 by Bin Hu