The scope of this page is to maintain the approved list of ONAP specific non-MANO artifact set identifiers. This page is required to be long-live.
...
| ONAP Release where the artifact ID is initially introduced | Non-MANO artifact ID | Description | Notes |
|---|---|---|---|
| Dublin | onap_ves_events | contains VES registration files for handling external events | See the below example and clarifications in 5G - FM Meta Data / 5G - PM Dictionary |
| onap_pm_dictionary | contains the PM dictionary files used for Performance Management | See the usage in 5G - FM Meta Data / 5G - PM Dictionary | |
| onap_yang_modules | contains Yang module files for configurations | See the usage in 5G - Configuration with NETCONF | |
| onap_ansible_playbooks | contains any ansible playbooks | See the usage in 5G - PNF Software Update | |
| onap_others | contains any other non_MANO artifacts, e.g. informational documents | See about its usage in 5G - PNF Pre-Onboarding & Onboarding | |
| Frankfurt | onap_pnf_sw_information | PNF software version | See about its usage in ONAP R6+ Onboarding VNF/PNF package format, non-MANO artifacts set definition |
EXAMPLES:
Example 1 (Dublin Release)
In the picture below, an example of a PNF onboarding package including a manifest file with URI's for non-MANO artifacts used in Dublin
...
4) Example package above does not include any certification file or other security options.
Example 2 (Frankfurt Release)
In the picture below, an example of a PNF onboarding package including a manifest file with URI's for non-MANO artifacts used in Frankfurt
TBA picture
A reference PNF CSAR PACKAGE as example is available dummyPnfv3.csar (TBD) to review directories structure and new .meta and .mf files format.