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.
The ONAP TSC is the organization that owns the non-MANO artifacts set. The ONAP official contact is onap-tsc@lists.onap.org
The editing of this page is limited to Michela Bevilacqua and andreik
META FILE AND MANIFEST FILE
The use of the TOSCA.meta and the Manifest file (.mf) in line with ETSI SOL004 will help to:
1) identify the path of the ETSI MANO artifacts (by the .meta file)
2) identify the path of the NON ETSI MANO artifacts (as defined in ETSI SOL004), by the .mf file.
According to ETSI SOL004, every non-MANO artifact set shall be identified by a non-MANO artifact set identifier (TAG) which shall be registered in the ETSI registry.
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 its own line after the "metadata" section.
All files belonging to the same non MANO artifact set shall share a common path prefix (e.g. multiple yang module files will share the same set identifiers).
ONAP PUBLIC NON-MANO ARTIFACTS SET APPROVED by ONAP TSC for REGISTRATION in ETSI
The followings are the public non-MANO artifact set identifiers which can be used in a PNF/VNF onboarding package.
The introduction in the manifest file allow to isolate the ONAP specific topics as follows:
onap_ves_events: contains VES registration files
onap_pm_dictionary: contains the PM dictionary files
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