genesis:genesis_project_proposal
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
genesis:genesis_project_proposal [2015/07/14 13:22] Frank Brockners |
genesis:genesis_project_proposal [2015/08/11 09:26] (current) Frank Brockners [Proposed Release Schedule] |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| * 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. | * 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. | ||
| * Work hand-in-hand and integrates with projects working on deployment tools ("installers") that have chosen to participate in Genesis. | * 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). Continue to maintain this CI/CD integration point under the genesis repository (/genesis/fuel/ci, /genesis/foreman/ci). | + | * 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 (Apex, OpenSteak, Fuel@OPNFV, Compass4NFV, JOID, .. (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 38: | Line 39: | ||
| * Additional contributors: | * Additional contributors: | ||
| * David Blaisonneau (david.blaisonneau@orange.com) | * David Blaisonneau (david.blaisonneau@orange.com) | ||
| - | * ... (TBD) | + | |
| ==== Planned deliverables ==== | ==== Planned deliverables ==== | ||
| Line 49: | 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 55: | 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 69: | Line 70: | ||
| Weidong Shao (weidong.shao@huawei.com)\\ | Weidong Shao (weidong.shao@huawei.com)\\ | ||
| Artur Tyloch (artur.tyloch@canonical.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.1436880156.txt.gz · Last modified: 2015/07/14 13:22 by Frank Brockners
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
