Agenda:
- Agenda bashing - 5 minutes
- Model Proposals
- allotted resource - 0 minutes
- 5G service - 0 minutes
- ETSI CNF support - 0 minutes
- PNF instance model - 0 minutes
- CPS model - 0 minutes
- Topology model - 0 minutes
- Modeling Documentation - 0 minutes
Material:
- Model proposals:
- Modeling requirements:
- Related information:
- Clean/Approved models:
- Model Specification:
Minutes:
- Agenda bashing
- reminder for filling R9 high level requirements: https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
- new requirements may be added after more use case presentations
- plan to review intent based networking model proposals next week
- time change for modeling subcommittee call
- Andy has discussed with Ben, and plan to not change the time for now, will have further discussion on modeling subcommittee call
- Joint call with use case realization team
- 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
- latest updates:
- Thinh has presented the alternative package solution in the CNF taskforce call, could be discussed in future calls
- CNF requirements collaboration pending discussions as well, could be discussed in this week's CNF taskforce call
- 5G service / CPS model
- PNF instance model
- reverse engineering
- gendoc has been created and is presented by Jacqueline
- the document is useful because of easier understanding
- for example, the description shows there are several attributes/models marked not working for now ("not correctly populated", etc.)
- question is which content to focus for now (considering the document has 500+ pages)
- Jacqueline prefer to start with PNF model (as originally proposed)
- Andy agrees to start with PNF, and can further look at topology related items
- Xu suggests to start with PNF, and then look at current model proposal related topics
- may need to have a seperate directory to host the AAI models, to avoid potential non-compatible issue of papyrus
- Andy suggests to mark all the models in experimental stereotype for now
- Jacqueline will help upload the gendoc document
- 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
- 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:
- Martin is working on the TAPI model, and has discussed with the SON use case team to receive feedback from them
- 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": 345, "requestCorrelationId": "bd517fb95bbcdfc8"}
