ONAP R3 Resource IM Call 2018-6-25

General Information:

• Date and Time: 2018, June 25, 9pm~10pm Beijing Time, 9am~10am US Eastern

• Meeting Room: https://zoom.us/j/645982535

Agenda:

• M1 Establish Model Plan

• Ongoing discussions

  • deprecate/obsolete attributes and datatypes

  • scaling

  • comparison with IFA spec

  • run time model

Material:

• Beijing F2F materials

  • resource information model overview and R3 plan (used to discuss the M1 model plan in this call)

  • resource information mode ongoing discussion overview (used to discuss deprecate/obsolete issue in this call)

• scaling

  • SOL001 updates and key points June19_ONAP

  • Proposed Scaling Related Class/Datatypes

• comparison with IFA spec

  • Comparison of Current R3 Clean Version with IFA011 v2.5.1

• run time model

  • VnfInstance & VnfcInstance

Minutes:

• M1 Establish Model Plan

  • List of interested topics for R3, and people who would like to contribute

    • run time model (e.g., VNF instance model): Kevin

      • need to check with DM team about their plan

    • WAN/VPN connections: Xu

    • PNF design time model: Thinh, reference IFA014 as a starting point

    • container/split VDU: Alex

    • hardware acceleration

      • need to check with 5G use case

      • seems like a stretch goal

    • scaling: discussion ongoing

    • monitoring/events: Fred/Alex, Kevin

    • define datatype/KVP values for attributes which are not clearly defined in the current VNFD model: Alex/Thinh for HPA related ones

    • element group enhancement: Kevin?

    • feedback from ETSI spec updates: discussion ongoing

    • format enhancement of the current VNFD model: discussion going

• Ongoing discussions

  • deprecate/obsolete attributes and datatypes

    • 3 comments received, discussed online and need further check with Jessie (on the mailing list/wiki). If all comments are addressed, would ask for approval on the modeling subcommittee

    • comments:

      • agree on use of "lifecycle" stereotype in the "applied stereotype" column

        • agreed

      • agree on whole "lifecycle", not solely "obsolete"

        • suggest to discuss as a seperate topic

      • the model should first go into "deprecate" stage before "obsolete", which means the model will stay at least two releases before removed

        • agreed

  • scaling

    • Thinh introduces the latest feedback from ETSI (SOL001 updates and key points June19_ONAP)

    • ETSI has decided to remove "element group" concept, Kevin/Andy has different opinions, need further discussion

  • comparison with IFA spec

    • no time for discussion

  • run time model

    • Kevin introduces the draft contribution

    • continue discussion next week