What is TAI? ● TAI is an interface between optical transponders and system software ● Allows system software to operate with any TAI-compliant transponders ● Allows transponders to operate in any system which supports TAI ● By decoupling the transponders from the rest of the system, it allows each to innovate independently ● Available here: ○ https://github.com/Telecominfraproject/oopt-tai ○ https://github.com/Telecominfraproject/oopt-tai-implementations HW Independent Application X TAI libtai.so (for vendor A) Transponder A HW Independent Application X TAI libtai.so (for vendor B) Transponder B Same codebase HW Independent Application Y TAI libtai.so (for vendor B) Transponder B Multiple NOS choices Disaggregated Same codebase Multiple transponder choices from TIP summit 2018
What is not TAI? ● TAI is not an API for operators like YANG models ● TAI is not trying to become a de jure standard or standardization body Application TAI libtai.so (for vendor A) Transponder A Application TAI libtai.so (for vendor B) Transponder B Application Transponder C Application Transponder D YANG model YANG model YANG model YANG model Operation Support Systems / SDN Controller / Orchestrator Operator Software Transport Component Transponders with TAI Transponders without TAI from TIP summit 2018
. . • Provision through OpenConfig common model • IP Infusion provides OpenConfig NBI interface to us with OcNOS (Thanks!) Application TAI libtai.so (for vendor A) Transponder A Application TAI libtai.so (for vendor B) Transponder B YANG model YANG model SDN Controller / Orchestrator Operator Software Transport Component OcNOS TAI libtai.so (for vendor A) Transponder A TAI libtai.so (for vendor B) Transponder B OpenConfig ODTN TAPI
Model-driven controller in ONOS: DCS • Subsystem to support NETCONF/YANG ecosystem • Launched in 2016 and has been developed to realize model-driven ctrl. 17
ODTN Implementation Framework: • ONOS YANG compiler, runtime • Dynamic config subsystems Features: • NBI(RESTCONF) auto-generation • SBI(NETCONF) auto-generation • Java library which enable easy implementation of Service Application • Distributed config store of NBI service configuration and device configuration
Device Device Device JSON / XML 3A3 3 6 *.yang Service Design Orchestrator 16 B 46 56 2 *.yang 6B 46 56 6 ) JSON / XML A 4 gRPC / RESTCONF / NETCONF SB YANG Runtime Dynamic Config Subsystem ODTN App YANG Compiler model.jar Distributed Config Store /services /devices 3 6C ( A 4 REST / gRPC / RESTCONF / NETCONF NB
. . • Made all component work together successfully • Mapping between OpenAPIs: TAPI => OpenConfig => TAI • Got confidence that Cassini/OcNOS/TAI are promising devices/NOS/API as whitebox transponder • Still work in progress • Some features of TAI are not implemented as of now • Exposed configurations are limited as well • Will be able to have a full capability of TAI in a year • Some critical issues are found in DCS • Should be addressed from its design • Good requirement for next DCS
• Challenge to use whitebox transponder for dis-aggregation network • ODTN and Cassini is a good starting point to realize whitebox transponder/controller • Come and join us!