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

Compare with Current View Page History

« Previous Version 2 Next »

DRAFT  - as of 3/1 

  1. Project Overview

    DCAE includes number of components collectively fulfilling the role of Data Collection, Analytics, and Events generation for ONAP.  The architecture of DCAE targets flexible, plug-able, micros-service oriented, model based component deployment and service composition.  DCAE also support multi-site collection and analytics operations which are essential for large ONAP deployments. 

    DCAE components generally fall into two categories: DCAE Platform Components and DCAE Services Components.

    DCAE Platform refers the set of controller components which manages the deployment and LCM of the DCAE service components which include all the collectors, analytics and event processor MS. 

     

  2. New component capabilities for Dublin, i.e. the functional enhancements

    Collectors

    RESTConf collector            

    Event Processors

    VES/Universal Mapper 
    3gpp PM-Mapper  
    BBS Event processor
    DL Handlers (POC)

    Analytics/RCA


    SON-Handler (former PCI-Handler)
    Heartbeat (STRETCH GOAL) 
    TCA-Gen2  (STRETCH GOAL)

     

  3. New or modified interfaces

      4.   <include arc diagram>

  4. Interface naming

                 <refer m1>

  5. Reference to the interfaces


  6. What are the system limits

    Relies on k8s for loadbalancing and scaling. DCAE platform handles the control flow and do not carry the data/event; DCAE service components can be scaled and support state management.
    Cloudify is 3rd party product; HA feature on community version will be available later in 2019; will be incorporated for E release

  7. Involved use cases, architectural capabilities or functional requirements

    1. Usecases

      •5G Use Case (Dublin)
      •5G - Bulk PM (Casablanca carry-over items)
      •5G - OOF and PCI (Casablanca carry-over items)
      •BBS Broadband Service Use Case (Dublin)
      •CCVPN (E-LAN Service (EP-LAN, EVP-LAN) *, https://wiki.onap.org/pages/viewpage.action?pageId=45296665
      •Model Driven Control Loop Requirements

    2. DL POC

  8. Listing of new or impacted models used by the project (for information only)

    1. Support for new policy model as required by Model driven control loop requirement.

  • No labels