DRAFT PROPOSAL FOR COMMENTS
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Dublin |
| Project Lifecycle State | Incubation/Mature |
| Participating Company | AT&T Ericsson |
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 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
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.
Epics
Stories
Longer term roadmap
DMaaP 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 |
|---|---|
| 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
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) |
|---|---|---|---|---|
| AAF | Authentication and Authorization Framework | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
API Outgoing Dependencies
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 |
|---|---|---|
| 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
- 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.
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
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).
| 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 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.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
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
- ...
Note
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.