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 deliverDublin |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information/Mature |
| Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended. | AT&T Ericsson |
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)5G Use Case is the principal driver for the enhancements in this release.
DMaaP - Message Router
Upgrade Kafka to v1.1.1
Support for Authenticated topics
Add Scaling support
Support for multi-site applications
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
The existing Casablanca use cases are still going to be supported. We also support 5G use case requirements.
Minimum Viable Product
Describe the MVP for this release.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.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox DMAAP and issuetype in (epic) and fixVersion = "Dublin Release" ORDER BY priority DESC, updated DESC serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox DMAAP and issuetype in (story) and fixVersion = "Dublin Release" ORDER BY priority DESC, updated DESC serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspectiveDMaaP is a premier 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.
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.
...
| Docker image | Custom Kafka image and DMaaP images |
| Source Code | Source code of DMaaP |
| Release Note | Release note of the release |
Sub-Components
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
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.
- Platform Maturity Requirements (S3P)-Dublin targets/guides on implementation
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Minimum Levels (Dublin) | Comments |
|---|---|---|---|---|---|
| Performance | 1 | 1 |
|
| |
| Stability | 1 | 2 |
|
| |
| Resiliency | 2 | 2 |
|
| |
| Security | 1 | 1 (2 stretch) |
|
| |
| Scalability | 1 | 1 |
|
| |
| Manageability | 1 | 2 |
|
| |
| Usability | 1 | 1 |
|
|
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 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
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|
|---|---|---|---|---|---|
| AJSC | Java services container | 3.0.10 | |||
| Kafka | Distributed messaging platform | 1.1.1 | |||
| Zoo Keeper | Centralized service for maintaining configuration information | 3.4.10 | |||
| 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.
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.
- 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.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| 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
...