Workshop on Prototyping and Deploying Software Defined Exchanges

Chip Elliott, BBN / GENIJune 5, 2014

Workshop Goals

• Follow-on to December 2013 workshop• Develop prototypes / deployment strategies– Software Defined Exchanges (SDXs)– for multi-domain Software Defined Networks (SDNs)– and Software Defined Infrastructure (SDI)

• We expect national / regional deployment of experimental SDXs of varying capabilities(e.g. ‘n’ instances as per December workshop)

Early days for “SDX”

Agreeing on One or More SDX Models

• “Near-term” SDX – pure connectivity– Layer 3 (IP) – e.g. connect AS’s– Layer 2 (Ethernet) – e.g. multi-domain circuits– SDN – connect SDN islands

• “Advanced” SDX – with compute/storage– Connect SDI islands– Compute / storage / network– GENI as an early instance

Workshop Charge

• For both “Near-term” and “Advanced” SDXs . . .• Create slides to form the basis for a workshop report– One or more conceptual SDX architectures– SDX functionality, ideally with one or more exemplar

applications– Identify key issues (e.g. trust, authentication,

authorization, interoperability, testing)– Specify staged set of research / prototyping activities– Provide strawman plan, with level of effort, for

experimenting with national scale SDX deployment

Agenda

• Today (now till 6 PM)– Initial presentations– Two break-outs (Near-term, Advanced) that will each create

slides as above– Reconvene for both presentations / discussion– Break out again for further refinement

• Tomorrow (8:30 – 1:00)– Convene for revised presentations / discussion– Break out to finalize slides– Reconvene for final presentations / discussion– Call for Volunteers

“Advanced SDXs”

and Software Defined Infrastructure

(my perspective)

Where I am coming from - GENI

We’re building out GENI through universities across the US

Fundsin hand

Needfunding

As of 2/2014

Selffunding

Slices and deep programmabilityInstall the software I want throughout my network slice(into firewalls, routers, clouds, …)

And keep my slice isolated from your slice,so we don’t interfere with each other

We can run many different “future internets” in parallel

Slices span many organizational boundaries

Goals: avoid technology “lock in,” add new technologies as they mature, and potentially grow quickly by incorporating existing infrastructure into the overall “GENI ecosystem”

NSF parts of GENI

Backbone #1

Backbone #2

Campus#3

Campus#2

Access#1

CommercialClouds

CorporateGENI suites

Other-NationProjects

ResearchTestbed

Campus

My experiment runs acrossthe evolving GENI federation.

My GENI Slice

This approach looks remarkably familiar . . .

Major trends are converging

Distributed DatacentersNetwork Functions Virtualization (NFV)

SoftwareDefined

Infrastructure

Multi-tenant Datacenters Software Defined Networks

We’re all heading to the same place

Inter-cloudNetwork functions

virtualization

Vnode

WiviFLARE

US Ignite

GENI

Software definednetworks

OfeliaGrid

Rapidly create entire “sliced”cyberinfrastructure / networks on demand

Fast spin new protocols, switching strategies, virtual machines

Clouds

Instantiating services into slices

• Soon each switching point will beable to sustain 10,000 – 100,000 slices

• Can run arbitrary software in each slice

• Decoupling of “service” from infrastructure

Thousands ofparallel slices

“Advanced SDX”

• A) Slice peering point –– Where slices cross administrative domains– An inter-cloud meeting point– But not just connectivity . . .– . . . also includes“for rent” (multi-tenant) compute /

storage in addition to connectivity• B) Service deployment point– Great place to instantiate certain kinds of service,

e.g., middle boxes, load balancers, measurement, content delivery, video translation, etc.

Conceptual sketch

Advanced SDX

Cloud A

Cloud B

Cloud C