You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

TABLE OF CONTENTS

PNF ONBOARDING OVERVIEW


PACKAGE DELIVERYONBOARDING PROCESSDESIGN TIMERUN TIME
WHENPNF PackageOnboarding ActivitiesDesign Time ActivitiesONAP Run Time
WHOVendor

Technology Specialist

Asset Manager

Service Designer

Operations Specialist

Operations Specialist
WHATOn-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

ETSISOL001 PNFDSOL004 Package--


ARTIFACTS & PRODUCTS

PACKAGE DELIVERYONBOARDING PROCESSDESIGN TIMERUN TIME
NF DescriptorPNF Onboarding Package

Platform Information Model

A&AI PNF Entry
NF RegistrationNF Descriptor ModelPlatform Data ModelPNF Instance
Informational Artifacts
SDC CatalogPNF Discovery & Plug and Play
Configuration Files
5G Service Definition5G Service Instantiation
Ansible Playbooks



DUBLIN ACTIVITIES FOR PNF ONBOARDING

DELIVERABLEDESCRIPTION
NF PackageProducing and collecting NF artifacts for a NF package. Vendor provided. Dublin Priorities are the PNFD and NF Registration YAML File.
PNF-SDKDevelop 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 PackageCreate a PNF onboarding package through PNF-SDK. This is the output of the PNF-SDK.
Onboard the PackageSDC 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 (VENDOR PROVIDED)

The NF Onboarding Package could contain the following things:

ARTIFACTDESCRIPTION
PNF DescriptorPNF 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 include:

  • Cloud Questionnaire,
  • Features,
  • Vendor Test Scripts,
  • Resource Security Template,
  • HEAT Template (Vendor),
  • Capacity Descriptive,
  • Other Informational Artifacts
Configuration FilesConfiguration Files related to the NF for configuration management
LicensingNF Licensing information that needs to be included in the Package
Ansible PlaybooksAnsible 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).

The PNF SDK will be used to VALIDATE the PNF Onboarding Package

It is possible for a user to bring in the PNF Onboarding Package (provided by a vendor) without the use of the PNF SDK tools.

PNF ONBOARDING PACKAGE

Creation of PNF Onboarding Package by using PNF-SDK


PNF-D Information Model:

Proposed PNFD Model


SDC ONBOARDING PACKAGE INTO SDC CATALOG

Enhancements to SDC to take PNF Onboarding Package into the SDC Catalog

SDC distributes services

NF CSAR package includes the artifacts and information for the resources for a service.

There is one CSAR file which includes all of the definition for that service.



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.


SDC CSAR Package Structure

Csar Structure

SDC Support Artifacts:

SDC supported artifact types

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.


SUPPORTING DOCUMENTS

Supporting documents related to PNF Onboarding

ETSI SOL Standards

The following has the ETSI SOL standards for your convenience

STANDARDFILE

ETSI SOL1

(PNF/VNF Descriptor)

ETSI SOL 4 (NF Package)



PNF Onboarding Artifacts

The following are mock-ups of the PNF Onboarding Artifacts

PNF ONBOARDING ARTIFACTSMOCK-UP
PNF Descriptor TOSCA

NF Registration (YAML) 

Defines records for NF events


Informational Artifacts


PNF ONBOARDING OVERVIEW SLIDE PACKS

PackageSlides
PNF Onboarding Package




VNF REQUIREMENTS

The PNF Package requirements need to be developed, and the VNF Package Requirements can be used as a guideline for what a PNF might need.

VNF Packaging Requirements - The appropriate Requirements page is at:

https://onap.readthedocs.io/en/beijing/submodules/vnfrqts/requirements.git/docs/Chapter7.html

Requirements Appendix:

https://onap.readthedocs.io/en/beijing/submodules/vnfrqts/requirements.git/docs/Chapter8.html

SDC Repository

https://gerrit.onap.org/r/#/admin/projects/sdc

(Click on BRANCHES, on the "MASTER" row, click on gitweb, click on TREE in the top navigation row)




  • No labels