ONAP R7 Resource IM Call 2020-9-28

• Date and Time: 2020, Sep 28th, 9pm~10pm Beijing Time, 9am~10am 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

  • CNF - 0 minutes

  • PNF instance model - 0 minutes

  • VES model update - 20 minutes

  • CPS model driven PoC - 20 minutes

• Modeling Documentation - 0 minutes

• Model proposals:

  • Allotted Resource Revised

    • comments: Allotted Resource Model Review Comments

  • Support for CPS Model Driven PoC R8+

• Modeling requirements:

  • ONAP R7 Modeling High Level Requirements

• Related information:

  • Allotted Resource for Network Slicing

  • 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt

• Agenda bashing

• Model Proposals
  
  

  • allotted resource

    • the plan is to finish the network slicing discussion in service model first, then discuss allotted resource

  • VES model update

    • no one shows up, postpone to next call

  • CPS model
    
    

    • move the old page under R8/Honolulu, create a simplified version for R7

    • discuss the R7 version:

      • assume the ResourceDesc will have at most one YangModelSet, and the ResourceInstance will have at most one ResourceInstanceAppData

• Modeling Documentation
  
  

  • R6 readthedocs review:

    • gendoc template improvement: ONAP Information Model - Gendoc Examples 

    • AP: simplify the sterotypes for the associations, Xu will help summarize the status and trigger the discussion

  • 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)

      • https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16442605

      • reviewed, no comments for now

      • will continue working on the pages