...
- VES – AT&T
- Data Model
- VEs Agent
- NVFI - Intel (collectD)
- On-baoarding 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 – REL-JIO, Futurewei
- Storage – REL – JIO, Futurewei
- Hadoop
- Postgres SQL
- Analytics CLAMP Support (Clamp Sub Team)
- 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
- TOSCA Modeling
- Controller aligned with ONAP 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?
...
- How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possibleDCAE 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
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)
...