...
The ASD onboarding package format is based ETSI NFV SOL 004ed431on the TOSCA CSAR with TOSCA-Metadata directory format, with the following detailsadditional:
The structure and format of an ASD package shall conform to the TOSCA Simple Profile YAML v1.1 or v1.3 Specification of the CSAR format, as specified in ETSI NFV SOL004ed431 section 4.1.1. The zip file format shall conform to Document Container Format File.
- An ASD onboard package shall contain a main TOSCA definitions YAML file representing all or part of the ASD, manifest file, artifact files, and additional files.
- 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
NonSupport non-MANO artifact sets description in the manifest file, as specified in ETSI NFV-SOL004ed431 section clause 4.3.7
Registered non-MANO artifact keywords (ONAP Non-MANO Artifacts Set Identifiers) 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 with the exception that table 4.3.2-1 (the valid names and values) is replaced with 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., application_name in ASD | O |
application_provider | A sequence of UTF-8 characters. | The value shall be identical to those specified in the MainServiceDescriptor, e.g., provider 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 |
...