Child pages
  • 2019-01-17 OIMT Meeting notes
Skip to end of metadata
Go to start of metadata





  • Administrative
    • March 18-22 Sydney Meeting
      • Registration
      • Agenda planning
    • Recap v1.5 & v2.0 work items
  • Follow-up on Core IM extension for specific technology
  • Specific work items (during agenda discussion)
  • AOB: Constraint Domain definition

Discussion Items





IM-DMarch Sydney meeting
 Core ExtensionThorsten Heinze
  • Thorsten indicated that he had not yet had an opportunity to complete his action from last week
  • Chris noted that if Thorsten could provide what is needed in the first phase that would be helpful.
  • Chris suggested that Nigel and he could meet to work on some material next week (considering the general need as well as Thorsten's request)
  • Thorsten noted that there is a need for guidance

March meeting 
  • Ran through the agenda planning and refined as below (see red text)
  • Agenda planning
    • Key topics for the meeting (description work items are in oimt2018.KL.001.14_oimt-work-items.xlsx)
      • #8 Equipment enhancements (TAPI equipment modeling)
      • #35 LTP port (TAPI integration)
      • #36 Compute model (CPU storage)
      • #9 IP switching, #53 IP Segment routing (to support 5G, complement SG15 work)
      • #26 Intent/Constraint, #55 TOSCA Profile
      • #37 Spec re-work, #44 Refactor LTP Spec to be Comp-Sys Spec, #56 Simplied Spec model, #58 Specification Pattern for new comer, including Thorsten's (Core model extension) work request (TAPI critical)
      • #41 Identity model investigation + other global class attributes (state etc.)
      • #39 Event driven solution investigation, #43 Operation pattern for general task, #57 Job Task process model, #55 TOSCA Profile
      • (related to #54) Managing Cloud Native (Kubernetes, Istio, Containers)
      • TAPI needs (Karthik Sethuraman: provides additional item, if any)
        • How to use the topology pacs in TAPI
        • Distinction between Connectivity model (service) vs Topology model (resource)
        • Catalog driven API related to ONAP (TMF), This is related to #55 TOSCA profile
        • ONAP usage of TAPI
        • Revisit the TAPI virtual network (What is the difference between VN Service End Point vs Service Interface Point)
          • Configuration v state, service v resource, CRUD pattern, operation patterns, intent
          • Examine the storage pattern and the model that relates the views (CH)
          • Examine Link capacity allocation pattern (MB)
          • Work towards the goal of Virtual Network
            • The point problem is relatively straight forward
            • The two ended link brings in the most basic form of graph
            • We can build from the above towards more complex graphs towards the full network problem
            • Eventually this will lead to system - system mapping (PC graphs)
        • Multilayer transitional link scenario (need this before 2.2)
        • Routing constraint (need this for 2.2), related to #26
  • Agreed to have the agenda plan stabilized one month before the meeting (i.e., Feb. 18)

Prioritize and assign (especially TAPI). Require contribution for the agenda item to be enabled.


Nigel noted that Malcolm had asked for the definition of ConstraintDomain and that when the definition from the UML model was assessed it had become clear that there was a need for update as the current definition does not explain the full capability.

Chris proposed that the definition be refined along the lines of that in the intro PAC ( TR-512.P.2-V0-1.pptx).

AI: Nigel: Refine CD definition for V1.4.1.

Action Items