/
ONAP R9 Resource IM Call 2021-7-5

ONAP R9 Resource IM Call 2021-7-5

General Information:

  • Date and Time: 2021, July 5, 9pm~10pm Beijing Time, 9am~10am US Eastern

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

  • Meeting Recording:  

  • Meeting Chat Log:  

Agenda:

  • Agenda bashing - 5 minutes

  • Model Proposals

    • ETSI CNF support - ? minutes

    • CNF runtime model - 10 minutes

    • PNF instance model - ? minutes

    • CPS model - 0 minutes

    • Topology model - 0 minutes

  • Modeling Documentation - 0 minutes

Material:

Minutes:

  • Agenda bashing

  • Model Proposals

    • ETSI support for CNF model

    • CNF runtime model

      • Proposal:

        • for Istanbul: add some necessary information as an enhancement of vf-module, to allow components to query k8s objects

        • for Jarkata: define a cnf-module, to store information like compute (pod), storage, etc.

        • the two sub-proposals can co-exist

      • Update:

      • AP:

        • will continue how to document the information model: Simplified K8S Resource Model - IM

        • question:

          • 1) need to create empty classes for "tenant", "vnf-module", etc.? A: will keep the comments as for now, and Jacqueline will help reverse-engineer the related classes

          • 2) whether the attribute definitions are acceptable? A: need further check, and needs double check with the model owner on "version", "group" descriptions.

    • 5G service / CPS model

    • PNF instance model

      • reverse engineering

      • migrating to new version

        • Jacqueline has done the experiment of creating gendocs using two different versions of eclipse

          • the gendoc of the new version seems fine, but the gendoc of the old version breaks (missing parent class information)

        • AP:

          • Xu will try to experiment the same things as well, and discuss again next week

    • Topology model

      • Proposal: https://lf-onap.atlassian.net/wiki/display/DW/Abstract+Topology+Model

        • Martin will update the models with the IM sketch

      • Model Sketch: https://wiki.onap.org/display/DW/Proposed+Topology+IM+Sketch

      • Andy has helped to create a high level requirement for the topology model

        • expecting ORAN to provide relavent use cases

        • Martin and Andy are aware of the different views of topology model presented last week by Cagatay

        • mainly triggered by ORAN WG10, also related to WG1's slicing use case, etc.

        • how to model different layers, physical, logical topology, etc.? current methodology is using UML/papyrus to capture the models

      • Latest updates:

        • Adding concepts like clients and servers, further discussion are needed to for the context of the new terms

        • also whether the whole objects should be put under "ManagedFunction" needs further discussion

  • Modeling Documentation