T-API Update

The Path to Open, Interoperable Optical Networking

OFC 2019

March 7

Lyndon Y. Ong (lyong@Ciena.com), OIF MA&E Committee Co-Chair

3/25/2019 OIF Copyright © 20191

T-API: A Confluence of Standards and Open SourceTAPI

Use cases & Requirements

TAPI UML

Information Model

TAPI YANG

Data Schema

OpenAPI (RESTConf)

Schema

ONF Core Information Model

ONF Technology Specific

Models

UML-YANG

Generation Tool

YANG-OpenAPI

Generation ToolONF TAPI SDK

EAGLE Modeling Tools

Open Model

Profile

Code

OTN

(ITU-T

G.874.1)

ETH

(ITU-T

G.8052)

Photonic

(ITU-T

G.807.1*)

Python Reference

Implementation

Python Stub

Generation Tool

MEF

Multi-carrier

T-SDN Interop

Implementation

Agreements &

Certification

OIF

Interop Implementations

MEF 59

NRM

MEF 60

NRP

ONF OIMT

Multiple Groups

ITU-T SG15

Technology Generic Core Model

(ITU-T G.7711)

IISOMI

OAM

Etc.

TIP

Open

OLS

Model

ONF T-API Standardization

• ONF Open Transport Config & Control Project (OTCC): • Goal: promote common configuration and control interfaces for transport networks in SDN, defining these interfaces with open

source software and software-defined standards.

• Steering Team: AT&T, Ciena, China Mobile, CTCC, Fiberhome, Huawei, Infinera, NEC, Nokia, SIAE, Telefonica

• Focus on API development and implementation, application of core information model to specific transport technologies (packet, optical and wireless) – working closely with OIF on requirements and interoperability testing for optical networks

• Subprojects:

• Transport API Sub-Project (Karthik Sethuraman, NEC)

• Open Transport Information Modeling (Kam Lam, FiberHome)

• Wireless Transport (Giorgio Cazzaniga, SIAE)

• Device Management Interface Profile (Thorsten Heinze, Telefonica)

• ONF Open Information Modeling & Tooling Project (OIMT):• Goal: evolve industry-wide Open Information Models and associated open source tooling software that guides/supports the

development of Software Defined Networks

• Steering Team: Ciena, DT, Fiberhome, NEC, ZTE

• Focus on development of Detailed but compact canonical networking models in UML

• Focus on development of tooling for automated translation of UML to YANG, OpenAPI and TOSCA

ONF Transport API (TAPI): Functional Architecture

Topology

ServiceConnectivity

ServicePath Computation

Service

Shared Network Information Context

OAM ServiceVirtual Network

Service

NENetwork Elements

NENESDN Controller

NENESDN ControllerNENEApplication

SBIs

Transport API

Notification

Service

Transport API

TAPI Evolution

• Topology Service– Logical (abstract/virtual) Topology, Node,

Link & Edge-Point (Across al layers)

• Connectivity Service– Retrieve & Request P2P, P2MP, MP2MP

connectivity (Across all layers)

• Path Computation Service– Request for Computation & Optimization of

paths

• Virtual Network Service– Create, Update, Delete Virtual Network

topologies

• Notification Framework– Subscription and filtering– Autonomous/Push mechanism

• Node Constraints– Ability to specify connectivity/blocking

constraints

• Resilience & Protection– Multi-layer, Multi-Domain– Based on use cases under discussion

• OAM/Monitoring/PM– Consistent Multi-layer abstraction and

model – L0-L2

• Alarm/TCA/Counter• ETH/OTN Spec Models

• Photonic Media Spec Model– Support of Optical Transport Disagg– Separation of Media Channel and

Transponder Control

TAPI SDK 1.x (2016) TAPI SDK 2.1 (2018)

OIF Transport API Interop Demos (2014, 2016, 2018)

Domain

Controller

Domain

Controller

Domain

Controller

Multi-Domain Controller

Techn

olo

gy/ V

end

or Sp

ecificm

od

els

TAPI Agent

OSS/App/Orchestrator

Co

mm

on

Ab

straction

m

od

el

Transport API

Test Vendors

Test Carriers

Transport API

TAPI Agent

Multi-Domain Controller

TAPI AgentTAPI Agent

TAPI Agent

MEF Lifecycle Service Orchestration Presto IF

Tested at Multiple MEF Hackathon Events

ONF ODTN (Open Disaggregated Transport) Project

Open Disaggregated System

OLS Controller

WSS TRN

Open Line System (OLS)

OpenConfig OpenConfig

MUX WSSAMP MUXTRN

ONOS

Partial Disaggregation With OLS Controller (Current ODTN Ph 1.5)

TAPI with Photonic Media Model

ROADMtopology

TAPI

Demonstrated in OFC 2019 Demo Zone

Abstractedtopology

Detailedtopology

TAPI Future Directions

• Provides functions necessary for multi-domain orchestration

– Abstraction and Virtualization

– Multilayer Topology

– Interoperability of the North/South SDN Controller interface

• Supports multiple transport technologies

– Packet Transport (Ethernet, MPLS-TP)

– Optical Transport (OTN)

– Wireless Transport

– Photonic Media Channel

• TAPI 2.2 Items (projected)

– Equipment Inventory & Configuration

– Equipment, Holders (Rack/Shelf, etc), Connectors, Span, etc

– LLDP Model

– Cross-layer discovery

– Other Enhancements

– Topology Pacs/Datatypes (Capacity, Cost, Latency, Risk parameters) enhancements

– Further tune the component-system pattern for Topology & Connectivity

General Benefits TAPI Next Steps

OIF T-API Certification Program

• Work in Progress• Survey shows multiple operators and vendors having interest• Network Operators Advisory Group formed

• Testing outlines discussed• Focus on TAPI 2.1 or later – addresses operator requirements, esp. photonic

media modeling• Focus on control plane testing – easier/faster, data plane can be tested later• Focus on basic functions: topology discovery, service provisioning,

alarm/event notification

• Next steps• Develop use cases and test specs (take advantage of 2018 interop testing)• Identify potential test facilities

3/25/2019 OIF Copyright © 201910

Further Details

• TAPI Wiki:• https://wiki.opennetworking.org/display/OTCC/TAPI

• TAPI SDK• https://github.com/OpenNetworkingFoundation/tapi

• Core model: TR-512 V1.4 (November 2018)• https://3vf60mmveq1g8vzn48q2o71a-wpengine.netdna-ssl.com/wp-content/uploads/2018/12/TR-

512_v1.4_OnfCoreIm-info.zip

• UML, Papyrus, YANG Guidelines TR 514/515 (July 2018)• Last published version → https://www.opennetworking.org/software-defined-standards/models-apis/• Latest working draft

• https://wiki.opennetworking.org/display/OIMT/Infrastructure+Sub-team+Guidelines• https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines

• UML to YANG & YAMG-OpenAPI Mapping Tools• Github repository: https://github.com/OpenNetworkingFoundation/EagleUmlYang• Github repository: https://github.com/OpenNetworkingFoundation/EagleYangOpenApi