...
- 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
- update showing the hierarchy from the root model, and also add relationship with several existing A&AI objects
- check if id, name (and other attributes) can be inheritated from the root
- relationship with tenant should be simple relationship
- VnfModule should be VfModule
- cardinality of the K8sResource end in the two composite relationship should be 0..N
- 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)
- Xu will try to has experiment the same things as well, and discuss again next weekthing, no issues are found
- 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
- 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)
- 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: