...
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.
PNF PRE-ONBOARDING and ONBOARDING SCOPE (R4 Dublin)
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 PNF package support in ONAP for 5G and other use cases.
Proposed UC to focus on new UCs in Dublin :
- PNF Pre-Onboarding:
- PNF Onboarding:
Reference Presentation provided to 5G UC meeting (Nov 15th, 2018): ONAP Dublin_PNFOnboarding.pptx
PNF PRE-ONBOARDING SCOPE (R4 Dublin)
The pre-onboarding step is optional and it can be used to verify the PNF package/Archive format by VNF SDK tools
Use Case Notes
- This 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 SOL004) and all the artifacts required by ONAP (non ETSI NFV artifacts provided managed as Non-MANO artifact (i.e. FM and PM dictionary))PNF Package/Archive shall be pre-onboarded & Verified by VNF SDK tools
- 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)
This is the scope (what is agreed to be delivered) in Dublin for this Use Case.
...
A vendor provided PNF package/file archive can be on-boarded in ONAP.
The onboarding step is mandatory to onboard artifacts and descriptor provided by the vendor.
Use Use Case Notes
- ONAP SDC shall also continue to support PNF definition by UI as in Casablanca Release
- ONAP artifacts associated to a PNF can be stored in ONAP catalogues in order to be then utilized also at RT.
PNF Archive can be onboarded through ONAP
- ONAP SDC shall also continue to support PNF definition by UI as in Casablanca Release.
...
PNF PRE-ONBOARDING & ONBOARDING DUBLIN WORK
| DELIVERABLE | DESCRIPTION | ||
|---|---|---|---|
PNF Onboarding Package § VNF SDK input NF Package§ SDC input | Producing and collecting NF artifacts for a NF package. Vendor provided. Dublin Priorities are the PNFD and , NF Registration YAML File, PM Dictionary. | ||
| PNF- VNF SDK : Enhance VNF-SDK to be able to create a PNF onboarding Package. The SDK is a set of tool which can take the NF Package and create the PNF onboarding package the SDC will use. Under discussion: the development a PNF-SDK for PNFs as opposed to using VNF-SDK for PNFs. PNF Onboarding Packagevalidate onboarding PNF package. | |||
Proper Distribution & Reception of SDC CSAR § VNF SDK output § SDC input | Create a PNF onboarding package through PNFVNF-SDK. This is the output of the PNFVNF-SDK. The SDK optionally can extend a package and provide as output a new onboarding PNF package the SDC will use. PNF | ||
| Onboarding the Package: | Onboard the Package | SDC Enhancements need to be made to onboard the PNF Package and enter into the SDC Catalog | |
Proper Distribution & Reception of SDC CSAR : SDC creates a CSAR package for the PNF including artifacts, and TOSCA definitions. This work will include the PNF artifacts into CSAR package. The CSAR package is distributed by SDC to ONAP Run-Time Components. Chances need to be made to verify the reception of the CSAR and use of the CSAR by the Components. Before it was assumed that VNFs are distributed, in Dublin PNF artifacts are distributed. So for example SO looked for Heat Templates (which were only applicable for VNFs). We need to insure that the distribution of PNF artifacts does not break the ONAP platform components. Some ONAP RT assume that any package notification only have VNF artifacts. In practice, there is only the subscription of artifacts (listeners) and the distribution of the PNF package, we need to make sure this behaves correctly and that there are no errors. Pre-integration checks and validation that the distribution of PNF artifacts will not cause side effects. Want to insure that FM & PM artifacts are distributed properly. PM dictionary would be used in DCAE & PM Mapper. FM Meta Data is new, and from the start (what is new in Dublin) is that it is being used for both VNFs and PNF. |
...
| COMPONENT | IMPACT DESCRIPTION | PTL |
|---|---|---|
| Service Design & Creation Project |
| Ofir Sonsino |
| VNF SDK Project | PACKAGE VERIFICATION - PNF package format verification MODEL - VNF SDK Model, PACKAGE USAGE - Package for PNF Onboarding Package for use in VNF SDK | Weitao Gao |
| Modeling Project | PNFD MAPPING - Onboarded PNFD to platform PNFD mapping | |
| VNF Requirements Project |
|
...