ONAP R7 Resource IM Call 2020-7-27

General Information:

• Date and Time: 2020, July 27th, 9pm~10pm Beijing Time, 9am~10am US Eastern
• Meeting Room: https://zoom.us/j/97595070639
• Meeting Recording:  zoom_0.mp4
• Meeting Chat Log:  meeting_saved_chat.txt

Agenda:

• Agenda bashing - 5 minutes
• Model Proposals
  
  • allotted resource - 0 minutes
  • ETSI alignment - 0 minutes
  • 5G RAN service - 40 minutes
  • CNF - 0 minutes
  • Geolocation - 0 minutes
  • PNF instance model - 0 minutes
  • CPS model driven PoC - 5 minutes
• Modeling Documentation & Glossary - 0 minutes
• Modeling Process discussion - 0 minutes

Material:

• 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

Minutes:

• Agenda bashing
  • vacation plan:
    • Michela: 3 weeks
• Model Proposals
  
  • ETSI alignment
    • identified changes: ONAP-ETSI-2.7.1-07-13-update.pptx
    • Fred will work on this topic this week, discuss next week
  • 5G Service model
    • original use case: base station configuration
    • 3GPP generic models: TS28.541/28.622
    • platform model: Ben's opinion is C&PS model, similar to the model classes in the root model (e.g., SDC/AAI models)
    • ONAP already has similar models as defined in TS 28.622 (managed entities, managed functions, etc.)
    • CPS is a PoC in R7 and plan to be a dedicated FB in Honolulu, now hosted as a CCSDK&SDN-C project
  • CPS model
    • Friday call ran by Ben: Configuration & Persistency Service Meeting Notes & Recordings
• Modeling Documentation
  
  • R6 readthedocs review:
    • gendoc template improvement: ONAP Information Model - Gendoc Examples 
    • AP: simplify the sterotypes for the associations 
      • Jacqueline Beaulac will help provide some suggestions
  • add relationship documentation to the UML guideline:  ONAPMODEL-28 - Getting issue details... STATUS
    • 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