Sparc use cases and results requirements and controller architecture
Download
1 / 43

SPARC: use-cases and results Requirements and Controller Architecture - PowerPoint PPT Presentation


  • 237 Views
  • Uploaded on

SPARC: use-cases and results Requirements and Controller Architecture. Wolfgang John [email protected] November 23th 2012. EU FP7 Project Start date: July 2010; End date: November 2012 (1 week ago …) 6 Partners:. Split Architecture for Carrier-Grade Networks. =. ER Budapest.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'SPARC: use-cases and results Requirements and Controller Architecture' - zora


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Sparc use cases and results requirements and controller architecture

SPARC: use-cases and resultsRequirements and Controller Architecture

Wolfgang John

[email protected]

November 23th 2012


Split architecture for carrier grade networks

  • EU FP7 Project

  • Start date: July 2010; End date: November 2012 (1 week ago …)

  • 6 Partners:

Split Architecture for Carrier-Grade Networks.

=

ER Budapest

ER Kista

23.11.2012

SPARC @ ACREO

2


Split architecture for carrier grade networks1

Split Architecture for Carrier-Grade Networks.

  • Mission: Applying Software Defined Networking (SDN) to operator networks

  • Results

    • 23 publications, presentations and demos (GENI engineering conference, World Telecommunication Congress, Globecom, etc.)

    • Standardization impact in ONF and IRTF

  • Key Project Deliverables

    • D2.2: Use cases, requirements, techno-economic study (CAPEX and OPEX), business environment

    • D3.3: Main technical document, study of architecture and required extensions

    • D4.2: Documentation of specific OpenFlow extensions

    • D4.3: Technical documentation of implementation and prototyping activities

    • D5.2: Results of validation and performance evaluation

    • Movie: Summarizing the most important demo’s

  • (Soon) all to find on: http://www.fp7-sparc.eu

23.11.2012

SPARC @ ACREO

3


SPARC.Project Team.

23.11.2012

SPARC @ ACREO

4


Use Case Areas.Focus on Access/Aggregation.

Auto-configuration

Network Management

Service Management

AAA

OAM subsystem

Other Service Platforms (mobile, business, IPTV, VoIP, ...)

BRAS

GPON OLT

Data Centre

RGW

Outdoor DSLAM

Backbone

Access/Aggregation

Business

AGS1

AGS2

LER

LSR

DSLAM

Optical transport

Optical transport

Switch / Router

Business

23.11.2012

SPARC @ ACREO

5


The vision of SPARC is to define, implement & evaluate a scalable carrier class Split Architecture.

Seven objectives of SPARC, with the three main objectives highlighted:

Definition of typical use cases for Split Architecture (D2.2)

Analysis and description of business potential (D2.2)

Definition of Split Architecture blueprint (D3.3)

Extension of the OpenFlow protocol (D3.3 and D4.2)

Development of SPARC prototype (D4.3)

Validation of SPARC prototype (D5.2)

Exploitation of results (papers, demos, presentations, videos)

SPARC.Main Objectives.

23.11.2012

SPARC @ ACREO

6


What is carrier-grade?

Scalability

Support large-scale deployments for carrier-grade networks. E.g. a controller shall be able to control forwarding devices that could count in the order of hundreds.

Availability and Reliability

The availability of networking services shall be equivalent to that of traditional technologies.

Network and service management

The ability to monitor, diagnose and centrally manage the network

Quality of Service

Allowing the assurance of SLAs using QoS guarantees for service attributes (e.g. rate, loss, delay) and service isolation

Support for legacy technology

allowing deployment of new services in parallel to existing legacy protocol stacks

SPARC Objectives.Carrier-grade.

23.11.2012

SPARC @ ACREO

7


1

2

SPARC Requirements and Study Topics.Overview.

23.11.2012

SPARC @ ACREO

8


Intro to SplitArchitecture.Evolution of SDN.

23.11.2012

SPARC @ ACREO

9


Intro to splitarchitecture software defined networking
Intro to SplitArchitecture.Software-Defined Networking.

business applications

SDN

control

network services

software

data

data

data

OpenFlow-based SDN model, defined by the ONF

23.11.2012

SPARC @ ACREO

10


Intro to splitarchitecture software defined networking1
Intro to SplitArchitecture. Software-Defined Networking.

business applications

business applications

control program

hypervisor

SDN

network operating

control

network services

system

software

data

data

data

data

data

data

  • OpenFlow-based SDN model, including a network hypervisor

    • Virtualization and abstraction layer

    • Position of hypervisor (below or above NOS) debatable

23.11.2012

SPARC @ ACREO

11


Intro to splitarchitecture the splitarchitectur e concept
Intro to SplitArchitecture.The SplitArchitecture concept.

business applications

control program

hypervisor

network operating

system

data

data

data

  • SPARC SplitArchitecture

    • Again a split between data and control plane

    • Forwarding and processing in data plane considered separately

23.11.2012

SPARC @ ACREO

12


Intro to splitarchitecture the splitarchitectur e concept1
Intro to SplitArchitecture.The SplitArchitecture concept.

hierarchical controller

concept

OpenFlow

forwarding

forwarding

forwarding

processing

processing

processing

  • SPARC SplitArchitecture

    • Again a split between data and control plane

    • Forwarding and processing in data plane considered separately

23.11.2012

SPARC @ ACREO

13


Intro to splitarchitecture the splitarchitectur e concept2
Intro to SplitArchitecture. The SplitArchitecture concept.

hierarchical controller

concept

network

management

system

OpenFlow

forwarding

forwarding

forwarding

processing

processing

processing

  • SPARC SplitArchitecture

    • Initial considerations on the role of network management

23.11.2012

SPARC @ ACREO

14


Intro to splitarchitecture the splitarchitectur e concept3
Intro to SplitArchitecture. The SplitArchitecture concept.

hier

.

control

plane

n

+

1

app

OpenFlow

filtered

,

hierarchical controller

abstract

hier

.

control

plane

n

app

concept

network

view

OpenFlow

hier

.

control

plane

n

-

1

app

OpenFlow

forwarding

forwarding

forwarding

processing

processing

processing

network

management

system

  • SPARC SplitArchitecture

    • Recursively stacked control planes

    • Abstracted network view ot higher planes via OpenFlow Interface

23.11.2012

SPARC @ ACREO

15


Intro to splitarchitecture the splitarchitectur e concept4
Intro to SplitArchitecture. The SplitArchitecture concept.

hier

.

control

plane

n

+

1

app

OpenFlow

filtered

,

hierarchical controller

abstract

hier

.

control

plane

n

app

concept

network

network

view

OpenFlow

management

system

hier

.

control

plane

n

-

1

app

OpenFlow

forwarding

forwarding

forwarding

processing

processing

processing

  • SPARC SplitArchitecture

    • Recursively stacked control planes

    • Abstracted network view ot higher planes via OpenFlow Interface

23.11.2012

SPARC @ ACREO

16


Hierarchical controller design goals
Hierarchical controller.Design goals.

  • Goals for a carrier-grade control layer:

    • Increase flexibility

      • Adapt control architecture to use-cases and business models

      • Distribute the control layer to adapt to network capabilities

      • Allowing both cross-layering and strict layering of control logic

    • Increase scalability

      • Operator networks are complex -> divide and conquer the problem space

    • Allow smooth migration

      • Supporting control protocol operations with legacy domains

23.11.2012

SPARC @ ACREO

17


Hierarchical controller.

  • Current situation: monolithic network elements

CP peers talk OSPF, IS-IS, STP, etc.

CP

CP

CP

DP

DP

DP

FWD engine (DP) and control logic (CP) sit jointly on a single network element

23.11.2012

SPARC @ ACREO

18


Hierarchical controller.Splitting Ccontrol and forwarding.

  • Step 1 of SDN: Splitting control from data plane

But still the old situation  the CP peers control a single network element and use the old protocol for sharing state as before (OSPF, IS-IS, LDP, STP, …)

CP

CP

CP

OpenFlow

DP

DP

DP

23.11.2012

SPARC @ ACREO

19


Hierarchical controller.Centralizing control.

  • Step 2 of SDN: Centralize control plane

Centralized control logic

OpenFlow

DP

DP

DP

Benefit: no complex protocols for sharing state among CP peers required any more.

23.11.2012

SPARC @ ACREO

20


Hierarchical controller.

OpenFlow as northbound interface.

  • SPARC Idea #1: Exposing services via OpenFlow again!

OpenFlow

Mgmt API

Centralized control logic

OpenFlow

DP

DP

DP

  • Domain acts like a backplane within the emulated data path element.

23.11.2012

SPARC @ ACREO

21


Hierarchical controller flow space registration
Hierarchical controller.Flow space registration.

  • SPARC Idea #2: Integrate FlowVisor functionality into controller

OpenFlow

OpenFlow

OpenFlow

Flowspace Mgmt

Mgmt API

Centralized control logic

OpenFlow

DP

DP

DP

Higher layer controllers subscribe to parts of the flowspace (i.e. slices)

Replace the pub/sub interface (as in NOX) with flowspace reservation

23.11.2012

SPARC @ ACREO

22


Hierarchical controller.Stacked control planes.

  • Result: Hierarchical structuring of control planes!

Requires OpenFlow protocol extensions for management of:

* Flowspaces: allow plane (n) to register a slice of the flowspace on (n-1)

* Transport endpoints: allow plane (n) to control (CRUD) logical ports on (n-1)

23.11.2012

SPARC @ ACREO

23


Hierarchical controller.Example: protocol stack.

  • Example: Modular layering of a controller

SMTP

APP-CTL

SMTP

IPv4

IP-CTL

IP

IPv4

IPv6

ETH

ETH

ETH

ETH

ETH

ETH-CTL

PHY

PHY

PHY

PHY

OpenFlow

An IP router  use case: build an IPv4/IPv6 router

An SMTP router  use case: build a Mail Transport Agent (MTA)

=

DP

PHY-CTL

The northbound interface is OPENFLOW!

  • IP-CTL  emulates a single IP layer

  • ETH-CTL  emulates Ethernet host stacks

  • PHY-CTL  is a data path element

8/20/2014

23.11.2012

SPARC @ ACREO

24


Considerations on network management the splitarchitectur e concept
Considerations on network management. The SplitArchitecture concept.

hier

.

control

plane

n

+

1

app

OpenFlow

filtered

,

hierarchical controller

abstract

hier

.

control

plane

n

app

concept

network

network

view

OpenFlow

management

system

hier

.

control

plane

n

-

1

app

OpenFlow

forwarding

forwarding

forwarding

processing

processing

processing

  • SPARC SplitArchitecture

    • Initial considerations on the role of network management

23.11.2012

SPARC @ ACREO

25


Considerations on network management.Control vs. management.

  • Boundary between management and control is blurred

    • Management functions are important in SplitArchitecture

Functionality

(Increased control granularity)

Today’sNetworkManagement

SplitArch/SDN

Automation

(Program driven, automatic adjustmentof the network)

Speed

(Beyond human time-scale)

23.11.2012

SPARC @ ACREO

26


Which NM functions to embed in a controller?

Q1: Already an essential part of SplitArchitecture/SDN control? If not,

Q2: Facilitates timely and automated configuration and flow steering? If so,

Q3: Possible with open and standardized extensions to the OF / OF-Config protocols? (no bloating with vendor or device specific models)

Apply this question to NM function according the TMN/FCAPS definitions of network management

Considerations on network management.Assessment of functions.

23.11.2012

SPARC @ ACREO

27


Considerations on network management.SPARC assessment example.

23.11.2012

SPARC @ ACREO

28


control plane B

control plane A

hierarchical controller

concept

network

management

system

OpenFlow

e.g. optical devices

forwarding

forwarding

forwarding

processing

processing

processing

Control and management architecture.Summary.

  • Result: A recursive and modular control plane architecture

23.11.2012

SPARC @ ACREO

29


Sparc use cases and results sparc prototype implementations

SPARC: use-cases and resultsSPARC prototype implementations

Wolfgang John

[email protected]

November 23th 2012


Seamless MPLSaka carrier grade packet transport

  • Seamless MPLS

    “…architecture which can be used to extend MPLS networks to integrate access and aggregation networks into a single MPLS domain…”

    draft-leymann-mpls-seamless-mpls-03

Forklifting access/aggregation to MPLS may be too expensive

 apply SDN principles for Seamless MPLS

23.11.2012

SPARC @ ACREO

31


OpenFlow

Service

OSPF, LDP,RSVP-TE, BGP …

IPMPLS

IPMPLS

IPMPLS

Switch

Switch

Switch

GW

Access

IP Edge

Seamless MPLS implementation.Basic concept.

APP (CP)

APP (CP)

Central element

SPARC Controller

ProtocolProxy

Aggregation

IP/MPLS core

CP

CP

CP

CP

CP

CP

CP

CP

23.11.2012

SPARC @ ACREO

32


OFSwitch

OFSwitch

OFSwitch

OFSwitch

OF

Edge

OF

Edge

CoreMPLS

CoreMPLS

OFSwitch

CoreMPLS

Video

WEB

Client

Client

Seamless MPLS implementation.Essential Functionalities.

NNI

OSPF, LDP

MPLSCP

MPLSCP

SPARC Controller

MPLSCP

OSPF

End-to-end MPLS CTRL

Protocol Proxy

Discovery

OpenFlow MPLS CTRL

LDP

NOX Kernel

Clients

Services

IP/MPLS core

OPENFLOW MPLS Aggregation

Topology discovery of MPLS aggregation & core

Management of MPLS LSPs in aggregation

Signal end-to-end MPLS LSPs

Provision MPLS transport services (e.g. Pseudowire)

23.11.2012

SPARC @ ACREO

33


MPLSCP

MPLSCP

MPLSCP

OFSwitch

OFSwitch

OFSwitch

OFSwitch

OFSwitch

OF

Access

OF

Access

CoreMPLS

CoreMPLS

CoreMPLS

Video

WEB

Clients

Services

OPENFLOW MPLS Aggregation

IP/MPLS core

Client

Client

Seamless MPLS implementation.1. Topology disovery of MPLS aggegation & core.

OSPF

Combine OpenFlow and legacy topology discovery information

Protocol Proxy

Discovery

NOX Kernel

23.11.2012

SPARC @ ACREO

34


MPLSCP

MPLSCP

MPLSCP

OFSwitch

OFSwitch

OFSwitch

OFSwitch

OFSwitch

OF

Access

CoreMPLS

OF

Access

CoreMPLS

CoreMPLS

Video

WEB

Services

Clients

OPENFLOW MPLS Aggregation

IP/MPLS core

Client

Client

Seamless MPLS implementation.2. Management of MPLS LSPs in aggregation.

SPARC Controller

  • Installs PtP, MPtP and PtMP tunnels

  • Reconfigures them upon topology changes

Discovery

OpenFlow MPLS CTRL

NOX Kernel

23.11.2012

SPARC @ ACREO

35


MPLSCP

MPLSCP

MPLSCP

OFSwitch

OFSwitch

OFSwitch

OFSwitch

OFSwitch

OF

Access

CoreMPLS

OF

Access

CoreMPLS

CoreMPLS

Video

WEB

IP/MPLS core

OPENFLOW MPLS Aggregation

Services

Clients

Client

Client

Seamless MPLS implementation.3. Signaling end-to-end MPLS LSPs.

  • Topology synchronization with OSPF

  • Spans end-to-end MPLS with LDP

    • Nests them in MPtP tunnels in aggregation

SPARC Controller

OSPF

MPLS Tunnel

End-to-end MPLS CTRL

Protocol Proxy

Discovery

OpenFlow MPLS CTRL

LDP

NOX Kernel

MPLS Tunnel

23.11.2012

SPARC @ ACREO

36


Split bras

Split-BRAS

  • Split-BRAS

    BRAS is complex and expensive integrated node since it must handle all subscriber traffic, hence it must cope with continuously increasing capacity need, this means increasing cost

Traditional way of deploying BRAS will not scale

 apply SDN principles to distribute BRAS functionality

23.11.2012

SPARC @ ACREO

37


IP Edge

RAWBRAS

RAWBRAS

BRAS

AGS 2

AGS 2

AGS 1

AGS 2

AGS 1

AGS 1

AN

AN

AN

RADIUS

RADIUS

RADIUS

Client(RGW)

Client(RGW)

Client(RGW)

Split BRAS.Basic concept.

Common residential model today with PPPoE

Split Control and raw forwarding

Roll raw BRAS towardAccess Node

BRAS CTRL

BRAS CTRL

Aggregationspecific tunnel

Control session

Control session

PPPoE tunnel

PPPoE tunnel

Control session

PPPoE tunnel

23.11.2012

SPARC @ ACREO

38


Split BRAS.Architecture Blueprint.

control plane A

control plane B

Applying a recursive control plane

L3 fwd engine

IPoE

PPP & PPPoE

data path element

L2 fwd engine (disabled)

EoPhy

EoPhy

23.11.2012

SPARC @ ACREO

39


RAWBRAS

GW

Access

IP Edge

Split BRAS.Concept.

Central element

SPARC Controller

BRAS CTRL

Relay PPP Request

Aggregation

IP/MPLS core

Ethernet

IP/MPLS

23.11.2012

SPARC @ ACREO

40


RAWBRAS

Switch

Switch

Switch

GW

Access

IP Edge

Split BRAS.Flexible placement.

Central element

SPARC Controller

BRAS CTRL

Aggregation

IP/MPLS core

PPPoE (over PWE)

23.11.2012

SPARC @ ACREO

41


RAWBRAS

RAWBRAS

Switch

Switch

Switch

GW

Access

IP Edge

Split BRAS.Increased scalability.

Central element

SPARC Controller

BRAS CTRL

Aggregation

IP/MPLS core

PPPoE (over PWE)

IP/MPLS

23.11.2012

SPARC @ ACREO

42


Summary of SPARC OpenFlow Protocol Extensions implemented.

  • MPLS

    • Parsing MPLS headers

    • Basic MPLS actions: push/pop header, change TTL, …

  • PPP & PPPoE

    • Terminate PPP & PPPoE tunnels

  • Connectivity Check

    • Pro-active monitoring of contuity with probe packets of MPLS-TP BFD format

    • Used for monitoring adjacency and flow pairs (bidirectional path)

  • OAM & Protection Notification

    • About state changes of monitoring entities

    • About protection events

  • Pseudo Wire

    • Support for Ethernet Pseudo Wire over MPLS PSN

    • Not full implementation (i.e., no sequence numbers)

23.11.2012

SPARC @ ACREO

43


ad