...
A Virtual Network Function can be developed in a stand-alone development environment without most of the tools – or even API libraries – used or furnished by ONAP. The completed VNF is submitted to the Certification Group (see Mailing Lists) as a collection of executable and text files, and must VNF must meet the set of requirements described in the Reference Documents for VNF Providers, below VNF Requirements.
The primary audiences for this documentation are
...
| Anchor | ||||
|---|---|---|---|---|
|
The following reference documents contain guidelines and requirements for VNF Providers.
VNF Guidelines for Network Cloud and OpenECOMP
- identifies audiences interested in VNFs
- describes the VNF environment
- gives an overview of requirements
- points out differences between ONAP VNFs and ETSI VNFs
VNF Cloud Readiness Requirements for OpenECOMP
- design requirements (API versioning, decomposition, reliance on open source database, packet size limitations)
- resiliency requirements
- security requirements
VNF Management Requirements for OpenECOMP
- requirements imposed by the targeted network cloud infrastructure, including the hypervisor
- identification requirements for the VNF and its components
- configuration management requirements
- a VNF must provide a Device YANG model
- a VNF must implement a NETCONF server; the required NETCONF API's are referenced, and the supplier must demonstrate mounting the NETCONF server on OpenDaylight
- monitoring and operations requirements
- format of messages (event records)
- frequency of reporting
- security
- licensing requirements
VNF Heat Template Requirements for OpenECOMP
...
ONAP release documentation is available at ONAP.readthedocs.io, including VNF Provider guidance: VNF Guidelines, VNF Requirements
Example VNFs Included with ONAP
...
The Setting Up ONAP pages describe how to design and operate Services using these VNFs.
Reference VNFs are managed by the Integration Project.