For R7 PNF Pre-onboarding

USE CASE

PNF Preonboarding / Onboarding		REQ-319 - Getting issue details... STATUS
	VNF SDK STORY JIRA	VNFSDK-597 - Getting issue details... STATUS
	VNF SDK planning	VNFSDK-609 - Getting issue details... STATUS
	VNF SDK	NFR commitment
Architecture Sub-committee Jira tracker		ONAPARC-575 - Getting issue details... STATUS
Key Contacts		Benjamin Cheung damian.nowak

BUSINESS DRIVER

This section describes Business Drivers needs.

EXECUTIVE SUMMARY - This requirement enhances the PNF (Onboarding) / Pre-onboarding use case. This requirement introduces package security Option2 improvements on Signature per artifact on the Vendor delivered package as defined in ETSI NFV SOL004 v2.7.1 section 5.2. The validation of onboarded PM dictionary data based on schema information will be done. The standard can be found here: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/004/02.07.01_60/gs_NFV-SOL004v020701p.pdf . In R4 and R6, Option 1 signature per package was developed but not Option 2.

BUSINESS IMPACT - The enhancement to Onboarding & Pre-onboarding is a critical business function because they are vital to design-time operation to properly onboard vendor packages.

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

FUNDING/FINANCIAL IMPACTS - The PNF Onboarding & Pre-onboarding use case has Operating Expense (OPEX) savings for operators because of the ability to saving time and expenses during installation and commissioning of PNF resources.

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
AAF	Jonathan Gathman
APPC	Takamune Cho
CLAMP	Gervais-Martial Ngueko
CC-SDK	Dan Timoney
DCAE	Vijay Kumar
DMaaP	Mandar Sawant
External API	Matthieu Geerebaert
MODELING	Hui Deng
Multi-VIM / Cloud	Bin Yang
OOF	Shankaranarayanan Puzhavakath Narayanan
POLICY	Pamela Dragosh
PORTAL	Manoop Talasila
SDN-C	Dan Timoney
SDC	Ofir Sonsino
SO	Seshu Kumar Mudiganti
VID	ittay
VNFRQTS	Steven wright
VNF-SDK	victor gao → Former user (Deleted)	EPIC #1 Package Validation enhancements notable Package security (option 2 security on entire package) - Signatures Hashchecks per artifact (applicable for both Option 1 & 2) – in R4/R5/R6 signature Hashcheck may exist for option 1. Improvements & Enhancements for PNFs.
CDS	Yuriy Malakov

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 Diagram Example.png

USE CASE FUNCTIONAL DEFINITIONS

Use Case Title	PNF Pre-onboarding & Onboarding
Actors (and System Components)	#1 - Vendor / #2 - SDC / #3 - VNF-SDK / #4 - ONAP Components
Description	The base PNF pre-onboarding / onboarding use case is at this wiki: 5G - PNF Pre-Onboarding & Onboarding SOL004 specifies Package integrity/authenticity OPTION #1 open package create sign each artifacts of package & create a digest; store calculated hashes in manifest file. Calculator checksum of each artifact. OPTION #2 – same but on entire CSAR package. Sign the entire package put with signature.
Points of Contact	Benjamin Cheung , Zu Qiang , Michela Bevilacqua , damian.nowak
Preconditions	The PNF Vendor package is delivered to ONAP The PNF Vendor package is described in detail in the "base" wiki page
Triggers / Begins when	Describes the trigger for beginning the Use Case
Steps / Flows (success)	Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced
Post-conditions	The expected results of the execution of the Use Case Includes description of Information Produced
Alternate / Exception Paths	Description of any exceptions or special process that could occur during Use Case
Related Use Cases	List of the Use Cases referenced by this Use Case
Assumptions	Describes any assumptions that are made for this use case
Tools / References / Artifacts	List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case

TESTING

Current Status

Testing Blockers
High visibility bugs
Other issues for testing that should be seen at a summary level
Where possible, always include JIRA links

END TO END FLOW TO BE TESTED

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
4	Test Cases should include enough detail for testing team to implement the test	FAILED

R7 PNF Pre-onboarding / (onboarding)