ODTN and TIP collaboration with Whitebox Transponder 'Cassini'

Transcript

1. Copyright © NTT Communications Corporation. All rights reserved. ntt.com Transform your business, transcend expectations with our technologically advanced solutions. .81 . . 8 2 .8 812 . 8 5 5 8 0. 8
2. . .
3. 3 3 3 .. 3 3 3 ) (( ( Optical telemetry Protection/ restoration Calendaring Power Management WSS TAPI Open Line System (OLS) OpenConfig OpenConfig MUX WSS AMP MUX xponder ODTN Controller TAPI xponder xponder . xponder xponder xponder Transponders from multiple vendors Book-ended transponders OLS Controller
4. . . . . . . 4
5. .. 0 . / 1, . WSS TAPI Open Line System (OLS) OpenConfig OpenConfig MUX WSS AMP MUX xponder ODTN Controller TAPI xponder xponder xponder xponder xponder OLS Controller 1, . 2 , . 1, . )(+ , . )(+ 1, . . 1 , . )(+ Jul. 2018 Mar. 2019 Jan. 2018
6. .. . 20 1 0 0 . WSS TAPI Open Line System (OLS) OpenConfig OpenConfig MUX WSS AMP MUX xponder ODTN Controller TAPI xponder xponder xponder xponder xponder OLS Controller (. (. + . 0 + + . /0 + . 0 ), + + . /0 ), + . 0 0 . /0 ), Jul. 2018 Mar. 2019 Jan. 2018 (.
7. . . . . . . &
8. . .)( . ( . . • Broadcom Tomahawk+ ASIC(3.2T) • 100Gbit/s QSFP28 x16 • 200Gbit/s CFP2-ACO x8 . )( ) .)
9. 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
10. 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
11. . . • 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
12. . . . . . . &
13. . . transceiver (CFP2_ACO) transceiver (QSFP28) logical-channel logical-channel ce1 ce2 ce3 ce4 ce5 ce6 ce1/1 ce2/1 ce3/1 ce4/1 ce5/1 ce6/1 100G 100G 200G oe1 oe1/1 oe1/2 oe2 oe2/1 oe2/2 oe3 oe3/1 oe4/2 10101 20101 20102 10201 . . 10301 20201 20202 10401 10501 20301 20302 10601 transceiver (CFP2_ACO) transceiver (QSFP28) logical-channel logical-channel ce1 ce2 ce3 ce4 ce5 ce6 ce1/1 ce2/1 ce3/1 ce4/1 ce5/1 ce6/1 100G 100G 200G oe1 oe1/1 oe1/2 oe2 oe2/1 oe2/2 oe3 oe3/1 oe4/2 10101 20101 20102 10201 10301 20201 20202 10401 10501 20301 20302 10601 . . . . . . . . Link (100G) DSR DSR x16 x16 x16 x16 x16 x16 1..1 1..1 OTSi layer(ignored) SIP NEP NEP TAPI Cassini
14. . . transceiver (CFP2_ACO) transceiver (QSFP28) logical-channel logical-channel ce1 ce2 ce3 ce4 ce5 ce6 ce1/1 ce2/1 ce3/1 ce4/1 ce5/1 ce6/1 100G 100G 200G oe1 oe1/1 oe1/2 oe2 oe2/1 oe2/2 oe3 oe3/1 oe4/2 10101 20101 20102 10201 . . 10301 20201 20202 10401 10501 20301 20302 10601 transceiver (CFP2_ACO) transceiver (QSFP28) logical-channel logical-channel ce1 ce2 ce3 ce4 ce5 ce6 ce1/1 ce2/1 ce3/1 ce4/1 ce5/1 ce6/1 100G 100G 200G oe1 oe1/1 oe1/2 oe2 oe2/1 oe2/2 oe3 oe3/1 oe4/2 10101 20101 20102 10201 10301 20201 20202 10401 10501 20301 20302 10601 . . . . . . . . Link (100G) DSR DSR Connection Connectivity Service x16 x16 x16 x16 x16 x16 1..1 1..1 OTSi layer(ignored) SIP NEP NEP CEP TAPI Cassini OSS/BSS
15. . . <logical-channels> <channel> <logical-channel-assignments> <assignment> <index>10101</index> <config> <index>10101</index> <assignment-type>LOGICAL_CHANNEL</assignment-type> <logical-channel>20101</logical-channel> <allocation>100.0</allocation> </config> </assignment> </logical-channel-assignments> </channel> Transponder1 DSR x16 x16 x16 Link (100G) 1..1 lower connection <connection xmlns="urn:onf:otcc:yang:tapi-connectivity"> <uuid>00000000-0000-3000-0001-111000000000</uuid> <connection-end-point> <topology-id>...-100000000000</topology-id> <node-id>...-100000000000</node-id> <owned-node-edge-point-id>...-121000000000</owned-node-edge-point-id> <connection-end-point-id>...-121000000000</connection-end-point-id> </connection-end-point> <connection-end-point> <topology-id>...-100000000000</topology-id> <node-id>...-100000000000</node-id> <owned-node-edge-point-id>...-111000000000</owned-node-edge-point-id> <connection-end-point-id>...-111000000000</connection-end-point-id> </connection-end-point> <layer-protocol-name>DSR</layer-protocol-name> </connection> client side line side tapi-sample-step2-intermediate.xml sbi-openconfig-sample-infinera.xml ce1 ce2 ce1/1 ce2/1 100G 100G 200G oe1 oe1/1 oe1/2 10101 20101 20102 10201
16. . . <logical-channels> <channel> <logical-channel-assignments> <assignment> <index>10101</index> <config> <index>10101</index> <assignment-type>LOGICAL_CHANNEL</assignment-type> <logical-channel>20101</logical-channel> <allocation>100.0</allocation> </config> </assignment> </logical-channel-assignments> </channel> Transponder1 DSR x16 x16 x16 Link (100G) 1..1 lower connection <connection xmlns="urn:onf:otcc:yang:tapi-connectivity"> <uuid>00000000-0000-3000-0001-111000000000</uuid> <connection-end-point> <topology-id>...-100000000000</topology-id> <node-id>...-100000000000</node-id> <owned-node-edge-point-id>...-121000000000</owned-node-edge-point-id> <connection-end-point-id>...-121000000000</connection-end-point-id> </connection-end-point> <connection-end-point> <topology-id>...-100000000000</topology-id> <node-id>...-100000000000</node-id> <owned-node-edge-point-id>...-111000000000</owned-node-edge-point-id> <connection-end-point-id>...-111000000000</connection-end-point-id> </connection-end-point> <layer-protocol-name>DSR</layer-protocol-name> </connection> client side line side tapi-sample-step2-intermediate.xml sbi-openconfig-sample-infinera.xml ce1 ce2 ce1/1 ce2/1 100G 100G 200G oe1 oe1/1 oe1/2 10101 20101 20102 10201 Device Port ONOS
17. 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
18. 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
19. . .
     OSS OSS createConnectivityService getConnectivityService ODTN ODTN
20. . . • 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
21. . .
     • 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!
22. . . . . . .