ONAP R8 Resource IM Call 2020-11-9

General Information:

• Date and Time: 2020, Nov 9th, 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 - ? minutes
  • ETSI CNF support - 20 minutes
  • PNF instance model - ? minutes
  • VES model update / Gendoc template update - 20 minutes
  • CPS model driven PoC - ? minutes
• Modeling Documentation - 0 minutes

Material:

• Model proposals:
  • Allotted Resource Revised
    • comments: Allotted Resource Model Review Comments
  • Support for CPS Model Driven PoC R8+
• Modeling requirements:
  • ONAP R8 Modeling High Level Requirements
• Related information:
  • Allotted Resource for Network Slicing
  • 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt

Minutes:

• Agenda bashing
• 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
    •  AP of last call:
      • Fred to add an association between OsContainerDesc and Vdu, and also a comment stating Vdu can only compose of OsContainerDesc or ComputeDesc at one time
      • fix typo in VersionSelector class
    • postpone to next week
  • VES model update / Gendoc template update
    • poll on VES 7.2 model update is ongoing
    • gendoc template discussion:
      • example: PnfModel-2020-11-08-233004.docx
      • conclusion:
        • change the column name to "Defined in"
        • remove the "namespace" row, and the "inheritance" key name
      • AP:
        • Xu will update the template and upload it to the gerrit (for Honolulu release and beyond)
  • CPS model
  • 5G service
  • PNF instance model
• Modeling Documentation
  
  • R6 readthedocs review:
    • gendoc template improvement: ONAP Information Model - Gendoc Examples 
    • AP: simplify the stereotypes for the associations, Xu will help summarize the status and trigger the discussion
      • conclusion: remove the stereotypes column for now
    • 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)
      • https://wiki.onap.org/pages/viewpage.action?pageId=84669384
      • reviewed, no comments for now
      • will continue working on the pages