ONAP R7 Resource IM Call 2020-7-20

• Date and Time: 2020, July 20th, 9pm~10pm Beijing Time, 9am~10am US Eastern

• Meeting Room: https://zoom.us/j/97595070639

• Meeting Recording: zoom_0.mp4

• Meeting Chat Log: 

Agenda:

• Agenda bashing - 5 minutes

• Model Proposals
  
  

  • allotted resource - 0 minutes

  • ETSI alignment - 10 minutes

  • 5G RAN service - 10 minutes

  • CNF - 0 minutes

  • Geolocation - 0 minutes

  • PNF instance model - 0 minutes

  • CPS model driven PoC - 0 minutes

• Modeling Documentation & Glossary - 5 minutes

• Modeling Process discussion - 0 minutes

• Model proposals:

  • Allotted Resource Revised

    • comments: Allotted Resource Model Review Comments

  • Support for CPS Model Driven PoC R8+

• Modeling process:

  • Proposed ONAP Release Process Updates for Information and Data Modeling

• 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

  • vacation plan:

    • Michela: 4 weeks

• Model Proposals
  
  

  • ETSI alignment

    • identified changes: ONAP-ETSI-2.7.1-07-13-update.pptx

    • papyrus problem:

      • cannot open the "model" sub-model in papyrus, have tried the recommended version as well as the test version on Using Papyrus for Modeling

        • seems to be an old problem, the papyrus team has acknowledged the issue, but no solutions are provided

        • suggest just not to touch the "model" part, and go around the problem

      • question on "only approved editors can edit the model"

    • suggested next steps:

      • Fred will create a wiki page under R7 resource IM workspace for further review

      • discuss next week and submit the changes to gerrit if no major issues are identified

  • 5G Service model

    • two approaches to implement the generic application model: 1) using 3GPP models to enhance the platform model; 2) attach generic application models to xNF resources, do not change platform models

    • approach 2 (seems more preferable):

      • Open

        

    • comments:

      • Zu: no need to re-define the 3GPP model, too complicate to enhance the platform

      • Fred: CDS can fulfill the needs well

      • Ben: Andy may suggest a hybrid approach

    • AP: Ben will contact Yuriy for CDS demo (this Wednesday)

• Modeling Documentation
  
  

  • R6 readthedocs review

    • AP: simplify the sterotypes for the associations

      • Jacqueline will help give some suggestions and discuss next week

  • add relationship documentation to the UML guideline: ONAPMODEL-28: Using the Documentation Property for RelationshipsOpen

    • UML principle wiki page:

      • under ONAP Modeling Design Principles and Guidelines

      • AP: Michela & Xu will check the current wiki pages whether they cover requirements for classes, relationships for Papyrus

        • Xu find nothing related in the current pages, suggest to create a new page to solve the issue