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.
...
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_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
FILE DIRECTORY — Need to be discussed, which option is better?
onap_nf_information
pnf_sw_version file / PNF information file (name ?)
vnf_info....
...
2) we define one directory for each file
FILE NAME
PNF_information ? /pnf_sw_version file?
FILE FORMAT
The file is a yml file
pnf_information.yaml
{
pnf_sw_version: type
}
pnf_software_version.yaml
{
description: PNF software version
parameters:
pnf-sw_version:
type: string
default: ” 5gDUv18.05.201”
}
an example. of the file attached (PNF infor file).......
...