...
- 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:
- SOL001 is delayed and expected to be stable at the end of July
- R9 DM proposal: https://wiki.onap.org/pages/viewpage.action?pageId=93011772
- CNF runtime model
- IM: Simplified K8S Resource Model - IM
- questioncomments:
- 1) need to create empty classes for "tenant", "vnf-module", etc.? A: will keep the comments as for now, and Jacqueline will help reverse-engineer the related classes 2) whether the attribute definitions are acceptable? A: need further check, and needs double check with the model owner on "version", "group" descriptions.
- the relationship between k8s-resource and cloud-region should be N:1 rather than 1:N
- prefer to show the relationship in the diagram
- suggest to add relationship with the root model
- Xu will update the IM and discuss next week
- 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
- Jacqueline has done the experiment of creating gendocs using two different versions of eclipse
- the gendoc of the new version seems fine, but the gendoc of the old version breaks (missing parent class information)
- AP:
- Xu will try to experiment the same things as well, and discuss again next week
- Jacqueline has done the experiment of creating gendocs using two different versions of eclipse
- 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
- Andy has helped to create a high level requirement for the topology model
- expecting ORAN to provide relavent use cases
- Martin and Andy are aware of the different views of topology model presented last week by Cagatay
- mainly triggered by ORAN WG10, also related to WG1's slicing use case, etc.
- how to model different layers, physical, logical topology, etc.? current methodology is using UML/papyrus to capture the models
- 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
- Andy will arrange further call to discuss the model
- Adding concepts like clients and servers, further discussion are needed to for the context of the new terms
- also whether the whole objects should be put under "ManagedFunction" needs further discussion
- 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: