...
- TOSCA-Metadata: TASK #<14>: SDC generates TOSCA-Metadata directory and TOSCA.meta based on the corresponding VSP
- TOSCA.meta
- Definitions: TASK #<15>: SDC maps the onboarding ASD models into the ONAP internal. See the mapping section below.
note: all necessary TOSCA types needs to be included as part of the ONAP TOSCA model. So they will all be included in those files, classified based on the type added.
- artifacts.yml
- capabilities.yml
- data.yml // TASK #<>: SDC extends data.yml for ASD types
- groups.yml. // TASK #<>: SDC extends the VF-Module for additional properties
- interfaces.yml
- nodes.yml // TASK #<>: SDC extends nodes.yml for ASD-based CNF
- policies.yml
- relationships.yml
- resource-<...>-template.yml. TASK #<16>: SDC generates this based on the onboarding ASD model
- resource-<...>-template-interface.yml TASK #<17>: SDC generates this based on the onboarding ASD model
- Artifacts
- Deployment: TASK #<18>: SDC preserves the original onboarding App package and additional License files thru SDC UI
- AS_PACKAGE (original)
- <App>.csar // original vendor CSAR
- VENDOR_LICENSE
- VF_LICENSE
- AS_PACKAGE (original)
- HELM
- <HELM Chart A file>
- <HLEM Chart B file>
- Informational
- OTHER
- VSP_<?>_Information.txt
- OTHER
- Deployment: TASK #<18>: SDC preserves the original onboarding App package and additional License files thru SDC UI
- csar.meta
- Files. (missing from SDC****; Its handling is under discussion)
- Images
- <image>
- <image>
- Images
- e.g.,
...