6th SDN Interest Group Seminar - Session5 (131210)

Post on 08-May-2015

128 views 0 download

description

지난 2013년 12월 10일 진행된 오픈플로우코리아와 Open Networking Foundation 이 공동으로 기획한 Open & Virtual Networking Conference 2013의 발표 자료입니다.

transcript

Byungjoon LeeETRI SDN Technology Research Section

bjlee@etri.re.kr

2013/Dec/10

Byungjoon Lee (bjlee@etri.re.kr)

Metro Ethernet Forum Definition– describes a set of functionalities and requirements that architectures

should support in order to fulfill the operational part of network operators

• Scalability

• Reliability

• Quality of Service (QoS)

• Service Management

In order to be applied to carrier grade networks, Openflow must be able to meet these requirements– D. Staessens et al., “Software Defined Networking: Meeting Carrier

Grade Requirements”, Local & Metropolitan Area Networks (LANMAN), 2011 18th IEEE Workshop on.

2

Byungjoon Lee (bjlee@etri.re.kr)

Reliability– The control plane should be always operational

• Should be resilient against targeted attacks

• Should be recovered fast from failures

– Data plane resiliency

• Detect and recover from incidents within 50ms interval(B. Niven-Jenkins et al., “MPLS-TP requirements”, RFC 5654.)

Scalability– The control plane should provide reasonable performance

regardless of the size of underlying network

Reliability and Scalability are so closely related termsif we start to consider scale-out designs for SDN controller

3

Byungjoon Lee (bjlee@etri.re.kr) 4

http://conferences.sigcomm.org/sigcomm/2013/papers/hotsdn/p7.pdf

Byungjoon Lee (bjlee@etri.re.kr) 5

http://onlab.us/tools.html#os

Byungjoon Lee (bjlee@etri.re.kr)

A Spin-off project from Floodlight

Floodlight– Openflow-based SDN Controller from BigSwitch (Open Source)– Supports Openflow 1.0 (and no further)– Adopted widely by research communities

IRIS– Yet another Openflow-based SDN Controller from ETRI – With an IO engine implemented from scratch on top of Java NIO

• 2.5 times faster than Floodlight

– Supports Openflow 1.0/1.3 • Openflow stack generator which produces codes similar to OpenflowJ

– Provides a northbound API which is fully compliant with that of Floodlight(to support 3rd party applications from various research communities)

– Focus on solving the scalability / availability issues of the centralized control

6

Byungjoon Lee (bjlee@etri.re.kr) 7

Guide various stakeholders to easily deploy their innovations to the carrier-grade networking

environment

““

Byungjoon Lee (bjlee@etri.re.kr) 8

Tested on

– OS : Ubuntu 12.04 LTS 64bit(Kernel : 3.5.0-23-generic)

– CPU : Intel Xeon X5690 @ 3.47GHz, 6 physical core(12 threads)

– RAM : 64G

Benchmarking with

– Cbench : single core

– IRIS and Floodlight: use 5 cores

0

500000

1000000

1500000

2000000

2500000

3000000

3500000

4000000

4500000

128 256 512

Floodlight

IRIS

# of switches

# o

f flow

s

Byungjoon Lee (bjlee@etri.re.kr)

http://openiris.etri.re.kr

– Open-source IRIS

– Developer Guide (Wiki Pages)

– Integrated with GitHub

9

Byungjoon Lee (bjlee@etri.re.kr)

OpenflowJ-IRIS– Automated OpenflowJ stack generator

– Also a spin-off project from Floodlight’s Loxigen

– Currently supports Openflow 1.0.1 and 1.3.2

• 1.0.1 is fully tested but 1.3.2 is now being tested and integrated(Thus, 1.3.2 is currently unstable)

– Available in the openflowgenerator branch of OpenIRIS

Loxigen– Another automated Openflow stack generator from Floodlight

– Not compliant with existing Floodlight modules

Why OpenflowJ-IRIS follows OpenflowJ code styles?– To guarantee the easy migration of existing Openflow 1.0.1 modules

to the new platform

10

Byungjoon Lee (bjlee@etri.re.kr) 11

Byungjoon Lee (bjlee@etri.re.kr) 12

Byungjoon Lee (bjlee@etri.re.kr)

Assumptions– A (large) network is possibly split into multiple unit networks

– A unit network is managed by a controller (cluster)

Design– Scalability & Availability for a (large) unit network is

provided by a controller cluster

• A cluster consists of multiple controller instances

• All controller instances are connected by a ‘middleware’

– Interoperability between unit networks is provided by a controller hierarchy

13

Byungjoon Lee (bjlee@etri.re.kr) 14

OF

switch

SA C

ontrolle

rUnit

OpenflowNetwork

IP #1

IP #2

IRISController(Cluster)

Openflow-basedmiddleware (IRIS-HiSA)* security, reliability, scalability

Haze

lcast

Controller instance

Controller instance

Controller instance

Controller instance

Controller instance

Byungjoon Lee (bjlee@etri.re.kr) 15

UnitOpenflowNetwork

UnitOpenflowNetwork

UnitOpenflowNetwork

Controller-to-Super ControllerCommunication channels

Controller

Network Topology

Byungjoon Lee (bjlee@etri.re.kr)

Openflow 1.3.2 support: Dec. 2013

Horizontal Scalability and High Availability for Carrier-Grade Network: Apr. 2014

Cooperation between IRIS controller clusters to guarantee end-to-end packet delivery: Dec. 2014

VTN application for IRIS is on its way to release: Apr. 2014

16

17