/
ONAP R9 Resource IM Call 2021-6-28

ONAP R9 Resource IM Call 2021-6-28

Owned by Xu Yang
Last updated: Jun 28, 2021
3 min read

General Information:

  • Date and Time: 2021, June 28, 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

      • R9 DM proposal: https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16463007

        • aligned with SOL001 v4.2.1, package format is still under discussion

        • will ask for approval after SOL001 v4.2.1 is stable

      • a proposal of updating the information model documentation is planned in R9

      • Updates：

        • SOL001 is delayed and expected to be stable at the end of July

        • Fred is preparing the IM updates aligning with the latest DM proposal, hope to be discussed next Monday

        • the alternative approach (ASD) is still under discussion, a concrete decision is still needed

    • 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 next week

          • 2 approaches: 1) create an abstract model capturing the current proposal; 2) wait till the A&AI schema to update, and create the IM through reverse engineering

          • Xu will help create the initial draft for discussion

    • 5G service / CPS model

    • PNF instance model

    • 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