...

• Service Designer
• Operations Specialist
• SDC (Deployment Studio)

For more information and exploration you can visit the Pre-Onboarding/Onboarding Wiki at: 5G - PNF Pre-Onboarding & Onboarding

OVERVIEW PNF ONBOARDING

 - Types on Onboarding: TOSCA Onboarding, HEAT Onboarding, Manual Onboarding #@#

...

A diagram showing the TOSCA method of VNF onboardingImage Removed

A diagram showing the HEAT Template based method of VNF onboarding

Image Removed

2. Pre-Conditions

ONAP is ready:

• SDC - SDC is ready to ingest a package. Platform Information & Platform Data model are available.
• CERTIFICATION STUDIO - The Certification Studio has certified the Package ready for distribution (VNF-SDK)
• ONAP SOFTWARE - There is an ONAP installation. Software images loaded in OpenStack installation, where instantiation will happen (since no S/W image repository). Need to be available in Target Cloud Instances.

VENDOR deliveries received

• DESCRIPTOR - Vendor PNF or VNF Descriptor Defined
• VENDOR xNF PACKAGE - Vendor PNF or VNF Package with associated artifacts Delivered

2.1 xNF ONBOARDING PACKAGE

2.1.1 PNF PACKAGE

Vendors will prepare the Onboarding package (if you are not manually onboarding) The Onboarding Package Contains:

The following shows a diagram of the PNF Onboarding package which must be put together

2.1.2 VNF PACKAGE

Image Added

Image Added

A description of the things in the VNF and PNF Onboarding Package Packages SOL004 TOSCA-based Package for PNFs(of the above diagrams).

• PNF DESCRIPTORS (PNFD) - (Instantiation/Design Time) PNFD and VNFD have been mapped to ONAP platform data/information model. That is, the onboarded descriptor models (vendor provided) have been mapped onto ONAP platform data & information models that are useable and known to ONAP. For a RAN PNF these are driven from the ETSI SOL001 standards.
• TOSCA METADATA - This file provided by the vendor describes the meta-information about the package. Notably it gives the directory location of key files in the package and their locations in the package as directory paths.
• MANIFEST FILE - The Manifest file include basic information about the package itself.
  • metadata with following keynames: pnfd_ provider, pnfd_name, pnfd_release_date_time, pnfd_archive_version
  • a list of all files contained in or referenced from the package with their location, expressed using a Source: location/name key-value pair. 
  • Non-mano-artifact tag: ONAP defined tags
• VES EVENT REGISTRATION - This file describes all of the VES events that are supported by the PNF. It defines the possible events that the PNF can support, such as faults, heartbeating, pnfRegistration, Performance measurements. These are defined in the VES Event specification document available in the repository. The Event Registration also defines all of the fields that each of these events have alsoto fill in when they send the event, and the details of the VES header also.
• PM DICTIONARY PM DICTIONARY - Performance Measurements and schema definitions. This is OPTIONAL, a PNF package does NOT necessarily have this artifact.
• ANSIBLE PLAYBOOKS - Ansible playbooks define the "scripts" that are used for remote ansible Ansible communications from ONAP towards a PNF or VNF. This is OPTIONAL, a PNF or VNF package does NOT necessarily have this artifact.
• NETCONF YANG MODELS - Defines the NetConf Yang Models that are used for NetConf communications between ONAP and the PNF or VNF. This is OPTIONAL, a PNF or VNf package does NOT necessarily have this artifact. Starting in R3 (Casablanca release) and continuing into R4 (Dublin) a U/C w/ PNFs. VNFs available since R1.
• CHEF COOKBOOKS - When Chef communications are supported between ONAP and the PNF or VNF, these define the communication playbooks that are used by Chef. This is OPTIONAL, a PNF or VNF package does NOT necessarily have this artifact.
• MANUALS - Manuals can be included as informational artifacts in the VNF / PNF onboarding package provided by the vendor. These are typically additional information that can be provided (free-form) by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time. This is OPTIONAL, a PNF package does NOT necessarily have this artifact.
• HELP FILES - Help files can be included as informational artifacts in the PNF onboarding package provided by informational artifacts in the PNF onboarding package provided by the vendor. These kinds of file can provide information for trouble shooting for example, but can be any kind of assistance in text from the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time. This is OPTIONAL, a PNF package does NOT necessarily have this artifact.
• CUSTOMER DOCUMENTATION PRODUCTS - Customer documentation products can be included as informational artifacts in the PNF onboarding package provided by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time. This is OPTIONAL, a PNF package does NOT necessarily have this artifact.
• TEST FILES - Manuals can be included as informational artifacts in the PNF onboarding package provided by the vendorTest files are files that might be for testing, or end-to-end integration of the PNF with ONAP. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time. This is not included in R4/Dublin.
• LICENSING AGREEMENTS - Licensing agreements can be included as informational artifacts in the PNF onboarding package provided by the vendor. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time. This is not included in R4/Dublin and has been postponed.
• RESOURCE CONFIGURATION INFORMATION - Resource Configuration Information can be included in the PNF onboarding package provided by the vendorprovided by the vendor. For example, these might be settings or other configuration management type data associated with the resource. These are optional files and are not necessarily included in a package. They can be viewed by an ONAP operator in design time. This is OPTIONAL, a PNF package does NOT necessarily have this artifact. Note: starting in Frankfurt (R6) there is a CM (Config Mgmt) 5G U/C.
• CONTROLLER BLUEPRINT ARTIFACT - From a controller perspective, there is a TOSCA implementation to execute template for configuration. These include Velocity templates, Jinja template. They can be generic or per PNF type (customized). This is OPTIONAL, a PNF package does NOT necessarily have this artifact. In future releases this could be incorporated into the PNF package. In R4/Dublin a ONAP user would manually upload the Controller Blueprint Artifact.

...

This section describes what an example of what an actual package might look like, showing . It shows some of the key files and directories and how they might be arranged and delivered.

The onboarding PNF/VNF Package must be defined as specified as ETSI SOL004v2SOL004 v2.6.1 + NFV CR NFVSOL(18)000746r3 

The package structure must be a CSAR with TOSCA-Metadata as specified in SOL004 section 4.1.2
The TOSCA.meta file keyname extension: SOL004 section 4.1.2.3. You can refer to the PNF Pre-onboarding & Onboarding Wiki for more information: 5G - PNF Pre-Onboarding & Onboarding

3. Information Flow

The following UML diagram shows the PNF Pre-onboarding Flow

...

SUPPORTING FILES & SLIDES