SDC creates an SDC VSP package thru onboarding of an Application Service CSAR based on ASD

• SDC copies the contents of TOSCA.meta 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
  • If VSP model can be ignored, this mapping can be skipped
• SDC generates the GlobalSubstitutionTypesServiceTemplate.yaml by including the app_main_descripter.mf information
• SDC generates Artifacts directory by copying artifacts from the onboarding App package

• • SDC should copy all the onboarding artifacts to VSP
• 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
• SDC uses the Artifacts > HELM directory to hold the onboarding Helm Charts