...
| 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 - Create ASD_1_0_types.yaml which represents Application Service Descriptor (ASD) in TOSCA
- Introduce the ASD-related metadata in the App package manifest file. By using the new metadata, SDC and orchestrator know this package is based on ASD
- Introduce a new key name to metadata, "ASD-Entry-Definitions" in the TOSCA.meta
|
|
| 1 | US 2 | SDC creates an SDC VSP package thru onboarding of an Application Service CSAR based on ASD - SDC copies the ASD-Entry-Definitions metadata from the onboarding App package TOSCA.meta
- SDC maps ASD to ONAP internal model in SDC VSP
- Design suggestion: ASD ↔ ONAP VF, DeploymentItems ↔ VF-Modules
- SDC generates the GlobalSubstitutionTypesServiceTemplate.yaml by including the app_main_descripter.mf information
- SDC does not use openecomp-heat directory for the App Package
- SDC generates Artifacts directory by copying artifacts from the onboarding App package
- SDC preserves the original onboarding App package in the Deployment directory
- SDC should be able to handle large-size image files. SDC stores the image files to the Kubernetes Object Storage temporarily and waits for the Runtime Catalog Manager picks up and stores the images files to the Image repository
- SDC preserves the original onboarding TOSCA.meta (rename TOSCA.meta.original) in the TOSCA-Metadata
|
|
| 1 | US 3 | SDC creates AS internal CSAR (VF resource) by importing VSP CSAR to add CNF/Application based on ASD - SDC generates TOSCA-Metadata directory and TOSCA.meta for ASD package
- SDC maps the onboarding ASD models into the ONAP internal model
- SDC generates resource-<...>-template and template-interface models based on the onboarding ASD model
- SDC preserves the original onboarding App package and adds additional License files thru SDC UI
- SDC UI should be able to modify some of ASD property values
- If values.schema.json files exist, SDC UI validates values.yaml files and populate customizable values
|
|
| 1 | US 4 | Create an Service CSAR consists of one or more CNF/Application based on ASD - SDC generates TOSCA-Metadata directory and TOSCA.meta
- SDC maps the onboarding ASD models into the ONAP internal models
- SDC uses the "HELM" directory under the Artifacts to contain Helm Charts
|
|
| 1 | US 5 | SDC distributes Service CSAR to ONAP runtime components thru DMaaP - Assuming no SDC impact for this
|
|
| 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 - Get Helm Charts from the Helm directory and stores the target Helm Artifact Repository
- Get Images from the Object Storage and stores the target Image Artifact Repository
|
|
|
|
|
|
...
- Files (optional; Images, Licenses and Artifacts directories can be located under the root directory)
- Images
- Licenses
- Artifacts
- Deployment
- HELM //REQUIREMENT #<>: use the "HELM" directory to contain Helm Charts
- <Helm Chart file> // Helm Charts can include values.schema.json along with values.yaml; it
- <Helm Chart file> // It is for imposing a structure on the values.yaml file<Helm Chart file>
// REQUIREMENT #<>: If values.schema.json files exist, SDC UI uses them to validate values.yaml files and populates customizable values
SDC creates VSP CSAR file for App Package Onboarding
...
