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 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.
- New no-MANO artifacts for PNF Software version is proposed and discussed on the ONAP R4 Resource IM Call 2019-6-17 AND get the agreement 'The option 1 is preferred in Frankfurt Release and going for a poll on modeling subcommittee call'
CSAR structure
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
onap_yang_modules: contains Yang module files for configurations
onap_ansible_playbooks: contains any ansible_playbooks
- 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 PNF Software Version file
...