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

Compare with Current View Page History

« Previous Version 50 Next »

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 top level repository name: dcaegen2
    • For the 4Q17 release, one of major goals for DCAE is to evolve from the "old" controller that is currently in gerrit.onap.org with a new controller that follows the Common Controller Framework.  The switch will maintain external (to other ONAP component) compatibility, but NOT backwards compatible internally.   That is, subcomponents built for the old controller will not work with the new controller or vice versa.  We are proposing to us a new top level naming “dcaegen2” for repos of subcomponents that are compatible with the new controller because it appears to be the cleanest approach to avoid confusion.  The existing "dcae" top level still hosts repos of subcomponent projects that are compatible with the old controller.  Eventually we will phase out the "dcae" tree but during the transition period both trees co-exist.

    • Detailed list of proposed subprojects and their repos
      DCAE Platform components:
      • DCAE Gen2 Controller
        • Repo:
          • dcaegen2/controller
          • dcaegen2/controller/dispatcher
          • dcaegen2/controller/inventory
          • dcaegen2/controller/sch
      • DCAE Gen2 Analytics Platform
        • Repo:
          • dcaegen2/apod/cdap
      • 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
      • Holmes correlation analytics
        • Repo:
          • dcaegen2/analytics/holmes

      Miscellaneous:
      • Demo
        • Repo:
          • dcaegen2/demo

Project description:

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


Because of the large potential scope for DCAE, the subprojects proposed for 4Q17 R1 are prioritized as follows: 

  1. DCAE Platform.  This is the foundation for DCAE, needed by any ONAP deployment that requires DCAE.  DCAE Platform includes the DCAE Controller Framework, dispatcher, inventory, service chaining, storage (Postgres), CDAP platform, etc.
  2. DCAE collectors and analytics that are needed by the 4Q17 use cases. So far we have identified the VES and SNMP Trap collectors; Threshold Crossing and String matching analytics.  We expect the list to grow and be finalized as the ONAP R1 use cases and the control loops for the use cases are fully defined.  
  3. Other collectors and analytics that have been identified as valuable by the community.

More specifically the DCAE team proposes the following sub-projects 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.
  • Analytics platform:
    • CDAP
  • 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.  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 vVoLTE and vCPE CLAMP flows.
    • 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 (depends on how 

(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?)


Scope:

For ONAP 4Q17 release, the proposed DCAE projects are centered around three high level objectives: 1. normalization with Open-O DCAE functions; 2. supporting ONAP TOSCA modeling approach; 3. supporting ONAP use cases including CLAMP, vCPE, VoLTE, and vFW/vDNS. 


Under these high level objectives, the scopes of DCAE projects cover the following functional items:

  • Normalization of OpenECOMP/OpenO data collection needs and realization
  • TOSCA model based artifact (component, VNF, and data) on-boarding
  • Catalog of artifact models
  • VNF/PNF data collection
  • New DCAE Controller that follows the Common Controller Framework, and supports DCAE component placement (e.g. edge/central) and federation
  • Supporting VES standardized VNF data modeling and collection
  • Event triggered life cycle management
  • Cloud computing Infrastructure event collection and analytics
  • Predictive analytics
  • AI/ML


Architecture Alignment:

  • 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 (OPNFV)
  • 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 Subproject
              Vijay Venkatesh Kumarvv770dAT&T

              vv770d@att.com

              		New Jersey, USA
              EST/EDT              		collectors

              controller

              Tony Hansen
              		AT&T tony@att.com

              New Jersey, USA

              EST/EDT

              		database,
              storage,
              analytics
              Adityakar Jha
              		Jioadityakar.jha@ril.comMumbai, India UTC +5:30Analytics platform
              Aayush Bhatnagar
              		Jioaayush.bhatnagar@ril.comMumbai, India UTC +5:30Analytics platform
              Yog Vashishth
              		Jioyog.vashishth@ril.comMumbai, India UTC +5:30Analytics platform
              Guangrong Fu
              		ZTEfu.guangrong@zte.com.cnBeijing, China. UTC +8holmes
              Tang Peng
              		ZTEtang.peng45@zte.com.cnBeijing, China. UTC +8holmes
              Avinash SAvinashSHuaweiavinash.s@huawei.comBangalore, India UTC +5:30???
              Alok Gupta
              		AT&Tag1367@att.com
              		collectors
              Lusheng Ji
              		AT&Tlji@research.att.com

              Yusuf Mirza
              		IBMymirza@ae.ibm.comDubai, UAE. UTC +4

              ???

              Mike Hwang
              		AT&Tmhwang@research.att.comNew Jersey, USA EST/EDTcontroller
              Yan Yang
              		China Mobileyangyanyjy@chinamobile.comBeijing, China. UTC +8collectors

          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 Verrall

          Orange

          Vincent Colas


          Olivier Augizeau


          		 Pawel Pawlak

          Reliance Jio

          Aayush Bhatnagar


          		Yog Vashishth

          		Adityakar Jha

          Intel 

          Maryam Tahhan


          Tim Verrall

          VMwareSumit Verdi
          HuaweiAvinash S
          IBMYusuf Mirza
          IBMDavid Parfett
          China MobileYuan Liu




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

      The current seed code has been already scanned and cleanup to remove all proprietary trademarks, logos, etc. except openecomp to be replaced by onap

      Subsequent modification to the existing seed code should continue to follow the same scanning and clean up principles.

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

Repo name: Lifecycle State: Primary Contact: Project Lead: mailing list tag [Should match Jira Project Prefix] 


Link to approval of additional submitters: 


  • No labels