Versions Compared

Key

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

...

According to ETSI SOL004 v.2.5.1, every non-MANO artifact set shall be identified by a non-MANO artifact set identifier (TAG) which shall be registered in the ETSI registry. The registration process including creation of the registration template is described in the

ETSI registry of non MANO artifact set identifier is available in ETSI wiki https://nfvwiki.etsi.org/index.php?title=Non_MANO_artifact_sets.

...

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 introducedNon-MANO artifact IDDescription

Reference ( R-146092 )

(“The published version link shall be updated after Frankfurt release”)

Notes
 Dublinonap_ves_eventscontains VES registration files for handling external events

The latest requirements:

R-22346

R-025941

See the below example and clarifications in 5G - FM Meta Data / 5G - PM Dictionary

onap_pm_dictionarycontains the PM dictionary files used for Performance Management

The latest requirements: 

R-816745

See the usage in 5G - FM Meta Data / 5G - PM Dictionary

onap_yang_modulescontains Yang module files for configurations 

The latest requirements:

R-93443

R-26115

See the usage in 5G - Configuration with NETCONF

onap_ansible_playbookscontains any ansible playbooks

The latest requirements:

R-75608

See the usage in 5G - PNF Software Update

onap_otherscontains any other non_MANO artifacts, e.g. informational documentsnoneSee about its usage in 5G - PNF Pre-Onboarding & Onboarding
 Frankfurtonap_pnf_sw_information PNF software version

The latest requirements:

R-972082

See about its usage in

Enable Service Level LCM Operations


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


Image Modified

NOTES about the example: Folder/file name MANDATORY according to  SOL004:

...

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

Image Added

A reference PNF CSAR PACKAGE as example is available dummyPnfv3.csar (TBD) to review directories structure and new .meta and .mf files format.