...
- 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
- Postgres SQLPostgreSQL
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.
...
Serban Jora sj2381@att.com
Tony Hansen tony@att.com
Link to approval of additional submitters:
...