This section describes how to design, develop, and submit a Virtual Network Function for use as a Network Resource in the ONAP environment.
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 must meet the set of VNF Requirements.
The primary audiences for this documentation are
The following readers may wish to refer to this documentation for a deeper understanding of VNFs, however, for operational information, they should read Using ONAP.
There are three stages in the life cycle of a VNF, shown here:
Figure 1. VNF complete life cycle stages
The ONAP release documentation is available at ONAP.readthedocs.io, including VNF Provider guidance: VNF Guidelines, VNF Requirements
The example VNFs distributed with ONAP are:
The Setting Up ONAP pages describe how to design and operate Services using these VNFs.
Reference VNFs are managed by the Integration Project.