R7 PNF Plug and Play PnP

Table of Contents

USE CASE KEY INFORMATION

USE CASE

LEAD CONTACTS / DESCRIPTION

WIKI

PNF Plug and Play

@Benjamin Cheung , @damian.nowak 

5G - PNF Plug and Play

Integration Leads

@Marcin Przybysz  , @Krzysztof Kuzmicki



Requirement ID

Epic Jira for the requirement



https://lf-onap.atlassian.net/browse/REQ-318



SO Story Jira for PnP

SO-2981: PNF Plug & Play in R7 - SO Building Block WorkClosed



Modeling Story jira for PnP

https://lf-onap.atlassian.net/browse/MODELING-368

Architecture Sub-committee Jira tracker

Architecture sub-committee presentation



https://lf-onap.atlassian.net/browse/ONAPARC-575

Model Place / Geolocation / AAI Schema

Meetings Register

PNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion

Papyrus model:

Proposed Location Model



Generic Information Element Definition

for Geolocation Model

Generic Information Element Definition for Geolocation Model



NON FUNCTIONAL REQUIREMENT CONTRIBUTION

COMPONENT

U/C STORY JIRA

NFR JIRA

COMPANY

DESCRIPTION

COMPONENT

U/C STORY JIRA

NFR JIRA

COMPANY

DESCRIPTION

SO

SO-2981: PNF Plug & Play in R7 - SO Building Block WorkClosed

REQ-351: ONAP must complete update of the java language (from v8 -> v11) Done

Nokia

Non Functional requirement associated contribution.

No technical dependency/ organizational dependency.

SO NFR Support: Component of SO/LIBs update to Java v11

SO Dashboard







Service Orchestrator Guilin Release M1

BUSINESS DRIVER

This section describes Business Drivers needs.

EXECUTIVE SUMMARY This requirement will augment the work-flow to building block management within SO for Plug and Play operation. The continues the work started in R6. In R6, some of the SO work-flow to building block work was finished, and in R7 this is enhanced. The description of the "base" work which will be enhanced is shown in the wiki: PNF PLUG and PLAY in R6 Frankfurt

BUSINESS IMPACT - The enhancement to Plug and Play operation in ONAP is a critical business function because they enhance installation and commissioning activities.

BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage.

FUNDING/FINANCIAL IMPACTS - The plug and play project has Operating Expense (OPEX) savings for operators because of the ability to saving time and expenses during installation and commissioning and contributes towards ZTM (Zero touch management).

ORGANIZATION MGMT, SALES STRATEGIES - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.



DEVELOPMENT STATUS

PROJECT

PTL

User Story / Epic

Requirement

A&AI

@James Forsyth  → @William Reehil

NO IMPACT



AAF

@Jonathan Gathman  →  x

EPIC #1

(TEST ONLY / Integration) CMPv2 - Enhanced Secure X.509 Certificate support

(email from @damian.nowak  suggests to remove this dependency - testing will occur with REQ-321)

REQ-318 PNF Plug & Play in R7

I think, we need to remove the dependency to AAF for REQ-318. REQ-318 covers mainly work in the SO component. Looking at PNF PNP feature E2E we might have some relation to REQ-321, but no strict dependency. Perhaps some AAF dependency was mentioned in REQ-318, before REQ-321 was created. I`d remove the AAF dependency from REQ-318 actually.



APPC

@Takamune Cho

NO IMPACT



CLAMP

@Gervais-Martial Ngueko

NO IMPACT



CC-SDK

@Dan Timoney

NO IMPACT



DCAE

@Vijay Kumar

NO IMPACT



DMaaP

@Mandar Sawant

NO IMPACT



External API

@Matthieu Geerebaert

NO IMPACT



MODELING

@Hui Deng

NO IMPACT



Multi-VIM /

Cloud

@Bin Yang  → @Eric Multanen

NO IMPACT



MUSIC

@bharathb  → (Empty)

NO IMPACT



OOF

@Shankaranarayanan Puzhavakath Narayanan

@krishna moorthy

NO IMPACT



POLICY

@Pamela Dragosh  →  @James Hahn

NO IMPACT



PORTAL

@Manoop Talasila  → @Sunder Tattavarada

NO IMPACT



SDN-C

@Dan Timoney

EPIC #3

Licensing Management flow w.r.t. PnP (q.v. Licensing Management Use Case)

(Dependency) Enhancements for requesting License Key File (LKF) & Licenses from License Service (message exchange)



SDC

@Ofir Sonsino

NO IMPACT



SO

@Seshu Kumar Mudiganti

EPIC #2

Workflow to Building Block Development

and integration

BB execution Framework, extended to understand PNFs.

Preparing input object used for different BBs.

Framework needs to take into PNFs. (Possible debug/work)

(Testing & Integration Work). Environment where this is run

Model parameters added, address the right CDS Blueprint.



VID

@ittay

NO IMPACT



VF-C

@Yuanhong Deng

NO IMPACT



VNFRQTS

@Steven wright

NO IMPACT



VNF-SDK

@victor gao

NO IMPACT



CDS

@Yuriy Malakov

NO IMPACT



List of PTLs:Approved Projects

*Each Requirement should be tracked by its own User Story in JIRA 

USE CASE DIAGRAM

Use cases define how different users interact with a system under design.  Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).

USE CASE FUNCTIONAL DEFINITIONS

Use Case Title

PNF Plug and Play - SO Building Block (Work flow)

Actors (and System Components)

PNF (5G DU)

ONAP DCAE-VES Event Listener / PRH: PNF Registration Handler

Description

PNF Plug and Play is used for installation and commissioning when a PNF registers with ONAP

Points of Contact

@Benjamin Cheung@damian.nowak

Preconditions

Design time activities have occurred, and Stage 1 of the Plug and Play Base Use Cases documented here:

5G - PNF Plug and Play

Triggers / Begins when

This is used during Installation & Commissioning for Plug and Play when SO needs to initiate the Building Block flow for PnP

Steps / Flows (success)

The flows are documented here:

5G - PNF Plug and Play

Post-conditions

The post-conditions are after the flows are after the ConfigDeployPNF.

The workflow has been completed and executed in SO

Alternate / Exception Paths

Errors can occur while executing the AssignPNF BB, Waiting for PNF ready BB, Config Assign PNF BB or Config Deploy PNF BB.

If the Waitfor PNF ready BB waiting for the PNF ready event never arrives because the PNF does not send the PNFRegistration event.

(the full details of the flows are in this wiki: 5G - PNF Plug and Play

Related Use Cases

None

Assumptions

None

Tools / References / Artifacts

References are listed in the base wiki: 5G - PNF Plug and Play

INFORMATION MODEL TEMPLATE

The modeling information for Geolocation can be found here:

Generic Information Element Definition for Geolocation Model

SUPPORTING FILES

Topic

File

Topic

File

Place / Geolocation Parameters & Analysis

PNFPlaceModel.xlsx

ETSI SOL001 proposal -

Geolocation Update

PLACE Proposal (Updated Aug 6 2020)

 





TESTING

Current Status

  1. Testing Blockers

  2. High visibility bugs

  3. Other issues for testing that should be seen at a summary level

  4. Where possible, always include JIRA links

END TO END FLOW TO BE TESTED



MEETING LOG

Regular meetings for PNFD/SDC AID/A&AI Schema Moeling and 5G Service Modeling

discussion for Geolocation & Place development for using using Plug and Play.

See this wiki for the Meetings: PNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion

you can watch/listen to previous recordings and meeting at the R6 PnP page: PNF PLUG and PLAY in R6 Frankfurt

TEST CASES AND STATUS



1

There should be a test case for each item in the sequence diagram

NOT YET TESTED

2

create additional requirements as needed for each discreet step

COMPLETE

3

Test cases should cover entire Use Case

PARTIALLY COMPLETE

 Test Cases should include enough detail for testing team to implement the test

 FAILED