ONAP R8 Resource IM Call 2021-3-29

• Date and Time: 2021, March 29th, 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 - 20 minutes

  • PNF instance model - 0 minutes

  • CPS model - 0 minutes

  • Topology model - 20 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

    • still empty

    • Ben would like the modeling team to join the use case realization call on May 3, to discuss the modeling high level reqs

  • service IM call proposal:

    • Chuyi is suggesting to merge service IM call with resource IM call or modeling subcommittee call, due to lack of topics

    • will raise and discuss the topic tomorrow

    • Xu: fine for merging with resource IM call, but afraid that may limit the time of individual topics' discussion; prefer new service model proposal be raised in modeling subcommittee call first, and then decide whether to discuss in Monday call or in a seperate/dedicated 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

    • information model is planned to have an update in R9

    • lack resources, no code implementation plan for Istanbul release

    • for backward compatibility, possibly only support v2.4.1 and v2.7.1 in the future

  • 5G service / CPS model

  • PNF instance model

    • reverse engineering

  • Topology model

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

    • call information: https://lists.onap.org/g/onap-modelingsub/topic/abstract_topology_model/80876474?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80876474

      • today, 15:00 UTC

      • it's proposed to have a general call for the topic, time and place TBD, may be at use case or resource IM call

    • ORAN alliance issues will be presented

    • has discussed several use cases, and working on basic concepts

• 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