Versions Compared

Key

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

...

PlantUML Macro
titlePNF Pre-onboarding/Onboarding
@startuml
participant VENDOR
participant ONAPUSER
participant VNFSDK
participant SDC
autonumber 

group PNF PACKAGE DELIVERY
	hnote over ONAPUSER : Vendor Delivery Mechanism/Options/API/Variable I/F(Multiple ways that a vendor deliver)
	hnote over ONAPUSER : Vendor Package Delivery
	VENDOR -> ONAPUSER : PNF Package Delivery 	
end

group PACKAGE VALIDATION
	hnote over VNFSDK : VNF SDK Package Validation
	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

group SDC PACKAGE ONBOARDING
	hnote over SDC : xNF Resources, Service ID
	SDC -> SDC : UUID Metadata added
 	SDC -> SDC: TOSCA MetaData added
	SDC -> SDC : TOSCA Descriptor Added
	SDC -> SDC : X License Model Files Added
	ONAPUSER -> SDC : Additional Artifacts Added (Manual/Optional)
end

@enduml

...

1. PNF PACKAGE DELIVERY – Vendor Delivers the Package.

There are multiple ways that a vendor could deliver a package. There is not SOL or any other kind of standard which specifies HOW a vendor shall deliver a package. There is no API, it could  be on a memory/flash drive or cloud shared delivery system or any other conceivable way to deliver digital information.

3.2 Flow Description: PACKAGE VALIDATION (VNF-SDK)

...