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?
    • VNFs 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: 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

...