Agenda:
- Agenda bashing - 5 minutes
- Model Proposals
- ETSI CNF support - ? minutes
- CNF runtime model - 0 minutes
- PNF instance model - ? minutes
- CPS model - 0 minutes
- Topology model - ? minutes
- Modeling Documentation - 0 minutes
Material:
- Model proposals:
- Modeling requirements:
- Related information:
- Clean/Approved models:
- Model Specification:
Minutes:
- Agenda bashing
- Model Proposals
- ETSI support for CNF model
- R9 DM proposal: https://wiki.onap.org/pages/viewpage.action?pageId=93011772
- aligned with SOL001 v4.2.1, package format is still under discussion
- will ask for approval after SOL001 v4.2.1 is stable
- a proposal of updating the information model documentation is planned in R9
- Updates:
- Fred presents the latest progress: a wiki page on IFA011 v4.2.1 changes, ETSI IFA011 v4.2.1 Changes to ONAP Resource Model.
- intention: update from v4.1.1 to v4.2.1
- adding of VipCpdProfile, VipCpLevel, LcmCoordinationActionMapping classes, and related changes
- introducing vnfdExtInvariantId at the vnfd
- add two attributes in VipCpd: intVirtualLinkDesc, dedicatedIpAddress
- name change of volumeTemplate → perVnfcInstance (in virtualStorageDesc)
- CNF runtime model
- IM: Simplified K8S Resource Model - IM
- Jacqueline also comments on the wiki page, about the description/definition of k8s-resource
- current proposal (with examples added): k8s-resource are objects that represent a concrete instance of a concept on one k8s cluster, like a pod, namespace, stateful set, service, persistent storage, etc.
- Jacqueline comment that the classes that are not for approval should be marked as experimental
- 5G service / CPS model
- PNF instance model
- reverse engineering
- migrating to new version
- Topology model
- Proposal: https://wiki.onap.org/display/DW/Abstract+Topology+Model
- Martin will update the models with the IM sketch
- Model Sketch: https://wiki.onap.org/display/DW/Proposed+Topology+IM+Sketch
- Latest updates:
- Tony provides some comments on the model sketch:
- simplify the "service" models
- relationship between the topology model and ONAP IM / root model
- currently working on high level concepts, discussing whether we need to have certain objects in the ONAP IM, and maybe part of the topology model
- e.g., Connectivity, EndPoint
- from developer's perspective, suggest to avoid too many hops to access the models/info
- intent part needs further discussion, and suggest to focus on aspects first
- Model discussed during the meeting (for the abstract models)
- will continue discussion next week
- Tony will take 3 week's off, and will be back in Oct
- Modeling Documentation
- gendoc template discussion:
- whether the description only applies for a navigatable end of an association
- add relationship documentation to the UML guideline:
ONAPMODEL-28
-
Getting issue details...
STATUS
- UML principle wiki page:
{"serverDuration": 263, "requestCorrelationId": "e7b569fc954b7da0"}