Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Istanbul R9 |
| Project Lifecycle State | Mature |
| Participating Company | Ericsson Software Technologies |
Scope
What is this release trying to address?
- Java11 upgrade for all components
Requirements
There are no functional requirements having code impacts on DMaaP components for Istanbul.
Minimum Viable Product
Implement changes mentioned in the Scope section above.
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
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
Architecture
High level architecture diagram
DMaaP is a Kafka based platform that is used by various ONAP components to publish and subscribe messages with each other required for processing events.
Platform Maturity
Honolulu Release Platform Maturity
API Incoming Dependencies
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.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| AAF | Authentication and Authorization Framework | already available | already available | 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 | MR API documentation |
| DMaaP Buscontroller API | Provisioning API for management of Topics and Feeds | Date for which the API is reviewed and agreed | M2 | BC API documentation |
| 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 | DR API documentation |
Third Party Products Dependencies
Name | Description | Version |
|---|---|---|
| Zoo Keeper | Centralized service for maintaining configuration information | 3.4.14 |
| Spring | Spring Framework | 4.3.18 |
| Kafka | Distributed messaging platform | 2.4.0 |
| Docker | Container engine | 18.09.x |
| AJSC | Java services container | 3.0.11 |
Testing and Integration Plans
- Unit test: No change from previous release.
- Functional test: No change from previous release.
- Integration test: No change from previous release.
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
None currently
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).
Please update any risk on the centralized wiki page - Honolulu Risks
Release Milestone
The milestones are defined at the Release Planning: Istanbul 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
Please update the following centralized wiki: Honolulu Documentation
That includes
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- 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.