Skip to content

Latest commit

 

History

History
42 lines (29 loc) · 3.27 KB

README.md

File metadata and controls

42 lines (29 loc) · 3.27 KB
Raw

This is the Transport API (TAPI) SDK. This SDK is released under the Apache 2.0 license.

The TAPI project is charted under the LF Open Network Modeling and Interfaces (ONMI) project, which is responsible for the development of this SDK as an Open Source project.

The SDK includes technology-agnostic interfaces to the following functional modules:

  • Topology Service
  • Connectivity Service
  • Path Computation Service
  • OAM Service
  • Fault Management Service
  • Equipment Inventory Service
  • Virtual Network Service
  • Notification Service
  • Streaming Service
  • gNMI Streaming Service

It also includes support for the following technology-specific interface profiles:

  • Photonic Media (L0-WDM)
  • Optical Transport Network (L1-OTN)
  • Carrier Ethernet (L2)

The SDK includes the following components:

  • TAPI UML Information Model - The TAPI UML models are a normative part of the TAPI SDK and are the only source for subsequent generated TAPI SDK components (YANG, OAS, etc.).

    • These models are pruned/refactored from the ONF Core Information Model
    • Some of the UML model artifacts (e.g., Classes, Attributes, Types) that the TAPI contributors consider to be evolving are marked as experimental using the UML OpenModelProfile stereotypes. These artifacts could either become mature or change/evolve in future releases.
    • Dump of the UML models in Microsoft Word format generated through Eclipse Gendoc tool.

  • TAPI YANG Schema - The TAPI YANG models are a normative part of the TAPI SDK.

    • The YANG specifications have been generated from the corresponding UML model using the EAGLE UML2YANG mapping tool ("Tapi_v2x" branch) and further edited manually to comply with the ONF IISOMI UML2YANG mapping guidelines.
    • Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts. As described in the UML models, some artifacts are considered experimental, and thus are the corresponding YANG artifacts.
    • The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases. The YANG model backward compatibility criteria are outlined in section 11 of (https://tools.ietf.org/html/rfc7950).

  • TAPI OpenAPI Specification - TAPI OAS (OpenAPI Specifications) are an informative part of the TAPI SDK.

    • The OAS have been generated from the YANG data models included in this release using the EAGLE YANG2OAS tool following the RESTConf protocol specification (https://tools.ietf.org/html/rfc8040). This specification makes no assessment as to the level of RESTConf compliance of the TAPI REST APIs.

  • The documentation associated to this delivery is available at the matching delivery of TAPI Documentation.