...
- Agenda bashing - 5 minutes
- Model Proposals
- allotted resource - 0 minutes
- 5G service - ? 15 minutes
- ETSI CNF support - ? 5 minutes
- PNF instance model - ? minutes
- CPS model driven PoC - ? 15 minutes
- Modeling Documentation - 30 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
- changes reviewed: add VES 7.2 (R8), ETSI IFA011 updates (R7) and location model (R7)
- link to the VES 7.2 model is pending due to no papyrus model available yet
- AP closed
- 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)
- Fred has done some minor changes to the model, will submit later this week
- suggest to disconnect VNFD with resource descriptor, will come up with a slides describing the proposal; hopefully next week
- question:
- Is the proposal capturing all the changes in v3.3.1 or choosing parts of the changes? Fred: should include all the changes.
- DM proposal available at: VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements
- plan to discuss it tomorrow
- CPS model
- poll ongoing (with the following comments)
- updates from the U/C realization call
- a change is needed to add "revision" attribute to the YangModuleIdentifier datatype
- 5G service
- will give a presentation on tomorrow's arch call
- 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?
- with Kamel's help, Ben has got the papyrus running
- the key thing is to use a papyrus version which is mapping to the Eclipse IDE version
- wiki page updated to capture the information
- suggest to further discuss the version recommended after Jacqueline come back
- with Kamel's help, Ben has got the papyrus running
- UML principle wiki page:
- R6 readthedocs review: