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 motivation for VNFs, the various audiences interested in VNFs, and 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" >>

A key distinction between VNFs created for OpenECOMP versus VNFs created for ETSI's MANO model is this: under OpenECOMP, VNF providers do not provide their own proprietary VNF Managers (VNFM) or Element Management Systems (EMS). Those capabilities are provided by OpenECOMP. Hence, VNFs are required to consume standard interfaces to OpenECOMP in support of management and control. The VNF Package must include the appropriate data models for integration with OpenECOMP to enable control of the VNFs. The resulting standardization of VNFs will allow them to interoperate and to be managed consistently.

Creating a VNF

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.