OOM Release Planning
- Sylvain Desbureaux
- Krzysztof Opasiak
The content of this template is expected to be fill out for M1 Release Planning Milestone.
Info
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.
Overview
Project Name | OOM suprisingly as we're on OOM folder |
|---|---|
Target Release Name | Guilin surprisingly as we're on Guilin folder |
Project Lifecycle State | Incubation cause I've not time to fill paperwork |
Participating Company | look at gerrit |
Scope
What is this release trying to address?
We'll do as best as we can
Requirements
Be able to deploy onap
Minimum Viable Product
ONAP installer
Functionalities
We'll deliver all that we can and nothing that we cannot. No promises.
Epics
Stories
Longer term roadmap
Have a stable and reliable ONAP installer that can work as both offline and online
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description |
|---|---|
helm charts | yaml files that are interpreted by helm |
Sub-Components
oom
offline-installer
Architecture
High level architecture diagram
It's just an installer don't expect fancy diagrams.
Platform Maturity
We believe that we lack a lot of functionality thus don't consider us as a mature project.
API Incoming Dependencies
We don't consume any project API.
API Outgoing Dependencies
We don't provide APIs.
Third Party Products Dependencies
Name | Description | Version |
|---|---|---|
Helm | helm | v2 or v3 if we manage to migrate |
Kubernetes | kubernetes | v1.15 or newer if we manage to migrate |
TESTING AND INTEGRATION PLANS
Continuous testing at the gate
GAPS
We have so many gaps that it would be infeasible to list all of them here.
KNOWN DEFECTS AND ISSUES
Please refer to Frankfurt Defect Status
RISKS
Please update any risk on the centralized wiki page - Frankfurt Risks
RESOURCES
Fill out the Resources Committed to the Release centralized page.
RELEASE MILESTONE
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
DOCUMENTATION, TRAINING
Please update the following centralized wiki: Frankfurt Documentation
That includes
Team contributions to the specific document related to he project (Config guide, installation guide...).
Team contributions to the overall Release Documentation and training asset
High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
Documentation includes items such as:
Installation instructions
Configuration instructions
Developer guide
End User guide
Admin guide
...
Note
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.