ONAP R8 Resource IM Call 2021-5-17

General Information:

Date and Time: 2021, May 17th, 9pm~10pm Beijing Time, 9am~10am US Eastern
Meeting Room: https://zoom.us/j/97595070639
Meeting Recording:
Meeting Chat Log:

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:
- Abstract Topology Model
Modeling requirements:
- https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
Related information:
- Allotted Resource for Network Slicing
- R8 5G Service Modeling
Clean/Approved models:
- ONAP Information Model - Clean and approved models across ONAP releases
Model Specification:
- Honolulu release: https://docs.onap.org/projects/onap-modeling-modelspec/en/honolulu/ONAP%20Model%20Spec/im/index.html

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
Joint call with use case realization team
- R9 use case & requirements: https://wiki.onap.org/pages/viewpage.action?pageId=99681185
- schedule of use case realization call: https://wiki.onap.org/display/DW/Use+Case+Realization+Meeting+Register+MoM
- major use cases of ONAP: https://wiki.onap.org/display/DW/ONAP+Major+Use+Cases
- next step:
  - Ben will help invite use case owners to have a presentation in the following modeling calls
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
- 5G service / CPS model
- PNF instance model
  - reverse engineering
    - AAI model is visible in papyrus now through reverse engineering
    - have to do the diagram by hand though
      - would like to simplify the view/links of PNF, but would prefer not to remove the content → may need sought of aggregation in the models
    - Jacqueline will try to create a gendoc document and share it next week
- 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
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:
    - 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