Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

STATUS: Copy - Draft (still has skeleton infomraiton that needs to be removed, hence its is not yet DMaaP)

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 NameInterface Definition Interface Capabilities
DMaaP-1Control Loop Lifecycle Management Interface.   A user interface for:
  • Selecting the control loop flow
  • entering configuration policy paramaters
  • entering operational policy parameters
  • Managing lifecycle of DCAE conrol flow blueprint 
CLAMPE-2Control loop dashboard.  User interface to show the overall status of the control loop through DMAAP events

 Display and update:

  • Events recieved and actions taken on the control loop.

Note:   xxxI interface is a Component internal interface.  xxxxE interface is a component external interface

The current API documents can be found at:

CLAMP consumes the following Interfaces:

Interface NamePurpose Reason For Use
SDCE-6To Recieve the Control Loop Blueprint from SDCTo recieve
PolicyE-2To 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:

??

6. System Deployment Architecture


DMaaP consists of X containers:

  • xx

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

  1.  CLAMP Overview & User Guide: https://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html 
  2. CLAMP internal interfaces:  https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf 


  • No labels