TABLE OF CONTENTS
PNF ONBOARDING OVERVIEW
| PACKAGE DELIVERY | ONBOARDING PROCESS | DESIGN TIME | RUN TIME | |
|---|---|---|---|---|
| WHEN | PNF Package | Onboarding Activities | Design Time Activities | ONAP Run Time |
| WHO | Vendor | Technology Specialist Asset Manager | Service Designer Operations Specialist | Operations Specialist |
| WHAT | On-Boarding Package | PNF Descriptor Model PNF SDK PNF Onboarding | Platform Information Model Platform Data Model 5G Service Definition | 5G Service Instantiation PNF Instance A&AI PNF Instance |
| ETSI | SOL001 PNFD | SOL004 Package | - | - |
ARTIFACTS & PRODUCTS
| PACKAGE DELIVERY | ONBOARDING PROCESS | DESIGN TIME | RUN TIME |
|---|---|---|---|
| NF Descriptor | PNF Onboarding Package | Platform Information Model | A&AI PNF Entry |
| NF Registration | NF Descriptor Model | Platform Data Model | PNF Instance |
| Informational Artifacts | SDC Catalog | PNF Discovery & Plug and Play | |
| Configuration Files | 5G Service Definition | 5G Service Instantiation | |
| Ansible Playbooks |
DUBLIN ACTIVITIES FOR PNF ONBOARDING
| DELIVERABLE | DESCRIPTION |
|---|---|
| NF Package | Producing and collecting NF artifacts for a NF package. Vendor provided. Dublin Priorities are the PNFD and NF Registration YAML File. |
| PNF-SDK | Develop PNF-SDK (or 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. |
| PNF Onboarding Package | Create a PNF onboarding package through PNF-SDK. This is the output of the PNF-SDK. |
| Onboard the Package | SDC Enhancements need to be made to onboard the PNF Package and enter into the SDC Catalog |
| Distribution of 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. |
PNF PACKAGE CREATION
The NF Onboarding Package could contain the following things:
| ARTIFACT | DESCRIPTION |
|---|---|
| PNF Descriptor | PNF Descriptor. The PNFD is a model which describes the requirements and capabilities of the PNF. The ETSI SOL 001 specification also suggests a model that can be used for a PNFD. This could be a TOSCA definition of the PNF. |
| NF Registration | Definition of VES Events. The NF Registration is defined by the VES Registration specification. You can read about the VES Event Listener here: Service: VES Event Listener 7.0.1 |
| Informational Artifacts | Informational artifacts including Cloud Questionnaire, Features, Vendor Test Scripts, Resource Security Template, HEAT Template (Vendor), Capacity Descriptive, Other Informational Artifacts |
| Configuration Files | Configuration Files related to the NF for configuration management |
| Ansible Playbooks | Ansible Playbooks to interact with NF. These are anticipated to be used with the communication of the NF controller to the NF. This can be seen in the PNF Plug and Play Wiki: 5G - PNF Plug and Play |
PNF-SDK DEVELOPMENT
PNF SDK development is needed to take PNF artifacts and add them to a PNF Onboarding Package in Dublin.
We expect the PNF SDK development to be able to reuse much of the functionality from VNF SDK, format delivery, processing are all the same except HEAT deployments templates are not used (as they do not apply to PNFs).
PNF ONBOARDING PACKAGE
Creation of PNF Onboarding Package by using PNF-SDK
SDC ONBOARDING PACKAGE INTO SDC CATALOG
Enhancements to SDC to take PNF Onboarding Package into the SDC Catalog
CSAR INGESTION
Inclusion of PNF artifacts into CSAR package, and ingestion of CSAR package by ONAP Run-Time Components and verification of reception and use.
The NF Package is composed of Artifacts, Definitions, TOSCA-MetaData.
PLATFORM MODELING
A Platform Information Model and Platform Data Model should be settled on and approved to represent resources that ONAP needs to work with such as a PNF and VNF that will be used to represent a 5G DU and 5G CU / VNF.
The was formerly known as a Internal Data Model, but has subsequently been renamed "Platform Data Model".
There are still a number of fundamental decisions that need to be made before finalizing on the Platform Data model for example, the separate of a PNF Device Object.