Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • How does this project fit into the rest of the ONAP Architecture?
    • Please Include architecture diagram if possibleVNFs are managed by ONAP but they are not part of the ONAP architecture. VNFs expose APIs that are used for management (by ONAP) and measurements/faults reports (to ONAP)
  • What other ONAP projects does this project depend on?
    • Reference VNFs depend on ONAP use cases
  • How does this align with external standards/specifications?
    • APIs/Interfaces: Reference VNFs export NETCONF and RestCONF APIs that allow ONAP to manage them
    • Information/data models: JSON objects are used for bi-directional communication with ONAP. VES is used to report metrics
  • Are there dependencies with other open source projects?
    • APIs/Interfaces
    • Integration Testing
    • etc.: vFirewall and vLoadBalancer are based on VPP (Cisco open source). The NETCONF and RestCONF interfaces depend on the Honeycomb project (FD.io), metrics reporting is based on VES

Resources:

  • Primary Contact Person: Marco Platania
  • Names, gerrit IDs, and company affiliations of the committers: Marco Platania, platania, AT&T
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

Other Information:

  • link to seed code (if applicable)http://gerrit.onap.org/r/dcae/demo
  • 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)

...

Repo name:
Lifecycle State:
Primary Contact: Marco Platania
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: