...
...
...
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 | Amsterdam Release |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Huawei, VMWare & VMWareAccenture |
Scope
What is this release trying to address?
In Amsterdam Release, DMaaP provides a platform for high performing and cost effective data movement services that transports and processes data from any source to any target with the format, quality, security, and concurrency required to serve the business and customer needs.
Use Cases
...
Use Case: Residential Broadband vCPE (Approved)
Minimum Viable Product
- Message Router (MR) - MR is responsible for transporting messages. The interface to DR will be exposed as a RESTful web service. The service will be built over Apache Kafka.
- Data Router (DR) - DR is responsible to provide a common framework by which data producers can make data available to data consumers and a way for potential consumers to find feeds with the data they require. The interface to DR will be exposed as a RESTful web service.
- Integrate Application Authorization framework with Message Rourter.
- Integrate Application Authorization framework with Data Rourter.
- Bus Controller - Provisioning DMaaP Elements
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.
...
Support transport of messages and data. Also support real time streaming, filtering and transformation.
Release Deliverables
...
| Deliverable Name | Deliverable Description |
|---|---|
| Message Router | Source Code / Executable / Docker Image |
| Data Router | Source Code / Executable / Docker Image |
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the API this release is expecting from other releases.
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 Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | MSB | Service registry|
|---|---|---|---|---|---|---|
API Outgoing Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| Holmes | Holmes is intended for correlation analysis between different alarms originated from different VNFs or different layers of a certain VNF | Holmes Documentation | ||
| DCAE | DCAE is the umbrella name for a number of components collectively fulfilling the role of Data Collection, Analytics, and Events generation for ONAP | DCAE API | ||
| SDN | ||||
| APPC | ||||
| Policy | ||||
| A&AI |
Third Party Products Dependencies
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.