Page History

...

ASD-Entry-Definitions: Definitions/main_app_template.yaml     

ETSI-Entry-Manifest: f5app_FWmain_cnfdescripter.mf

ETSI-Entry-Licenses: Licenses

...

• Files (optional; Images, Licenses and Artifacts directories can be located under the root directory)
  • Images
    • <image>.          // or image reference
    • <image>           // or image reference
  • Licenses
    • LICENSE.txt
  • Artifacts
    • Deployment
      • HELM             //REQUIREMENT #<>: use the "HELM" directory to contain Helm Charts
        • <Helm Chart A file>                                  // Helm Charts can include values.schema.json along with values.yaml
        • <Helm Chart B file>                                  // It is for imposing a structure on the values.yaml file

                                                                                                                        // REQUIREMENT #<>: If values.schema.json files exist, SDC UI uses them to validate values.yaml files and populates customizable values

...

• • main_app_template.yaml
  • GlobalSubstitutionTypesServiceTemplate.yaml.            // REQUIREMENT #<>: SDC generates this by including the app_main_descripter.mf information
  •  onap (TBD)
    • _index.yml
    • artifacts.yml
    • capabilities.yml
    • data.yml
    • interfaces.yml
    • nodes.yml
    • relationships.yml
  • onapecomp                                // TBD
    
    • _index.yml
    • artifacts.yml
    • capabilities.yml
    • data.yml
    • interfaces.yml
    • nodes.yml
    • relationships.yml
  • openecomp-heat                       // REQUIREMENT #<>: 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: REQUIREMENT #<>: SDC generates this directory by copying artifacts from the onboarding App package
  
  • F5_FW<?>_cnf.mf
  • Definitions
    • main_app_template.yaml
  • Deployment: REQUIREMENT #<>: SDC preserves the original onboarding App package 
    • APP_PACKAGE.              // copy of the original AS package
  • Images: REQUIREMENT #<>: 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>
  • Informational
    • <Guide>
      • VSP_f5<?>_Information.txt
  • LcmScripts
    • <scripts>
  • Licenses
    • LICENSE.txt
  • TOSCA-Metadata: REQUIREMENT #<>: 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 OLD way; not used for the ASDoriginal way

• TOSCA-Metadata: REQUIREMENT #<>: SDC generates TOSCA-Metadata directory and TOSCA.meta
  • TOSCA.meta
• Definitions: REQUIREMENT #<>: SDC maps the onboarding ASD models into the ONAP internal. Note: mapping is under discussion.
  • artifacts.yml
  • capabilities.yml
  • data.yml (if mapping, extra date types will be here)
  • groups.yml
  • interfaces.yml
  • nodes.yml (add ASD nodes)
  • policies.yml
  • relationships.yml
  • resource-<...>-template.yml. REQUIREMENT #<>: SDC generates this based on the onboarding ASD model
  • resource-<...>-template-interface.yml REQUIREMENT #<>: SDC generates this based on the onboarding ASD model
• Artifacts
  • Deployment: REQUIREMENT #<>: 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>
  •  InformationalInformational
    • OTHER
      • VSP_f5<?>_Information.txt
• csar.meta
• Files. (missing from SDC****; Its handling is under discussion)
  • Images
    • <image>
    • <image>
• e.g.,

tosca_definitions_version: tosca_simple_yaml_1_3
metadata:
  invariantUUID: 92e593ad-cc7d-4a97-8b64-83bc301e2e4f
  UUID: 90c7b63b-001a-4398-abb9-951e1a842437
  name: asd1
  description: f
  category: Generic
  type: VF
  subcategory: Network Elements
  resourceVendor: d
  resourceVendorRelease: 2.6.1
  reourceVendorModelNumber: ''
imports:
- nodes:
    file: nodes.yml
- datatypes:
    file: data.yml
- capabilities:
    file: capabilities.yml
- relationships:
    file: relationships.yml
- groups:
    file: groups.yml
- policies:
    file: policies.yml
- annotations:
    file: annotations.yml
- resource-asd1-interface:
    file: resource-Asd1-template-interface.yml
topology_template:
  inputs:
    skip_post_instantiation_configuration:
      default: true
      type: boolean
      required: false
    nf_naming:
      default:
        ecomp_generated_naming: true
      type: org.openecomp.datatypes.Naming
      required: false
    multi_stage_design:
      default: false
      type: boolean
      required: false
    nf_naming_code:
      type: string
      required: false
    nf_function:
      type: string
      required: false
    controller_actor:
      default: SO-REF-DATA
      type: string
      required: false
    availability_zone_max_count:
      default: 1
      type: integer
      required: false
    sdnc_artifact_name:
      type: string
      required: false
    max_instances:
      type: integer
      required: false
    nf_type:
      type: string
      required: false
    sdnc_model_version:
      type: string
      required: false
    nf_role:
      type: string
      required: false
    min_instances:
      type: integer
      required: false
    sdnc_model_name:
      type: string
      required: false
  node_templates:
    asd_instance:
      type: org.onap.asd.CNF
      metadata:
        invariantUUID: 3948bd3d-f4e2-41a9-b3b4-edc6c6db927e
        UUID: 05329593-52f8-482d-a967-8dbb28bb117a
        name: Asd1.CNF
        description: Not reusable inner VFC
        category: Generic
        version: '1.0'
        customizationUUID: 59c10655-f68e-47d3-bf7b-d8f5698f6f75
        type: VFC. // ??
        subcategory: Abstract
        resourceVendor: d
        resourceVendorRelease: 2.6.1
        reourceVendorModelNumber: ''
      properties:
        asd_id: ASD Instance
        asc_schema_version: 1.0.0
  group:
    Asd..helmA..module-0:
      type: org.openecomp.groups.VfModule
      metadata:
        vfModuleModelName: Asd..helmA..module-0
        vfModuleModelInvariantUUID: 766017db-5c11-47f9-a3c4-1fed0dbae9cb
        vfModuleModelUUID: 57a35aad-4290-4b55-a0b2-150aad6da058
        vfModuleModelVersion: '0.0'
      properties:
        min_vf_module_instances: 1
        vf_module_label: helmA
        max_vf_module_instances: 1
        vf_module_type: Base
        isBase: true
        initial_count: 1
        volume_group: false
    Asd..helmB..module-1:
      type: org.openecomp.groups.VfModule
      metadata:
        vfModuleModelName: Asd..helmB..module-0
        vfModuleModelInvariantUUID: 766017db-5c11-47f9-a3c4-1fed0dbae9cb
        vfModuleModelUUID: 57a35aad-4290-4b55-a0b2-150aad6da058
        vfModuleModelVersion: '0.0'
      properties:
        min_vf_module_instances: 0
        vf_module_label: helmB
        vf_module_type: Expansion
        isBase: false
        initial_count: 0
        volume_group: false
  substitution_mappings:
    node_type: org.openecomp.resource.vf.Asd1
    properties:
      nf_naming:
      - nf_naming
      skip_post_instantiation_configuration:
      - skip_post_instantiation_configuration
      multi_stage_design:
      - multi_stage_design
      nf_function:
      - nf_function
      nf_naming_code:
      - nf_naming_code
      controller_actor:
      - controller_actor
      availability_zone_max_count:
      - availability_zone_max_count
      sdnc_artifact_name:
      - sdnc_artifact_name
      max_instances:
      - max_instances
      nf_type:
      - nf_type
      sdnc_model_version:
      - sdnc_model_version
      nf_role:
      - nf_role
      min_instances:
      - min_instances
      sdnc_model_name:
      - sdnc_model_name

Create VF CSAR Create VF CSAR file thru the SDC Multi Model Way.       // Propose to use for the AS Package Onboarding

• TOSCA-Metadata
  • TOSCA.meta REQUIREMENT #<>: SDC generates TOSCA-Metadata directory and TOSCA.meta
• Definitions: REQUIREMENT #<>: for the Multi Model way, SDC does not use ONAP internal model. Note: impact to the existing ONAP components are under discussion.
•  
  • 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
  • resource-<...>-template.yml.       // REQUIREMENT #<>: SDC UI modifies onboarding ASD for changing the default values
  • resource-<...>-template-interface.yml.  // REQUIREMENT #<>: SDC UI modifies onboarding ASD for changing the default values.
• Artifacts
  • Deployment
    • AS_PACKAGE
      • AS_<...>DataTypes.csar
    • HELM
      • <HELM Chart file>
      • <HLEM Chart file>
    •  VENDORVENDOR_LICENSE
      • vendor-license-model.xml

...