Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.

Info
titleInfo

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.

Table of Contents
outlinetrue

Overview

Project NameEnter the name of the project
Target Release NameEnter the name of the release you are targeting to deliverCasablana
Project Lifecycle StateEither 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.

Epics

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=sanbox and issuetype in (epic)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Stories

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=sanbox and issuetype in (story)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspectivehttps://jira.onap.org/browse/OOM-10?jql=project%3D%22ONAP%20Operations%20Manager%22%20and%20issuetype%3DEpic%20and%20fixVersion%3D%22Casablanca%20Release%22%20and%20not%20status%3DClosed

Stories

https://jira.onap.org/browse/OOM-10?jql=project%3D%22ONAP%20Operations%20Manager%22%20and%20issuetype%3DStory%20and%20fixVersion%3D%22Casablanca%20Release%22%20and%20not%20status%3DClosed

Longer term roadmap

OOM 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.

...