© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

AT&T’s SDN Controller Implementation Based on OpenDaylight

Margaret T. Chiosi & Brian Freeman

AT&T Labs Distinguished Network Architect

D2.0 SDN-NFV Realization

July 29, 2015

The SDN+NFV Components & Common Use Cases

Service Provider Use Cases – A Wish List

Agenda

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

Page 2

SDN in a Virtualized World

VM Container (NFVi)

Virtual Network Function

Cloud Orchestrator

Controller

Physical Network Function

Service Orchestrator

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

Page 3

SDN Global

SDN Local Overlay

Adapter Adapter

vS/vR

ESXi

Controllers – How They Fit Together

Fabric Switch

SDN Local Fabric Switch (“Underlay”)

Adapter

SDN Local Access

Access NEs

Adapter

Optical NEs

SDN Local Optical

Adapter

MAN/WAN NEs (PNFsVNFs)

SDN Local MAN/WAN

KVM

Application/Service-aware End-to-end Service Configuration

& Global Resource Optimization Controls

Dis

trib

ute

d L

oca

l C

on

figu

rati

on

Co

ntr

ol

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

SP SDN Customer SDN

Page 4

THE Controller?

SDN Global SDN Local Overlay

SDN Local Fabric Switch

(Underlay) © 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

SDN Controller ?

Page 5

Virtualize Function

Server Failover

Site Failover

Scale out/in/up/down VF – in one location or multiple locations based on time or traffic

Customer request causing VF spin up

Customer bandwidth on demand

Multi-tenancy to application

Common Use Cases

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

Page 6

The SDN+NFV Components & Common Use Cases

Service Provider Use Cases – A Wish List

Agenda

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

Page 7

AT&T Global SDN Controller Software Architecture

Page 8 Device Type 1 Device Type N

Service Logic Interpreter

Svc Templates

Cloud Orchestrators

AT&T & 3rd Party

Control Apps SDN Controller

Compiler

REST API

Service Orchestrator

API Handler

Network Resource Autonomous Controller

FCAPS++ Data

AT&T Applications

ECOMP

Policy

Neutron Agent

Vendor &

Standard

Network

Yang

Models

Service

Models &

Directed

Graphs

Adapters

Network DCAE

Network A&AI

Legacy, Tail-F, vSphere, other vendors NetConf, PCE-P, OF, Open Source

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

Service Definition Distribution

Net App Onboarding

High-Level View of ECOMP (Enhanced, Control, Orchestration, Management, Policy)

Service & Network Design

vCE vCE

VNFs vCE

vCE Net Apps VM

Instantiate Multi-tenant

VNFs

Network Adapters Application Adapters

Service Orchestrator

AIC Cloud

AIC Platform Orchestrator OpenStack

Controller Framework

Net Ops

Service Logic

Service Logic

Service Logic

Service Logic

Service Logic

Service Recipe

VNF Adapter

Application Adapter

Neutron Adapter

Policy Creation Framework

Service Logic

Network Adapter

Network Transport Application

SDN-C APP-C

Policy Mgmt.

Infrastructure Portal

Service Orders

OSS/BSS

Service Recipe (TOSCA+) Distribution

OSS

Configuration Mgmt.

VM & Image Mgmt. Fault,

Performance, Usage

ASDC Catalog Discovery

Design

HEAT Templates &

Service Recipes

YANG Definitions, Adapters & VNF

Config.

A&AI

D2 Inventory

Registry

DCAE

Manual Fault & Performance

Exceptions

Analytics

Distribution

Collection

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

Page 9

Service Provider Use Cases

Working with cloud orchestration

• Closed User Group Networks – vCE to vPE network

– vPE is an internal tenant

– vCE is an external tenant per customer

– The network between them crosses tenant boundaries

– Its not shared across all tenants that might be on that node

– Need better support for sets of tenants that can access a shared network (a form of extra-net in our parlance)

• HEAT templates are HOT for us ! – We already use HEAT templates for our controller NBI

and are increasing the number and variety of HEAT resources we will use.

– Beside Neutron ML2, we think there may need to be resources defined both within Neutron and outside of Neutron to meet our needs in advance of OpenStack releases.

vPE

vCE3

vCE2

vCE1

Tenant 1

Tenant 2

Tenant 3

Tenant 4

Neutron Resources

Provider Resources

ML2 VPN LBaS Controller

NBI

HEAT Template

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

Page 10

Service Provider Use Cases (1) Clustering

• Controllers will be in more than one site

• Local, Regional, National

• N-way cluster within a site is sufficient for HA but not disaster recovery

• Need cluster to cluster replication/synchronization

MD-SAL Utilities

• We have an application called the Service Logic Interpreter (SLI) that makes heavy use of MD-SAL and YANG Tools

• The SLI updates the config and operational trees depending on the service, feature and external system interactions (east/west).

• Need support for better “diff” and “merge” of the tree

– Compare config to operational

– Merge operational into config (sync from , synch to)

– Merge this branch into the similar branch in another part of the tree

• Need support for “on data commit” so we can do things before the response goes back.

South West Cluster North East Cluster

Dallas Cluster

Houston Cluster

New York Cluster

White Plains Cluster

Diff

Merge YANG Modeled

Instances

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

Page 11

SDN Controller South-Bound Interfaces/Protocols

Traffic Routing Control with BGP & PCEP

• Use BGP/BGP-Flow-Spec for flow redirection (selection of egress point “BGP-Next-Hop” for a targeted flow) at ingress PE

– Need extension of BGP Flow-spec for support of address families (AFI/SAFI) other than IPv4/v6

– Need controller logic for support of multiple simultaneous “best paths” (BGP Add-Path)

• Use PCEP for optimal routing/re-routing of MPLS LSPs

– Need extension for use with Segmented-Routing

Service Control with NETCONF

• Too stringent to use get-schema

• Need a lighter weight NETCONF integration when vendor supports Netconf but doesn’t have a YANG model

ODL

Netconf 1.1 Device

Netconf Adaptor

Get-Schema

Netconf-Lite Adaptor

Legacy Netconf Device

Provider YANG Model

Vendor Netconf

XML

PE1 PE2

PE3

P1

P2

P3

BGP/BGP-FS PCEP

Page 12

L3 iPE WAN

L3 Multi-Tenancy Models

OVS

Neutron L3 Router

OVR OVR

VM

Neutron L3 Router

VRF

VRF

VRF

VRF

VRF

VRF

VRF

VRF

VRF

L3 iPE WAN

VRF

VRF

VRF

VM VM VM VM VM VM VM

OVS

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

TODAY TARGET

Page 13

L3 iPE WAN

L3 Hub-Spoke Model

OVR

VM

VRF

VRF-H

VRF

VRF

VRF-S

VRF

VM VM VM

© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change

VM VM VM VM

OVR

VRF

VRF-S

VRF

OVR

VRF

VRF-S

VRF

OVR

VRF

VRF-S

VRF

Export Hub RT Import Spoke RT

Import Hub RT Export Spoke RT

Page 14

Q&A

15 © 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. The information contained herein is not an offer, commitment, representation or warranty by AT&T and is subject to change