STATUS: Draft
DMaaP (Data Movement as a Platform):
1 High Level Component Definition and Architecteral Relationships
DMaaP is comonent that provides data movement services that transports and processes data from any source to any target. It provides the capability to:
Support the tranfer of messages between ONAP components, as well as to other components
Support the transfer of data between ONAP comonents as well as to other components.
Data Filtering capabilities
Data Compression capabilties
Data routing (file based transport)
Message routing (event based transport)
Batch and event based processing
The data providers and data consumers are
- Service Design and Creation
- Policy
- Data Collection Analytics and Events
- Other
2. DMaaP API definitions
DMaaP provides the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| DMaaP-1 | DMaaP Controller Interface Allows a DMaaP User to control the behaviour of DMaaP | Provides services to enable a DMaaP user to:
|
| DMaaP-2 | DMaaP Message Router Source Interface Provices a message sending service to the DMaaP user | The message sender can:
|
| DMaaP-3 | DMaaP Message Router Consuming Interface Provides a message recieving service to the DMaaP user | |
| DMaaP-4 | DMaaP Data Routing Source Interface Provides a data sending serivce to the DMaaP user | |
| DMaaP-5 | DMaaP Data Routing Comsumption Interface Provides a data consumtion service to the DMaaP user |
Note: xxxI interface is a Component internal interface. xxxxE interface is a component external interface
The current API documents can be found at:
- Message Router Interface: https://docs.onap.org/en/casablanca/submodules/dmaap/messagerouter/messageservice.git/docs/offeredapis/offeredapis.html
- DMaaP Controller Interface: https://docs.onap.org/en/casablanca/submodules/dmaap/dbcapi.git/docs/api.html
- Data Routing: https://docs.onap.org/en/casablanca/submodules/dmaap/datarouter.git/docs/index.html
The following interfaces are consumed by DMaaP
| Interface Name | Purpose Reason For Use |
|---|---|
| N/A | N/A |
3. Component Description:
DMaaP consists of 4 software syatems
- 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 Movement Director (DMD) - A client to DMaaP platform to publish & subscribe data.
- Data Bus Controller - Provisioning API of the Data Movement Platform
Futher detailing will be done later.
4. known system limitations
To be documented
5. Used Models
DMaaP uses the following models:
??
6. System Deployment Architecture
DMaaP consists of 2 containers:
- One container for the data movement director and the data bus controller
- One container for the data router and message router
I wasn't sure what was correct, hence I didn't update this
7. New Capabilities in this Release
This release, DMaaP adds the following Capabilities:
- DMaaP - Message Router
- Upgrade Kafka to v1.1.1
- Support for Authenticated topics
- Add scalign support
- Support for multi-site applications
- Add Mirrormaket to allo for message replication accross Kfka clusters
- DMaaP - data router
- Date Router updates to support 5G Bulk PM use case
- DMaaP - Bus Controller
- DMaaP Provisioning via Bus Controller
8. References
- CLAMP Overview & User Guide: https://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html
- CLAMP internal interfaces: https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf