...
...
Note: the page is on-going contracted and finalized information shall be updated
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.
Comparing to PNF On-boarding on R4 Dublin Release, the updated information is marked as light blue.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 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).
This page is covering ETSI SOL004 Package on-boarding option with ETSI SOL001 TOSCA VNF/PNF Descriptor.
Other on-boarding package options are not covered, e.g. HEAT, TOSCA VNFD in NON-ETSI compliant package.
CSAR structure on SDC
TOSCA YAML CSAR file is an archive file using the ZIP file format. Two CSAR structures are defined in ETSI SOL004.
...
onap_ves_events: contains VES registration files
onap_pm_dictionary: contains the PM dictionary 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_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
...