ONAP R8 Resource IM Call 2020-11-23

• Date and Time: 2020, Nov 23rd, 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 - ? minutes

  • PNF instance model - ? minutes

  • CPS model driven PoC - ? 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 R8 Modeling High Level Requirements

• Related information:

  • Allotted Resource for Network Slicing

  • 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt

• Agenda bashing

  • AP:

    • Jacqueline to submit papyrus changes for the approved location model

    • papyrus changes for VES 7.2 is required, and needs review / double check

  • clean model page update

    • Michela volunteered to update the pages, approved models not captured include:

      • ETSI alignment with v2.7.1 NFV spec (R7)

      • location model (R7)

      • VES 7.2 (R8)

• 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

    • Michela and Jacqueline provide comments, expect further updates this week

    • Plan to discuss the IM updates next week and further check if it's possible to share DM plan/proposal

  • CPS model

    • plan to ask for a poll on the simplified model (Support for CPS Model Driven PoC R7)

  • 5G service

  • PNF instance model

    • Jacqueline is working on the models

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

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

      • continue discussion on association part:

        • name, documentation and type are required

        • direction/navigable is optional