...
App Onboarding Package Requirement
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | REQ-1043 |
---|
|
Requirement | Description | Comments |
---|
R1 | In the TOSCA.meta, reuse the same metadata structure defined by TOSCA and ETSI - TOSCA-Meta-File-Version:
- CSAR-Version:
- Created-By:
- Entry-Definitions: // e.g., Definitions/asd.yml
|
|
R2 | In the TOSCA.meta, reuse the same ETSI defined Entry Keywords - ETSI-Entry-Manifest: // e.g., asd.mf
- ETSI-Entry-Change-Log: // it Is optional for ASD
- ETSI-Entry-Licenses: // it is optional for ASD
- ETSI-Entry-Tests: // it is optional for ASD
- ETSI-Entry-Certificate: // it is optional for ASD
|
|
R3 | In the main manifest file, reuse the metadata structure defined by ETSI with new keywords Note: the following proposal is under discussion - application_name: // e.g., vCU
- application_provider: // e.g., Ericsson
- release_date_time: // e.g., 2021-10-21T11:30:00+05:00
- entry_definition_type: [asd]
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 |
Note: there could be additional optional keywords. |
|
R4 | 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 |
|
R5 | 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:
- onap_pm_directory:
- onap_yang_module:
- onap_others:
|
|
...