General Information:
- Date and Time: 2021, April 12, 9pm~10pm Beijing Time, 9am~10am US Eastern
- Meeting Room: https://zoom.us/j/97595070639
- Meeting Recording:
- Meeting Chat Log:
Agenda:
- Agenda bashing - 5 minutes
- Model Proposals
- allotted resource - 0 minutes
- 5G service - 0 minutes
- ETSI CNF support - 0 minutes
- PNF instance model - 0 minutes
- CPS model - 0 minutes
- Topology model - 20 minutes
- Modeling Documentation - 0 minutes
Material:
- Model proposals:
- Modeling requirements:
- Related information:
- Clean/Approved models:
Minutes:
- Agenda bashing
- reminder for filling R9 high level requirements: https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
- Ben would like the modeling team to join the use case realization call on May 3, to discuss the modeling high level reqs
- please notice the modeling subcommittee call has moved 1 hour earlier
- reminder for filling R9 high level requirements: https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
- Model Proposals
- ETSI support for CNF model
- R9 DM proposal: https://wiki.onap.org/pages/viewpage.action?pageId=93011772
- aligned with SOL001 v4.2.1, package format is still under discussion
- will ask for approval after SOL001 v4.2.1 is stable
- a proposal of updating the information model documentation is planned in R9
- lack resources, no code implementation plan for Istanbul release
- for backward compatibility, possibly only support SOL001 v2.5.1 and v2.7.1 in the future
- R9 DM proposal: https://wiki.onap.org/pages/viewpage.action?pageId=93011772
- 5G service / CPS model
- PNF instance model
- reverse engineering: still facing trouble opening the workspace, the reason could be mismatch between the papyrus versions of the profile and workspace
- Topology model
- Proposal: https://wiki.onap.org/display/DW/Abstract+Topology+Model
- discussion material: Proposed Topology IM Sketch
- inspired by TAPI model to add "link", "connection" classes
- looking at ORAN use cases and see if the models can fulfill the requirements
- Andy will help provide the slides (on the wiki)
- it's proposed to continue the discussion in this call
- ETSI support for CNF 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:
-
ONAPMODEL-28Getting issue details...
STATUS
- 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
- Michela suggest whether it's possible to add information of associations into the class definitions
- Using Papyrus for Modeling updates
- suggest to further discuss the version recommended after Jacqueline come back
- UML principle wiki page:
- R6 readthedocs review: