TABLE OF CONTENTS
Table of Contents |
---|
...
SCOPE
Introduce PNF package support in ONAP for 5G and other use cases.
...
- PNF Pre-Onboarding
- PNF Onboarding
Reference Presentation provided to 5G UC meeting (Nov 15th, 2018): ONAP Dublin_PNFOnboarding.pptx
...
USE CASES
PNF Pre-Onboarding
A vendor provided PNF package/ file archive shall be pre-onboarded in ONAP
The pre-onboarding step can be used to verify the PNF package format by VNF SDK tools
...
- 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.
Development Status
...
SDC
...
- SDC-1970: (H) Support PNF package onboarding
- SDC-1973: (H) Supporting PNF onboarding CSAR package based SOL004
- SDC-1974: (H) Supporting PNF manifest file
- SDC-1975: (H) Design time catalog to associate artifacts with PNF
- SDC-1976: (H) Supporting PNFD (SOL001) mapping to AID model
- SDC-1977: (M) Removing folder name dependence
- SDC-1978: (M) Removing the duplicate descriptor yaml file
- SDC-1979: (M) Allowing the dedicated artifact folder with Entry-point in TOSCA.meta
- SDC-1980: (M) Supporting packaging security
...
- 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
USE CASE ANALYSIS, SUPPORTING MATERIAL
The
VNF SDK,
VNF SDK Model, Package
...
- PNF package format
PTL to be notified
VNF SDK Model, Package notified (11/30)
...
...
- Onboarding PNFD to internal PNFD mapping
The project can help to identify the mapping to be implemented in SDC in Dublin timeframe
...
...
- VNFRQTS-497: Adding xNF Package security
- VNFRQTS-498: Adding VES Event Registration requirement to PNF package
- VNFRQTS-499: PNF on boarding CSAR Package
...
- 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.
...
Michela Bevilacqua - Add the PNF Onboarding diagram here
PNF PRE-ONBOARDING: LICENSING MANAGEMENT
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.
Licensing schema is expected to be used to identify or authorize the existence a particular PNF into the network of the service provider.
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.
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: PNF-SDK DEVELOPMENT
...
Development Status
Project | PTL | JIRA | Description | Status |
---|---|---|---|---|
SDC |
|
| PTL notified (11/19 ) Started discussions with SDC project | |
VNF SDK, VNF SDK Model, Package |
| PTL to be notified VNF SDK Model, Package notified (11/30) | ||
Resource Data Information Model |
| PTL notified (11/26) | ||
VNFRQTS |
|
| PTL to be notified (planned |
Appendix, Supporting Documents
...