...
- 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
- Model Proposalsallotted resourceservice model discussion has concluded, the discussion can be resumed
- ETSI support for CNF model
- related R9 DM modelproposal: VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancementshttps://wiki.onap.org/pages/viewpage.action?pageId=93011772
- aligned with SOL001 v4.2.1
- question about version alignment: IM aligned with v4.1.1, DM aligned with v4.2.1, shall the IM be revisited?
- the answer is yes, but the changes are very minor for the time being
- no major structure change for the VNFD compared to previous DM proposal
- MciopProfile renamed to Mciop, now a dedicated node type under VNF, still reference Helm Chart
- OsContainerGroup renamed to OsContainerDeployableUnit, stands for a Pod, and still reference to individual OsContainer(s)
- no changes for VirtualCp node type
- minor changes for node and data type definitions
- TOSCA example will be available on the wiki page later
- package format
- use non-MANO artifact to describe Helm Charts
- discussion is still ongoing
- 5G service / CPS model
- PNF instance model
- Topology model
- Proposal: https://wiki.onap.org/display/DW/Abstract+Topology+Model
- call information: https://lists.onap.org/g/onap-modelingsub/topic/abstract_topology_model/80876474?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80876474
- today, 1615:00 UTC (1 hour earlier than last week)
- investigating whether can reuse the TAPI (ONAP transport API) topology model
- 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:
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
- 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: