...
| Table of Contents |
|---|
USE CASES (Scope)
BACKGROUND: (R3 CASABLANCA)
In Casablanca Release, the PnP Use Case covered :
...
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
...
R4 Dublin
...
SCOPE
This is the scope (what is agreed to be delivered) in Dublin for this Use Case. A vendor provided PNF package/ file archive shall be pre-onboarded in ONAP
...
Proposed new UCs in Dublin :
- PNF Pre-Onboarding:
- PNF Onboarding:
Reference Presentation provided to 5G UC meeting (Nov 15th, 2018): ONAP Dublin_PNFOnboarding.pptx
...
PNF PRE-ONBOARDING SCOPE (R4 Dublin)
...
The pre-onboarding step is optional and it can be used to verify the PNF package/Archive format by VNF SDK tools
Use Case Notes
- 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))
- 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)
A vendor provided PNF package/file archive can be on-boarded in ONAP. The onboarding step is mandatory to onboard artifacts and descriptor provided by the vendor.
...
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 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 | ||
|---|---|---|---|
PNF Onboarding Package § VNF SDK input § SDC input | Producing and collecting NF artifacts for a NF package. Vendor provided. Dublin Priorities are the PNFD, NF Registration YAML File, PM Dictionary. | ||
VNF SDK: Enhance VNF-SDK to be able to validate onboarding PNF package. Optionally Create a PNF onboarding package through VNF-SDK. | |||
Proper Distribution & Reception of SDC CSARPNF Onboarding Package § VNF SDK output § SDC input | Create a PNF onboarding package through VNF-SDK. This This is the output of the VNF-SDK. The SDK optionally can extend a package and provide as output a new onboarding PNF package the SDC will use. PNF Onboarding Package, output of the VNF SDK (as optional step) must be compliant and aligned to the PNF package onboarding format provided by the vendor as both can be used as input to SDC for the ONAP onboarding package. | ||
| Onboarding the Package: SDC Enhancements the Package: SDC Enhancements need to be made to onboard the PNF Package and enter into the SDC CatalogProper Distribution & Reception of SDC CSAR: SDC creates a CSAR package for the PNF including artifacts, and TOSCA definitions. This | |||
| SDC PNF CSAR | The CSAR package provided by SDC as output of the onboarding process. This work will include the PNF artifacts into CSAR package. | ||
Proper Distribution & Reception of SDC CSAR: The SDC 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.Components. | We need to insure that the distribution of PNF artifacts does not break the ONAP platform components. (for example SO looked for Heat Templates, which were only applicable for VNFs). 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.
| COMPONENT | IMPACT DESCRIPTION | PTL |
|---|---|---|
| Service Design & Creation Project |
| Ofir Sonsino |
| VNF SDK Project | PACKAGE VERIFICATION - PNF package format verification |
PNF PACKAGE FORMAT PACKAGE USAGE - Package for PNF Onboarding Package for use in VNF SDK | Weitao Gao |
| Modelling Subcommittee | PNFD MAPPING - Onboarded PNFD to platform PNFD mapping THis activity is traced as a sw implementation task in SDC but PNFD mapping will be discussed as part of the ONAP Resource Data Model. | |
| VNF Requirements Project |
|
DEVELOPMENT STATUS
| 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 |
...
- The Use Case is not functional yet, nor in the test laps and is not yet ready for the Dublin release
- Testing has not begun yet to show the test case works
Summary Testing Status:
| GOAL | TEST CASE | STATUS | ||||||
|---|---|---|---|---|---|---|---|---|
| SDC1: PNF Package Format. | ## |
| ||||||
| SDC2: Package Mapping | ## |
| ||||||
| SDC3: PNFD Mapping | ## |
| ||||||
| SDC4: Artifact Management | ## |
| ||||||
| VNFSDK1: PNF Package Verification | ## |
| ||||||
| VNFSDK2: PNFD Model | ## |
| ||||||
| MODEL1: Mapping PNFD Model to PNFD Platform Model | ## |
| ||||||
| VNFRQT1: PNF Package Descriptor, Artifacts requirements | ## |
|
APPENDIX SUPPORTING DOCUMENTS
...