...
- DCAE Platform. This is the foundation for DCAE, needed by any ONAP deployment that requires DCAE. DCAE Platform includes the DCAE Controller Framework, dispatcher, inventory, service chaining, storage (Postgres), CDAP platform, etc.
- DCAE collector collectors and analytics that are needed by the 4Q17 use cases. So far we have identified the VES and SNMP Trap collectors; Threshold Crossing and String matching analytics. We expect the list to grow and be finalized as the ONAP R1 use cases and the control loops for the use cases are fully defined.
- Other collectors and analytics that have been identified as valuable by the community.
...
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, PNFs, 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, Integration
- How does this align with external standards/specifications?
- TOSCA
- VES (OPNFV)
- Are there dependencies with other open source projects?
- CDAP, Cloudify, Consul, Hadoop, Elastic Search, PostgreSQL, MariaDB
...
- link to seed code (if applicable)
- https://gerrit.onap.org/r/#/admin/projects/dcae/*
- https://gerrit.open-o.org/r/#/admin/projects/holmes-[actions,gui,rule-management,engine-management]
- 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?
The current seed code has been already scanned and cleanup to remove all proprietary trademarks, logos, etc. except openecomp to be replaced by onap
Subsequent modification to the existing seed code should continue to follow the same scanning and clean up principles.
- 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)
...