Page Comparison

General Information:

• Date and Time: 2021, April 19, 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://wikilf-onap.onapatlassian.orgnet/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://wikilf-onap.onapatlassian.orgnet/wiki/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://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=9301177216463007
      • 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://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Abstract+Topology+Model
    • discussion material: 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
      • it's proposed to continue the discussion in this call
    • Cagatay Buyukkoc
      • ORAN requirements on topology model, the background is to have different views (including logical views, deployment views, etc.) on how NF are/will be deployed
        • could be company specific
      • ORAN is discussing on developing a tool to transform IM into DM automatically
• 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: 

    Jira Legacy
    server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key ONAPMODEL-28

    • 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