Agenda:
- Agenda bashing - 5 minutes
- Model Proposals
- ETSI CNF support - ? minutes
- ASD model - 20 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)
- papyrus changes already submitted by Fred
- ASD model
- Thinh present the overview and status of the ASD model
- Marian explains the detailed models for the extCpd and clusterEnchancement parts
- Byung-woo explains the plan for the PoC
- next step:
- Xu to update the R10 resource model wiki tree, and Thinh/Marian will create a dedicated page for the IM
- 5G service / CPS model
- PNF instance model
- 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)
![](/download/attachments/111125196/image2021-8-30_22-2-41.png?version=1&modificationDate=1635141428000&api=v2)
- updated proposal from Andy:
![](/download/attachments/111125196/image2021-10-18_21-10-6.png?version=1&modificationDate=1635141427000&api=v2)
- Tony has updated the "ownership" section of the model adding ManagementPurpose attribute to the resource class (composed of ManagementReferenceRole and ManagementPurpose parts)
- Andy commented that management aspects should be discussed seperately and keep simple
- LayerParameter session
- Andy commented to add 0..N association to the diagram
- Topology grouping session
- Andy suggested to add examples
- 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": 206, "requestCorrelationId": "e3e1a412b26d79be"}