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
  • entry_defintion_type in the ASD package will be copied into TOSCA.meta
• SDC maps the onboarding ASD models into the ONAP internal model
  • Design suggestion: ASD ↔ ONAP VF, DeploymentItems ↔ VF-Modules
  • see the mapping, MappingbetweenASDandSDCInternalModel 
  • extend the org.openecomp.groups.VfModule to hold the DeploymentItems properties, such as deployment_order and lifecycle parameters Note: SO CNFM can read the properties from ASD.
• 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 uses the Artifacts > HELM directory to hold the onboarding Helm Charts
• SDC UI should be able to modify some of ASD property values
  • SDC UI populates lifecycleManagement values as needed
  • If values.schema.json files exist, SDC UI validates values.yaml files and populate customizable values