ONAP R8 Resource IM Call 2021-1-11

General Information:

• Date and Time: 2021, Jan 11th, 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 - 2 minutes
  • 5G service - 0 minutes
  • ETSI CNF support - 10 minutes
  • PNF instance model - 0 minutes
  • CPS model - 0 minutes
• Modeling Documentation - 0 minutes

Material:

• 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
• 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
  • 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
      • Ben will discuss with Timo to sign the agreements and see if that can address the problem
      • Chuyi also suggests to avoid having multiple unsubmitted changes which could cause error
• Model Proposals
  
  • allotted resource
    • the plan is to finish the network slicing discussion in service model first, then discuss allotted resource
  • ETSI support for CNF model
    • ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs
      • Fred has submitted changes to address comments from Jacqueline
      • comments:
        • need to double check the class "VnfLcmOperationCoordination", if that's aligned with IFA
        • modify the note, change "Vnfd" to "Vdu"
    • related DM model: VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements
      • Fred go through the proposal
  • 5G service
  • PNF instance model
• 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 - Getting issue details... STATUS
    • 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