...
Proposed UC to focus on in Dublin :
- PNF Pre-Onboarding
- PNF OnboardingOnboardin
- Reference Presentation provided to 5G UC meeting (Nov 15th, 2018): ONAP Dublin_PNFOnboarding.pptx
USE CASES
CASES
Background
In Casabablanca Release, the PnP Use Case covered This Use Case Covers in Casablanca (R3) :
- PNF Definition at Design Time
- PNF Instantiation in ONAP at Run Time (Including Initial Configuration)Time
In Casablanca Release, the PnP Use Case did not This Use Case Today does NOT cover the PNF Onboarding - The , the Onboarding process of a Vendor PNF archive including a PNF descriptor and a set of Artifacts.UCs for DUBLIN (R4) Release
PNF Pre-ONBOARDING Onboarding Use CASECase in Dublin
- PNF 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 Use Case :in Dublin
- PNF Archive can be onboarded through ONAP
- ONAP SDC shall also continue to support PNF definition by UI as in Casablanca Release.
![](/download/attachments/45303641/image2018-12-6_16-33-4.png?version=1&modificationDate=1544110385000&api=v2)
![](/download/attachments/45303641/image2018-12-6_16-33-34.png?version=1&modificationDate=1544110414000&api=v2)
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
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
...
COMPONENT | IMPACT DESCRIPTION | PTL |
---|
Service Design & Creation Project | - 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
| 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 | - 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
| |
DEVELOPMENT STATUS
Project | PTL | JIRA | Description | Status |
---|
SDC
| | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1970 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1973 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1974 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1975 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1976 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1977 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1978 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1979 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | 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 | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFSDK-337 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFSDK-338 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-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) PNF package to ONAP.pptx |
Resource Data Model | | No JIRA ticket required, project can help to identify the mappings required in SDC in Dublin timeframe | - Onboarded PNFD to Platform PNFD mapping
| PTL notified (11/26) |
VNFRQTS | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFRQTS-506 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFRQTS-496 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFRQTS-497 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFRQTS-498 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFRQTS-499 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFRQTS-505 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFRQTS-507 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VNFRQTS-508 |
---|
|
| - Network Function requirements shall be updated to cover PNF package, descriptor and artifacts
- VNF requirements could be reviewed.
| PTL to be notified |
USE CASE ANALYSIS, SUPPORTING MATERIAL
...