Child pages
  • 2019-02-07 OIMT Meeting Notes

Versions Compared

Key

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

...

Attendees

Apologies

Agenda

...

Time

Item

Who

Notes

IM-DMarch Sydney meetingAll
  • 2019 March 18-22 ONF OIMT & OTCC Sydney Meeting
    • General information (venue, travel etc.): oimt2019.ND.001.00_SydneyMeetingInfo.docx
    • Registration List for 2019 March 18-22 ONF OIMT & OTCC Sydney Meeting
    • Agenda planning
      • Template created at wiki page: Agenda Plan of 2019 March 18-22 ONF OIMT & OTCC Sydney Meeting
      • Key topics (for traveling approval and planning) from January 17 meeting minutes:
          • #8 Equipment enhancements (TAPI equipment modeling)(Color code: This color means Have material already)
          • #35 LTP port (TAPI integration)
          • #36 Compute model (CPU storage)
          • #9 IP switching, #53 IP Segment routing (to support 5G, complement SG15 work)(Kam)
          • #26 Intent/Constraint, #55 TOSCA Profile (Color code: This color means Ready to go) (CH)
          • #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)
          • #13 Model refactoring (Color code: This color means New agenda item)
          • #41 Identity model investigation + other global class attributes (state etc.) (Ready to go) (CH)
          • #39 Event driven solution investigation, including Streaming, #43 Operation pattern for general task, #57 Job Task process model, (CH) #55 TOSCA Profile
          • (related to #54) Managing Cloud Native (Kubernetes, Istio, Containers)
        • TAPI needs (Karthik Sethuraman: Provides additiona 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)(ND)
          • 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)(AM)
          • 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.
        • Description of work items are in oimt2018.KL.001.14_oimt-work-items.xlsx
    • Will further discuss this with Karthik Sethuraman for TAPI topics in IM-Ethe TAPI list and slot allocation with in the Feb. 8 Friday Prep call (Nigel Davis , Karthik Sethuraman, Andrea Mazzini , Hing-Kam Lam )

Brief discussion on Streaming

Nigel Davis

  • Providing and maintaining a view (Streaming for TAPI)
    • Differnece between Notification and Streaming:
      • Notification: reports reporttes the changes
      • Streaming: reports the states
    • Definitions of (distinction between) Compaction, Compression, Sampling
      • Example usage of Compaction: can be used to deal with alarm flooding
    • Alarm recording (of raise/clean/change) is a streaming mechanism
    • AI - Nigel Davis : Repalce the following screenshot with the slide deck.
  • Will continue the discussion next week in the Tuesday TAPI call
IM-EITU-T SG15 Media architectureStephen Shew
  • SG15-LS177: LS/o on Media work in ITU-T SG15 (to OIMT and OTCC)
  • Slides: presentation
    • IF = Intermediate frequency band
    • OMS OSME & OTS OSME can exist without an OSC. The current information model needs to de-couple them,
    • A defined grequency slot is not necessary of an ITU-T grid.
    • Need to look into the modeling implication from the two new maintenance indications (slide 11) and the parameters (slide 10).
    • Clause 13 of the previous version of G.807 is now Clause 15.
  • For TAPI next week (Karthik Sethuraman )
    • Discuss Streaming
    • Discuss the Media LS (will focus on the part impacting the management of the optical line system (OLS))

Action Items

  •   
  •