...
- 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).
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 in Dublin, EL-ALTO and Frankfurt.
META FILE AND MANIFEST FILE
The use of the TOSCA.meta and the Manifest file (.mf) in line with ETSI SOL004 will help to:
...
2) identify the path of the NON ETSI MANO artifacts (as defined in ETSI SOL004), by the .mf file.
NON ETSI MANO ARTIFACTS
NON-ETSI-MANO Artifacts in the onbarding package are provided by the vendor. They provide information that may enable additional functionalities in ONAP.
...
4) Ansible files
5) information documents documents provided in the onap_others set identifier
6) PNF 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).
ONAP PUBLIC NON-MANO ARTIFACTS SET APPROVED by ONAP TSC for REGISTRATION in ETSI
The followings are the public non-MANO artifact set identifiers which can be used in a PNF/VNF onboarding package.
...
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?
NON-MANO Artifact Set Identifier name
onap_nf_information pnf_sw_version file / PNF information file (name ?)
vnf_info....
Two options:
1) we define a single onap nf info directory with different files (i.e pnf specific info, vnf specific info, xnf specific 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”
}
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
An an example. of the file attached (PNF infor file).......Update it later
NEXT STEPS IN FRANKFURT TIMEFRAME
1) In FRANKFURT timeframe SDC is going to implement the PNF package onboarding in line with the agreed non-MANO artifact set identifiers. (JIRA TICKET)
2) Register the NON-MANO artifact set identifiers in ETSI and update the reference ONAP page (add the reference).
3) Document the ONAP non-MANO artifact set identifiers in the VNF RQT as new ONAP requirements.(JIRA TICKET)
4) create a csar package file example aligned to Frankfurt release to be added in this page(UPDATE IT LATER)
5) Is CMCC going to test Onboarding Package for VNF in ElAlto ? Can we extend the onboarding package support to VNF ? (Jira ticket ?: SDC-2072)
PNF ONBOARDING PACKAGE EXAMPLE WITH USING NON-MANO ARTIFACTS in FRANKFURT
In the picture below, an example of a PNF onboarding package including a manifest file with URI's for non-MANO artifacts used in Frankfurt
...
During the 2019-01-18 VNFPKG meeting we agreed to evaluate further the introduction of public identifiers to be approved in ETSI for ONAP.
Example Signed Packages
Here are two example signed packages. The packages are signed according to security option 2 in ETSI SOL004. The two file package has the signing certificate in the cryptographic message syntax. The three file has the certificate in a separate file and not in the cryptographic syntax.
...
Files related to example signed packages here
ACTIONS
TO BE UPDATED