ONAP R7 Resource IM Call 2020-8-3

• Date and Time: 2020, Aug 3rd, 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 - 0 minutes

  • 5G RAN service - 50 minutes

  • CNF - 0 minutes

  • Geolocation - 0 minutes

  • PNF instance model - 0 minutes

  • CPS model driven PoC - 0 minutes

• Modeling Documentation & Glossary - 0 minutes

• Modeling Process discussion - 0 minutes

• Model proposals:

  • Allotted Resource Revised

    • comments: Allotted Resource Model Review Comments

  • Support for CPS Model Driven PoC R8+

  • ETSI alignment: ONAP-ETSI-2.7.1-07-13-update.pptx

• 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: 2 weeks

• Model Proposals
  
  

  • ETSI alignment

    • not ready for this week

    • Byung-woo and Fred plan to share some ideas on mapping between ETSI model and SDC AID on Wednesday

  • 5G Service model
    
    

    • 3 potential solutions:

      • generic application model + 3GPP NRM model (as artifact)

        • define new artifact type, design & run time use the artifact to retrieve information, minor change to code

      • augumenting platform IM

      • hybrid way: generic application model + potential changes to platform IM + 3GPP NRM model (as artifact)

    • 2 ways to analysis:

      • top down: what are different in process/behavior for the two ways

      • bottom up: have concrete parameter examples and analysis

    • next steps:

      • ACTION: SDC team – S/W change support new non-MANO artifact type

      • ACTION: Jacqueline mapping from onboarded NRM to the C&PS Record (modeling Subcommittee). Gen. Application Modeling defined.

      • ACTION: new nonMANO artifact types (defined in Modeling SubCommittee)

      • ACTION: C&PS team to describe solution

      • ACTION: VNF-SDK to validate

• Modeling Documentation
  
  

  • R6 readthedocs review:

    • gendoc template improvement: ONAP Information Model - Gendoc Examples 

    • AP: simplify the sterotypes for the associations 

      • @Jacqueline Beaulac [Ericsson] will help provide some suggestions

  • 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