ONF Transport API SDK 1.0.1
·
842 commits
to develop
since this release
This is the ONF Transport API SDK bug fix release version 1.0.1. This SDK is being released under the Apache 2.0 license.
The ONF Transport API (TAPI) project charted under the ONF Open Transport Working Group (OTWG) is responsible for the development of this SDK as an Open Source SDN project SNOWMASS. This release is based on Functional Requirements for Transport API (June 2016 | TR-527) and supports interfaces to the following functional modules:
- Topology Service
- Connectivity Service
- Path Computation Service
- Virtual Network Service
- Notification Service
The SDK includes the following components:
- TAPI UML Information Model - which is pruned/refactored from the ONF Core Information Model 1.1
- TAPI YANG Schema - which is generated using the OSSDN EAGLE UML-to-YANG mapping tool
- TAPI SWAGGER definitions - which is generated using the OSSDN EAGLE YANG-to-JSON tool
- TAPI Reference Implementation - the code stubs for which are generated using the OSSDN EAGLE JSON-to-Python tool
- TAPI Development Guide - a PDF document providing an overview of the SDK.
This release addresses the following issues since release v1.0.0
- #135 - Fix #129 - LocalClass should have a 'name' attribute/property contributed by Karthik Sethuraman (karthik-sethuraman)
- #134 - Fix #133 contributed by Ricard Vilalta (rvilalta)
- #133 - Include Restoring as a LifeCycleState +enhancement
- #129 - name is missing for LocalClass +enhancement
- #128 - Fixes #103 #126 #124 #127 #125 contributed by Ricard Vilalta (rvilalta)
- #127 - RIFix references (should be without server:port) +fix
- #126 - In TapiOduSpec.swagger the definition of “OduPoolPropertySpec� is empty, it causes problems. +fix
- #125 - RI should handle POST for creation without ID +fix
- #124 - RI created connection connectionports are incorrect given the example scenario +fix
- #123 - Minor fixes in TapiNotification contributed by Karthik Sethuraman (karthik-sethuraman)
- #122 - syntax error in Tapi.swagger and TapiNotification.swagger +fix
- #121 - Fix #107 contributed by Ricard Vilalta (rvilalta)
- #120 - TapiNotification.swagger /restconf/config/Context/ missing getSupportedNotificationTypes. +fix
- #119 - Fix #105 and #118 contributed by Ricard Vilalta (rvilalta)
- #118 - Return of yang list should be in the JSON form +enhancement
- #117 - Fixing #108 and #112 contributed by Ricard Vilalta (rvilalta)
- #116 - Incorrect definitions for properties in ContextSchema type from Tapi.swagger.
- #114 - Swagger Code Generator Error.
- #113 - Swagger Error. Different swagger files contain "Swagger Error" +fix
- #112 - Different files contain a lot of the same objects. +enhancement
- #111 - NameAndValue fields are mixed in different files. +enhancement
- #110 - Connection and _connectionSchema objects are equal. +enhancement
- #109 - ServiceEndPoint type in swagger files has different definitions +fix
- #108 - NodeEdgePoint type in swagger files has different definitions +fix
- #107 - POST(create) operation should post to a collection URI +fix
- #105 - Link type in swagger files has different definitions +fix
- #104 - Swagger errors for TapiTopology.swagger +fix
- #103 - pyang cannot parse Tapi.yang +fix
- #102 - Update Master with Release 1.0.0 contributed by Karthik Sethuraman (karthik-sethuraman)
- #99 - Using the Maven pom to build source code +fix
Commits: e6dd993...ea92430