Authors: Benjamin Cheung , Michela Bevilacqua , Zu Qiang
...
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 | Pre-Onboarding 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 NF validation Activities | PNF Package, PNF Descriptor PNF Onboarding SDC Meta-data added (vendor onboarded CSAR to SDC onboarded CSAR) | ONAP Common Information Model SDC Data Model 5G Service Definition Service Design SDC Model mapping | 5G Service Instantiation PNF Instance A&AI PNF Instance |
| ETSI NFV reference | SOL001 PNFD SOL004 Package | ETSI SOL004 Package | ETSI SOL001 PNFD, SOL004 Package | - |
PNF PRE-ONBOARDING & ONBOARDING DUBLIN WORK
...
| Project / PTL | JIRA | Description | Status | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PTL notified (11/19 ) Code is ready for M4(11/04) | ||||||||||||||||||||
| VNFSDK PTL notified (12/05) VNF SDK Model, Package notified (11/30) Scope planned for Dublin completed ...except from package security item: E2E work tracked in this Jira item:
| ||||||||||||||||||||
RESOURCE DATA MODEL | No JIRA ticket required, project can help to identify the mappings required in SDC in Dublin timeframe |
| PTL notified (11/26) | ||||||||||||||||||
VNF RQTS |
| PTL notified (01/16) |
...
| PACKAGE DELIVERY | ONBOARDING PROCESS | DESIGN TIME | RUN TIME |
|---|---|---|---|
| NF Descriptor | NF Descriptor Model | SDC Data Model | A&AI PNF Data model, PNF instance |
VES event registration file/ PM dictionary | artifact | SDC Catalog | Run time Catalog |
| Informational Artifacts | artifact | SDC Catalog | Run time Catalog |
Configuration Models and Files, (including Ansible Playbooks) | artifact | SDC Catalog | Run time Catalog |
Multiple artifacts can be provided by a vendor in the Package. A list of the supported artifacts by ONAP will be finalized during Dublin timeframe.
...
| 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 N/A for PNF |
| 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 |
PACKAGE DELIVERY: PNF PACKAGE FILES & DIRECTORIES
...
- 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-artefact tag: ONAP defined tags
EXAMPLE of the PNF manifeat file
...
The following diagram illustrates a basic PNF package and some suggested file structure and content in the directories.
The PNF package is expected to be a CSAR package with file extension .csar.
...
| FUNCTION | DUBLIN (R4) | FRANKFURT (R6) | GUILIN (R7) |
|---|---|---|---|
| Package Delivery | Initial Delivery | ||
Pre-onboarding: VNF-SDK Package Validation | Initial Delivery | ||
Onboarding: Package into SDC Catalog | Initial Delivery | ||
Onboarding: xNF Descriptor mapped to Platform Info/Data Model | Initial Delivery | ||
Design Time: Usage of Onboarded Package Creation of Resource/Svc | Initial Delivery | ||
Run Time: Ingestion of Service CSAR by ONAP Run-time components | Initial Delivery |
The following table has a list of the references pages for the Roadmap
| Release | Wiki |
|---|---|
| Dublin (R4) | 5G - PNF Pre-Onboarding & Onboarding |
| Frankfurt (R6) | PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt |
REQUIREMENTS
This section describes the requirements that are to be updated & added
(This section under development)
| REQUIREMENTS CATEGORIES | DESCRIPTION | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CSAR structure | New requirements related to the CSAR structure for the PNF Onboarded package. Section 5.1.6, VNF CSAR requirements based on SOL004 based only for VNFs. Associated Tickets:
| ||||||||||||||||||||||||
| PNFD Descriptor | New VNF-RQTS requirements related to the PNF Descriptor. The requirements describe the VNF-Descriptor and new updates need to be made to support PNF Descriptors. Associated Tickets:
| ||||||||||||||||||||||||
| Onboarding Requirements | New VNF-RQTS onboarding requirements. In the document 7.2, xNF onboarding requirements but aren't clear what is needed. These requirements were copied from RFP but are outdated and some requirements are irrelevant, so in R4 for this use case, these requirements needs to be reviewed, updated, and revised. Associated Tickets: (TBD) | ||||||||||||||||||||||||
...