...
- Model proposals:
- Modeling requirements:
- Related information:
Minutes:
- Agenda bashing
- AP:
- Jacqueline to submit papyrus changes for the approved location model
- papyrus changes for VES 7.2 is required, and needs review / double check
- clean model page update
- Michela volunteered to update the pages, approved models not captured include:
- ETSI alignment with v2.7.1 NFV spec (R7)
- location model (R7)
- VES 7.2 (R8)
- Michela volunteered to update the pages, approved models not captured include:
- AP:
- 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
- Updates?
- Michela and Jacqueline provide comments, expect further updates this week
- Plan to discuss the IM updates next week and further check if it's possible to share DM present the plan/proposal on DM changes?
- CPS model
- plan to ask for a poll on the simplified model
- 5G service
- PNF instance model
- Jacqueline is working on the models
- 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)
- https://wiki.onap.org/pages/viewpage.action?pageId=84669384
- reviewed, no comments for now
- continue discussion on association part:
- name, documentation and type are required
- direction/navigable is optional
- UML principle wiki page:
- R6 readthedocs review: