Page Comparison

General Information:

• Date and Time: 2021, March 1st, 9pm~10pm Beijing Time, 8am~9am 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 - 5 minutes
  • PNF instance model - 0 minutes
  • CPS model - 0 minutes
  • Topology model - 20 minutes
• Modeling Documentation - 0 minutes

...

• Agenda bashing
  • APs from previous meetings:
    • Jacqueline to submit papyrus changes for the approved location model and CPS model: done
    • Ben to submit papyrus changes for VES 7.2
      • Jacqueline's solution to the account issue: Using Papyrus for Modeling, First-time Setup section
• Model Proposals
  
  • allotted resource
    • service model discussion has concluded, the discussion can be resumed
  • ETSI support for CNF model
    • related DM model: VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements
      • updates:
        • Thinh has proposed a slight different packaging solutions in the CNF taskforce call, will present the details next week
        • hope the discussion with SOL WG can be finalized this Thursday
      • the time conflict issue (of CNF taskforce call and modeling subcommittee call) will be discussed tomorrow
  • 5G service / CPS model
  • PNF instance model
  • Topology model
    • Martin gives a brief presentation on abstract topology model: https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Abstract+Topology+Model
    • ORAN meeting has started to investigate TAPI / ONAP transport API
    • call info: https://lists.onap.org/g/onap-modelingsub/topic/abstract_topology_model/80876474?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80876474
      • today, 16:00 UTC
• R9 planning
  • Andy will help create the Istanbul Release modeling requirements page, and discuss tomorrow on modeling subcommittee call
  • Ben suggest people can also go to share requirements on requirement subcommittee call
• 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