Skip to end of metadata
Go to start of metadata




  • Administrative

  • TAPI Outstanding Issues review and plan for 2.2 release

Discussion items

5 minsAdministrative
  • Next TAPI Call: Skip next week (July 2) - next call on July 9

20 minsTAPI 2.x Release Plan
  • TAPI 2.2 Release update
    • RC1 - Released on April 8, 2019Included items:
      • Equipment inventory model (new feature)
      • Routing & Resilience Constraints fixes/updates
        • Some of the constraints were changed to read-write from read-only
        • Minor structural changes (related Topology/Connectivity constraints)
      • OAM, Notification Framework updates
        • OAM Job structure refactoring and renaming
        • OAM/Threshold profile
        • Threshold/PM parameter
        • Alarm/TCA linkage to Threshold/PM parameter
      • Topology Model update
        • added TopologyAggregatesNEP association
        • marked NodeAggregatesNEP as deprecated
        • renamed Node.ownedNodeEdgePoint to Node.nodeEdgePoint
      • ETH Technology model updates
        • mainly OAM based on MEF NRM-OAM requirements, review and feedback
      • Photonic model updates
        • mainly power control management & photonic-layer-qualifier labels
    • RC2 - Released on May 24, 2019
      • Includes UML, YANG, Tree files only.
        • TAPI yang currently does not include any Yang 1.1 features/modules - so we can state that we use 1.0
        • As far as using leafref within a read-write tree to point to read-only attributes, we should use Yang 1.1 require-instance, but if we want to stick to Yang 1.0, we can use uuid instead of leafref
    • RC3 - do we need it or should we submit RC2 for TST approval?
      • OpenAPI & RI are NOT included in RC2 (not normative) - should we include this in 2.2?
      • Decision: Yes, Create RC3 with OpenAPI this week.
      • Plan: Submit it to OTCC TST for approval on Jul 9 (decision in TAPI call). 2-week approval period for TST (ends Jul 23).

Open Issues for 2.2 RC3Andrea Mazzini

Discussed following issues: Discussion notes/decisions on the Issue link below

Action items