ONAP R9 Resource IM Call 2021-8-9
General Information:
Date and Time: 2021, Aug 9, 9pm~10pm Beijing Time, 9am~10am US Eastern
Meeting Room: https://zoom.us/j/97595070639?pwd=ajFTZGdlTmRVNjU5MSt1YVpycmlrdz09
Meeting Recording:
Meeting Chat Log:
Agenda:
Agenda bashing - 5 minutes
Model Proposals
ETSI CNF support - ? minutes
CNF runtime model - 10 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://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16463007
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:
SOL001 is delayed and expected to be stable at the end of July
CNF runtime model
comments regarding the DM are received last Tuesday
Should be there a container (object) between “tenant” and “k8s-resource”, instead of tenant directly connects to k8s-resource now?
Based on the URI, it seems like the relationship among “tenant”, “cloud-region” and “k8s-resource” should be “cloud-region”->”tenant”->”k8s-resource”, should the direct relationship between “cloud-region” and “k8s-resource” be modified accordingly?
Lukasz shows the updated models
Xu will update the IM accordingly
Jacqueline also comments on the wiki page, about the description/definition of k8s-resource
will continue discussion on the wiki / in the following calls
5G service / CPS model
PNF instance model
reverse engineering
feedback to A&AI team:
some relationship lack description, and the existing description may not be meaningful enough
current status: AAI Schema Reverse-Engineering to Papyrus
migrating to new version
poll ongoing
Topology model
Proposal: https://lf-onap.atlassian.net/wiki/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
inspired by TAPI model to add "link", "connection" classes
looking at ORAN use cases and see if the models can fulfill the requirements
TAPI presentation may be found here: otcc2019.KS.002_TAPI_Concepts_Topology_Connectivity.pptx
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)
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: Using the Documentation Property for RelationshipsOpen
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
Using Papyrus for Modeling updates