Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Deliverable Name

Deliverable Description

Docker imageCustom Kafka image and DMaaP images
Source CodeSource code of DMaaP
Release NoteRelease note of the release

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 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)

AAFAuthentication and Authorization Frameworkalready availablealready availableLink toward the detailed API description

...

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

DMaaP MR APIAPI used to create Topics ,publish a message,subscribe to a Topic etc.Date for which the API is reviewed and agreedTBDMR API documentation
DMaaP Buscontroller APIProvisioning API for management of Topics and FeedsDate for which the API is reviewed and agreedM2BC API documentation (ReadTheDocs)
DMaaP DataRouter APIAPI used to create feeds ,publish to this feed, subscribe to a feedDate for which the API is reviewed and agreedM2  DR API documentation


  • Third Party Products Dependencies

...

  • Testing and Integration Plans

  1. Unit test: Unit tests has at least 50% code coverageNo change from previous release.
  2. Functional test: Leverage the robot framework infrastructure to provide the functional testNo change from previous release.
  3. 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 InfrastructureNo 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.

...

The milestones are defined at the Release Planning: Honolulu and all the supporting project agreed to comply with these dates.

...