Page Comparison

General Information:

• Date and Time: 2021, March 15th, 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 - 20 minutes
  • PNF instance model - 0 minutes
  • CPS model - 0 minutes
  • Topology model - 20 minutes
• Modeling Documentation - 0 minutes

...

• Model proposals:
  • Allotted Resource Revised
    • comments: Allotted Resource Model Review Comments
  • Support for CPS Model Driven PoC R8+
  • Abstract Topology Model
• Modeling requirements:
  • ONAP R8 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
  Model Proposals
  
  • allotted resource
    • service model discussion has concluded, the discussion can be resumed
  • reminder for filling R9 high level requirements: https://lf-onap.atlassian.net/wiki/display/DW/ONAP+R9+Modeling+High+Level+Requirements
  • Model Proposals
    
    • ETSI support for CNF model
      • related R9 DM modelproposal: VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancementshttps://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16463007
      • aligned with SOL001 v4.2.1
        • question about version alignment: IM aligned with v4.1.1, DM aligned with v4.2.1, shall the IM be revisited?
        • the answer is yes, but the changes are very minor for the time being
      • no major structure change for the VNFD compared to previous DM proposal
        • MciopProfile renamed to Mciop, now a dedicated node type under VNF, still reference Helm Chart
        • OsContainerGroup renamed to OsContainerDeployableUnit, stands for a Pod, and still reference to individual OsContainer(s)
        • no changes for VirtualCp node type
        • minor changes for node and data type definitions
        • TOSCA example will be available on the wiki page later
      • package format
        • use non-MANO artifact to describe Helm Charts
        • discussion is still ongoing
    • 5G service / CPS model
    • PNF instance model
    • Topology model
      • Proposal: https://wikilf-onap.onapatlassian.orgnet/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, 1615:00 UTC (1 hour earlier than last week)
      • investigating whether can reuse the TAPI (ONAP transport API) topology model
        • TAPI: https://wiki.opennetworking.org/display/OTCC/TAPI 
        • YANG model: https://github.com/OpenNetworkingFoundation/TAPI/releases
  • 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