ONAP R10 Resource IM Call 2022-1-10

• Date and Time: 2022, Jan 10, 9pm~10pm Beijing Time, 8am~9am 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

  • ASD model - ? minutes

  • PNF instance model - ? minutes

  • Topology model - ? minutes

• Modeling Documentation - 0 minutes

• Model proposals:
  
  

  • Abstract Topology Model

• Modeling requirements:

  • ONAP R10 Modeling High Level Requirements

• Clean/Approved models:

  • ONAP Information Model - Clean and approved models across ONAP releases

• Model Specification:

  • Istanbul release: https://docs.onap.org/projects/onap-modeling-modelspec/en/istanbul/index.html

• Agenda bashing:
  
  

  • Plans to discuss the merging of modeling subcommittee calls and resource IM calls in Jan

• Model Proposals
  
  

  • ETSI support for CNF model

    • R9 DM proposal: https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16463007

      • aligned with SOL001 v4.2.1, package format is still under discussion

      • will ask for approval after SOL001 v4.2.1 is stable

    • 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

  • ASD model
    
    

    • Plan for the PoC: Application Package Onboarding to SDC

    • Marian presents the IM and DM proposals of the ASD model

      • IM: Application Service Descriptor (ASD) onboarding IM

      • DM: Application Service Descriptor (ASD) Resource Data Model
        
        

        • for the node type:

          • Xu suggest to add "version" into the IM

          • it's clarified that "funciton_description" maps to "asdInfoDescription" in the IM

      • ASD in NSD: NSD requirements for ASD deployment

        • use substitution mapping for asd_in_NS and asd node type

        • Mehmet asks how the current proposal describes the (multiple) connections related to the links, and recommend to check the NFV approach for that

    • Zu presents the packaging proposal

      • Application Service Descriptor (ASD) Onboarding Packaging Format

        • Thinh have question on the "entry_definition_type"

  • Reverse engineering

    • Proposal: AAI Reverse-engineering -- K8S resource

  • Topology model

    • Proposal: https://lf-onap.atlassian.net/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:

      • comment: remove ManagedReference to simplify the model

      • Open

        

• Modeling Documentation
  
  

  • gendoc template discussion:

    • whether the description only applies for a navigatable end of an association

    • add relationship documentation to the UML guideline: ONAPMODEL-28: Using the Documentation Property for RelationshipsOpen

    • UML principle wiki page:

      • Principle and Guideline for Information Model Proposal Using Papyrus (Draft)

      • Using Papyrus for Modeling