Transcript
SDN Framework and API
Lyndon OngOIF MA&E Committee Co-Chair
Ciena
Layer123 SDN & NFV World CongressDusseldorf, Germany
October 15, 2015
Transport SDN ToolkitWork in Progress
Essential tools for Transport SDN deployment• How to apply SDN to a carrier’s multi-domain,
multi-layer transport network• How to make SDN interoperable, high
performance and secure for carrier use• How to operationalize SDN
Architecture
Identifiers
FrameworkSCN APIs
Integration with MP
Interoperability demosSecurity
OIF/ONF Global Transport SDN Demo Where to go from here?
OIF/ONF Joint Prototype Demo in Fall 2014 – reported last L123 World Congress Multi-layer control Multi-vendor, Multi-domain Demo
• 5 Carrier Labs• 9 Vendors
OpenFlow Optical Transport Extensions Prototype NBI for Connectivity Service
and Topology Whitepaper available with details
Moving Transport SDN ForwardOIF Framework for Transport SDN and Work in
Progress
SDN Reference Architecture Carrier SDN Requirements Meaningful demo and testing in
carrier environment Framework for Transport SDN
• http://www.oiforum.com/documents/framework-for-transport-sdn-components-and-apis
4
Application Layer
Control Layer
Infrastructure LayerDomain 1
NE NE NE
Domain 2
NE NE NE
Domain 3
NE NE NE
Network Orchestrator
Parent Controlle
r
DomainControlle
r
DomainControlle
r
DomainControlle
rSBI
NBI
SBI
CloudOrchestrator
Compute Storage
SDN Framework for Transport Multi-Domain Integration
Transport SDN Demo validated framework for carriers
• Can be realized over WAN and provide carrier benefits
• Highly flexible - multiple technology layers, multiple domains, greenfield and brownfield
Lack of definition for how user applications interact with transport network resource functions
• The programmability of Transport SDN requires some of the internal interfaces used by ASON to become open
SDN Access to Network ControlNB Interfaces
Standard APIs defined for interfaces to functional entities APIs for Call/Connection Control, Topology, Path Query,
Virtualization Replace internal, proprietary interfaces Decoupling of functional blocks enables augmentation and/or
replacement Important for delivering new network behaviors
BusinessApplication
BusinessApplication
Virtualization/Abstraction
API Divergence ProblemAbsent Standards
Potential APIs• Vendor-specific• Controller-specific• Technology-specific• Language-specific• SDO-specific
Need commonality• Common core model• Common minimal
subset• Plus extensions
Achieving Common APIs The Tools and Remaining Challenges
Existing Tools Current API work is being done in fragmented silos Some linkage of APIs to existing protocol environments
Keys to achieving interoperable common APIs Getting to a common Information Model and API
specification ONF Common Information Model project – aligns ONF, ITU,
TMF, MEF, OIF Verifying APIs provide the necessary functionality
Use case review Refinement for transport network applications
OIF Transport API Project
Work in ProgressProgress standards for Transport APIs Joint with ONF OpenTransport WG T-API Project
• Common, Standardized Transport API Specifications
• Functional Specification• Information Model• YANG Data Model/JSON Schema
Draft documents made openly available via Open Source (ONF “Snowmass” OpenTransport project)
https://github.com/OpenNetworkingFoundation/ONFOpenTransport
• Open Source Implementation project “Englewood”
OIF Demonstrations and Implementation Agreements to follow
top related