ONAP R8 Resource IM Call 2021-4-26

• Date and Time: 2021, April 26, 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
  
  

  • allotted resource - 0 minutes

  • 5G service - 0 minutes

  • ETSI CNF support - 0 minutes

  • PNF instance model - 0 minutes

  • CPS model - 0 minutes

  • Topology model - 0 minutes

• Modeling Documentation - 0 minutes

• Model proposals:

  • Support for CPS Model Driven PoC R8+

  • Abstract Topology Model

• Modeling requirements:

  • https://lf-onap.atlassian.net/wiki/display/DW/ONAP+R9+Modeling+High+Level+Requirements

• Related information:

  • Allotted Resource for Network Slicing

  • R8 5G Service Modeling

• Clean/Approved models:

  • ONAP Information Model - Clean and approved models across ONAP releases

• Agenda bashing

  • reminder for filling R9 high level requirements: https://lf-onap.atlassian.net/wiki/display/DW/ONAP+R9+Modeling+High+Level+Requirements
    
    

    • Ben will check with Alla and use case team to see May 10th is a proper time for the joint call between modeling team and use case realization team

  • will cancel next week's resource IM call

• 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

  • 5G service / CPS model

  • PNF instance model

    • reverse engineering

  • 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
      
      

      • inspired by TAPI model to add "link", "connection" classes

      • looking at ORAN use cases and see if the models can fulfill the requirements

      • TAPI presentation may be found here: otcc2019.KS.002_TAPI_Concepts_Topology_Connectivity.pptx

    • 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

• Modeling Documentation
  
  

  • R6 readthedocs review:

    • gendoc template improvement: ONAP Information Model - Gendoc Examples 

    • discussion whether the description only applies for a navigatable end of an association

      • continue discussion later

  • add relationship documentation to the UML guideline: ONAPMODEL-28: Using the Documentation Property for RelationshipsOpen

    • UML principle wiki page:

      • Principle and Guideline for Information Model Proposal Using Papyrus (Draft)

      • review the updates to the Gendoc requirements part

        • Michela suggest whether it's possible to add information of associations into the class definitions

          • Xu will investigate it offline

      • Using Papyrus for Modeling updates

        • suggest to further discuss the version recommended after Jacqueline come back