STATUS: Copy - Draft (still has skeleton infomraiton that needs to be removed, hence its is not yet DMaaP)
DMaaP (Data Movement as a Platform):
...
draw.io Diagram | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 capabilities
Data Compression capabilities
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
...
Interface Name | Interface Definition | Interface Capabilities | |||
---|---|---|---|---|---|
CLAMPEDMaaP-1 | Control Loop Lifecycle Management Interface. | A user interface for:
| DMaaP Bus Controller Interface Allows a DMaaP User to control the behavior of DMaaP | Provides services to enable a DMaaP user to:
| |
DMaaP-2 | DMaaP Message Router Source Interface Provides a message sending service to the DMaaP user | The message sender can:
| |||
DMaaP-3 | DMaaP Message Router Consuming Interface Provides a message receiving service to the DMaaP user | The message receiver can:
| |||
DMaaP-4 | DMaaP Data Routing Source Interface Provides a data sending service to the DMaaP user | The data sender can:
| |||
DMaaP-5 | DMaaP Data Routing Consumption Interface Provides a data consumtion service to the DMaaP user | The data consumer can:
| CLAMPE-2 | Control loop dashboard. User interface to show the overall status of the control loop through DMAAP events | Display and update:
|
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:
...
The provided UI interfaces are found at: CLAMP latest user guide
- CLAMP internal APIs can be found: clamp swagger pdf
- 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 DMaaPCLAMP consumes the following Interfaces:
Interface Name | Purpose Reason For Use |
---|---|
SDCE-6 | To Recieve the Control Loop Blueprint from SDCTo recieve |
PolicyE-2 | To create and configure the closed Loop Operational Policies and Confguration policies(DCAE Aps. Config.) |
DCAEE-x | Retrieve DCAE appplication status |
DCAEE-y | Deploy/remove DCAE application. |
3. Component Description:
A more detailed figure and description of the component.
<< For later inclusion >>
4. known system limitations
Runtime: None
Clamp data redundancy is dependant on kubernetes and the persisten volume.
Clamp appliation redundancy HA reliease on kubernetes
5. Used Models
DMaaP uses the following models:
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 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 X containers:of 3 main components:
- DMaaP Message Router
- DMaaP Data Router
- DMaaP Buss Controllerxx
draw.io Diagram border true viewerToolbar true fitWindow false diagramName CLAMP DMaaP runtime architectruearchitecture simpleViewer false width diagramWidth 821896 revision 16
This needs to be updated as this is not likely correct.
7. New Capabilities in this Release
...
- 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 at OOM deployment time via Bus Controller
8. References
- CLAMP Overview & User GuideDMaaP 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.readthedocs.io/en/latestcasablanca/submodules/clampdmaap/messagerouter/messageservice.git/docs/offeredapis/indexofferedapis.html CLAMP internal interfaces
- Controller: https://docs.onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf .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