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

Compare with Current View Page History

« Previous Version 7 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 repository: DCAE

Project description:

  • VES – AT&T
    • Data Model
    • VEs Agent
    • NVFI - Intel  (collectD)
    • On-baoarding Yaml (Specification AT&T)
  • DCAE Collector - AT&T
    • VES
    • SNMP => VES
  • DCAE Controller – AT&T (TOSCA Model Based)
    • DMaaP Topic – AT&T
    • Component on-boarding
  • Call Flows – REL-JIO, Futurewei
  • Storage – REL – JIO, Futurewei
    • Hadoop
    • Postgres SQL
  • Analytics
    • CLAMP Support (Clamp Sub Team)
    • Use Cases (VNFs ??)
    • Micro-Service (Sub-Team)

Scope:

  • To align with the ONAP release 1 objectives
    • Open-O
    • Use cases
  • TOSCA Modeling
    • Controller aligned with ONAP Controller flow and format, on-boarding, VES yaml,
    • Run time support for dynamic DCAE parameters (e.g. VNF life cycle).
  • Questions
    • What do the R1 use cases need from DCAE?

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?
    • Please Include architecture diagram if possible
    • What other ONAP projects does this project depend on?
      • A&AI, Policy, Micro Services, CLAMP, SDC, ONAP Controller, Common Controller Framework
  • How does this align with external standards/specifications?
    • TOSCA
  • Are there dependencies with other open source projects?
    • CDAP, Cloudify, Consul

Resources:

  • Primary Contact Person

  • Company

    Name

    AT&T

    Alok Gupta


    Jerry Robinson


    Lusheng Ji

    Tech Mahindra

    Sandeep Singh


    Abhinav Singh


    Gokul Singraju

    Futurewei

     Xin Miao

    Deutsch Telcom

    Mark Fiedler

    Intel 

    Tim Verral

    Orange

    Vincent Colas

    Reliance Jio

    Aaush Bhatnagar

    Intel 

    Maryam Tahhan


    Tim Verral

  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • 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:
  • JIRA project prefix:

Repo name: Lifecycle State: Primary Contact: Project Lead: mailing list tag [Should match Jira Project Prefix]  Committers: foo@bar.com baz@qux.com *Link to TSC approval: 
Link to approval of additional submitters: 

  • No labels