Versions Compared

Old Version 21

changes.mady.by.user Zu Qiang (Ericsson)

Saved on

compared with

New Version 22

changes.mady.by.user Zu Qiang (Ericsson)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Package Requirements

In order to facilitate compatibility with ETSI, ONAP and other telco standards, the CSAR (NFV SOL 004ed431) packaging format is used The ASD onboarding package format is based ETSI NFV SOL 004ed431, with following details:  

  • 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.

  • 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

  • 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:

...