ONAP R8 Resource IM Call 2021-2-22

• Date and Time: 2021, Feb 22nd, 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 - 10 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+

  • ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs

  • 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

• Agenda bashing

  • APs from previous meetings:

    • Jacqueline to submit papyrus changes for the approved location model and CPS model

    • Ben to submit papyrus changes for VES 7.2

    • papyrus issue:

      • Jacqueline is still trying to solve the problem in Eclipse, the user setting seems pointing to a uneditable file; and Jacqueline will help enhance the guidance if she solves the problem

      • Martin can help look at if it's the SSH issue

• Model Proposals
  
  

  • allotted resource

    • service model discussion has concluded, the discussion can be resumed

  • ETSI support for CNF model

    • ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs
      
      

      • during call for agreement

    • related DM model: VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements

      • continue the work in discussing with ETSI SOL team, ETSI is very supportive, expect to have a stable draft at the end of March

      • there are additional changes suggested by ETSI, will bring back once the proposal is stable (target to Istanbul release, for Honolulu, roughly the same as previous proposal)

      • for packaging: Thinh will have a proposal to be discussed tomorrow, CNF taskforce call (now overlapped with modeling subcommittee call)

        • Andy will help discuss how to resolve the overlap

  • 5G service

  • PNF instance model

  • Topology model

    • Martin gives a brief presentation on abstract topology model: https://lf-onap.atlassian.net/wiki/display/DW/Abstract+Topology+Model

    • Purpose: triggered by ORAN discussion, topology model is planned to be used on O1 reference point (SMO)

      • Open

        

    • next step: identify use case and requirements of the model

      • Chuyi mentioned network slicing use case has plan to display the topology of network slices, which may relavent to this proposal

      • Martin will reach out to people who are interested for dedicated discussion, will be announced in mailing list / wiki

• 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: ONAPMODEL-28: Using the Documentation Property for RelationshipsOpen

    • 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