Versions Compared

Old Version 12

changes.mady.by.user Paul Dennehy

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Terrill

Saved on

Key

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

...

draw.io Diagram
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameDMaaP System Context View
simpleViewerfalse
diagramWidth8781031
revision58


DMaaP is comonent component that provides data movement services that transports and processes data from any source to any target.  It provides the capability to:

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

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

  • Data Filtering capabilities

  • Data Compression capabiltiescapabilities

  • Data routing (file based transport)

  • Message routing (event based transport)

  • Batch and event based processing

...

Interface NameInterface Definition Interface Capabilities
DMaaP-1

DMaaP Bus Controller Interface

Allows a DMaaP User to control the behaviour behavior of DMaaP

  Provides services to enable a DMaaP user to:
Please add the capabilities here
  • Provision a Topic in Message Router
    • Creates the topic on MR instance
    • Creates topic Permissions in AAF
    • Creates topic Roles in AAF with appropriate Permissions
    • Associates ONAP application identities to topic Roles
  • Provision a Feed in Data Router
    • Associates publisher credentials with Feed
    • Creates any ingress rules for publish route optimization
  • Provision a Subscriber in Data Router
    • Associates subscriber credentials with feed delivery
    • Creates any egress rules for delivery route optimization
  • Provisions Mirror Maker for any message replication between 2 MR instances
  • Tracks the deployment of DMaaP components vs some network location
DMaaP-2

DMaaP Message Router Source Interface

Provices Provides a message sending service to the DMaaP user

 The message sender can:

  • Provision (create/modify/delete) Message Router topics
  • Retrieve individual topic details
  • Retrieve a list of all topics on the message router
  • Publish messages to a message router topic
DMaaP-3

DMaaP Message Router Consuming Interface

Provides a message recieving receiving service to the DMaaP user

The message reciever receiver can:

  • Retrieve a list of all topics on the message router
  • Retrieve individual topic details
  • Subscribe / Unsubscriber Unsubscribe to message router topics
  • Recieve Receive (with filter) messages
DMaaP-4

DMaaP Data Routing Source Interface

Provides a data sending serivce service to the DMaaP user

The data sender can:

  • Create/Update/Delete a data feed
  • Retrieve a representation of the data feed
  • Publish data to a data feed
  • Delete a published data from a data feed
DMaaP-5

DMaaP Data Routing Comsumption Consumption Interface

Provides a data consumtion service to the DMaaP user

The data consumer can:

  • Retrieve a representation of the data feed
  • Subscribe / Unsubscriber to a data feed
  • Retrieve data from a data feed.

...

  • 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 - Provisioning API of the Data Movement Platform

Futher detailing will be done later.

4. known system limitations

...

  • that can be used for provisioning topics in the Message Router and feeds in Data Router. In addition Bus Controller is also used for provisioning Mirror Maker capability between two Message Router instances to replicate messages

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 uses the following models:??does not use any models.

6. System Deployment Architecture


DMaaP consists of 3 containersmain components:

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

...