(1) Package Delivery

PNF Onboarding Package

§ VNF SDK input

§ SDC input

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.

VNF SDK: Enhance VNF-SDK to be able to validate onboarding (optionally) the on-boarding PNF package. Optionally Create , create a PNF onboarding package through VNF-SDK.PNF Onboarding Package

 This is the output of the VNF-SDK.

§ VNF SDK output

§ SDC input

-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.

(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.

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.

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.