...
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.
2. PNF PACKAGE DELIVERY – Package is accepted into ONAP
the Vendor provided package is imported by a Technology Specialist/Asset manager into SDC.
3.2 Flow Description: PACKAGE VALIDATION (VNF-SDK)
23. LICENSE FILE CHECK – VNF-SDK performs a license file check within the vendor-delivered PNF package.
34.CERTIFICATE FILE CHECK – VNF-SDK performs a certificate file check within the vendor-delivered PNF package.
45.FILE AND DESTINATION CHECK – VNF-SDK examines the MainServiceTemplate.mf (Manifest file) and performs a cross-check of the files & pathway directories specified within the manifest faile against the actual files within the vendor-delivered PNF package. It checks that the files that have been specified in the manifest file are actually in the given destination (directories).
56. MANIFEST FILE TAG VALIDATION – VNF-SDK performs a check of the PNF keywords in the MainServiceTemplate.mf (Manifest file). The tags are pnf_product_name, pnf_provider_id, pnf_package_version, pnf_release_data_time, and non-mano_artifact_sets.
67. TOSCA METADATA FILE VALIDATION – VNF checks the Meta Data file (TOSCA.meta) in the PNF package with the ETSI SOL004 validation tags. The checks performed are the Entry definition, Entry-manifest, Entry-change-log, Entry-tests, Entry certificates.
78. USER CHECKS VALIDATION – The end user may then inspect that the PNF package has been appropriately verified in the Certification studio.
...
In the next steps, SDC brings that Vendor provided package into the SDC Catalog and creates an SDC internal representation of that package.
8A. UUID IDENTIFIER – SDC adds a UUID identifier.
9B.TOSCA METADATA – SDC adds additional TOSCA Meta-data.
10C.TOSCA DESCRIPTOR – SDC may add a TOSCA Descriptor
11D. LICENSE MODEL FILE – SDC can add a license model file.
12E. ADDITIONAL ARTIFACTS – The User may optionally manually add additional artifacts.
PACKAGE ONBOARDING
There are two options to onboard into SDC. OPTION #1 is to "automatically" onboard a package.
In this case, a VSP model is created using an Onboarding package (PNF CSAR, VNF CSAR or Heat)
9. ONBOARD PACKAGE - The onboarding package is accessed by a Technology specialist/Asset manager
10. INTERNAL MODEL - An internal model is created in SDC with MetaData added.
11. TRANSFORM ARTIFACTS - The artifacts from the PNF or VNF package are transformed into onboarding artifacts during SDC onboarding.
12. ONBOARD DESCRIPTOR - SDC transforms the xNF onboarding descriptor into an SDC internal descriptor
13. LICENSE MODEL FILES - License Model Files are added
MANUAL VNF VSP CREATION
The second option is to manually onboard into SDC, this entails the manual creation of a VNF VSP.
In this case, a VNF VSP model is manually created.
14. CREATE A VSP - The Technology specilist/Asset manager initiates a manual VSP creation.
15. INTERNAL MODEL - SDC is used to create an internal model with Metadata added
16. INTERNAL DESCRIPTOR - The internal descriptor proprieties are updated
17. LICENSE MODEL FILES - The License Model Files are then added to the VSP
18. ARTIFACTS ADDED - Finally, additional artifacts are added if necessary
CREATE RESOURCE - FROM A VSP
There are two ways to create a resource. A resource can be: (option 1) created from a VSP or (option 2) through manual creation.
these are the steps for creating a resource from a VSP.
19.
20.
21.
22.
23.
CREATE RESOURCE - MANUAL CREATION OF xNF RESOURCE
24.
25.
26.
27.
CREATE A SERVICE
28.
29.
30.
4. Post Condition
The post-conditions for this flow are:
...