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 | Dublin |
| Project Lifecycle State | Incubation/Mature |
| Participating Company | AT&T Ericsson Nokia |
Scope
What is this release trying to address?
5G Use Case is the principal driver for the enhancements in this release.
DMaaP - Message Router
Upgrade Kafka to 1v1.1.1
Data Router updates to support Bulk PM use cases
Support for Authenticated topics in MR
Add Scaling support for DMaaP MR
DMaaP support Support for multi-site applicationsDMaaP Provisioning via Bus Controllerapplications
Add MirrorMaker to allow for message replication across Kafka clusters
DMaaP - Data Router
Data Router updates to support Bulk PM use cases
DMaaP - Bus Controller
DMaaP Provisioning via Bus Controller
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case)The existing Casablanca use cases are still going to be supported. We also support 5G use case requirements.
Minimum Viable Product
...
Kafka is updated to 1.1.1
Kafka MirrorMaker support
Support for authenticated topics
Provisioning the mirrormaker using buscontroller
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.
...
| Deliverable Name | Deliverable Description |
|---|---|
| Docker image | Custom Kafka image and DMaaP images |
| Source Code | Source code of DMaaP |
| Release Note | Release note of the release |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
kafka AAF plugin
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.
Platform Maturity
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Minimum Levels (Dublin) | Comments |
|---|---|---|---|---|---|
| Performance | 1 | 1 |
|
| |
| Stability | 11 | 2 |
|
| |
| Resiliency | 2 | 2 |
|
| |
| Security | 1 | 1 (2 stretch) |
|
| |
| Scalability | 1 | 1 |
|
| |
| Manageability | 11 | 2 |
|
| |
| Usability | 1 | 1 |
|
|
...
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 Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
|---|---|---|---|---|---|
| To fill out | High level description of the APIAAF | Authentication and Authorization Framework | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
...
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
| DMaaP MR API | API used to create Topics ,publish a message,subscribe to a Topic etc. | Date for which the API is reviewed and agreed | TBD | API documentation |
| DMaaP Buscontroller API | Provisioning API for management of Topics and Feeds | Date for which the API is reviewed and agreed | M2 | API documentation (ReadTheDocs) |
| DMaaP DataRouter API | API used to create feeds ,publish to this feed, subscribe to a feed | Date for which the API is reviewed and agreed |
| M2 | API documentation |
Third Party Products Dependencies
...
| Name | Description | Version |
|---|---|---|
| AJSC | Java services container | ? 3.0.6-oss10 |
| Kafka | Distributed messaging platform | ? 01.111.01 |
| Zoo Keeper | Centralized service for maintaining configuration information | ? 3.4.610 |
| Spring | Spring Framework | ? 1.4 |
| Docker | Container engine | ? 1.12 |
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.
...
- Unit test: Unit tests has at least 50% code coverage.
- Functional test: Leverage the robot framework infrastructure to provide the functional test.
- Integration test: Support integration team to provide the end to end integration test.
- All the above should be automation tests run on the LF Jenkins Infrastructure.
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.
...
| 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
...