Releases: Open-Network-Models-and-Interfaces-ONMI/TAPI
ONF Transport API SDK 1.0.3
This is the ONF Transport API SDK bug fix release version 1.0.3. 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.2
- #171 - Bug Fixes for 1.0.3 contributed by Karthik Sethuraman (karthik-sethuraman)
- #166 - Typo in TapiConnectivity.swagger +fix
- #162 - ConnectionEndPoint and _clientNodeEdgePoint/_serverNodeEdgePoint
- #160 - Different between YANG and SWAGGER for UUID. +fix
- #158 - Partial fix #157 contributed by Ricard Vilalta (rvilalta)
- #157 - YANG compliance +fix
- #154 - TapiNotification.swagger contain TimeRange with field in a different sequence than other swagger files. +enhancement
- #153 - TapiNotification.swagger contain GlobalClass with field in a different sequence than other swagger files +enhancement
- #149 - Loss of integrity between objects such as ServiceEndPoint and NodeEdgePoint
- #142 - new ConnectivityService provisioning question
Commits: b7f60af...da3f612
ONF Transport API SDK 1.0.2
This is the ONF Transport API SDK bug fix release version 1.0.2. 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.1
- #155 - Fixes for #152, #153, #154 contributed by Karthik Sethuraman (karthik-sethuraman)
- #154 - TapiNotification.swagger contain TimeRange with field in a different sequence than other swagger files. +enhancement
- #153 - TapiNotification.swagger contain GlobalClass with field in a different sequence than other swagger files +enhancement
- #152 - Issue #148 is not fully fixed. ServiceEndPoint skipped. +fix
- #150 - Bug Fix: #148 - LocalClass definitions in all swagger files contributed by Karthik Sethuraman (karthik-sethuraman)
- #149 - Loss of integrity between objects such as ServiceEndPoint and NodeEdgePoint
- #148 - Different object definition from other swagger files +fix
- #144 - Fix #143 #138 #136 contributed by Ricard Vilalta (rvilalta)
- #143 - _corouteInclusion object in Connectivity Constraint +enhancement
- #142 - new ConnectivityService provisioning question
- #139 - GET /config/Context/_connection/{uuid} issue
- #138 - Request to add /operations/getConnectionList/ for RPC calls. +enhancement
- #136 - RI scenario misleading ports +fix
- #132 - remove serviceIdOrName for getConnectionDetails operation
- #115 - Path to retrieve _connection from _connectivityService is missing in TapiConnectivity.swagger file
- #106 - ConnectionEndPoint specification - Modeling Issue
Commits: c7c455e...93fa8ee
ONF Transport API SDK 1.0.1
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
ONF Transport API SDK 1.0.0
This is the ONF Transport API SDK release version 1.0.0. 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 contains the following fixes since release 1.0.0-RC.1
•#101 - Bug Fix: #100 contributed by Karthik Sethuraman (karthik-sethuraman)
•#100 - Capacity properties in the augmented Swagger modules do not contain the enum values +fix
•#97 - Bug Fix: GetTopology RPC should return the array of references, not topologies contributed by Karthik Sethuraman (karthik-sethuraman)
•#96 - GetTopology RPC should return the array of references, not all topologies +fix
•#95 - Bug Fix: Moved ServiceEndPoint RPC operations to common Tapi module contributed by Karthik Sethuraman (karthik-sethuraman)
•#94 - TAPI SDK overview and developer guide drafts contributed by Karthik Sethuraman (karthik-sethuraman)
•#93 - Adding response to connectivity service creation contributed by Ricard Vilalta (rvilalta)
•#92 - Multiple bug fixes related to ServiceEndPoint, NotificationFilter & augmented classes duplicate attributes contributed by Karthik Sethuraman (karthik-sethuraman)
•#91 - ServiceEndPoint definition does not include ResourceSpec/GlobalClass attributes +fix
•#90 - Create .gitignore file contributed by Pavel Likin (burnout171)
•#89 - Manually fixed Tapi services swagger files that augment base Tapi module contributed by Karthik Sethuraman (karthik-sethuraman)
•#87 - Enhancements for #85. Fixing #86 contributed by Ricard Vilalta (rvilalta)
•#86 - Bug in notification creation - old callId +fix
•#85 - Respond JSON to list responses using param itemlist +enhancement
•#84 - TAPI Context should not be createable/deletable +fix
•#83 - Tapi.yang: Context class "instantiated" as a list statement +fix
•#82 - Fixing bugs for r1.0 contributed by Ricard Vilalta (rvilalta)
•#81 - StatePac properties in the augmented Swagger modules do not contain the enum values +fix
•#80 - Module name in leafref path
Commits: 007020e...47b9435
ONF Transport API SDK 1.0.0 Release Candidate 1
This is a pre-release version of the ONF Transport API SDK 1.0.0.
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.