Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This is a potential draft of a project proposal template.  It is not final or to be used until the TSC approves it.

Project Name:

  • 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 Gen2  VES Collector
      • Repo:
        • dcaegen2/collectors/ves
    • DCAE Gen2 SNMP Trap Collector
      • Repo:
        • 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 Analytics
      • Repo:
        • dcaegen2/apod/analytics-ms

    • DCAE Gen2 Utilities
      • Repo:
        • dcaegen2/utils

    • Demo
      • Repo:
        • dcaegen2/demo

    • Holmes
      • Repos: ??

Project description:


DCAE is the umbrella name for a number of projects, 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.

...

  • 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 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
  • 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

Resources:

  • Primary Contact Person

    John F. Murray (AT&T)

    Lusheng Ji (AT&T)

    Names, gerrit IDs, and company affiliations of the committers

    (Note to DCAE team members: due to the scope and number of projects under DCAE, and number of willing committers may exceed Linux Foundation tradition, usually 2~3 committers per project, we may need to partition based on sub-projects/repos if being requested.  Please specify the sub-projects/repos that you are interested in. )

    NameGerrit IDCompanyEmailTime ZoneDCAE Project
    Vijay Venkatesh Kumarvv770dAT&T

     vv770d@att.com

    New Jersey, USA
    EST/EDT

    Serban Jora
    AT&T

     sj2381@att.com



    Tony Hansen
    AT&T tony@att.com

    New Jersey, USA

    EST/EDT


    Guangrong Fu
    ZTEfu.guangrong@zte.com.cnBeijing, China. UTC +8
    Tang Peng
    ZTEtang.peng45@zte.com.cnBeijing, China. UTC +8
    Alok Gupta
    AT&Tag1367@att.com

    Lusheng Ji
    AT&Tlji@research.att.com


    • Names and affiliations of any other contributors

      Company

      Name

      AT&T

      Alok Gupta


      Jerry Robinson


      Lusheng Ji


      Tony Hansen

      Vijay Venkatesh Kumar

      Tech Mahindra

      Sandeep Singh


      Abhinav Singh


      Gokul Singraju

      Futurewei

       Xin Miao

      Deutsch Telcom

      Mark Fiedler

      Intel 

      Tim Verral

      Orange

      Vincent Colas

      Reliance Jio

      Aayush Bhatnagar

      Intel 

      Maryam Tahhan


      Tim Verral

      VMwareSumit Verdi
  • Project Roles (include RACI chart, if applicable)

Other Information:

  • link to seed code (if applicable)
  • Vendor Neutral
    • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
  • Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name: DCAE
  • JIRA project prefix: DCAE

...