Smarter Cities on Open SDN Networks

© 2015 Open Networking Foundation

Smarter Cities on Open SDN Networks

Dan Pitt, Executive Director

www.opennetworking.org

ONF-BIO Workshop

July 7, 2015 Bristol


SDN drivers

2

Mobile

Computing

Hyperscale, Virtualized

Data Centers

On-Demand Network Services

Internet of Things

TSUNAMI OF DATA


Traditional networking limitations

3

Not Cost-Effective

• CAPEX

• OPEX

Not Agile Enough for On-Demand

• Time-to-market

• Rapid service provisioning

Not Designed for Virtualization or Cloud

• East-west traffic support

• Bottleneck for server virtualization

Worst of all: vendors call the shots


The real force behind SDN

• Orchestration

• Automation

• Centralized policy mgt.Save Money

• Service creation

• Revenue acceleration

• Customer customizationMake Money

• We define what the network does for us, not the vendors!

• Democratization of technology

Operator Control!

This is why ONF exists:

To empower anyone who operates a network


Urbanization & its discontents

• The world’s population: consolidating

in urban areas, 84% by 2050

• High-density challenges: scale

scarce resources, ensure urban

health & safety while protecting the

environment

• Cities: make at least as smart as the

smart phones in our pockets


Smarter cities for an urban species

• Smart public lighting systems grow

brighter as pedestrians approach &

smart thermostats readjust as people

leave the room

• Smart home cameras alert emergency

response, give first responders traffic

assistance, and pre-alert emergency

room personnel

• Smart driverless cars optimize traffic

routes & reduce accidents


Smarter cities communication grid

• Adaptive & Programmable

– Enhance resiliency for disaster management

– program security based on devices & applications

– reduce latency & prioritize traffic for public safety

alerting.

• Open & Standards-based

- Platform & Vendor agnostic


Infrastructure Layer

Control Layer

Application Layer

Business Applications

AP

I

Network Services

AP

I

AP

I Common APIs• Diverse applications• Open service models

Standard Protocol

Open Platform• Common framework• Multi-vendor software• Network abstractions

• Standard, programmatic• Common data models

Open, standard I/Fs for innovation

8

“Open” = Not controlled by a single party


ONF in general

9

We are:

• A non-profit supported only by member dues

• Standardizing as little as necessary

• Advocates of experimentation, coding, open-source

To us, SDN is:

• Physical separation of forwarding and control

• Simplification of networking devices

• Creating value through operator software

To us, ONF success means:

• SDN products

• SDN-based services

• Best-of-breed market, absent vendor lock-in


ONF in 2015

10

• Open SDN

– NBIs, information models, security

– Partnerships: OCP, OIF, ODL, ONOS, OPNFV, ETSI NFV, OpenStack

• OpenFlow

– Optical extensions, wireless extensions

– TTPs, PIF

– Interoperability, conformance, performance

• Open Source

– OpenSourceSDN.org

• 2 NBIs

• PIF IR

• OF-Config/OVSDB

• Atrium

• Orchestration/automation/LB?

– Community projects


ONF software leadership council

• Lightweight governance, stewardship, wisdom

Jono Bacon

XPRIZE

Foundation

Stuart Bailey

Infoblox

(Chair)

Jasson Casey

Flowgrammable

Saurav Das

ONF

Bithika

Khargharia

Extreme

Networks

Inder Monga

ESnet

Carl Moberg

Cisco

Dave Lenrow

HP

Steve Noble

NetDef

Ben Pfaff

VMware

Rob Sherwood

Big Switch

(Vice Chair)

Dan Talayco,

Self-Referential

Software


Support multiple

controller frameworks

Adopt existing open source

Incorporate feedback into new projects

Built on ONOS now, ODL

coming

Available at OpenSourceSD

N.org

12

MissionProvide an open source SDN distribution to accelerate open

SDN evaluation and adoption of OpenFlow HW switches

Qualifiers

Atrium overview


13

Problem: SDN applications dependent on switching pipelines

Solution: Flow Objectives I/F– foster application portability on any switch

Problem: SDN controllers dependent on switching pipelines

Solution: Switch plugins – enable stack to run over hardware from multiple vendors

Problem: OpenFlow switches don’t interoperate

Solution: Integration – drive common OpenFlow 1.3 features from vendor-neutral controller

Problem: Open source SDN components are typically standalone

Solution: Integration – provide an integrated distribution consisting of open source components

Atrium objectives


Network operator impact

14

Appeal to many operator types

Lower barrier to SDN adoption

Expand horizontally (controllers) and vertically (applications)


Vendor impact

15

Provide rapid deployment of complete SDN solution

Demonstrate controller & application compatibility, switch interoperability

Build market confidence in HW OpenFlow


The Smart Cities impact:

A collaborative exploration with Bristol Is Open

16

• Contribute to the BIO Smart Cities Stack

for rapid creation of new SDN services for

consumption by Smart City app developers

• Feed experience back into OpenFlow &

Atrium to support innovative Smart City

applications, use cases

• Expand adoption globally based on the

Bristol blueprint

ONF: accelerating the adoption of open SDN

Technology

Smarter Cities on Open SDN Networks