Proposal for PNF software version in PNF upgrade in Frankfurt release

_{Further discussion for non-MANO artifact called PNF Software Version in PNF upgrade on ONAP Frankfurt Release  and got basic agreement on ONAP R6 Resource IM Call 2019-9-23.}

• _{On ONAP Modeling Sub-committee meeting on 2019-10-15, get the APPROVED for below proposal. The next step to get a poll for non-MANO artifact key word, file format and key words in .yaml file as below red font.}

  • _{onap_pnf_sw_information for non-MANO artifact Registered in ETSI&IANA}

  • _{.yaml format is proposed,} 

  • _{Key words in .yaml file}

    • _{pnf_ software_infomation:}  

    • _{- pnf_software_version:  ”5gDUv18.05.201”}

• The voting result on ONAP Modeling Sub-committee meeting on 2019-10-15 as below

  • Call for vote: PNF Software Version  (Fei Zhang )

    • See: Proposal for PNF software version in PNF upgrade in Frankfurt release
    • Results: YES: Ericsson, AT&T, Amdocs, Huawei, CMCC
    • Will share the recommendation with the ONAP TSC before forwarding registration request to ETSI.

Material:

• Software version

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. All the artifacts are optional in the onboarding package.

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

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.