STATUS: Draft
DMaaP (Data Movement as a Platform):
1 High Level Component Definition and
...
Architectural Relationships
| Drawio | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
DMaaP is component that provides data movement services that transports and processes data from any source to any target. It provides the capability to:
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 capabilitiesData Compression capabilities
Data routing (file based transport)
Message routing (event based transport)
Batch and event based processing
...
- Service Design and Creation
- Policy
- Data Collection Analytics and Events
- Other
2. DMaaP API definitions
DMaaP provides the following interfaces:
...
| Interface Name | Purpose Reason For Use |
|---|---|
| N/A | N/A |
3. Component Description:
DMaaP consists of 4 3 software syatemscomponents
- 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 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 does not use any models.
6. System Deployment Architecture
DMaaP consists of 3 main components:
...
Drawio border true viewerToolbar true fitWindow false diagramName DMaaP runtime architecture simpleViewer false widthdiagramWidth 896 revision 1
This needs to be updated as this is not likely correct.
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 ControllerDMaaP Provisioning at OOM deployment time via Bus ControllerJava11 upgrade for all components
- Init containers for certificate management
- SSL Listeners for Kafka internal communication
- TSC Priority 1 Non-functional requirements
8. References
- DMaaP on readthedocs: https://docs.onap.org/en/casablanca/guides/onap-developer/developing/index.html#data-management-as-a-platform-data-bus-controller
- Message Router: https://docs.onap.org/en/casablanca/submodules/dmaap/messagerouter/messageservice.git/docs/offeredapis/offeredapis.html
- Controller: https://docs.onap.org/en/casablanca/submodules/dmaap/dbcapi.git/docs/api.html
- Data Router: https://docs.onap.org/en/casablanca/submodules/dmaap/datarouter.git/docs/index.html
...