Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

Version 1 Next »

This page is still in draft mode

  • Brief Project Overview (brief as it should be known)
    • DMaaP is a premier platform for high performing and cost effective data movement services that transports and processes data from any source to any target with the format, quality, security, and concurrency required to serve the business and customer needs.
    • DMaaP has  four components
      • 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 (BC): Provisioning API of the Data Movement Platform.
    • For a more detailed overview - https://wiki.onap.org/pages/viewpage.action?pageId=3247130
  • New component capabilities for Dublin, i.e. the functional enhancements.
    • DMaaP - Message Router
      • Upgrade Kafka to v1.1.1
      • Support for Authenticated topics
      • Add Scaling support
      • Support for multi-site applications
      • Add MirrorMaker to allow for message replication across Kafka clusters
    • DMaaP - Data Router
      • Data Router updates to support Bulk PM use cases
    • DMaaP - Bus Controller
      • DMaaP Provisioning via Bus Controller
  • New or modified interfaces
    • None
  • If they are modified, are the backwards compatible?
    • N/A
  • Interface naming (point to an example)
    • REST interface with various APIs for the three components. Details the API signature at the links below
  • Reference to the interfaces.
  • What are the system limits?
    • TBD
  • Involved use cases, architectural capabilities or functional requirements.
  • Listing of new or impacted models used by the project (for information only).
    • None

 

 

AT&T Proprietary (Internal Use Only)
Not for use or disclosure outside the AT&T companies except under written agreement

 

  • No labels