Page History

...

• Agenda bashing - 5 minutes
• Model Proposals
  
  • allotted resource - ? 0 minutes
  • ETSI alignment - 10 20 minutes
  • 5G RAN service - 0 minutes
  • CNF - 0 minutes
  • Geolocation - ? 20 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
• Model Proposals
  
  • ETSI alignment
    • Fred shared the proposals for IM change: ETSI IFA011 v2.7.1 Changes
    • no comments received offline
    • question:
      • will mapping replace the current wrapper solution? A: plans to do so in the future
      • support both v2.5.1 and v2.7.1? A: Yes, and deprecate v2.5.1 in the future. Note: v2.7.1 has some incompatibility issues with v2.5.1 (e.g., policy type).
    • AP:
      • Fred will update the stereotypes
      • ask for poll on modeling subcommittee call
  • CPS model
    • Jacqueline prefers to postpone to next week
    • Ben's summary for last week's call:
      • Zu suggest to define a non-MANO artifact type for NRM (except for YANG schema, which already has a non-MANO artifact)
  • Geolocation/Place model
    • draft model available at: Proposed Location Model
    • call for comments, please share on the wiki or email
  • allotted resource
    • dangling question: how allotted resource will be used in resource instead of service models
    • Michela will attend tomorrow's network slicing call for updates and continue the discussion next week
• 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: 

    Jira
    server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key ONAPMODEL-28

    • 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