Transport API (TAPI) WIM connector for RO
Proposers
- Lluis Gifre (CTTC)
- Ricard Vilalta (CTTC)
- Ramon Casellas (CTTC)
Description
As described in the ONF Transport API (TAPI or T-API) documentation [1-2], "T-API is designed to allow network operators to deploy SDN across a multi-layer, multi-domain, multi-vendor transport infrastructure, extending programmability across their networks end-to-end."
Integrating a TAPI WIM connector in OSM will enhance the interoperability of OSM with transport SDN controllers to establish WAN connections. Indeed, the "Mandatory Use case requirements for SDN for Transport" (MUST) from the Telecom Infra Project (TIP) leaded by leader network operators considers TAPI as one of the interfaces between orchestrators and SDN controllers to be supported [3].
There is already a work in progress regarding this WIM connector for the ONF and the TeraFlow projects that will be used in this context.
Demo or definition of done
The TAPI WIM connector should enable a TAPI-enabled transport SDN controllers (acting as a WIM for OSM) to establish transport connectivity between VIMs without knowing further details of the network. A new robot test might be created, even if it not enabled in the daily job, to test the deployment of NS across two datacenters with an SDN making use of the new TAPI connector.
References
- ONF TAPI Overview
- ONF TR-547 TAPI v2.1.3 Reference Implementation Agreement
- TIP MUST Open Transport SDN Architecture
- Ll. Gifre, C. Manso, R. Casellas, R. Martinez, R. Vilalta, R. Muñoz, “Experimental Demonstration of End-to-end NFV Orchestration on Top of the ADRENALINE Testbed,” accepted in IEEE NetSoft Demo Track, 2022.