...
The scope of this page is to define the Onboarding package for a PNF as well as non-MANO artifact specification to be registered with ETSI on ONAP Frankfurt Release. The
Comparing to PNF On-boarding on R4 Dublin Release, the updated information is marked as light blue comparing to R4 Dublin Release.
Note: the page is on-going contracted and finalized information might be updated
...
New in Frankfurt Release for OnBoarding PNF package.
- A new non-MANO artifact for called PNF Software version is proposed and discussed on the ONAP R4 Resource IM Call 2019-6-17 AND get the following agreement
- 'The option 1 is preferred in Frankfurt Release and going for a poll on modeling subcommittee call' (details will be described in this page).
CSAR structure
TOSCA YAML CSAR file is an archive file using the ZIP file format. Two CSAR structures are defined in ETSI SOL004.
...
Option 1) is the unique option supported in ONAP from Dublin.
META FILE AND MANIFEST FILE
...
2) identify the path of the NON ETSI MANO artifacts (as defined in ETSI SOL004), by the .mf file.
NON ETSI MANO ARTIFACTS
Non NON-ETSI-MANO artifacts Artifacts in the onbarding package are provided by the vendor. They provide information that may enable additional functionalities in ONAP.
All the artifacts are optional in the onboarding package.
In Dublin and El Alto following NON-ETSI-MANO artifacts are supported in ONAP:
...
5) information documents provided in the onap_others set identifier
In Frankfurt, following NON-ETSI-MANO artifacts are expected to be supported in ONAP
...
5) information documents
6) PNF information file
According to ETSI SOL004, every nonNON-ETSI-MANO artifact set shall be identified by a nona NON-ETSI-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.
NonNON-ETSI-MANO artifact 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.
...
onap_ves_events: contains VES registration files
onap_pm_dictionary: contains the PM dictionary files files (file names are not defined in ONAP)
onap_yang_modules: contains Yang module files for configurations (file names are not defined in ONAP)
onap_ansible_playbooks: contains any ansible_playbooks (file names are not defined in ONAP)
onap_scripts: contains any scripts, e.g. installation scripts (NOT REQUIRED IN DUBLIN TIMEFRAME BUT MAY BE REGISTERED LATER)onap_others: contains any other non_MANO artifacts, e.g. informational documents
- onap_nf_information: contains NF(Network Function) related information. e.g. PNF, VNF or xNF itself information. In Frankfurt, it contains a new file for PNF information
...