Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Status: Updated for

...

London 
Component Status: Pending PTL updates and ArchCom Review

Last Reviewed on:

Certified by:

DMaaP (Data Movement as a Platform):

1 High Level Component Definition and Architectural Relationships 

draw.io Diagram
bordertrue
diagramNamedmaap_r10
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth1183
revision27

...

  • Support the transfer of messages between ONAP components, as well as to other components

  • Support the transfer of data between ONAP components as well as to other components.

  • Data Filtering capabilities

  • Data Compression capabilities

  • Data routing (file based transport)

  • Message routing (event based transport)

  • Batch and event based processing

2. DMaaP API definitions

DMaaP provides the following interfaces:

...

Interface NamePurpose Reason For UseAPI Spec (Swagger)
N/AN/A


3. Component Description:

DMaaP consists of 3 software systems

  • Message Router (MR) - Message Router is a reliable, high-volume pub/sub messaging service with a RESTful HTTP API. It is intended to be deployed by Platform Service providers so that it is available to Platform clients as a web service. The service is initially built over Apache Kafka.
  • Data Router (DR) - The Data Routing System project is intended to provide a common framework by which data producers can make data available to data consumers and a way for potential consumers to find feeds with the data they require. The interface to DR is exposed as a RESTful web service known as the DR Publishing and Delivery API
  • Data Bus Controller (BC) - Provisioning API of the Data Movement Platform that can be used for provisioning topics in the Message Router and feeds in Data Router.

4. Known system limitations

Current know system limitations

  • DMaaP uses persistent volumes to store data used by topics and feeds. Persistent volumes need to have enough storage space to handle anticipated volume.

5. Used Models

DMaaP does not use any models.

6. System Deployment Architecture

DMaaP consists of 3 main components:

  • DMaaP Message Router
  • DMaaP Data Router
  • DMaaP Buss Controller


7. New Capabilities in this Release

The addition of the Strimzi Apache Kafka project for the management of the Kafka deployment within Kubernetes

The addition of the Strimzi kafka bridge to provide REsT access to the kafka deployment.

8. References

  1. DMaaP Wiki: Data Movement as a Platform Project
  2. DMaaP on readthedocs: https://docs.onap.org/en/latest/guides/onap-developer/developing/index.html#dmaap-data-management-as-a-platform
  3. Message Router: https://docs.onap.org/projects/onap-dmaap-messagerouter-messageservice/en/latest/index.html#master-index
  4. Bus Controller: https://docs.onap.org/projects/onap-dmaap-buscontroller/en/latest/index.html#master-index
  5. Data Router: https://docs.onap.org/projects/onap-dmaap-datarouter/en/latest/index.html#master-index

...