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.
...
GENERAL
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 wiki https://nfvwiki.etsi.org/index.php?title=Non_MANO_artifact_sets.
Set identifiers can be public or private. ONAP as a public community initiative decided to introduce a set of public identifiers.
Non-MANO artifact sets shall be declared in the manifest file. If the package contains at least one non-MANO artifact set, an entry named "non_mano_artifact_sets:" shall be present in the package on the manifest file on its own line after the "metadata" section.
...
| 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 |
| onap_pm_dictionary | contains the PM dictionary files used for Performance Management | ||
| onap_yang_modules | contains Yang module files for configurations | ||
| onap_ansible_playbooks | contains any ansible playbooks | ||
| onap_others | contains any other non_MANO artifacts, e.g. informational documents |
...