...
- 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
- 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?
- Describe the functionality to be provided by the project. Please provide the full intended scope of the project; not just what is intended for the project's first release.
- Specify any interface/API specification proposed,
- Identity a list of features and functionality will be developed.
- Identify what is in or out of scope. During the development phase, it helps reduce discussion.
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 SevicesServices, CLAMP, SDC, ONAP Controller
- Please Include architecture diagram if possible
- How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
- Are there dependencies with other open source projects?
- APIs/Interfaces
- Integration Testing
- etc.
...