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-boarding 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 – Reliance Jio, Futurewei
As part of this activity, end to end flows shall be identified and published for achieving the following purpose:
a) To understand the dependencies of other components on the DCAE (APIs and interfaces needed from other components)
b) To identify the APIs which the DCAE will need to expose to support other components
c) In order to realise the use cases of vEPC, vIMS and vCPE, any additional delta functionalities that may be needed. - Storage – Reliance Jio, Futurewei, Tony Hansen (AT&T)
- Hadoop
- PostgreSQL
The DCAE should be able to plug into multiple storage software options - especially to make the data collected by the DCAE collector "queriable", so that meaningful actions can be taken based on the query results. One of the possible options to support additional storage fabrics is Elastic Search. The need and applicability of storage options will be closely tied to the use cases and call flows.
- Analytics
- Use Cases (VNFs ??)
- Micro-Service (Sub-Team)
- CLAMP Support (interfacing with Clamp Team)
Scope:
- To align with the ONAP release 1 objectives
- Open-O integration
- Use cases
- develop DCAE Adapter and DCAE functions for supporting VoLTE usecase
- TOSCA Modeling
- Controller aligned with Common Controller Framework 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?
- DCAE follows the current ONAP architecture
- 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, Hadoop
Resources:
- Primary Contact Person
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
Names, gerrit IDs, and company affiliations of the committers
Name Gerrit ID Company Email Time Zone Vijay Venkatesh Kumar AT&T Beijing, China. UTC +8 Serban Jora AT&T Beijing, China. UTC +8 Tony Hansen AT&T tony@att.com Beijing, China. UTC +8 Guangrong Fu ZTE fu.guangrong@zte.com.cn Beijing, China. UTC +8 Tang Peng ZTE tang.peng45@zte.com.cn Beijing, China. UTC +8 - 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:
Vijay Venkatesh Kumar vv770d@att.com
Serban Jora sj2381@att.com
Tony Hansen tony@att.com
Link to approval of additional submitters: