Page History

...

• • Informational
    • OTHER
      • VSP_<?>_Information.txt
• csar.meta

Mapping between ASD and SDC Internal Model

• Node type for ASD and data type for the deployment items added to Definitions/nodes.yaml and Definitions/data.yaml respectively

• interface type (i.e. the substitution mapping type) created from org.openecomp.resource.abstract.nodes.VF, in standard ONAP way, with the standard ONAP properties
• Main template generated as follows: 
• node template added for the ASD type generated from the definition in the onboarded csar
• vfModule group type added for each deployment item. see below for explanation of the properties and values used
• sub. mapping added in standard ONAP way
• Helm charts added to Artifacts/Deployment/HELM (similar to what is done today for onap zip cnf packages)
• Original onboarded ASD csar is included in the same way as we do for ETSI.
• I have added anything specific to allow SO identify the package as ASD, it could be done by SO deducing from the info already there (e.g. does it have a node template of the ASD type), but will be straightforward to add something explicitly if that is preferred, similar to what you have suggested in the TOSCA.meta
• We need a way for SDC to recognise the onboarded csar as an ASD, for etsi we reply on presence of ETSI-... metdata. We can add something similar for ASD

Create Service CSAR file

• TOSCA-Metadata REQUIREMENT #<23>: SDC generates TOSCA-Metadata directory and TOSCA.meta
  • TOSCA.meta
• Definitions. REQUIREMENT #<24>: SDC maps the onboarding ASD models into the ONAP internal. Note: mapping is under discussion
  • annotations.yml
  • artifacts.yml
  • capabilities.yml
  • data.yml
  • groups.yml
  • interfaces.yml
  • nodes.yml
  • policies.yml
  • relationships.yml
  • asd_types.yaml.                            // instead of using ONAP type definitions, support the ASD model specific definitions are included; TBD
  • resource-<...>-template-inteface.yml (came from VF)
  • resource-<...>-template.yml
  • service-<...>-template-interface.yml
  • service-<...>-template.yml. (put input parameters, additional properties...)
• Artifacts
  • Resources
    • <VF-name>
      • Deployment //REQUIREMENT #<25>: use the "HELM" directory to contain Helm Charts
        • HELM
          • <helm files>
• csar.meta
• NS.mf