...
The package structure must be a CSAR with TOSCA-Metadata as specified in SOL004 section 4.1.2
The TOSCA.meta file keyname extension: SOL004 section 4.1.2.3. You can refer to the PNF Pre-onboarding & Onboarding Wiki for more information: 5G - PNF Pre-Onboarding & Onboarding
3. Information Flow
3.1 Pre-onboarding Flow
The following UML diagram shows the VNF/PNF Pre-onboarding Flow
| PlantUML Macro | ||
|---|---|---|
| ||
@startuml
participant VENDOR
participant ONAPUSER
participant VNFSDK
participant SDC
autonumber
group PNF PACKAGE DELIVERY
hnote over ONAPUSER : Vendor Package Delivery
VENDOR -> ONAPUSER : VNF/PNF Package Delivery
end
group PRE-ONBOARDING
hnote over VNFSDK : VNF SDK Package Validation (optional)
ONAPUSER -> VNFSDK : PNF Package Delivery
VNFSDK -> VNFSDK : License File Check
VNFSDK -> VNFSDK : Certificate File Check
VNFSDK -> VNFSDK : Manifest file & destination cross-check
VNFSDK -> VNFSDK : Manifest file tag Validation
VNFSDK -> VNFSDK : TOSCA Metadata file validation
hnote over VNFSDK : Certification Studio
VNFSDK -> ONAPUSER : User checks validation
end
@enduml |
3.2 Onboarding Flow
The following UML diagram shows Onboarding Flow:
| PlantUML Macro | ||
|---|---|---|
| ||
@startuml participant VENDOR participant ONAPUSER participant VNFSDK participant SDC autonumber group VNF/PNF PACKAGE DELIVERY hnote over ONAPUSER : Vendor Package Delivery VENDOR -> ONAPUSER : VNF/PNF Package Delivery end group PRE-ONBOARDING hnote over VNFSDK : Optional step end group Create a resource hnote over SDC : Options to create a resource in SDC group Onboarding hnote over SDC : Two onboarding options group Options group PACKAGE ONBOARDING hnote over SDC : Create a VSP model using onboarding package (PNF csar, VNF csar, or Heat) ONAPUSER -> SDC : onboarding a package SDC -> SDC : Create an internal model with Metadata added SDC -> SDC : Transform onboarding artifacts into SDC onboarding SDC -> SDC : Transform onboarding descriptor into internal descriptor SDC -> SDC : License Model Files Added end group Manual VNF VSP creation hnote over SDC : Manual create a VNF VSP model ONAPUSER -> SDC : Create a VSP SDC -> SDC : Create an internal model with Metadata added ONAPUSER -> SDC : Update internal descriptor proprieties ONAPUSER -> SDC : License Model Files Added ONAPUSER -> SDC : Artifacts Added end end end group Create a resource group Create resource from a VSP hnote over SDC : Create resource model from a VSP ONAPUSER -> SDC : Create a VSP SDC -> SDC : Transform a VSP into a resource model SDC -> SDC : update internal descriptor proprieties SDC -> SDC : update License Model Files ONAPUSER -> SDC : Additional Artifacts Added (Manual/Optional) end group Manual create a VNF or PNF resource hnote over SDC : Manual create a VNF / PNF Resources SDC -> SDC : create an internal VNF / PNF model with Metadata added ONAPUSER -> SDC : Update internal descriptor proprieties ONAPUSER -> SDC : License Model Files Added ONAPUSER -> SDC : Additional Artifacts Added (Manual/Optional) end end end group Create a Service hnote over SDC : Manual create a Service model SDC -> SDC : create an internal service model with Metadata added ONAPUSER -> SDC : Add Resource(s) ONAPUSER -> SDC : Additional Artifacts Added end @enduml |
...
The following sections describe the above (UML) steps in more detail:
3.
...
3 Flow Description: PNF PACKAGE DELIVERY
1. PNF PACKAGE DELIVERY – Vendor Delivers the Package.
...
the Vendor provided package is imported by a Technology Specialist/Asset manager into SDC.
3.
...
4 Flow Description: PACKAGE VALIDATION (VNF-SDK)
3. LICENSE FILE CHECK – VNF-SDK performs a license file check within the vendor-delivered PNF package.
...
8. USER CHECKS VALIDATION – The end user may then inspect that the PNF package has been appropriately verified in the Certification studio.
3.
...
5 Flow Description: SDC PACKAGE ONBOARDING
In the next steps, SDC brings that Vendor provided package into the SDC Catalog and creates an SDC internal representation of that package.
...