...
All the artifacts are optional in the onboarding package.
In Dublin and El Alto following NON-ETSI-MANO artifacts are supported in ONAP:
1) VES dictionary
2) PM dictionary
3) YANG module files
4) Ansible files
5) information documents provided in the onap_others set identifier
In Frankfurt, following NON-ETSI-MANO artifacts are expected to be supported in ONAP
1) VES dictionary
2) PM dictionary
3) YANG module files
4) Ansible files
5) information documents provided in the onap_others set identifier
6) PNF software information file
According to ETSI SOL004, every NON-ETSI-MANO artifact set shall be identified by a NON-ETSI-MANO artifact set identifier (TAG) which shall be registered in the ETSI registry.
The Set identifiers can be public or private. ONAP as a public community initiative decided to introduce a set of public identifiers. The following page lists the registered ONAP set identifiers in ETSI registry.
ONAP Non-MANO Artifacts Set Identifiers
NON-ETSI-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).
In Dublin and El Alto following NON-ETSI-MANO artifacts are supported in ONAP:
1) VES dictionary
2) PM dictionary
3) YANG module files
4) Ansible files
5) information documents provided in the onap_others set identifier
In Frankfurt, following NON-ETSI-MANO artifacts are expected to be supported in ONAP
1) VES dictionary
2) PM dictionary
3) YANG module files
4) Ansible files
5) information documents provided in the onap_others set identifier
6) PNF software information file
ONAP PUBLIC NON-MANO ARTIFACTS SET APPROVED by ONAP TSC for REGISTRATION in ETSI
...