General Information:
- Date and Time: 2021, Feb 8th, 9pm~10pm Beijing Time, 8am~9am 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 - 10 minutes
- PNF instance model - 0 minutes
- CPS model - 0 minutes
- Topology model - 0 10 minutes
- Modeling Documentation - 0 minutes
...
- Model proposals:
- Modeling requirements:
- Related information:
- Clean/Approved models:
...
- Agenda bashing
- APs from previous meetings:
- Jacqueline to submit papyrus changes for the approved location model and CPS model
- Ben to submit papyrus changes for VES 7.2
- TBD: papyrus issueJacqueline will try Git bash this week
- propose to cancel next week's call due to Chinese holiday
- APs from previous meetings:
- Model Proposals
- allotted resource
- service model discussion has concluded, the discussion can be resumed
- ETSI support for CNF model
- ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs
- comments from last time:
- need to double check the class "VnfLcmOperationCoordination", if that's aligned with IFA
- Fernando Oliveira VnfLcmOperationCoordination is a new Information element that was introduced in IFA011 v3.3.1 https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/03.03.01_60/gs_nfv-ifa011v030301p.pdf section 7.1.6 page 73. SOL001 v3.3.1 does not yet support this datatype and functionality.
- will add a note to highlight the info
- modify the note, change "Vnfd" to "Vdu"
- need to double check the class "VnfLcmOperationCoordination", if that's aligned with IFA
- comments from last time:
- related DM model: VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements
- has submitted a contribution to SOL001, hope to reach agreement in March
- question:
- swImageArtifact is overlapping with helm charts, why have 2 paths? A: main rationale is to avoid parsing the helm charts
- what if there are misalignments between helm charts and other files? A: plan to develop a VNF validation tool in future release
- what's the benefits for having VNFD on top of helm charts? A from Thinh: VNFD contains more connectivity info than helm charts, but would suggest to avoid duplication where possible, e.g., container level compute/network resources could be described within helm charts
- whether SO would parse helm charts is open to the community
- will discuss with direct path team about the common package issue
- ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs
- 5G service
- PNF instance model
- Topology model
- Martin gives a brief presentation on abstract topology model: https://lf-onap.atlassian.net/wiki/display/DW/Abstract+Topology+Model
- triggered by discussion between ONAP and O-RAN
- could be extended to other use cases
- 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 Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 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: