User Tools

Site Tools


project_proposals:yardstick

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
project_proposals:yardstick [2015/04/01 15:10]
Ana Cunha improved text
project_proposals:yardstick [2015/04/29 07:56] (current)
Ana Cunha Added committer
Line 31: Line 31:
   * test stimuli, to enable infrastructure testing such as infrastructure upgrade, infrastructure recovery   * test stimuli, to enable infrastructure testing such as infrastructure upgrade, infrastructure recovery
   * test framework based upon open APIs (OpenStack/​Heat) for easy deployment   * test framework based upon open APIs (OpenStack/​Heat) for easy deployment
 +
 +This project will develop additional functionality to the base system testing covered by the project "​Functest",​ such as metrics, parallel testing, fault injection, multiple topologies, scenario testing, enabling verification of more complex test cases.
  
 This project proposes to contribute a first implementation for evaluation, which: This project proposes to contribute a first implementation for evaluation, which:
Line 64: Line 66:
 ==== Dependencies:​ ==== ==== Dependencies:​ ====
  
-  * The test framework is hardware, VNF application,​ operator and vendor independent +  * The test framework is hardware, VNF application,​ operator and vendor independent. 
-  * Current limitation: OpenStack+  * Current limitation: OpenStack
 +  * Yardstick will consider outputs of the ETSI ISG NFV about testing an NFV environment. Only public documents can be used, so Yardstick might need to adapt the timeplan for the deliverables where output from ongoing work, e.g. from TST working group needs to be considered, accordingly. 
 +  * Since verification as done in Yardstick has to prepare the ground for any certification activity, the Yardstick project is dependent on the Certification & Compliance Committee and will put those issues on high priority that are needed for any certification activities that will be needed for certification or compliance if there will be a decision to engage in this.
  
 ==== Committers and Contributors:​ ==== ==== Committers and Contributors:​ ====
Line 76: Line 80:
     * Hans Feldt (Ericsson): hans.feldt@ericsson.com     * Hans Feldt (Ericsson): hans.feldt@ericsson.com
     * Jörgen Karlsson (Ericsson): jorgen.w.karlsson@ericsson.com     * Jörgen Karlsson (Ericsson): jorgen.w.karlsson@ericsson.com
 +    * Houjingwen (Huawei): houjingwen@huawei.com ​
 +    * Trevor Cooper (Intel): trevor.cooper@intel.com
 +    * Wenjing Chu (DELL): Wenjing_Chu@DELL.com
   * Names and affiliations of other contributors   * Names and affiliations of other contributors
     * Morgan Richomme (Orange): morgan.richomme@orange.com     * Morgan Richomme (Orange): morgan.richomme@orange.com
     * Dr. Rebecca Steinert (SICS): rebste@sics.se     * Dr. Rebecca Steinert (SICS): rebste@sics.se
     * Fatih Degirmenci (Ericsson): fatih.degirmenci@ericsson.com     * Fatih Degirmenci (Ericsson): fatih.degirmenci@ericsson.com
 +    * Pierre Lynch (Ixia): PLynch@ixiacom.com
 +    * Julien Zhang (ZTE) :​zhang.jun3g@zte.com.cn
  
    
- 
 ==== Planned deliverables ==== ==== Planned deliverables ====
    
Line 92: Line 100:
  
   * OPNFV Release R2   * OPNFV Release R2
- 
project_proposals/yardstick.1427901006.txt.gz · Last modified: 2015/04/01 15:10 by Ana Cunha