Versions Compared

Old Version 185

changes.mady.by.user Zu Qiang (Ericsson)

Saved on

compared with

New Version 186

changes.mady.by.user Zu Qiang (Ericsson)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In Casablanca Release, the PnP Use Case covered :

 - manually onboarding a PNF Definition at Design Time

 - PNF Instantiation in ONAP at Run Time

In Casablanca Release, the PnP  Use Case did not cover the PNF Onboarding, the Onboarding process of a Vendor PNF archive including a PNF descriptor and a set of Artifacts pre-onboarding / onboarding.

PNF R4 Dublin SCOPE

This is the scope (what is agreed to be delivered) in Dublin for this Use Case. A vendor provided PNF package/ file archive shall be pre-onboarded in ONAP 

Introduce pre-onboarding and onboarding a vendor PNF onboarding package Introduce PNF package support in ONAP for 5G and other use cases.

...

The pre-onboarding step is optional and it can be used to verify the a vendor PNF onboarding package/Archive format by VNF SDK tools 

...

  • Use Case shall be aligned as much as possible to the ONAP VNF package pre-onboarding UC
  • PNF archive is provided by a vendor and it will include PNFD (based on ETSI SOL001v2.5.1) and all the artifacts required by ONAP (non ETSI NFV artifacts provided managed as Non-MANO artifact (i.e. FM and PM dictionary)). The PNF package structure shall be based on ETSI SOL004v2.6.1.
  • This UC shall be aligned as much as possible to the ONAP VNF package pre-onboarding U/C the artifacts required by ONAP (non-ETSI NFV artifact provided managed as Non-MANO Artifact (i.e. FM Meta Data and PM dictionary)

PNF ONBOARDING SCOPE (R4 Dublin)

 A vendor provided PNF onboarding package /file archive can be on-boarded in ONAP. The onboarding step is mandatory to onboard artifacts and descriptor provided by the vendor.

...

  • ONAP SDC shall also continue to support PNF definition by UI as support manually onboarding a PNF as in Casablanca Release
  • ONAP SDC shall also continue to support VNF onboarding as in Casablanca Release
  • PNF descriptor and artifacts can be onboarded through ONAP and stored artifacts associated to a PNF can be stored in ONAP catalogues in order to be then utilized also at RTrun time. 
  • The PNF Archive can be onboarded through ONAPONAP SDC shall also continue to support PNF definition by UI as in Casablanca Release.package structure shall be based on ETSI SOL004v2.6.1. And the PNFD is based on ETSI SOL001v2.5.1

BUSINESS DRIVER

This section describes Business Drivers needs.

...