- 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 - 10 minutes
- Modeling Documentation - 0 minutes
Material:
- Model proposals:
- Modeling requirements:
- Related information:
- Clean/Approved models:
Minutes:
- 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: Jacqueline will try Git bash this week
- propose to cancel next week's call due to Chinese holiday
- 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
- modify the note, change "Vnfd" to "Vdu"
- 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
- 5G service
- PNF instance model
- Topology model
- Modeling Documentation
- R6 readthedocs review:
- add relationship documentation to the UML guideline:
ONAPMODEL-28
-
Getting issue details...
STATUS
{"serverDuration": 199, "requestCorrelationId": "a13f86e4f66539aa"}