Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


New in Frankfurt Release for OnBoarding PNF package. The propsoal is APPROVED on ONAP TSC 2019-10-24

...

...

  • .
    • The next step to get a poll for
    following
    • 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
          • information:  
        •  Get approved for non-MANO artifact key word, file format and key words in .yaml file as below red font.
          • pnf_software_version:  ”5gDUv18.05.201”
    • On ONAP Modeling Sub-committee meeting on 2019-10-15, get the approved for above proposal with voting result.
    • On TSC 2019-10-24 meeting for voting, the final approved in ONAP. Good news!!!
      • The next step to register such keyname in IANA/ETSI.

    Material:

    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.

    Image Added