This page describes how to create, register, and activate a Virtual Network Function, which is a Network Virtual Network Function (VNF) Onboarding.

In this specification, the terms must, must not, should, should not, and may have specific meanings defined here.

Guidelines for Virtual Network Functions in a Network Cloud

The following document describes, in general terms, the requirements for VNFs. It also provides background material: the motivation for VNFs, and the various audiences interested in VNFs. In addition, it points out, in general terms, the differences between OpenECOMP VNFs and ETSI VNFs.

<< "Guidelines for Virtual Network Functions in a Network Cloud" >>

Figure 1 VNF Complete Lifecycle Stages

VNF Requirements

VNFs must meet requirements that fall into the categories of packaging, configuration, run-time monitoring and management, and licensing. Also VNF must communicate using event records (indicating a change of state, or loggable event, for example).

With respect to packaging, the specification states that "Initially this information may be provided in documents, but in the near future a method will be developed to automate as much of the transfer of data as possible...".

Regarding configuration management, "The VNF providers must provide the device YANG model and NETCONF server, supporting NETCONF APIs, to comply with target OpenECOMP and industry standards." In addition, the supplier "shall demonstrate mounting the NETCONF server on OpenDaylight (client)...", and successfully carry out specified operations thereon.

For run-time monitoring and management, a VNF must provide event records as specified in the document.

Finally, VNFs must conform to certain licensing restrictions, such as providing a universal license key, providing metrics (such as the number of subscribers), an not depending on a license server.

The following reference document lists, in detail, the requirements for VNFs. These requirements are grouped into the following categories: Network Cloud Infrastructure, Resiliency, Security, Deployment, Testing, Validation and Support, and Network.

<< Reference: "Common Requirements for Virtual Network Functions" >>

Specific additional requirements for VNFs to run in OpenECOMP can be found in: << Reference: "OpenECOMP Requirements for Virtual Network Functions:>>

The VNF API

VNF Attribute Definitions

Registering a VNF

Activating a VNF

The <<SDC Demo Guide>> gives an example of onboarding a VNF.