Page History

...

• Model proposals:
  • Allotted Resource Revised
    • comments: Allotted Resource Model Review Comments
  • Support for CPS Model Driven PoC R8+
• Modeling requirements:
  • ONAP R8 Modeling High Level Requirements
• Related information:
  • Allotted Resource for Network Slicing
  • 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt
• Clean/Approved models:
  • ONAP Information Model - Clean and approved models across ONAP releases

Minutes:

• Agenda bashing
  • APs from previous meetings:
    • Jacqueline to submit papyrus changes for the approved location model
    • papyrus changes for VES 7.2 is required, and needs review / double check
    • Michela volunteered to update the clean model page: ONAP Information Model - Clean and approved models across ONAP releases
  • Ben shows the R8 time schedule (possibly shifting names of milestones):
    • M2: Jan 21, M3: Feb 25
    • DDF: early Feb, 2~4
• Model Proposals
  
  • allotted resource
    • the plan is to finish the network slicing discussion in service model first, then discuss allotted resource
  • ETSI support for CNF model
    • ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs
    • Michela and Jacqueline provide comments, expect further updates this week
      • no updates yet
      • Fred will further check whether need to change data type into class; and whether to ask for approval for those v3.3.1 features (not intended to implement in R8)
      • DM plans to implement a subset of v4.1.1 changes; Byung-woo and Fred will try to finalise the DM proposal this week
      • the ETSI VNFD is for onboarding, currently discussing how to process it internally (mapping to internal DM)
      • Michela suggest to connect the current VNFD model with the common IM model (in the Papyrus)
        • one way is to connect current VNFD with ETSI VNFD, the other is to connect current VNFD with the ResourceDesc class
  • CPS model
    • poll expected
    • there's a modeling session in tomorrow's arch meeting introducing the C&PS model

      • information can be found at https://wiki.onap.org/pages/viewpage.action?pageId=84644224

  • 5G service
  • PNF instance model
• Modeling Documentation
  
  • R6 readthedocs review:
    • gendoc template improvement: ONAP Information Model - Gendoc Examples 
    • discussion whether the description only applies for a navigatable end of an association
      • continue discussion later
  • add relationship documentation to the UML guideline: 

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

    • UML principle wiki page:
      • Principle and Guideline for Information Model Proposal Using Papyrus (Draft)
      • review the updates to the Gendoc requirements part
        • Michela suggest whether it's possible to add information of associations into the class definitions
          • Xu will investigate it offline