ONAP R3 Resource IM Call 2018-9-10

General Information:

Agenda:

  • NSD papyrus model status

  • PNFD R3 implementation status

  • Performance Measurement model

Material:

Minutes:

  • NSD papyrus model status

    • currently having a model conflict for papyrus

    • need to address the conflict this week to move forward

      • continue discussion on Wednesday call (same time slot as this call, https://zoom.us/j/4996638718)

      • Kevin would send email notifications on the mailing list

      • 2 recommended options on the table, and could have more

      • suggest to move NSD into an independent model domain

      • encourage people who are interested in contributing papyrus to attend the meeting and negotiate before actually contributing

  • PNFD R3 implementation status

    • current SDC weekly call is conflict with Modeling subcommittee call

    • R3 introduces "software_version" into the PNFD model

    • plan to introduce more concepts in R4+, e.g., sub-components; and plan to define a "software" object in R4+

    • PNFD is for onboarding, PNF model is for SDC design; some of the attributes are not included in PNF model because ONAP has different structures to describe them (e.g., geographic location)

  • Performance Measurement model

    • PM dictionary is proposed to be recorded in a yaml file and applied to VNF/PNFs; the yaml file is onboarded to ONAP, and used by SDC, DCAE, etc.

    • measType, measInfoId and measFamily can be 3GPP defined names or vendor specific names; and have corresponding interger identifiers (unique to a type of NF) to be used in GPB for efficiency

    • relationship to VES event: the events would include the measurements; seperate spec from VES measurement domain, the scope is 3GPP defined/related performance measurements

Video and Audio:

audio

video