application-oriented bandwidth and latency aware routing with openflow network

Application-Oriented Bandwidth and Latency Aware Routing with OpenFlow NetworkPONGSAKORN U-CHUPALA , KOHEI ICHIKAWA, HAJIMU I IDA, NAWAWIT KESSARAPHONG, PUTCHONG UTHAYOPAS, SUSUMU DATE, HIROTAKE ABE, HIROAKI YAMANAKA AND EI J I KAWAI

EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 112/22/2014

Agenda1. Introduction

2. Approach

3. Design

4. Evaluation

5. Conclusion and Future Work

EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 212/22/2014

Applications

EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 4

Remote Desktop

Web ServerVoIP

Video Streaming

GameSocial Network

Secure Shell

12/22/2014

Network Properties

EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 512/22/2014

Latency

Bandwidth

Distance

Jitter

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 6

“Requirements”

Remote Desktop

Game

ApplicationsNetwork

Properties

LatencySecure Shell

BandwidthVideo Streaming

Objective

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 7

Align applications’ diverse requirements with

different properties of each path in the network

and route accordingly to improve application

performance and network utilization

Agenda1. Introduction

2. Approach

3. Design

4. Evaluation

5. Conclusion and Future Work

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 9

Categorizing Network Application

BANDWIDTH-ORIENTED

File Transfer

Computation of Big Data

Video/Audio Streaming

LATENCY-ORIENTED

VoIP

Game

Remote Desktop

Secure Shell

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 11

Network DynamicityLink Status Dynamicity

◦ Cable type and condition

◦ Congestion

◦ Traffic engineering policies

Path Status Dynamicity◦ Link status dynamicity is

propagated and multiplied

Direct Network Measurement◦ Calculating available resources by

usage accounting is not accurate

◦ Direct measurement yields more accurate result

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 13

Bandwidth?

Latency?

Bandwidth and Latency Aware Routing

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 14

Monitor bydirect measurement

Agenda1. Introduction

2. Approach

3. Design

4. Evaluation

5. Conclusion and Future Work

EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 1512/22/2014

Architecture1. OpenFlow Network

2. Bandwidth and Latency (BW/LAT) Monitor

3. BW/LAT Aware OpenFlow Controller

4. BW/LAT Controller Supported Application

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 16

1. OpenFlow NetworkOpenFlow allows us to control route specifically for each application

Centralize programmable controller allows us to aggregate information into a single location and reroute any connection as needed

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 17

OpenFlow Switch

OpenFlow Controller

2. Bandwidth and Latency MonitorOverlord* provides near-real-time available bandwidth and currentlatency information of each link

Monitored information is forwarded to OpenFlow controller through REST API

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 18

* N. Kessaraphong, P. Uthayopas, and K. Ichikawa, “Building a Network Performance Benchmarking System Using Monitoring as a Service Infrastructure,” in The 18th International Computer Science and Engineering Conference, 2014, pp. 2–5.

3. BW/LAT Supported ApplicationEach application register its preference to BW/LAT controller through REST API

Preference information includes◦ Flow Identifier: source IP:port, destination IP:port

◦ Preference: MIN_HOP, MAX_BW, MIN_LAT

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 19

Flow Identifier(src_ip, src_port, dst_ip, dst_port)

Preference(MIN_HOP / MAX_BW / MIN_LAT)

(10.0.0.1, 1234, 10.0.0.2, 80) MIN_HOP

(10.0.0.1, *, 10.0.0.2, 80) MAX_BW

(10.0.0.2, 80, 10.0.0.1, *) MAX_BW

(10.0.0.1, *, 10.0.0.2, *) MIN_LAT

(*, *, *, *) MIN_HOP

4. BW/LAT Aware ControllerCentral to the design of BW/LAT aware network

Take◦ Available bandwidth of each link

◦ Current latency of each link

◦ Application preferences

Pre-calculate possible routes for each pair of switches

Allocate route for each application accordingly

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 20

Route Pre-calculation

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 21

Minimum latency path and minimum hop count path is calculated with Dijkstra AlgorithmMaximum bandwidth path is calculated with a slightly modified version of Dijkstra Algorithm

Route Selection

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 25

BW/LAT Controller

Flow Preference Table

(src, *, dst, *) | BW

BW

LAT

HOP

Agenda1. Introduction

2. Approach

3. Design

4. Evaluation

5. Conclusion and Future Work

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 26

Experiments withVirtual EnvironmentMeasure average all-pair bandwidth and latency

Repeat the experiment for 100 times

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 28

Reduce bandwidth and add latencyfor congestion simulation

Average All-pair Bandwidth

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 30

118.0616333

85.768021495.48433667 93.0250646

0

20

40

60

80

100

120

140

All links at 100 Mbps 5 links are selected at random and gotlimited to 40 Mbps (repeated for 100

iterations)

Ban

dw

idth

(M

bp

s)

Traditional Routing Bandwidth and Latency Aware Routing

Average All-pair Latency

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 31

0.362566667

10.946468

0.23111.146959

0

2

4

6

8

10

12

14

16

18

All links at full speed 5 links are selected at random and got10 ms latency added (repeated for 100

iterations)

Late

ncy

(m

s)

Traditional Routing Bandwidth and Latency Aware Routing

Conclusion and Future WorkBandwidth and Latency Aware Routing

◦ Aligning application requirements with network properties using OpenFlow

◦ Bandwidth-oriented and latency-oriented application

◦ Direct network measurement

◦ Route each flow individually according to flow preference

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 33

Evaluation◦ Experiments with Virtual

Environment1. Bandwidth Experiment

2. Latency Experiment

Future Work◦ Experiment with Real-World

OpenFlow Network◦ PRAGMA-ENT (DONE)

◦ More precise monitoring

◦ BW/LAT Orientation Classification

◦ Improve Implementation Performance

12/22/2014 EMERGING ISSUES IN CLOUD WORKSHOP | CLOUDCOM 2014 34