Overview

Scope

What is this release trying to address?

• Java11 upgrade for all components
• Init containers for certificate management
• SSL Listeners for Kafka internal communication
• TSC Priority 1 Non-functional requirements

Requirements

There are no functional requirements having code impacts on DMaaP components for Guilin. There are non-functional requirements mentioned above that will be targeted to be achieved for in Guilin release.

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

Sub-Components

DMaaP 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

Frankfurt 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 Outgoing Dependencies

API this project is delivering to other projects.

• Third Party Products Dependencies

• Testing and Integration Plans

1. Unit test: Unit tests has at least 50% code coverage.
2. Functional test: Leverage the robot framework infrastructure to provide the functional test.
3. Integration test: Support integration team to provide the end to end integration test.
4. 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.

• Known Defects and Issues

None currently

Please refer to Frankfurt Defect Status

• 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 - Frankfurt Risks

• 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.

• Documentation, Training

Please update the following centralized wiki: Frankfurt 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
  • ...

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.