Page History

...

• •  onap (TBD)
    • _index.yml
    • artifacts.yml
    • capabilities.yml
    • data.yml
    • interfaces.yml
    • nodes.yml
    • relationships.yml
  • onapecomp                                
    
    • _index.yml
    • artifacts.yml
    • capabilities.yml
    • data.yml
    • interfaces.yml
    • nodes.yml
    • relationships.yml
  • openecomp-heat                      
    • _index.yml
    • data.yml
    • groups.yml
    • nodes.yml
  •  tosca
    • _index.yml
    • artifacts.yml
    • capabilities.yml
    • data.yml
    • groups.yml
    • interfaces.yml
    • nodes.yml
    • policies.yml
    • relationships.yml
• Artifacts: TASK #<10>: SDC generates this directory by copying artifacts from the onboarding App package
  
  • <cnf>.mf                   // TASK #<>: based on the app/asd metadata in the onboarding manifest file, SDC creates app/asd-specific metadata (e.g., subcategory: ASD)

// note: We can define a specific category for ASD package types, which the Resource created based on this VSP (Import VSP feature) will be associated with.

// The category associated will be defined in the main TOSCA descriptor metadata. So, runtime components solutions could know what type of resource they are dealing with.

• • Definitions
    • ASD_1_0_types.yaml
    • <main_app_template>.yaml
  • Deployment: TASK #<11>: SDC preserves the original onboarding App package 
    • APP_PACKAGE.              // copy of the original AS package
  • Images: TASK #<12>: 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.  
    • <image>
    • <image>
  • HELM (TBD)
    • <helm file>
    • <helm file>
  •  Informational
    • <Guide>
      • VSP_<?>_Information.txt
  • LcmScripts
    • <scripts>
  • Licenses
    • LICENSE.txt
  • TOSCA-Metadata: TASK #<13>: SDC preserves the original onboarding TOSCA.metadata
    • TOSCA.meta.original
  • ChangeLog.txt
  • vendor-license-model.xml (not sure how SO uses)
  • vf-license-model.xml (not sure how SO uses)

Create VF CSAR file - an original way (this is the preferred way for PoC)

• 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 betlowbelow.
  • 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
  • HELM
    • <HELM Chart A file>
    • <HLEM Chart B file>
  •  Informational
    • OTHER
      • VSP_<?>_Information.txt
• csar.meta
• Files. (missing from SDC****; Its handling is under discussion)
  • Images
    • <image>
    • <image>
• e.g.,

...