Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

    • main_app_template.yaml.                                                // TASK #<>: SDC copies the asd manifest entries to this main TOSCA definition file
    • GlobalSubstitutionTypesServiceTemplate.yaml.            // TASK #<8>: SDC generates this based on the onboarding descriptors and metadata

note: for App package onboarding, the following SDC internal structures are under discussion with the SDC teamThe following definitions files are there for all VSPs, but not really used outside of SDC; i.g., The VSP itself is an internal SDC structure, and I believe it is not supposed to be read/used outside of SDC.


    •  onap (TBD)
      • _index.yml
      • artifacts.yml
      • capabilities.yml
      • data.yml
      • interfaces.yml
      • nodes.yml
      • relationships.yml
    • onapecomp onapecomp                                 // TBD  
      • _index.yml
      • artifacts.yml
      • capabilities.yml
      • data.yml
      • interfaces.yml
      • nodes.yml
      • relationships.yml
    • openecomp-heat heat                        // TASK #<9>: SDC does not use this directory for the App Package  
      • _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)
    • 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)

...