ONAP R8 Resource IM Call 2021-4-12

General Information:

• Date and Time: 2021, April 12, 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 - 20 minutes
• Modeling Documentation - 0 minutes

Material:

• Model proposals:
  • Support for CPS Model Driven PoC R8+
  • Abstract Topology Model
• Modeling requirements:
  • https://wiki.onap.org/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

Minutes:

• Agenda bashing
  • reminder for filling R9 high level requirements: https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
    
    • Ben would like the modeling team to join the use case realization call on May 3, to discuss the modeling high level reqs
• 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
    • 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://wiki.onap.org/display/DW/Abstract+Topology+Model
• 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 - Getting issue details... STATUS
    • 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