Note: the page is on-going contracted and finalized information shall be updated
...
onap_ves_events: contains VES registration files
onap_pm_dictionary: contains the PM dictionary files (file names are not defined in ONAP)
onap_yang_modules: contains Yang module files for configurations (file names are not defined in ONAP)
onap_ansible_playbooks: contains any ansible_playbooks (file names are not defined in ONAP)
onap_others: contains any other non_MANO artifacts, e.g. informational documents
- onap_pnf_sw_information: contains PNF software related information. In Frankfurt, it contains a new file for PNF software information
...
4) create a csar package file example aligned to Frankfurt release to be added in this page(UPDATE IT LATERdummyPnfv3.csar )
5) Is CMCC going to test Onboarding Package for VNF in ElAlto ? Can we extend the onboarding package support to VNF ? (Jira ticket: SDC-2072)
...
1) Only csar package structure with TOSCA-Metadata directory will be supported in Dublin Frankfurt timeframe
2) PM Dictionary, Event registration, Yang modules and PNF software information are the only NON MANO ARTIFACTS that will be listed in the manifest file
...
4) Example package above does not include any certification file or other security options.During the 2019-01-18 VNFPKG meeting we agreed to evaluate further the introduction of public identifiers to be approved in ETSI for ONAP.
Example Signed Packages
Here are two example signed packages. The packages are signed according to security option 2 in ETSI SOL004. The two file package has the signing certificate in the cryptographic message syntax. The three file has the certificate in a separate file and not in the cryptographic syntax.
...
- get a poll for non-MANO artifact for pnf software version proposal in PNF Software Version in PNF upgrade on ONAP Frankfurt ReleaseTO BE UPDATED — Done
- Update example PNF CSAR file ---Done