In order to facilitate compatibility with ETSI, ONAP and other telco standards, the CSAR (NFV SOL 004ed421) packaging format is used with following details:
The structure and format of an ASD package shall conform to the TOSCA Simple Profile YAML v1.1 Specification of the CSAR format. The zip file format shall conform to Document Container Format File
- CSAR format with TOSCA-Metadata directory, specified in ETSI NFV SOL004ed431 section 4.1.2, with the differences that the following TOSCA.meta file keynames extensions are optional:
- ETSI-Entry-Change-Log
- ETSI-Entry-Tests
- ETSI-Entry-Licenses
Non-MANO artifact sets, specified in ETSI NFV SOL004ed431 section 4.3.7
Registered non-MANO artifact keywords can be reused, to avoid duplication
Package and artifacts security, specified in ETSI NFV SOL004 ed431 section 5 and 4.3.6
- Package manifest file, specified in ETSI NFV SOL004ed431 section 4.3.2, with new manifest metadata proposed in the following table:
Name | Value | Notes | Qualifier |
application_name | A sequence of UTF-8 characters. | The value shall be identical to those specified in the MainServiceDescriptor, e.g., asdApplicationName in ASD | O |
application_provider | A sequence of UTF-8 characters. | The value shall be identical to those specified in the MainServiceDescriptor, e.g., asdProvider in ASD | O |
release_date_time | A string formatted according to IETF RFC 3339 | Timestamp of the package release time | M |
entry_definition_type | enum[asd] | asd: only ASD is included in the package | M |
The following is an example of ASD metadata:
metadata:
application_name: vCU
application_provider: Ericsson
release_date_time: 2021-10-21T11:30:00+05:00
entry_definition_type: asd
The following is an example of an ASD onboarding package :
Working/discussion material: