...
TASK #<2>: ASD_1_0_types.yaml will represent Application Service Descriptor (ASD) in TOSCA
!----- MRF<MRF>.mf // main manifest file
...
- TASK #<3>: The App package shall introduce the following metadata to define the package type/model.
- TASK #<4>: SDC shall detect the asd/app oran_entry_defintion_type="asd" metadata and process the Application package onboarding path.
- Note: metadata candidates. To be finalized (asd, app?? or else)
app_id.app_provider_idapp_product_nameapp_release_date_timeapp_software_versionapp_package_version- oran_id
- oran_product_name
- oran_provider_id
- oran_package_version
- oran_release_date_time
- oran_entry_definition_type. [ "asd", "app", "app-asd", ... ]
- e.g., app_main_descripter.mf
metadata:
asd_id: 2116fd24-83f2-416b-bf3c-ca1964793bcf
app_provider_id: <vendorA>
app_product_name: vFW
app_release_date_time: 2021-10-18T10:00:00+03:00
app_software_version: 1.0.0
app_package_version: 1.0
oran_id: 2116fd24-83f2-416b-bf3c-ca1964793bcf
oran_product_name: vFW
oran_provider_id: vendorA
oran_package_version: 1.0
oran_release_date_time: 2021-10-18T10:00:00+03:00
oran_entry_definition_type: asd
- Define Source paths:
- Source: ChangeLog
- Source: Definitions/main_app_template.yaml
- Source: Definitions/oran_asd_types.yaml
- Source: Definitions/oran_asd_types.sig.cms
- Source: ChangeLog
- Source: Definitions
- Source: Images
- Source: Artifacts
- Source: LcmScripts
- Source: License
- Source: TOSCA-Metadata
- Define Source paths:
...
note: for ASD, we don't need to use all the following entries. SDC does not copy most of the keynames, except ETSI-Entry-Manifest for validation.
note: in ETSI NFV, making the ETSI-Entry-Lincense optional is under discussion.
- TOSCA.meta
- TASK #<4>: for ASD, SDC use the same metadata structure defined by TOSCA and SOL004, plus use only ETSI-Entry-Manifest from the above list
- TOSCA-Meta-File-Version
- CSAR-Version
- Created-By
- Entry-Definitions
- TASK #<4>: for ASD, SDC use the same metadata structure defined by TOSCA and SOL004, plus use only ETSI-Entry-Manifest from the above list
- TOSCA.meta
plus
- ETSI-Entry-Manifest
e.g.,
TOSCA-Meta-File-Version: 1.0
CSAR-Version: 1.1
Created-By: <vendor>vendorA
Entry-Definitions: Definitions/main_app_template.yaml
ETSI-Entry-Manifest: app_main_descripter.mfETSI-Entry-Licenses: Licenses
ETSI-Entry-Change-Log: ChangeLog.txt
...