Page History

...

• Proposed name for the project: DCAE
• Proposed name for the repository: dcaegen2
  (Note. Due to new requirements, for this release DCAE will switch to adopting the Common Controller Framework/ONAP Operations Manager for its control and orchestration functions.  To avoid confusions in code compatibility under the current v.s. new controller frameworks, we propose to use a new top level repo name: dcaegen2) 
  DCAE Platform components:
  Gen2  VES Collector
  • Repo:
    • dcaegen2/collectors/ves
  DCAE Gen2 SNMP Trap CollectorRepo:dcaegen2/collectors/snmptrap
  • DCAE Gen2 Controller
    • Repo:
      • dcaegen2/controller
      • dcaegen2/controller/dispatcher
      • dcaegen2/controller/inventory
      • dcaegen2/controller/sch
  • DCAE Gen2 Persistent Storage
    • Repo:
      • dcaegen2/storage/pgaas
      • dcaegen2/storage/esaas
      • dcaegen2/storage/mdbaas
  • DCAE Gen2 Utilities
    • Repo:
      • dcaegen2/utils
        
        
  DCAE applications and service components:
  
  • DCAE Gen2  VES Collector
    • Repo:
      • dcaegen2/collectors/ves
  • DCAE Gen2 SNMP Trap Collector
    • Repo:
      • dcaegen2/collectors/snmptrap

• • DCAE Gen2 CDAP Analytics
    • Repo:
      • dcaegen2/apod/analytics-ms
    DCAE Gen2 Utilities
  • Holmes correlation analytics
    • Repo:
      • dcaegen2/utils/analytics/holmes
        
        
  Miscellaneous:
  
  • Demo
    • Repo:
      • dcaegen2/demo
        
    Holmes
    • Repos: ??

Project description:

DCAE is the umbrella name for a number of projectssubprojects, collectively fulfilling the role of Data Collection Events and Analytics for ONAP.  The architecture of DCAE targets flexible, plug-able, micros-service oriented, and model based component deployment and service composition.

The DCAE team proposes the following projects subprojects for 4Q17 R1 ONAP release.

...

DCAE Platform components:

• Controller:
  • The new ONAP DCAE (gen2)  controller follows the paradigm of Common Controller Framework for command and control.  Hence the core function of the DCAE Controller code resides within the Common Controller Framework project.  This project is for adaptation of the Common Controller Framework for DCAE use.
• Storage: this group of projects provides data storage solutions for DCAE.  The common usages include supporting DCAE's own functions; storage for data analytics; persistent data storage; etc.  For this release we target three popular database technologies.
  • Postgres as a Service (PGaaS)
  • Elastic Search as a Service (ESaaS)
  • MariaDB as a Service (MDBaaS)
• Utilities: this project contains various utility for DCAE development, testing, and operations.
  

DCAE applications and service components:

• Collectors:
  • VES Collector:  VNF Event Stream collector
  • SNMP Trap collector
  • ... (Possibly more based on identified 4Q17 use case needs, community interests, and available resources).
    
• Analytics: this group of projects include various analytics related components and applications.   At this point, we have only placed placeholders for repos for analytics, due to the fact that the DCAE requirements (i.e. what kind of analytics are  Three projects are proposed under this group:
  • Threshold Crossing Analytics: for performance metric threshold crossing analysis that is needed for supporting vFW/vDNS control flow.
  • String Match: for SNMP trap analysis that is needed for supporting the
  vCPE and VoLTE use cases) are still unknown
  • vVoLTE and vCPE CLAMP flows.
  Utilities: this project contains various utility for DCAE development, testing, and operations.
  • Holmes: integration of the OpenO Mercury release alert correlation analytics.

Miscellaneous:

• Demo: this project contains additional, scripts, and miscellaneous data and files for supporting demo use cases
  
• Holmes: this is an OpenO project that performs similar/related role to DCAE.  Further information is needed for identifying path for normalization.
• 
  

(Notes to DCAE team members:  previously we also had DMaaP topics and Call Flow proposals.  After consulting with other project teams, DMaaP topic related work is better suited under the DMaaP project; and call flow related work overlaps with the CLAMP team work.  It would seem that these two do not need separate project proposals under DCAE.  In addition, there were items related to code that is done outside of ONAP, e.g. collectd, VES agent.  ONAP will use them but do they need separate projects/repos under DCAE?)

...

• How does this project fit into the rest of the ONAP Architecture?
  
  DCAE performs a vital function within the ONAP architecture.  DCAE collects performance metrics and fault data from the VNFs, PNFs, and computing infrastructure, performing local and global analytics, and generating events that are provided for downstream ONAP components (e.g. Policy) for further operations.
  
  

  DCAE follows the TOSCA model based Common Controller Framework architecture for component on-boarding, close-loop triggered or event (e.g. A&AI) triggered collector and analytics deployment, configuration, and scaling.

• 
• What other ONAP projects does this project depend on?
  • A&AI, Policy, Micro Services, Modeling, CLAMP, SDC, ONAP Controller, Common Controller Framework, DMaaP, Common Services, Integration
• How does this align with external standards/specifications?
  • TOSCA
  • VES
• Are there dependencies with other open source projects?
  • CDAP, Cloudify, Consul, Hadoop, Elastic Search, PostgreSQL, MariaDB

...