Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ONAP Release where the artifact ID is initially introducedNon-MANO artifact IDDescriptionNotes
 Dublinonap_ves_eventscontains VES registration files for handling external eventsSee the below example and clarifications in 5G - FM Meta Data / 5G - PM Dictionary

onap_pm_dictionarycontains the PM dictionary files used for Performance ManagementSee the usage in 5G - FM Meta Data / 5G - PM Dictionary

onap_yang_modulescontains Yang module files for configurations See the usage in 5G - Configuration with NETCONF

onap_ansible_playbookscontains any ansible playbooksSee the usage in 5G - PNF Software Update

onap_otherscontains any other non_MANO artifacts, e.g. informational documentsSee about its usage in 5G - PNF Pre-Onboarding & Onboarding
 Frankfurtonap_pnf_sw_information PNF software versionSee 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.