2pm Andrea Campanella ODTN Brief Overview and Update 2019 09 11
2pm Andrea Campanella ODTN Brief Overview and Update 2019 09 11
2pm Andrea Campanella ODTN Brief Overview and Update 2019 09 11
2.
3.
4.
5.
6.
7.
8.
Disaggregated Transport Networks
4
•
•
•
•
•
•
• …
•
•
Open APIs
Only Open APIs with public models will be used.
Reach industry consensus and agreement on Open and Public APIs
Open and Standard API:
- provide layers of abstractions
- enable plug and play
- mandate interaction between software and hardware
- mix and match of components
- multi-vendor integration
7
- -
-
- -
Cassini Cassini
Tx TX
TX TX
1. Discover optical topology with details (devices, ports, links)
2. Expose topology details on the northbound TAPI API
3. Receive TAPI connectivity requests from an OSS/BSS on NB
4. Automated compute of end to end optical path with lambda
5. Install configuration for optical path to OLS controller and Transponders
line side
6. Transponder cross connection for client to line side connection
7. Power configuration on line side ports (manual)
8. Modulation configuration on line side ports (manual)
9. ONOS is deployed in a three node instance for resiliency and failover
11
OLS
OLS
Edge
WA
Cloud
N
Edge
Cloud
-
-
-
Cassini Cassini
Together We Build
16
Copyright © 2019 Telecom Infra Project, Inc.
TIP
Open Optical & Packet Transport
What is TIP?
FOUNDED IN 2016
Together We Build
17
Copyright © 2019 Telecom Infra Project, Inc.
What is TIP?
FOUNDED IN 2016
Together We Build
18
Copyright © 2019 Telecom Infra Project, Inc.
What is TIP?
FOUNDED IN 2016
Together We Build
19
Copyright © 2019 Telecom Infra Project, Inc.
Collaboration Benefits and Goals
1. Reduce duplicated effort in Optical Disaggregation
2. Share knowledge, resources, findings and development
3. Discuss and achieve a stronger industry consensus in APIs and solutions
4. Stronger impact and accelerate trials and production deployments of
complete white box hardware and open source software in optical networks.
5. Common test labs
SDN Controller ODTN / ONOS
Network
Operating OcNOS TAI
System
Stratum
OcNOS
P4Runtime
Stratum
TAI TAI
SDKLT
libtai.so libtai.so
(for vendor B) (for vendor B)
BRCM
Transponder B Transponder B
Tomahawk +
3 months time frame
1. FEC
2. OSNR retrieval
3. GUI extension with more information and parameters
4. Testing for an automated CI/CD with regression testing
6 months time frame
1. End to end Power configuration workflow with OLS negotiation
2. Platform hardening
1 year (and more) time frame
1. Alarms
2. Expanding pool of Transponders (Adva, Fujitsu, ZTE)
3. Expanding Pools of OLS/Roadm
4. Integration with Optical planning tools (gNPy)
5. In band control
P2P, TX + OLS/ROADM
Resiliency, Power, Modulation
P2P, TX + OLS/ROADM
FEC, OSNR, GUI, Tests
P2P, TX + OLS/ROADM
E2E Power, E2E testing,
Hardening
Evaluation scenarios SDN Controller ONOS
1. Metro: Optical layer 1 interoperability with OEM Southbound API OpenConfig
O-SNCP devices.
Network OcNOS
2. Longhaul: Optical layer 0/1 reach performance in
Operating TAI
100G and 200G mode. System
-
-
-
-
- →
-
Designed to recognize top ONF Community members who are:
● Top Code Contributors (or Code Removers)
● Top Reviewers and Mentors
● Top Ambassadors or Advocates
● Contributors of Significant Components of a system
● Consistently "chopping wood and carrying water" (helping everyone be more productive)
- Well know API
- Supported already by many vendors
- Proper abstraction model for transponder devices capabilities and information
- Defines capabilities at correct level for programmability but also abstraction
from physical details
- Capability and Flexibility to support vendor specific features
- Can represent both multi-layer w/ and w/o OTN
- Extensible and Open Source
- Well know API
- Extensible and Open Source
- Tested and deployed (See Interop Testing)
- Proper abstraction for high level optical domain programming
- Can represent both multi-layer end to end provisioning with optical
parameters
- Great community of vendors and Service Providers
Service Provisioning
1. OSS/BSS requests connectivity-service with TAPI
2. Connectivity services and provisioning config is stored in
distributed Maps for redundancy and failover
3. ONOS translates into Optical Intent and TX configuration
4. provisions a connectivity service through TAPI on OLS
5. Logical channel (cross-connection from client to line side) and
wavelength Tuning through Openconfig on Transponders
→
→
Physical Simulation Environment (gNPY)
Open Source Optical Simulation tool
Currently working in offline mode, with manual feedback to controller
TAPI
41