Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

General Information:

  • Date and Time: 2021, June 21, 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 - 20 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://wiki.onap.org/pages/viewpage.action?pageId=93011772
        • 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
      • latest updates:
        • Thinh has presented the alternative package solution in the CNF taskforce call, could be discussed in future calls
        • CNF requirements collaboration pending discussions as well, could be discussed in this week's CNF taskforce call
      • plan to have a conclusion next Monday, and then share to modeling team
        • current gap is that whether NFVO needs to understand the helm chart, and whether ASD can be totally non-overlap with helm chart
    • 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:
        • the idea is to capture the basic information from k8s
        • the proposal has been presented to the A&AI team, and no major concerns
      • Questions:
        • if A&AI team can support modification of existing models (in case in later release, ETSI alignment team/ETSI standard identified changes needed for the runtime model), Lukasz will help check with A&AI PTL
        • align with ETSI alignment team
    • 5G service / CPS model
    • PNF instance model
    • Topology model
      • Proposal: https://wiki.onap.org/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:
        • Andy has updated the diagram to better align with the TAPI names
  • Modeling Documentation
  • No labels