...
- 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.
- also working on corresponding DM and papyrus changes
- R9 DM proposal: https://wiki.onap.org/pages/viewpage.action?pageId=93011772
- CNF runtime model
- IM: Simplified K8S Resource Model - IM
- Jacqueline also comments on the wiki page, about the description/definition of k8s-resource
- will continue discussion on the wiki / in the following calls
- 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.double check whether k8s-resource can contain other k8s-resources
- Jacqueline comment that the classes that are not for approval should be marked as experimental
- 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
- feedback to A&AI team:
- migrating to new version
- poll ongoing
- reverse engineering
- 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
- 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)
- will continue discussion next week
- Tony will take 3 week's off, and will be back in Oct
- Tony provides some comments on the model sketch:
- Proposal: https://wiki.onap.org/display/DW/Abstract+Topology+Model
- ETSI support for CNF model
- Modeling Documentation
- gendoc template discussion:
- whether the description only applies for a navigatable end of an association
- add relationship documentation to the UML guideline:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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
- gendoc template discussion: