This section describes how to design, develop, and submit a Virtual Network Function for use as a Network Resource in the OpenECOMP 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 OpenECOMP. The completed VNF is submitted to the Certification Group (see Mailing Lists) as a collection of executable and text files, and must meet the set of requirements described in Creating a Virtual Network Function (VNF).
The primary audiences for this documentation are
- VNF providers: creators of VNFs (executables and related configuration files)
- Acceptance personnel: those tasked with certifying VNFs (approving them to run in OpenECOMP environments)
The following readers may wish to refer to this documentation for a deeper understanding of VNFs, however, for operational information, they should read Using OpenECOMP.
- Service Designers: those who combine Virtual Functions (including VNFs) into Services in OpenECOMP
- DevOps: those who deploy, operate, and monitor OpenECOMP Services containing VNFs
...
- vFW (Firewall)
- vDNS (Domain Name Server).
The Installation Installing and Running the OpenECOMP Demo page describes how to design and operate Services using these VNFs.