...
The following table contains the public non-MANO artifact set identifiers which can be used in a PNF/VNF onboarding package per ONAP releases. The relevant examples of using the artifact tags are following the table
| ONAP Release where the artifact ID is initially introduced | Non-MANO artifact ID | Description |
|---|
Reference ( R-146092) (“The published version link shall be updated after Frankfurt release”) | Notes | |
|---|---|---|
| Dublin | onap_ves_events | contains VES registration files for handling external events |
The latest requirements: | 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 |
The latest requirements: | See the usage in 5G - FM Meta Data / 5G - PM Dictionary | |
| onap_yang_modules | contains Yang module files for configurations |
The latest requirements: | See the usage in 5G - Configuration with NETCONF | |
| onap_ansible_playbooks | contains any ansible playbooks |
The latest requirements: | See the usage in 5G - PNF Software Update | |
| onap_others | contains any other non_MANO artifacts, e.g. informational documents |
| none | See about its usage in 5G - PNF Pre-Onboarding & Onboarding | |
| Frankfurt | onap_pnf_sw_information | PNF software version |
The latest requirements: | See about its usage in |
EXAMPLES:
Example 1 (Dublin Release)
...