User Tools

Site Tools


project_proposals:fuel_opnfv

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
Last revision Both sides next revision
project_proposals:fuel_opnfv [2015/05/19 08:22]
Jonas Bjurel
project_proposals:fuel_opnfv [2015/07/03 10:21]
Jonas Bjurel
Line 15: Line 15:
  
 The scope of the proposal includes the following: The scope of the proposal includes the following:
-  * Absorbing all of OPNFV'​s release cadence features.+  * Absorbing all of OPNFV'​s release cadence features ​through the genesis project.
   * Ensuring a healthy Fuel@OPNFV architecture/​structure by feeding requirements to the fuel community.   * Ensuring a healthy Fuel@OPNFV architecture/​structure by feeding requirements to the fuel community.
   * Ensuring a healthy Fuel@OPNFV architecture/​structure by staying close to the fuel community trunk, using the fuel plug-in architecture for needed differentiation.   * Ensuring a healthy Fuel@OPNFV architecture/​structure by staying close to the fuel community trunk, using the fuel plug-in architecture for needed differentiation.
-  * Providing needed OPNFV CI pipeline ​integration, including:+  * Providing needed ​capabilities for the OPNFV CI pipeline, including:
       * Build       * Build
       * Deployment       * Deployment
-      * Low-level verification (tempest) +      * Needed hooks for low-level verification (tempest) 
-      * High-level verification (Scenario testing)+      * Needed hooks for high-level verification (Scenario testing) ​- Yardstick
  
 __**Building blocks**__ __**Building blocks**__
Line 42: Line 42:
  
   * Jonas Bjurel (Ericsson): jonas.bjurel@ericsson.com   * Jonas Bjurel (Ericsson): jonas.bjurel@ericsson.com
-  * Stefan Berg (Ericsson):​ +  * Stefan Berg (Ericsson): ​stefan.k.berg@ericsson.com 
-  * Daniel Smith (Ericsson):​ +  * Daniel Smith (Ericsson): ​daniel.smith@ericsson.com 
-  * Szylard (Ericsson):​ +  * Szilard Cserey ​(Ericsson): ​szilard.cserey@ericsson.com
-  * Jose (Ericsson):+
   * Michal Skalski (Mirantis): mskalski@mirantis.com   * Michal Skalski (Mirantis): mskalski@mirantis.com
-  * Someone ​(Intel):+  * Ruijing Guo (Intel): ​ruijing.guo@intel.com
  
 **Names and affiliations of the contributors:​** **Names and affiliations of the contributors:​**
  
   * Fatih Degirmenci (Ericsson): fatih.degirmenci@ericsson.com   * Fatih Degirmenci (Ericsson): fatih.degirmenci@ericsson.com
-  * Juan (Ericsson)+  ​* Jose Lausuch (Ericsson): jose.lausuch@ericsson.com 
 +  ​* Juan Osorio Robles ​(Ericsson): juan.osorio.robles@ericsson.com
   * Szymon Banka (Mirantis): sbanka@mirantis.com   * Szymon Banka (Mirantis): sbanka@mirantis.com
-  * Someone ​(Intel)+  * Tadi Bhargava ​(Tata): tadi.bhargava@tcs.com 
 +  * Tuan Luong (Ericsson): tuan.luong@ericsson.com
  
 __**Planned deliverables**__ __**Planned deliverables**__
Line 68: Line 69:
 Initial release of OPNFV@Fuel was as part of the joint OPNFV Bootstrap/​Get started (BGS) Arno release. Initial release of OPNFV@Fuel was as part of the joint OPNFV Bootstrap/​Get started (BGS) Arno release.
  
-First OPNFV autonomous release will be OPNFV R2 release ​(around November 2015) with the following tentative release content: +First OPNFV autonomous release will be OPNFV R2 release with the following tentative release content: 
-    * OpenStack release: Kilo (Features to be supported TBD) +    * OpenStack release: Kilo/​Liberty ​(Features to be supported TBD) 
-    * Fuel release: 7.0.x (Features to be supported TBD)+    * Fuel release: 7.0.x/8.0.x (Features to be supported TBD)
     * OpenDaylight release: Lithium (Features to be supported TBD)     * OpenDaylight release: Lithium (Features to be supported TBD)
     * OPNFV carried R2 patches     * OPNFV carried R2 patches
Line 80: Line 81:
   * Fuel - Any needed requirements will be articulated by Fuel@OPNFV and implemented by the Fuel community, Fuel@OPNFV will source upstream OpenStack through Fuel. OpenStack requirements will origin from other OPNFV projects than Fuel@OPNFV   * Fuel - Any needed requirements will be articulated by Fuel@OPNFV and implemented by the Fuel community, Fuel@OPNFV will source upstream OpenStack through Fuel. OpenStack requirements will origin from other OPNFV projects than Fuel@OPNFV
   * Open Daylight - Requirements will origin from other OPNFV projects than Fuel@OPNFV   * Open Daylight - Requirements will origin from other OPNFV projects than Fuel@OPNFV
 +  * KVM - Requirements will origin from other OPNFV projects than Fuel@OPNFV
   * OVS - OVS requirements will origin from other OPNFV projects than Fuel@OPNFV ​   * OVS - OVS requirements will origin from other OPNFV projects than Fuel@OPNFV ​
   * Ubuntu - Debian/​Ubuntu requirements will origin from other OPNFV projects than Fuel@OPNFV   * Ubuntu - Debian/​Ubuntu requirements will origin from other OPNFV projects than Fuel@OPNFV
Line 87: Line 89:
  
   * A small yet very competent end2end team   * A small yet very competent end2end team
-  * Tightly working with other installer projects, CI and functest teams - contributing and reviewing across boarders+  * Tightly working with other installer projects, genesis, CI and functest teams - contributing and reviewing across boarders
   * Using IRC as main communication medium, blended by a few bi-weekly audio calls.   * Using IRC as main communication medium, blended by a few bi-weekly audio calls.
  
project_proposals/fuel_opnfv.txt · Last modified: 2015/07/07 15:40 by Jonas Bjurel