User Tools

Site Tools


project_proposals:apex_opnfv

Differences

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

Link to this comparison view

Next revision
Previous revision
project_proposals:apex_opnfv [2015/06/24 14:39]
Tim Rozet created
project_proposals:apex_opnfv [2015/07/09 13:36] (current)
Tim Rozet
Line 6: Line 6:
  
 ==== Project description:​ ==== ==== Project description:​ ====
-  ​Apex will serve as the natural continuation of the Foreman/​QuickStack involvement in the former BGS project. ​ Apex will continue to support Foreman/​QuickStack from Arno release along with moving to a better installer based on TripleO. ​ The goal of this project is to create a stable platform for OPNFV while meeting all of the requirements put forth for the target system.+ 
 +Apex will serve as the natural continuation of the Foreman/​QuickStack involvement in the former BGS project. ​ Apex will continue to support Foreman/​QuickStack from Arno release along with moving to a better installer based on TripleO. ​ The goal of this project is to create a stable platform for OPNFV while meeting all of the requirements put forth for the target system.
   ​   ​
 ==== Scope: ==== ==== Scope: ====
  
-  * Integrate into CI environment for virtual and baremetal deployments. +  * Integrate into CI environment for virtual and baremetal deployments 
-  * Work closely with FuncTest to facilitate debugging and integration testing of components. +  * Work closely with FuncTest to facilitate debugging and integration testing of components 
-  * Purpose of this project is to encourage collaboration. ​ Will help to integrate all SDN controllers. +  * Purpose of this project is to encourage collaboration. ​ Will help to integrate all SDN controllers 
-  * TripleO based implementation of deployment (OpenStack used to deploy OPNFV) +  * TripleO based implementation of deployment (OpenStack used to deploy OPNFV) 
-  * Continuation of Foreman/​QuickStack support post Arno. +  * Continuation of Foreman/​QuickStack support post Arno 
-  * All code changes will be made as upstream as possible into respective projects.+  * All code changes will be made as upstream as possible into respective projects
  
 ==== Dependencies:​ ==== ==== Dependencies:​ ====
  
-  * Relies on Octopus project for CI and testing. +  * Relies on Octopus project for CI and testing 
-  * Uses upstream projects RDO (vanilla OpenStack), RDO Manager (TripleO derivative) and Opendaylight +  * Uses upstream projects RDO (vanilla OpenStack), RDO Manager (TripleO derivative) and OpenDaylight 
-  * Identify any specific development be staged with respect to the upstream project and releases.+  * Other upstream SDN controller projects 
 +  * Identify any specific development be staged with respect to the upstream project and releases
  
 ==== Committers and Contributors:​ ==== ==== Committers and Contributors:​ ====
  
 +Committers:
   * Tim Rozet (Red Hat): trozet@redhat.com   * Tim Rozet (Red Hat): trozet@redhat.com
   * Dan Radez (Red Hat): radez@redhat.com   * Dan Radez (Red Hat): radez@redhat.com
 +
 +Contributors:​
 +  * Daniel Farrell (Red Hat): dfarrell@redhat.com
 +  * Randy Levensalor (CableLabs):​ R.Levensalor@cablelabs.com
  
 ==== Planned deliverables ==== ==== Planned deliverables ====
  
-  * Described the project release package as OPNFV or open source upstream projects. +  * Deployment tool to deliver ​OPNFV Target System 
-  * If project deliverables have multiple dependencies across other project categories, described linkage ​of the deliverables.+  * Meets all OPNFV requirements ​of OPNFV platform 
 +  * Plugins to CI for deployment 
 +  * Multi-SDN Controller integration 
 +  * Documentation and User Guide 
 +  * Virtual and Baremetal Support
  
 ==== Proposed Release Schedule: ==== ==== Proposed Release Schedule: ====
  
-  * When is the first release ​planned? +  * Releases will be part of OPNFV release ​cycle 
-  * Will this align with the current ​release ​cadence +  * Next release will be OPNFV R2 release
  
-Use the above information to create a key project facts section on your project page 
 ===== Key Project Facts ===== ===== Key Project Facts =====
  
-** Project Name: ** Project Name (repo name) \\ +** Project Name: ** Apex \\ 
-** Repo name: ** \\ +** Repo name: ** apex \\ 
-** Project Category: ** \\ +** Project Category: ** Integration and testing ​\\ 
-** Lifecycle State: ** \\ +** Lifecycle State: ** Proposal ​\\ 
-** Primary Contact: ** \\ +** Primary Contact: ** Tim Rozet (trozet@redhat.com) ​\\ 
-** Project Lead: ** \\ +** Project Lead: ** Tim Rozet (trozet@redhat.com) ​\\ 
-** Jira Project Name: ** Same as Project name \\ +** Jira Project Name: ** Apex \\ 
-** Jira Project Prefix: ** [10 Characters max [A-Z] ] \\ +** Jira Project Prefix: ** Apex \\ 
-** mailing list tag ** [Should match Jira Project Prefix] \\+** mailing list tag** [Apex] \\
 ** Committers: ** \\ ** Committers: ** \\
-foo@bar.com \\ +Tim Rozet (trozet@redhat.com\\ 
-baz@qux.com \\ +Dan Radez (radez@redhat.com\\ 
-** Link to TSC approval: ​Example http://​meetbot.opnfv.org/​meetings/​opnfv-meeting/​2015/​opnfv-meeting.2015-03-03-15.01.html ​** \\  +** Link to TSC approval: ** TBD \\  
-** Link to approval of additional submitters: ** Example http://​meetbot.opnfv.org/​meetings/​opnfv-meeting/​2015/​opnfv-meeting.2015-03-03-15.01.html ​\\+** Link to approval of additional submitters: ** TBD \\
project_proposals/apex_opnfv.1435156789.txt.gz · Last modified: 2015/06/24 14:39 by Tim Rozet