• Created by Unknown User (fay), last modified on Jan 12, 2017

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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.

Overview: Guidelines for Virtual Network Functions in a Network Cloud

The following document describes the high-level requirements for VNFs, and should be considered required reading for VNF developers. It also provides background material: the motivation for VNFs, and the various audiences interested in VNFs. In addition, it spells out the differences between OpenECOMP VNFs and ETSI VNFs.

<< point to the document "Guidelines for Virtual Network Functions in a Network Cloud" when it is "open" >>

Figure 1 VNF Complete Lifecycle Stages

VNF Requirements

The following document provides a comprehensive set of requirements that a VNF must meet. These fall into the categories of packaging, configuration, run-time monitoring and management, and licensing. The document also specifies the contents of 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.

<< Another Reference: "OpenECOMP Requirements for Virtual Network Functions:>>

The VNF API

All VNF's (in fact, all Virtual Functions of any kind) should contain monitoring properties.

VNF Attribute Definitions

Registering a VNF

Activating a VNF


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


  • No labels