...
- 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
- APs from previous meetings:
- 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
- Michela suggest to connect the current VNFD model with the common IM model (in the Papyrus)
- DM proposal available at: VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements
- CPS model
- poll ongoing
- 5G service
- PNF instance model
- allotted resource
- 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?
- UML principle wiki page:
- R6 readthedocs review: