5G - PNF Pre-Onboarding & Onboarding
- Benjamin Cheung
- damian.nowak
- Zu Qiang
- Michela Bevilacqua
Authors: Benjamin Cheung , Michela Bevilacqua , Zu Qiang
Table of Contents
USE CASES (Scope)
BACKGROUND: (R3 CASABLANCA)
In Casablanca Release, the PnP Use Case covered :
- manually onboarding a PNF at Design Time
- PNF Instantiation in ONAP at Run Time
In Casablanca Release, the PnP Use Case did not cover the PNF pre-onboarding / onboarding.
PNF R4 Dublin SCOPE
This is the scope (what is agreed to be delivered) in Dublin for this Use Case.
Introduce pre-onboarding and onboarding a vendor PNF onboarding package in ONAP for 5G and other use cases.
Proposed 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 a vendor PNF onboarding package/Archive format by VNF SDK tools
Use Case Notes
- 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 can be on-boarded in ONAP. The onboarding step is mandatory to onboard artifacts and descriptor provided by the vendor.
Use Case Notes
- ONAP SDC shall also continue to 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 in ONAP catalogues in order to be then utilized also at run time.
- The PNF 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.
Executive Summary - Pre-onboarding & onboarding is used to "upload" a vendor's PNF onboarding package which contains the descriptor and artifacts for the PNF. (VNFs are handled with a different wiki)
Business Impact - Pre-onboarding & onboarding is a business imperative because it is vital because ONAP needs to be able to "load" PNF descriptor and artifacts which define the PNF capabilities and functionalities.
Business Markets - Applies to PNFs within a service operator's network. Applies to all markets that might use PNFs including Wireless, wireless, optical.
Funding/Financial Impacts - This use case can potentially save a large amount of OPEX because there is a lot of time associated with manually onboarding a PNF which would have to be done if this use case were not implemented.
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
INTRODUCTION
PNF PRE-ONBOARDING & ONBOARDING OVERVIEW
Descriptor, Artifacts and Package Delivery | PNF Package Pre-onboarding | ONAP onboarding process, PNF Package onboarding | ONAP Design Time activities | ONAP Run Time activities | |
|---|---|---|---|---|---|
| WHEN | PNF delivery time | Pre-Onboarding activities | Onboarding Activities | ONAP Design Time Activities | ONAP Run Time |
| WHO | Vendor | Technology Specialist | Technology Specialist Asset Manager | Service Designer Operations Specialist | Operations Specialist |
| WHAT | Descriptor, Artifacts and Package delivery | PNF Package NF validation Activities | PNF Package, PNF Descriptor PNF Onboarding SDC Meta-data added (vendor onboarded CSAR to SDC onboarded CSAR) | ONAP Common Information Model SDC Data Model 5G Service Definition Service Design SDC Model mapping | 5G Service Instantiation PNF Instance A&AI PNF Instance |
| ETSI NFV reference | SOL001 PNFD SOL004 Package | ETSI SOL004 Package | ETSI SOL001 PNFD, SOL004 Package | - |
PNF PRE-ONBOARDING & ONBOARDING DUBLIN WORK
| STAGE | DESCRIPTION | DELIVERABLE |
|---|---|---|
(1) Package Delivery | Producing and collecting NF artifacts for a NF package. Vendor provided. Dublin Priorities are the artifacts & descriptor files of the PNF package. These include: 1. PNFD, 2. NF Registration YAML File (for VES event definition), 3. PM Dictionary & Schema. | PNF Onboarding Package |
| (2) PNF Pre-Onboarding | VNF SDK: Enhance VNF-SDK to be able to validate (optionally) the on-boarding PNF package. Optionally, create a PNF onboarding package through VNF-SDK. VNF-SDK can: [1] (optionally) Create a PNF package. VNF-SDK optionally can extend a package and provide as output a new onboarding PNF package the SDC will use. Package, output of the VNF SDK (as optional step) must be compliant and aligned to the PNF package onboarding format provided by the vendor as both can be used as input to SDC for the ONAP onboarding package. [2] (optionally) Validate a PNF package. Validate the package according to available VES specifications and onboarding package structure. SDC/CDS: Load PNF model & Controller blue-print for PNF orchestration and Network communication. Before R3/Casalanca a Preload interim solution was used for Network Assignments. | VNF SDK validates PNF onboarding Package |
(3) PNF Onboarding | In PNF Onboarding, SDC takes the PNF vendor-provided package and adds meta-data content and recomposes a new CSAR into the SDC expected directory structure format. It copies the PNF vendor-provided PNF onboarded package and put it into a vendor-provided directory. Onboarding the Package: SDC Enhancements need to be made to onboard the PNF Package and enter into the SDC Catalog The CSAR package provided by SDC as output of the onboarding process. This work will include the PNF artifacts into CSAR package. | SDC CSAR Package of PNF Onboarded Package (CSAR) |
| (4) Design Time Activities (SDC) | Design time activities occur where an operator and define services. A Service is defined, and a new CSAR package is produced with service-related artifacts associated with outputs of SDC ready for distribution to other ONAP run-time components. | SDC CSAR (output) |
| (5) ONAP RT Component Ingestion of CSAR package & PNF Onboarding package artifacts | Proper Distribution & Reception of SDC CSAR: The SDC 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. We need to insure that the distribution of PNF artifacts does not break the ONAP platform components. (for example SO looked for Heat Templates, which were only applicable for VNFs). 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. | SDC CSAR (service artifacts from SDC) |
PROJECT IMPACT OVERVIEW
The following table gives an overview and summary of the ONAP RT Component Project impacts.
| COMPONENT | IMPACT DESCRIPTION | PTL |
|---|---|---|
| Service Design & Creation Project |
5. RESOURCE VIEW TO DISPLAY PNF ONBOARDED ARTIFACTS
| Ofir Sonsino |
| VNF SDK Project | PACKAGE VERIFICATION - PNF package format verification PNF PACKAGE FORMAT PACKAGE USAGE - Package for PNF Onboarding Package for use in VNF SDK | victor gao |
| Modelling Subcommittee | PNFD MAPPING - Onboarded PNFD to platform PNFD mapping THis activity is traced as a sw implementation task in SDC but PNFD mapping will be discussed as part of the ONAP Resource Data Model. | |
| VNF Requirements Project |
|
DEVELOPMENT STATUS
| Project / PTL | JIRA | Description | Status |
|---|---|---|---|
|