...
Proposed UC to focus on in Dublin :
- PNF Pre-Onboarding
- PNF OnboardinOnboarding
- Reference Presentation provided to 5G UC meeting (Nov 15th, 2018): ONAP Dublin_PNFOnboarding.pptx
USE
...
CASES (Scope)
...
PNF ONBOARDING BACKGROUND (CASABLANCA)
In Casabablanca Casablanca Release, the PnP Use Case covered :
...
- PNF Instantiation in ONAP at Run Time Time
In Casablanca Release, the PnP Use Case did not cover the PNF Onboarding, the Onboarding process of a Vendor PNF archive including a PNF descriptor and a set of Artifacts.
PNF PRE ONBOARDING SCOPE (R4 Dublin)
This is the scope (what is agreed to be delivered) in Dublin for this Use Case. A vendor provided PNF package/ file archive Pre-Onboarding Use Case in Dublin
- PNF Package/Archive shall be pre-onboarded & Verified in ONAP
The pre-onboarding step can be used to verify the PNF package format by VNF SDK tools
...
Use Case Notes
- This Use Case shall be aligned as much as possible to the ONAP VNF package pre-onboarding
...
- UC
- PNF archive is provided by a vendor and it will include PNFD (based on ETSI SOL004) and all the artifacts required by ONAP (non
...
- ETSI NFV
...
- artifacts provided managed as Non-MANO
...
- artifact (i.e. FM
...
- and PM dictionary))
- PNF
...
- PNF Archive can be onboarded through ONAP
- ONAP SDC shall also continue to support PNF definition by UI as in Casablanca Release.
PNF PRE ONBOARDING
...
- Package/Archive shall be pre-onboarded & Verified by VNF SDK tools
- This UC shall be aligned as much as possible to the ONAP VNF package pre-onboarding U/C the artifacts required by ONAP (non-ETSI NFV artifact provided managed as Non-MANO Artifact (i.e. FM Meta Data and PM dictionary)
PNF ONBOARDING SCOPE (R4 Dublin)
This is the scope (what is agreed to be delivered) in Dublin for this Use Case.
- A vendor provided PNF package/file archive
...
- can be
...
- on-
...
- boarded in ONAP
The pre-onboarding step can be used to verify the PNF package format by VNF SDK tools
Use Case Notes
- This Use Case shall be aligned as much as possible to the ONAP VNF package pre-onboarding UC
- PNF archive is provided by a vendor and it will include PNFD (based on ETSI SOL004) and all the artifacts required by ONAP (non ETSI NFV artifacts provided managed as Non-MANO artifact (i.e. FM and PM dictionary))
PNF ONBOARDING
- A vendor provided PNF package/file archive can be on-boarded in ONAP
Use Case Notes
- 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 ONAP SDC shall also continue to support PNF definition by UI as in Casablanca ReleaseONAP artifacts associated to a PNF can be stored in ONAP catalogues in order to be then utilized also at RT.
PNF PRE-ONBOARDING & ONBOARDING
...
...
Descriptor, Artifacts and Package Delivery
...
PNF Package
Pre-onboarding
...
ONAP onboarding process,
PNF Package onboarding
...
Technology Specialist
Asset Manager
...
Service Designer
Operations Specialist
...
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
...
SOL001 PNFD
SOL004 Package
...
SOL001 PNFD,
SOL004 Package
...
PROJECT IMPACT OVERVIEW
The following table gives an overview and summary of the ONAP RT Component Project impacts.
...
- PNF PACKAGE FORMAT
- Identify current VNF package format constraints in SDC
- Propose a PNF Package format
- Evaluate VNF and PNF package alignment
- PACKAGE MAPPING - Onboarding PNF package to internal PNF package mapping
- PNFD MAPPING - Onboarding PNFD to internal PNFD mapping
- A new flow to map ETSI SOL001 PNFD in SDC AID model.
- ARTIFACT MANAGEMENT
- Design-time catalog update to associate artifacts to a PNF
- Run-time catalog update to associate artifacts to a PNF
...
PACKAGE VERIFICATION - PNF package format verification
MODEL - VNF SDK Model,
PACKAGE USAGE - Package for PNF Onboarding Package for use in VNF SDK
...
- PACKAGE, DESCRIPTOR, ARTIFACTS - VNF requirements to cover PNF package contents and directory structures and mandatory elements.
- PNF DESCRIPTOR - Requirements for the PNF Descriptor
- ARTIFACTS - Requirements for Artifacts of PNF and PNF Package
...
(SCOPE)
| 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. |
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 | - | - |
PROJECT IMPACT OVERVIEW
The following table gives an overview and summary of the ONAP RT Component Project impacts.
| COMPONENT | IMPACT DESCRIPTION | PTL |
|---|---|---|
| Service Design & Creation Project |
| Ofir Sonsino |
| VNF SDK Project | PACKAGE VERIFICATION - PNF package format verification MODEL - VNF SDK Model, PACKAGE USAGE - Package for PNF Onboarding Package for use in VNF SDK | Weitao Gao |
| Modeling Project | PNFD MAPPING - Onboarded PNFD to platform PNFD mapping | Hui Deng |
| VNF Requirements Project |
|
DEVELOPMENT STATUS
| Project | PTL | JIRA | Description | Status |
|---|---|---|---|---|
SDC |
DEVELOPMENT STATUS
| Project | PTL | JIRA | Description | Status | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SDC
Jira | server | ONAP JIRA | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | SDC-1975 |
| PTL notified (11/19 ) Started discussions with SDC project |
VNF SDK VNF SDK Model, Package VNFSDK
| VNFSDK-338 |
| Jira | ||||||
|---|---|---|---|---|---|---|
|
SDC-1980
- PNF package format
- Identify current VNF package format constraints in SDC
- Propose a PNF Package format
- Evaluate VNF and PNF package alignment
- Onboarding PNF package to internal PNF package mapping
- Onboarding PNFD to internal PNFD mapping
- A new flow will be introduced in SDC to map ETSI SOL001 PNFD in SDC AID model.
- Artifact management
- Design time catalog update to associate artifacts to a PNF
- Run time catalog update to associate artifacts to a PNF
PTL notified (11/19 )
Started discussions with SDC project
VNF SDK
VNF SDK Model, Package
341Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFSDK- 337 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFSDK-342338 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFSDK-343
- PNF package format verification
VNFSDK PTL notified (12/05)
VNF SDK Model, Package notified (11/30)
- Onboarded PNFD to Platform PNFD mapping
-579789cceedb key VNFSDK-339 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFSDK-340
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key
VNFSDK-
341 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key
VNFSDK-
342 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key
VNFSDK-343
- PNF package format verification
VNFSDK PTL notified (12/05)
VNF SDK Model, Package notified (11/30)
- Onboarded PNFD to Platform PNFD mapping
499Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS- 506
505Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS- 496
507Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS- 497
508Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS-
- Network Function requirements shall be updated to cover PNF package, descriptor and artifacts
- VNF requirements could be reviewed.
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.
PRE-ONBOARDING: ARTIFACTS & PRODUCTS
...
SDC Data Model
...
VES event registration file/
FM dictionary,
PM dictionary
...
Run time Catalog
...
Configuration Models and Files,
(including Ansible Playbooks)
...
Multiple artifacts can be provided by avendor in the Package. A list of the supported artifacts by ONAP will be finalized during Dublin timeframe.
Note about the picture: NF Registration stands for VES event registration file. Info model provided in the picture, just as example
DUBLIN ACTIVITIES FOR PNF PRE-ONBOARDING & ONBOARDING
...
|
| PTL to be notified |
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.
PRE-ONBOARDING: 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 |
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.
Note about the picture: NF Registration stands for VES event registration file. Info model provided in the picture, just as example
...
PNF PRE-ONBOARDING: PACKAGE CREATION (VENDOR PROVIDED)
...
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
...
| Package | Slides | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PNF Onboarding Package |
| ||||||||||||
| PNF Packaging Discussion |
|
...