Page History

In the TOSCA.meta, reuse the same metadata structure defined by TOSCA and ETSI

• TOSCA-Meta-File-Version:
• CSAR-Version:
• Created-By:
• Entry-Definitions:

In the TOSCA.meta, reuse the same ETSI defined Entry Keywords

• ETSI-Entry-Manifest:
• ETSI-Entry-Change-Log:                  // it optional
• ETSI-Entry-Licenses:                        // it is optional 
• ETSI-Entry-Tests:                              // it is optional 
• ETSI-Entry-Certificate:                     // it is optional

In the main manifest file, reuse the artifact security as defined by ETSI

• Source:
• Signature:                // for security option #1
• Certificate:               // for security option #1

For Jakarta PoC, ONAP shall support the security option #2. So, the App provider delivers one zip file consisting of the CSAR file, a signature file and a certificate file that includes the App provider public key.

-- AppPackage.zip

    –- AppPackage.csar

    –- AppPackage.csar signature

    –- Signing certificate

In the main manifest file non_mano_artifact_sets, reuse the same structure with the existing keywords defined by ONAP

• non_mano_artifact_sets:
  • onap_vest_events:
    • source:
  • onap_pm_directory:
    • source:
  • onap_yang_module:
    • source:
  • onap_others:
    • source:
    • source: