DRAFT PROPOSAL FOR COMMENTS
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. |
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverCasablana |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company List | the company participating in this release. At least 3-4 organizations, including an operator are recommendedAmdocs, AT&T, Bell Canada, etc. |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case)During the Casablanca release OOM will further the "Production" aspects of ONAP deployments by enabling geographic distribution, backup & restores, and elimination of extraneous database instances. In addition, during this release the OOM team will start to transfer ownership of OOM artifacts to the project teams should that wish to do so and accept the inherent responsibility of doing so.
Use Cases
OOM isn't impact by, nor does it impact ONAP use cases.
Minimum Viable Product
Describe the MVP for this releaseAll of the changes being proposed enhance existing OOM capabilities and none are required to have a viable product.
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox and issuetype in (epic) oom and type=epic and fixversion="Casablanca Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Stories
| Jira Legacy | |||||
|---|---|---|---|---|---|
|
|
|
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspectiveOOM will evolve to improve the production qualities of ONAP deployments and enable a wider variety of Cloud types including Kubernetes native public clouds.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| To fill out | To fill out |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
...
| Helm charts | Further enhancements to the existing set of ONAP helm charts. |
| Helm charts | Examples of custom deployment specifications to enable new features like auto-scaling. |
| Documentation | Read-the-docs documentation of new features. |
Sub-Components
The Helm repo requested by the OOM team during the Beijing release is required (See LF #53102).
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
...
Not applicable. OOM is the ONAP manager not an ONAP component.
Platform Maturity
OOM has already and will continue to provide capabilities to the project teams to fulfill 'platform maturity' but in itself can't achieve any of these goals. As for usability, no significant changes are planned to the OOM documentation. Test coverage doesn't apply as this is a DevOps project without traditional source code.
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | *N/A | *N/A |
| |
| Stability | *N/A | *N/A |
| |
| Resiliency | *N/A | *N/A |
| |
| Security | *N/A | *N/A |
| |
| Scalability | *N/A | *N/A |
| |
| Manageability | *N/A | *N/A |
| |
| Usability | 1 | 1 | docs updated as required |
|
API Incoming Dependencies
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
API Outgoing Dependencies
API this project is delivering to other projects.
...
*N/A - as mentioned above, OOM will support other projects to achieve their S3P requirements
API Incoming Dependencies
None.
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version |
|---|---|---|
| To fill out | To fill out | To fill out |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
...
Known Defects and Issues
...
| Kubernetes | Cloud Manager | 1.8.10+ |
| Helm | Cloud Package Manager | 2.8.2+ |
| Consul | Health Monitor / State Management | latest |
The Integration team only tests with a Rancher deployment of K8s.
Testing and Integration Plans
Testing continues to be done by deploying ONAP and monitoring Robot automated tests including health checks.
Gaps
N/A
Known Defects and Issues
List of all known project bugs:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
...
As OOM is fully functional as is there are no significant risks to project.
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.
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
...
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the 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
- ...
...
| title | Note |
|---|
...
N/A
Documentation, Training
- No significant changes to the existing OOM documents are planned.
- The following is the current OOM document structure:
- ONAP Operations Manager Project
- OOM Quick Start Guide
- OOM User Guide
- OOM Developer Guide
- OOM Cloud Setup Guide
- Release Notes
- ONAP on Kubernetes with Rancher
Other Information
Vendor Neutral
...