ONAP R6 Resource IM Call 2020-4-13

General Information:

• Date and Time: 2020, Apr 13th, 10pm~11pm Beijing Time, 10am~11am US Eastern
• Meeting Room: https://zoom.us/j/645982535
• Meeting Recording:
• Meeting Chat Log:

Agenda:

• Agenda bashing - 5 minutes
• Model Proposals - 0 minutes
  
  • license management - 0 minutes
  • allotted resource - 0 minutes
  • 5G RAN service - 0 minutes
• Modeling Documentation - 10 minutes
• Modeling Glossary - 20 minutes
• Modeling Process discussion - 15 minutes
• R7 Modeling Requirements - 5 minutes

Material:

• License Management (Moved to Clean)
• License Model Review Comments
• Allotted Resource Revised
• Allotted Resource Model Review Comments
• 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt
• Proposed ONAP Release Process Updates for Information and Data Modeling
• ONAP R7 Modeling High Level Requirements

Minutes:

• Agenda bashing
  • PNF instance model status & plan
  • Meeting time poll
    • https://doodle.com/poll/inhnt7acahmivsb7
    • currently most people prefer to move 1 hour earlier, will decide tomorrow
• Model Proposals
  • license management
    • poll ongoing
    • https://lists.onap.org/g/onap-modelingsub/message/521?p=,,,20,0,0,0::Created,,license,20,2,0,72771316
  • allotted resource
    • status check
  • 5G RAN service model
• Modeling Documentation
  • wiki page to record approved models
    • ONAP Information Model - Clean and approved models across ONAP releases
    • suggest to create sub pages under the above one to capture the latest clean model of each sub category, i.e., common, resource, service IM
      • sub page will contain the latest gendoc (word document) of each sub model
  • how to document relationship classes in Papyrus and readthedocs
  • how to treat "experimental" objects in readthedocs
    • Xu will look at how to modify the templates to include relationship and adding condition filters
    • Jacqueline will help look at how to handle the spaces in the file path
• Modeling Glossary
  • Common Model Glossary Review Comments
  • review:
    • #1 and #2, tend to agree we remove the items with no descriptions, record these items and provide descriptions where necessary
    • #3, #5, #6: refine the gendoc template for the glossary
    • #4: prefer to create an acronym list (in a seperate document)
    • #7: maybe refine the descriptions to remove the duplications
    • #8 and #9: refine the escaped characters?
    • #11: may take suggestion 1 at the moment, only provide a terminology document
• Modeling Process Discussion
  • start M4 process
    • update platform IM due to updates in the API swagger file
    • create readthedocs
    • assessing new model requirements for the next release
• R7 Modeling Requirements
  • ONAP R7 Modeling High Level Requirements