...
| 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 (VENDOR PROVIDED)
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 include:
|
| Configuration Files | Configuration Files related to the NF for configuration management |
| Licensing | NF Licensing information that needs to be included in the Package |
| 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 |
...