User Tools

Site Tools


genesis:genesis_project_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
genesis:genesis_project_proposal [2015/06/25 15:59]
Frank Brockners [Scope]
genesis:genesis_project_proposal [2015/08/11 09:26] (current)
Frank Brockners [Proposed Release Schedule]
Line 2: Line 2:
  
   * Proposed name for the project: ''​Genesis''​ (__GENE__ral __S__ystem __I__nstallation __S__ervices)   * Proposed name for the project: ''​Genesis''​ (__GENE__ral __S__ystem __I__nstallation __S__ervices)
-  * Proposed name for the repository: ''​genesis''​+  * Proposed name for the repository: ''​genesisreq''​
   * Project Category: Requirements   * Project Category: Requirements
  
Line 13: Line 13:
  
   * Define a common set of requirements,​ capabilities and common user-observable behavior of a deployed system that all projects participating in Genesis have to conform to.   * Define a common set of requirements,​ capabilities and common user-observable behavior of a deployed system that all projects participating in Genesis have to conform to.
-  * Maintain common artifacts used by all deployment tools (e.g. build, deploy, or configuration scripts): Evolve and maintain “common” tree of existing genesis repository. ​Artifacts which are specific to an installer will be moved into the repository ​of the associated installer ​project+  * Maintain common artifacts used by all deployment tools (e.g. build, deploy, or configuration scripts): Evolve and maintain “common” ​source ​tree in the existing ​[[https://​gerrit.opnfv.org/​gerrit/​gitweb?​p=genesis.git;​a=summary|genesis Gerrit / Git repository]] and [[http://​artifacts.opnfv.org/​|binary artifacts repository]]. ​ Changes to the common repository will be reviewed and approved by the genesis team in collaboration with the project teams. ​ With a goal of leveraging as much common code as possible. 
-  * Work hand-in-hand and integrate ​with projects working on deployment tools that have chosen to participate in Genesis. +  * Source and binary files specific to an individual ​installer will be moved to a separate Gerrit / Git project and directory structure in the artifacts ​repository.  These repositories will be reviewed and approved by the project team associated ​with the installer. 
-  * Works hand-in-hand with test projects, release engineering,​ and CI/CD and define installer requirements for interaction with test projects, release engineering,​ CI/CD. Example: Definition of an entry point that CI/CD uses to trigger a deployment, such as a "​deploy.sh"​ script (as is already done for Arno). +  * Work hand-in-hand and integrates ​with projects working on deployment tools ("​installers"​) ​that have chosen to participate in Genesis. 
- +  * Works hand-in-hand with test projects, release engineering,​ and CI/CD and define installer requirements for interaction with test projects, release engineering,​ CI/CD. Example: Definition of an entry point that CI/CD uses to trigger a deployment, such as a "​deploy.sh"​ script (as is already done for Arno).  
 +  * Genesis will serve as an interface for projects with OPNFV Platform dependencies to initiate and prioritize the requests for their requirements. The requesting project is responsible for the integration and implementation work of their requirements. ​ Requesting projects and individual installers will collaborate on the implementation.
 ==== Dependencies ==== ==== Dependencies ====
  
-  * Deployment tool projects who choose to participate in Genesis (TBD+  * Deployment tool projects who choose to participate in Genesis (Apex, OpenSteak, Fuel@OPNFV, Compass4NFV,​ JOID, ..  ​
-  * Testing related projects (Functest, Qtip, Yardstick, Vsperf) +  * Testing related projects (Functest, Qtip, Yardstick, Vsperf,...
-  * CD/CI infrasturcture (Octopus)+  * CD/CI infrasturcture ​and release engineering ​(Octopus, Releng)
   * Hardware infrastructure (Pharos)   * Hardware infrastructure (Pharos)
  
Line 31: Line 31:
  
   * Committers:   * Committers:
-    * Tim Rozet (trozet@redhat.com) +    * Tim Rozet (trozet@redhat.com) ​- representing Apex 
-    * ...+    * Arnaud Morin (arnaud1.morin@orange.com) - representing OpenSteak 
 +    * Jonas Bjurel (jonas.bjurel@ericsson.com) - representing Fuel@OPNFV 
 +    * Weidong Shao (weidong.shao@huawei.com) - representing Compass4NFV 
 +    * Artur Tyloch (artur.tyloch@canonical.com) - representing JOID
  
   * Additional contributors:​   * Additional contributors:​
-    * ... (TBD)+    * David Blaisonneau (david.blaisonneau@orange.com) 
  
 ==== Planned deliverables ==== ==== Planned deliverables ====
Line 46: Line 50:
 ==== Proposed Release Schedule ==== ==== Proposed Release Schedule ====
  
-The Genesis project provides requirements for a set of projects which provide deployment tools. Genesis ​will not formally participate ​in any OPNFV release.+The Genesis project provides requirements for a set of projects which provide deployment tools. Genesis ​implicitly participates ​in OPNFV releases in that it defines requirements that deployment tools will meet for a specific ​release.
  
  
Line 52: Line 56:
  
 ** Project Name: ** genesis \\ ** Project Name: ** genesis \\
-** Repo name: ** genesis ​\\+** Repo name: ** genesisreq ​\\
 ** Project Category: requirements ** \\ ** Project Category: requirements ** \\
 ** Lifecycle State: ** \\ ** Lifecycle State: ** \\
-** Primary Contact: ** \\ +** Primary Contact: ** Frank Brockners\\ 
-** Project Lead: ** \\+** Project Lead: ** Frank Brockners\\
 ** Jira Project Name: ** Genesis \\ ** Jira Project Name: ** Genesis \\
 ** Jira Project Prefix: ** [GENESIS] \\ ** Jira Project Prefix: ** [GENESIS] \\
Line 62: Line 66:
 ** Committers: ** \\ ** Committers: ** \\
 Tim Rozet (trozet@redhat.com)\\ Tim Rozet (trozet@redhat.com)\\
 +Arnaud Morin (arnaud1.morin@orange.com)\\
 +Jonas Bjurel (jonas.bjurel@ericsson.com)\\
 +Weidong Shao (weidong.shao@huawei.com)\\
 +Artur Tyloch (artur.tyloch@canonical.com)\\
 +Frank Brockners (fbrockne@cisco.com)\\
  \\  \\
 ** Link to TSC approval: ** TBD \\  ** Link to TSC approval: ** TBD \\ 
 ** Link to approval of additional submitters: ** TBD \\ ** Link to approval of additional submitters: ** TBD \\
genesis/genesis_project_proposal.1435247947.txt.gz · Last modified: 2015/06/25 15:59 by Frank Brockners