...
- SDC shall support Application Package onboarding and distribution, where the onboarding package conforms to ETSI SOL004 and the embedded model conforms to ASD.
App Onboarding Package Requirement
Requirement | Description | JIRA |
---|---|---|
R1 | In the TOSCA.meta, reuse the same metadata structure defined by TOSCA and ETSI
| |
R2 | In the TOSCA.meta, reuse the same ETSI defined Entry Keywords
| |
R3 | In the main manifest file, reuse the metadata structure defined by ETSI with new keywords (the following proposal is under discussion)
| |
R4 | In the main manifest file, reuse the artifact security as defined by ETSI
For Jakarta PoC, ONAP shall support the security option #2. So, the App provider delivers one zip file consisting of the CSAR file, a signature file and a certificate file that includes the App provider public key. -- AppPackage.zip –- AppPackage.csar –- AppPackage.csar signature –- Signing certificate | |
R5 | In the main manifest file non_mano_artifact_sets, reuse the same structure with the existing keywords defined by ONAP
|
User Story
Priority | User Story | Description | JIRA Ticket |
---|---|---|---|
1 | US 1 | The App Package shall be compliant to the ETSI NFV SOL004 CSAR structure with the TOSCA-Metadata directory
| |
1 | US 2 | SDC creates an SDC VSP package thru onboarding of an Application Service CSAR based on ASD
| |
1 | US 3 | SDC creates AS internal CSAR (VF resource) by importing VSP CSAR to add CNF/Application based on ASD
| |
1 | US 4 | Create an Service CSAR consists of one or more CNF/Application based on ASD
| |
1 | US 5 | SDC distributes Service CSAR to ONAP runtime components thru DMaaP
| |
1 | US 6 | For the App Package notification, ONAP Runtime Catalog Manager queries from SDC and stores associated Helm Charts and Images to the target Helm and Image Artifact Repositories
| |
...
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
Vendor App Onboarding Package
Application Service Onboarding Package conforms to the ETSI SOL004 ( inspired ) until SOL004
- 1) makes the SOL001 VNFD optional (to allow ASD and/or APP Descriptor) and
- 2) allow App package-specific metadata
...
ONAP SDC supports SOL004-conformed CSAR onboarding with the TOSCA-Metadata directory, which includes the TOSCA.meta metadata file, providing and entry information for processing a CSAR file.
- TASK #<1>: The App Package shall be compliant to the ETSI NFV SOL004 CSAR structure with the TOSCA-Metadata directory
- ONAP SDC supports only the CSAR onboarding with the TOSCA-Metadata directory
- ASSUMPTION: SOL001 VNFD mandatory requirement in the current SOL004 needs to be changed; i.e., make SOL001 VNFD in SOL004 optional.
- Note: this PoC assumes the SOL001 VNFD is optional in the SOL004 package. Instead, ASD will be embedded in the App package
- Locations of files in CSAR are defined by Tosca.meta, Manifest and main TOSCA definition files
...
- TOSCA.meta
- TASK #<5>: for ASD, SDC use the same metadata structure defined by TOSCA and SOL004, plus use only ETSI-Entry-Manifest and ETSI-Entry-Change-Log from the above list
- TOSCA-Meta-File-Version
- CSAR-Version
- Created-By
- Entry-Definitions
- TASK #<5>: for ASD, SDC use the same metadata structure defined by TOSCA and SOL004, plus use only ETSI-Entry-Manifest and ETSI-Entry-Change-Log from the above list
- TOSCA.meta
...
- ETSI-Entry-Manifest
- ETSI-Entry-ManifestChange-Log
e.g.,
TOSCA-Meta-File-Version: 1.0
...
Entry-Definitions: Definitions/main_app_template.yaml
ETSI-Entry-Manifest: app_main_descripter.mf
ETSI-Entry-Change-Log: Artifacts/ChangeLog.txt
- Definitions
- ASD_1_0_types.yaml // TASK #<6>: define ASD data models for node_types, artifact_types, data_types...
...