...
- ONAP SDC shall also continue to support PNF definition by UI as in Casablanca Release
- ONAP artifacts associated to a PNF can be stored in ONAP catalogues in order to be then utilized also at RT.
PNF Archive can be onboarded through ONAP
- ONAP SDC shall also continue to support PNF definition by UI as in Casablanca Release.
INTRODUCTION
PNF PRE-ONBOARDING & ONBOARDING OVERVIEW
...
Descriptor, Artifacts and Package Delivery | PNF Package Pre-onboarding | ONAP onboarding process, PNF Package onboarding | ONAP Design Time activities | ONAP Run Time activities | |
|---|---|---|---|---|---|
| WHEN | PNF delivery time | NF validation Activities | Onboarding Activities | ONAP Design Time Activities | ONAP Run Time |
| WHO | Vendor | Technology Specialist | Technology Specialist Asset Manager | Service Designer Operations Specialist | Operations Specialist |
| WHAT | Descriptor, Artifacts and Package delivery | PNF Package | PNF Package, PNF Descriptor PNF Onboarding | ONAP Common Information Model SDC Data Model 5G Service Definition | 5G Service Instantiation PNF Instance A&AI PNF Instance |
| ETSI NFV reference | SOL001 PNFD SOL004 Package | SOL004 Package | SOL001 PNFD, SOL004 Package | - | - |
PNF PRE-ONBOARDING & ONBOARDING
...
DUBLIN WORK
| 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 | 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. Under discussion: the development a PNF-SDK for PNFs as opposed to using VNF-SDK for PNFs. |
| 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 |
| Proper Distribution & Reception of SDC 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. Before it was assumed that VNFs are distributed, in Dublin PNF artifacts are distributed. So for example SO looked for Heat Templates (which were only applicable for VNFs). We need to insure that the distribution of PNF artifacts does not break the ONAP platform components. 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. |
PROJECT IMPACT OVERVIEW
The following table gives an overview and summary of the ONAP RT Component Project impacts.
...
| 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. MANDATORY |
| 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 MANDATORY |
| Licensing | NF Licensing information that needs to be included in the Package MANDATORYOPTIONAL |
| Informational Artifacts | Informational artifacts include:
OPTIONAL |
| Configuration Files | Configuration Files related to the NF for configuration management OPTIONAL |
| 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 OPTIONAL |
...
The PNF package is expected to be a CSAR package.
PNF PACKAGE & FILE - "BASELINE"
The following things are agreed and will be targeted for delivery in Dublin:
PNF PACKAGE & FILE - UNDER DISCUSSION
The following things are still under discussion and investigation:
...
PNF PRE-ONBOARDING: LICENSING MANAGEMENT
...
PNF PACKAGE LICENSING
The PNF package requires a license.
Similarly to the VNF package, there is a directory dedicated to License(s).
It is expected that the PNF package will also have a similar directory dedicated to Licenses.
This implies that the Service Provider has defined a licensing schema or has licensing management software to manage licenses.
It might also be possible that multiple licenses are needed for different functions or authentication.
"shall" have a Licensing.term (file)
This is also still under discussion (driven from the standards)
This section will be updated with what is contained in the actual PNF package.
LICENSING MANAGEMENT & SCHEMA
DEFINITION: The licensing schema could vary and be dependent upon the service provider. Licensing schema is expected to be used to identify or authorize the existence a particular PNF into the network of the service provider.. It might also be possible that multiple licenses are needed for different functions or authentication. It may also be important to provide a license during PNF Plug and Play.
The licensing schema could vary and be dependent upon the service provider.
This implies that the Service Provider has defined a licensing schema or has licensing management software to manage licenses.
R4 DUBLIN: For Dublin, it is to be determined what will be done (maybe nothing). This is likely to be FUTURE work (El Alto and beyond)
Note: SDC adds files related to Licensing AFTER Onboarding.
STANDARDS & LICENSING (ETSI SOL004)
In ETSI SOL004 requires a "License.term", but it is still being defined & under discussion.
(this section will be updated when the standards have been finalized)For Dublin, we are expecting to put in place a simple licensing mechanism or schema as a proof of concept at least. TBD.
PNF PRE-ONBOARDING: VNF-SDK DEVELOPMENT
...