Content Comparison

...

1. DCAE Platform: This is top priority because everything DCAE depends on it.  All platform components listed above fall under this priority.
2. DCAE Services: collectors and analytics that are needed for supporting the 4Q17 use cases and Open-O harmonization. We have identified the VES and SNMP Trap collectors; Threshold Crossing and Data Normalization Analytics, and Holmes.  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. 
3. Other collectors, analytics, and functions that have been identified as valuable by the community will be included based on resource availabilities in this and future releases of ONAP. 

...

• 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 ONAP Operations Manager and Common Controller SDK 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, OOM, CCSDK, DMaaP, Common Services, MultiVIM, Integration, Holmes
• 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.

• Meets Board policy (including IPR)

...

• Mature code that needs enhancement/integration: VES collector, TCA analytics, Dispatcher, Service Changing Handler, Inventory PGaaS, CDAP infrastructure, CDAP Broker, Holmes
• Incubation: Policy Handler, SNMP Trap collector, additional use case specific collectors/analytics/Blueprints, ESaaS,

...

...