Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

General Information:

Agenda:

  • Agenda bashing - 5 minutes
  • Model Proposals
    • ETSI CNF support - ? minutes
    • CNF runtime model - 10 minutes
    • PNF instance model - ? minutes
    • CPS model - 0 minutes
    • Topology model - ? minutes
  • Modeling Documentation - 0 minutes

...

...

  • Agenda bashing
  • Model Proposals
    • ETSI support for CNF model
      • R9 DM proposal: https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=9301177216463007
        • 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
    • 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: k8s-resource are objects that represent a concrete instance of a concept on one k8s cluster, like a pod or namespace.
    • 5G service / CPS model
    • PNF instance model
      • reverse engineering
      • migrating to new version
        • poll ongoing
    • Topology model
      • Proposal: https://wikilf-onap.onapatlassian.orgnet/wiki/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
      • 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)
          • ManagedFunction/ManagedReference needs more work, services are to be removed
          • O1 interface is currently working on 3GPP NRM support
  • 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 Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyONAPMODEL-28
      • UML principle wiki page: