Versions Compared

Old Version 192

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version 193

changes.mady.by.user Zu Qiang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Authors: Ben Benjamin Cheung Image Removed , Michela Bevilacqua Image Removed , Zu QiangImage Removed

Table of Contents

...

PNF PRE-ONBOARDING & ONBOARDING OVERVIEW




Descriptor, Artifacts and Package Delivery

PNF Package

Pre-onboarding

ONAP onboarding process,

PNF Package onboarding

ONAP Design Time activitiesONAP Run Time activities
WHENPNF delivery timePre-Onboarding activitiesOnboarding ActivitiesONAP Design Time ActivitiesONAP Run Time
WHOVendorTechnology Specialist

Technology Specialist

Asset Manager

Service Designer

Operations Specialist

Operations Specialist
WHATDescriptor, Artifacts and Package delivery

PNF Package

NF validation Activities

PNF Package,

PNF Descriptor

PNF Onboarding

SDC Meta-data added (vendor onboarded CSAR to SDC onboarded CSAR)

ONAP Common Information Model

SDC Data Model

5G Service Definition

Service Design

SDC Model mapping

5G Service Instantiation

PNF Instance

A&AI PNF Instance

ETSI NFV reference

SOL001 PNFD

SOL004 Package

ETSI SOL004 Package

ETSI SOL001 PNFD,

SOL004 Package


-


PNF PRE-ONBOARDING & ONBOARDING DUBLIN WORK

...

Project / PTLJIRADescriptionStatus

SDC

Michael Lando
Vitaly E
Ofir Sonsino


SDC Development Status

  1. PNF package format
    • Identify current VNF package format constraints in SDC
    • Propose a PNF Package format
    • Evaluate VNF and PNF package alignment
  2. Onboarding PNF package to internal PNF package mapping
    • including adding the manifest file with new key words
    • including adding metadata file with new key words
    • non_Mano artifacts based on the public non_mano_artifact_sets key name
    • Package security to be supported (starting with option 2)
  3. Keep a copy of the original on boarding package under artifact folder (agreed in SDC weekly meeting)
  4. Onboarding PNFD to internal PNFD mapping
    • A new flow will be introduced in SDC to map ETSI SOL001 PNFD into SDC AID model.
  5. 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 )

Code is ready for M4(11/04)

VNF SDK

victor gao

VNFSDK Model Package

Andy Mayer


VNFSDK Development Status

  1. PNF package format verification

VNFSDK PTL notified (12/05)

VNF SDK Model, Package notified (11/30)

PNF package to ONAP.pptx

Scope planned for Dublin completed ...except from package security item:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVNFSDK-342

E2E work tracked in this Jira item:

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVNFSDK-337

RESOURCE DATA MODEL

Anatoly Katzman

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)

VNF RQTS

Steven wright

VNF Requirement Development Status

  1. Network Function requirements shall be updated to cover PNF package, descriptor and artifacts
  2. VNF requirements could be reviewed.
  3. Remove or modify the existing package / documentation requirements (some of them is from the RFP or heat template only)
PTL notified (01/16)

...

PACKAGE DELIVERYONBOARDING PROCESSDESIGN TIMERUN TIME
NF DescriptorNF Descriptor Model

SDC Data Model

A&AI PNF Data model, PNF instance

VES event registration file/
FM dictionary,

PM dictionary

artifactSDC Catalog

Run time Catalog


Informational ArtifactsartifactSDC CatalogRun time Catalog

Configuration Models and Files,

(including Ansible Playbooks)

artifactSDC CatalogRun 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.

...

FUNCTIONDUBLIN (R4)

FRANKFURT (R6)


GUILIN (R7)
Package DeliveryInitial Delivery

Pre-onboarding:

VNF-SDK Package Validation

Initial Delivery

Onboarding:

Package into SDC Catalog

Initial Delivery

Onboarding:

xNF Descriptor mapped to

Platform Info/Data Model

Initial Delivery

Design Time:

Usage of Onboarded Package

Creation of Resource/Svc

Initial Delivery

Run Time:

Ingestion of Service CSAR by

ONAP Run-time components

Initial Delivery

The following table has a list of the references pages for the Roadmap

ReleaseWiki
Dublin (R4)5G - PNF Pre-Onboarding & Onboarding
Frankfurt (R6)PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt

REQUIREMENTS


This section describes the requirements that are to be updated & added

(This section under development)


REQUIREMENTS CATEGORIESDESCRIPTION
CSAR structure

New requirements related to the CSAR structure for the PNF Onboarded package.

Section 5.1.6, VNF CSAR requirements based on SOL004 based only for VNFs.

Associated Tickets:

  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyVNFRQTS-497
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyVNFRQTS-499

  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyVNFRQTS-505
PNFD Descriptor

New VNF-RQTS requirements related to the PNF Descriptor.

The requirements describe the VNF-Descriptor and new updates need to be made to support PNF Descriptors.

Associated Tickets:

  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyVNFRQTS-508
Onboarding Requirements

New VNF-RQTS onboarding requirements.

In the document 7.2, xNF onboarding requirements but aren't clear what is needed. These requirements were copied from RFP but are outdated and some requirements are irrelevant, so in R4 for this use case, these requirements needs to be reviewed, updated, and revised.

Associated Tickets:

(TBD)



...