...
| Project | PTL | JIRA | Description | Status | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SDC |
|
| PTL notified (11/19 ) Started discussions with SDC project | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
VNF SDK VNF SDK Model, Package |
|
| VNFSDK PTL notified (12/05) VNF SDK Model, Package notified (11/30) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Resource Data Model | No JIRA ticket required, project can help to identify the mappings required in SDC in Dublin timeframe |
| PTL notified (11/26) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| VNFRQTS |
|
| PTL to be notified |
INVESTIGATE: is there impact to SO (for Runtime PNF artifact & SDC CSAR package ingestion)
USE CASE ANALYSIS, SUPPORTING MATERIAL
The following material is used during Dublin timeframe as input for discussion. It is subject to updates during Dublin timeframe. A final version will be available by Dublin signoff.
...
PACKAGE DELIVERY: ARTIFACTS & PRODUCTS
| 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 |
...
Note about the picture: NF Registration stands for VES event registration file. Info model provided in the picture, just as example
...
PACKAGE DELIVERY: 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. 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 OPTIONAL |
| 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
The PNF Package files and directories is described in this section.
...
The following things are still under discussion and investigation:
PNF PRE-ONBOARDING: VNF-SDK
...
ENHANCEMENTS
VNF SDK is (optionally) responsible to validate the PNF package provided by the vendor.
VNF SDK can also be used (optionally) to create a PNF package.
Today, optionally, the VNF SDK is also able to provide
...
[INVESTIGATE] What are artifacts that SDC adds during the Onboarding process, looking at SDC supported artifact types, possibly VENDOR LICENSE and MODEL INVENTORY (are there others?)
PNF ONBOARDING PACKAGE: PNF ONBOARDING PACKAGE LOADED
PNF Onboarding Package (vendor provided) is successfully loaded into ONAP.
In Dublin timeframe, the focus is the onboarding package mapping in the internal package and AID model.
...
DESIGN TIME ACTIVITIES: SDC ONBOARDING PACKAGE MAPPING INTO INTERNAL PACKAGE
SDC is used to map the Vendor provided onboarding package & PNF descriptor into the Internal Package & Internal (Platform) Data Model
...
DESIGN TIME ACTIVITIES: SDC ONBOARDING PACKAGE INTO SDC CATALOG
SDC Design Studio is then used to define a Service, and the output of that is a CSAR package which defines the Service.
...
The work-flows are created by SDC DS.
...
RUN TIME ACTIVITIES: CSAR INGESTION TO ONAP RT PLATFORM COMPONENTS
Inclusion of PNF artifacts into CSAR package, and ingestion of CSAR package by ONAP Run-Time Components and verification of reception and use.
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.
The NF Package is composed of Artifacts, Definitions, TOSCA-MetaData.
...