DCAE (5/11/17)

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: dcaegen2
(Note. Due to new requirements, for this release DCAE will switch to adopting the Common Controller Framework/ONAP Operations Manager for its control and orchestration functions. To avoid confusions in code compatibility under the current v.s. new controller frameworks, we propose to use a new top level repo name: dcaegen2)
- DCAE Gen2 VES Collector
  - Repo:
    - dcaegen2/collectors/ves
- DCAE Gen2 SNMP Trap Collector
  - Repo:
    - dcaegen2/collectors/snmptrap
- DCAE Gen2 Controller
  - Repo:
    - dcaegen2/controller
    - dcaegen2/controller/dispatcher
    - dcaegen2/controller/inventory
    - dcaegen2/controller/sch
- DCAE Gen2 Persistent Storage
  - Repo:
- dcaegen2/storage/pgaas
- dcaegen2/storage/esaas
- dcaegen2/storage/mdbaas

- DCAE Gen2 Analytics
  - Repo:
    - dcaegen2/apod/analytics-ms
- DCAE Gen2 Utilities
  - Repo:
    - dcaegen2/utils
- Demo
  - Repo:
    - dcaegen2/demo
- Holmes
  - Repos: ??

Project description:

DCAE is the umbrella name for a number of projects, collectively fulfilling the role of Data Collection Events and Analytics for ONAP. The architecture of DCAE targets flexible, plug-able, micros-service oriented, and model based component deployment and service composition.

The DCAE team proposes the following projects for 4Q17 R1 ONAP release.

Collectors:

VES Collector: VNF Event Stream collector
SNMP Trap collector:

Controller:

The new ONAP DCAE (gen2) controller follows the paradigm of Common Controller Framework for command and control. Hence the core function of the DCAE Controller code resides within the Common Controller Framework project. This project is for adaptation of the Common Controller Framework for DCAE use.

Storage: this group of projects provides data storage solutions for DCAE. The common usages include supporting DCAE's own functions; storage for data analytics; persistent data storage; etc. For this release we target three popular database technologies.

Postgres as a Service (PGaaS)
Elastic Search as a Service (ESaaS)
MariaDB as a Service (MDBaaS)

Analytics: this group of projects include various analytics related components and applications. At this point, we have only placed placeholders for repos for analytics, due to the fact that the DCAE requirements (i.e. what kind of analytics are needed for supporting the vCPE and VoLTE use cases) are still unknown.
Utilities: this project contains various utility for DCAE development, testing, and operations.
Demo: this project contains additional, scripts, and miscellaneous data and files for supporting demo use cases
Holmes: this is an OpenO project that performs similar/related role to DCAE. Further information is needed for identifying path for normalization.

(Notes to DCAE team members: previously we also had DMaaP topics and Call Flow proposals. After consulting with other project teams, DMaaP topic related work is better suited under the DMaaP project; and call flow related work overlaps with the CLAMP team work. It would seem that these two do not need separate project proposals under DCAE. In addition, there were items related to code that is done outside of ONAP, e.g. collectd, VES agent. ONAP will use them but do they need separate projects/repos under DCAE?)

Scope:

For ONAP 4Q17 release, the proposed DCAE projects are centered around three high level objectives: 1. normalization with Open-O DCAE functions; 2. supporting ONAP TOSCA modeling approach; 3. supporting ONAP use cases including CLAMP, vCPE, VoLTE, and vFW/vDNS.

Under these high level objectives, the scopes of DCAE projects cover the following functional items:

Normalization of OpenECOMP/OpenO data collection needs and realization
TOSCA model based artifact (component, VNF, and data) on-boarding
Catalog of artifact models
VNF/PNF data collection
New DCAE Controller that follows the Common Controller Framework, and supports DCAE component placement (e.g. edge/central) and federation
Supporting VES standardized VNF data modeling and collection
Event triggered life cycle management
Cloud computing Infrastructure event collection and analytics
Predictive analytics
AI/ML

Architecture Alignment:

How does this project fit into the rest of the ONAP Architecture?

DCAE performs a vital function within the ONAP architecture. DCAE collects performance metrics and fault data from the VNFs and computing infrastructure, performing local and global analytics, and generating events that are provided for downstream ONAP components (e.g. Policy) for further operations.

DCAE follows the TOSCA model based Common Controller Framework architecture for component on-boarding, close-loop triggered or event (e.g. A&AI) triggered collector and analytics deployment, configuration, and scaling.
What other ONAP projects does this project depend on?
- A&AI, Policy, Micro Services, Modeling, CLAMP, SDC, ONAP Controller, Common Controller Framework, DMaaP, Common Services
How does this align with external standards/specifications?
- TOSCA
- VES
Are there dependencies with other open source projects?
- CDAP, Cloudify, Consul, Hadoop, Elastic Search, PostgreSQL, MariaDB

Resources:

Primary Contact Person

John F. Murray (AT&T)

Lusheng Ji (AT&T)

Names, gerrit IDs, and company affiliations of the committers

(Note to DCAE team members: due to the scope and number of projects under DCAE, and number of willing committers may exceed Linux Foundation tradition, usually 2~3 committers per project, we may need to partition based on sub-projects/repos if being requested. Please specify the sub-projects/repos that you are interested in. )

Name	Gerrit ID	Company	Email	Time Zone
Vijay Venkatesh Kumar	vv770d	AT&T	vv770d@att.com	New Jersey, USA EST/EDT
Serban Jora		AT&T	sj2381@att.com
Tony Hansen		AT&T	tony@att.com	New Jersey, USA EST/EDT
Guangrong Fu		ZTE	fu.guangrong@zte.com.cn	Beijing, China. UTC +8
Tang Peng		ZTE	tang.peng45@zte.com.cn	Beijing, China. UTC +8
Avinash S	AvinashS	Huawei	avinash.s@huawei.com	Bangalore, India UTC +5:30
Alok Gupta		AT&T	ag1367@att.com
Lusheng Ji		AT&T	lji@research.att.com

Names and affiliations of any other contributors

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
	Yog Vashishth
	Adityakar Jha
Intel	Maryam Tahhan
	Tim Verral
VMware	Sumit Verdi
Huawei	Avinash S

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