Page Comparison

General Information:

• Date and Time: 2021, Oct 18, 9pm~10pm Beijing Time, 9am~10am US Eastern
• Meeting Room: https://zoom.us/j/97595070639?pwd=ajFTZGdlTmRVNjU5MSt1YVpycmlrdz09
• Meeting Recording:  
• Meeting Chat Log:  

Agenda:

• Agenda bashing - 5 minutes
• Model Proposals
  
  • ETSI CNF support - ? minutes
  • PNF instance model - ? minutes
  • CPS model - 0 minutes
  • Topology model - ? minutes
• Modeling Documentation - 0 minutes

...

• Model proposals:
  
  • 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
• Model Specification:
  • Honolulu release: https://docs.onap.org/projects/onap-modeling-modelspec/en/honolulu/ONAP%20Model%20Spec/im/index.html

...

• Agenda bashing
• 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
    • Updates：
      • Fred presents the latest progress: a wiki page on IFA011 v4.2.1 changes, ETSI IFA011 v4.2.1 Changes to ONAP Resource Model.
      • intention: update from v4.1.1 to v4.2.1
        • adding of VipCpdProfile, VipCpLevel, LcmCoordinationActionMapping classes, and related changes
        • introducing vnfdExtInvariantId at the vnfd
        • add two attributes in VipCpd: intVirtualLinkDesc, dedicatedIpAddress
        • name change of volumeTemplate → perVnfcInstance (in virtualStorageDesc)
      • papyrus changes already submitted by Fred
  • 5G service / CPS model
  • PNF instance model
    • reverse engineering
      
      • feedback to A&AI team:
        • some relationship lack description, and the existing description may not be meaningful enough
      • current status: AAI Schema Reverse-Engineering to Papyrus
  • Topology model
    • Proposal: https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Abstract+Topology+Model
      • Martin will update the models with the IM sketch
    • Model Sketch: https://wiki.onap.org/display/DW/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
    • Latest updates:
      • Tony provides some comments on the model sketch:
        • simplify the "service" models
        • relationship between the topology model and ONAP IM / root model
          • currently working on high level concepts, discussing whether we need to have certain objects in the ONAP IM, and maybe part of the topology model
          • e.g., Connectivity, EndPoint
        • from developer's perspective, suggest to avoid too many hops to access the models/info
        • intent part needs further discussion, and suggest to focus on aspects first
      • Model discussed during the meeting (for the abstract models)
        • 
        • will continue discussion next week
        Tony will take 3 week's off, and will be back in Oct
        • updated proposal from Andy:
        • Image Added
        • Tony has updated the "ownership" section of the model adding ManagementPurpose attribute to the resource class (composed of ManagementReferenceRole and ManagementPurpose parts)
          • Andy commented that management aspects should be discussed seperately and keep simple
        • LayerParameter session
          • Andy commented to add 0..N association to the diagram
        • Topology grouping session
          • Andy suggested to add examples
• Modeling Documentation
  
  • gendoc template discussion:
    • whether the description only applies for a navigatable end of an association
    • 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