Page History

...

The following describes the App package structure.

Note: blue directory names and file type suffixes are requested by SOL004

REQUIREMENT #<2>: ASD_1_0_types.yaml will represent Application Service Descriptor (ASD) in TOSCA

...

!------TOSCA.meta.sig.cms

!------Definitions

!----- MRF.yaml.   (main App yaml)

...

• • REQUIREMENT <3>: introduce the following metadata for App package. By using the new metadata, SDC and orchestrator know this package is based on ASD 
    • asd_id
    • app_provider_id
    • app_product_name
    • app_release_date_time
    • app_software_version
    • app_package_version
    • compatible_specification_versions
    • cnfm_info

• • • e.g., app_main_descripter.mf

...

compatible_specification_versions: 1.0.0

cnfm_info: cnfm:v1.0.0

• • Define Source paths: 
    • Source: ChangeLog
    • Source: Definitions
    • Source: Images
    • Source: Artifacts
    • Source: LcmScripts
    • Source: License
    • Source: TOSCA-Metadata
  • non-MANO-Artifacts
    • include HELM files ?

• TOSCA-Metadata directory: It contains the entry points:

<ETSI keynames extension>

• • TOSCA.meta
    • ASDREQUIREMENT #<4>: introduce a new key name to metadata, "for ASD, use only ETSI-Entry-Definitions"
      • note: we are evaluating the above manifest metadata is enough to distinguish the app package model from other models.
      Manifest

e.g.,

TOSCA-Meta-File-Version: 1.0

...

Entry-Definitions: Definitions/main_app_template.yamlASD-Entry-Definitions: Definitions/main_app_template.yaml     

ETSI-Entry-Manifest: app_main_descripter.mf

ETSI-Entry-Licenses: Licenses

ETSI-Entry-Change-Log: ChangeLog.txt

• Definitions
  
  • ASD_1_0_types.yaml                        // node_types, artifact_types, data_types
  • main_app_template.yaml.               // descriptor leveraging ASD

...