SDN網路機制...

Wireless Networks and Evolutional Communications Laboratory

SDN網路機制 於跨雲端運算之應用

陳俊良 台灣科技大學電機系

• Introduction

• SDN Industry Overview

• SDN Development Challenge

• Cloud Computing with SDN Networking

• Inter-Cloud Computing with SDN Networking

• Conclusion

2

3

4

• Introduction

• SDN Industry Overview

• SDN Development Challenge

• Cloud Computing with SDN Networking

• Inter-Cloud Computing with SDN Networking

• Conclusion

5

6

OpenFlow

Techniques: 1. Separate data and

control planes 2. Standard interface

Advantages: 1. Easy to control flow 2. Open source

Open network standard

Techniques: 1. Open networking

specification 2. Standard API

Advantages: 1. High utilization of

current devices 2. Rapidly deploying

Overlay network

Techniques: 1. Network virtualization

solution 2. Overlay technique

Advantages: 1. Connect the physical

network 2. Flexibly deploying

NFV(Network Function Virtualization)

Techniques: 1. Software-defined

functions 2. Single platform

Advantages: 1. Provide service rapidly 2. Cost down

7

Service/ISP

Solution /Device Provider

Chip Provider

IC Design Software

Development End-Device Production

Operators & Service

Provider

8

Intel, Broadcom, Freescale, TI, Marvell, MTK, Centec Networks…

Microsoft, IBM, VMware, Oracle, Vello…

Cisco, ALU, NEC, Juniper, HP, Dell, Ericsson, NETGEAR, Brocade, Big Switch, Extreme Networks, Hitachi, IP Infusion, Spirent, Pica 8, Huawei, ZTE…

Verizon Wireless, DT,NTT, Google, Facebook, KDDI, SK Telecom, Baidu …

Some manufacturers

provide commercial products.

Most of developers

adopt OpenFlow standard.

Some manufacturers

provide commercial products.

Google is the successful case

and Verizon field-test.

8

9

10

Board Members

From: Open Networking Foundation

11 From: OpenDayLight

12

Controller

Flow Table

OpenFlow Channel

Openflow

Switch

Group Table

Flow Table

OpenFlow Protocol

Pipeline

Main components of a flow entry in a flow table.

Match Fields

Priority Counters Instructions Timeouts Cookie

© 2012; The Open Networking Foundation Spec-1.3.1

git clone git://noxrepo.org/noxcore cd noxcore/ ./boot.sh mkdir build/ cd build/ ../configure --with-python=yes make make check

NOX installation and configuration commands

SDN controller

switch

control plane

data plane

OpenFlow

switch

control plane

data plane

switch

control plane

data plane

switch

control plane

data plane

SDN controller

switch

data plane

switch

data plane

switch

data plane

switch

data plane

switch

data plane

switch

data plane

OpenFlow

OpenFlow

Distributed Control Hybrid Control Centralized Control

switch

control plane

data plane

switch

control plane

data plane

switch

control plane

data plane

switch

control plane

data plane

13

14

15

16

17

18

SDN Product Strategy Solution/Application

SDN Device

Cisco: 3560-X, 3750-X series HP: 2920, 3500, 3800, 5400,6600, 8200 series. IBM: RackSwitch G8264 NEC: ProgrammableFlow Family Brocade: CES 2000, VDX 8770, MLX series Pica8: 3290, 3295, 3780, 3920 series

Network Virtualization VMware: VMware NSX Microsoft: Hyper-V 3.0

SDN Application

BigSwitch: FloodLight Cisco: One Platform Kit (OnePK) HP: HP Open Ecosystem Google: Traffic Engineering Redware: DDoS Protection

• Introduction

• SDN Industry Overview

• SDN Development Challenge

• Cloud Computing with SDN Networking

• Inter-Cloud Computing with SDN Networking

• Conclusion

19

20 From: OpenDayLight

21

From : Google

22

From : Google

Google’s WAN is organized as two backbones : • I-scale network : Carries user traffic; • G-scale network : Carries traffic between datacenters. And G-scale network in which Google has deployed an OpenFlow powered SDN solution.

23

From : Google

24

From: HP

25 From: HP

26 From: HP

Network Virtualization

27

Rules

From: Cisco

28

From : Data Center Journal

Attack Information

29

Microsoft

NEC

From : NEC

30

From : A10

31

eNodeB 3

eNodeB 1

eNodeB 2

Internet and Other IP Networks

UE 2

UE 1 SDN Switch

Middlebox

Phase1:

• SDN provides fine grained packet classification and flexible routing.

• A key factor in middlebox deployments is to balance the processing load to avoid overload.

Phase2:

SDN switch can support some middlebox functionality.

Path setup for UE by SDN controller

From :Bell Labs

• Introduction

• SDN Industry Overview

• SDN Development Challenge

• Cloud Computing with SDN Networking

• Inter-Cloud Computing with SDN Networking

• Conclusion

32

Products

materiality Controller’s performance

issue

Potential technical

vulnerabilities

Supplier

unclear

strategy

Few

use cases

Different manufacturers’

integration

Network equipment

replacement

33

• Introduction

• SDN Industry Overview

• SDN Development Challenge

• Cloud Computing with SDN Networking

• Inter-Cloud Computing with SDN Networking

• Conclusion

34

Data Plane(Specialized Hardware)

Control Plane

Data Plane(Forwarding Abstraction)

Control Plane

Network OS

Controller

(NetworkOS)

Separation

a.3 single physical network

b.3 Multiple, isolated, virtual networks

Network OS

Client

Client

Server

Server

Mobiltye.g., Content Routing

Energy efficient forwarding

SDN

Languages

a.1 control and data planes tightly-coupled b.1 control and data planes separated

a.2 distributed control of network equipments

SDN

Apps

b.2 centralized, programmable control of network equipments

a. Current networking technology b. SDN networking technology

Source: Network Virtualization and Service Awareness Properties of FNs in ITU-T Q.21/SG13

Control plane and data plane separate

Centralized and programmable controller

Virtualization of the underlying network

“On-box”

Legacy SDN

Legacy Networks vs. SDN Networks

35

36

• Packet Capture • Packet Filtering • Packet Classification • Switching/Routing

• Security • SLA • Slice • …

37

Monitor and manage the devices User

Node Controller

VM

VM

VM

VM

192.168.1.3

Node Controller

VM VM

192.168.1.4

Node Controller

VM

192.168.1.5

OpenFlow Switch NOX Controller

Secure Chanel Flow Table

1. Packets Passing, Lookup, Forwarding

2. Match fields 3. Counters 4. Instructions

Mission: VM Deployed - Load Balancing

38 © 2012; The Open Networking Foundation Spec-1.3.1

Packet In Start at table 0

Match in table n?

Table miss Flow entry

exists?

Packet In Start at table 0

Update counters Execute instructions: • update action set • update packet/match set fields • update metadata

Yes

No

No

Goto- Table n?

Execute action set

No

Yes

Figure : Flowchart detailing packet flow through an OpenFlow switch.

Yes

Flowchart

39

Virtual Machine Deployment Mechanism

40

VM Placement Method： • Round Robin • Greedy • Network Utilization • …

Cloud Controller

Cluster Controller

Storage Controller

Walrus

Agent

Controller

Node Controller 192.168.1.5

Node Controller 192.168.1.3

VM VM

VM4 Node Controller

192.168.1.4

VM1

VM3

VM2

VM

Bottleneck

Node Controller 192.168.1.5

Node Controller 192.168.1.3

VM3

Node Controller 192.168.1.4

VM

VM

VM2 VM4

VM

VM1

Cloud Controller

Cluster Controller

Storage Controller

Walrus

Agent

Controller

• Introduction

• SDN Industry Overview

• SDN Development Challenge

• Cloud Computing with SDN Networking

• Inter-Cloud Computing with SDN Networking

• Conclusion

41

42

Inter-Cloud Computing

Cloud A Cloud B

Services Inter-Changing

Virtual Machines Dynamic Migration

Different Performance Orientation

• The link Availability becomes new performance indicator • Systems need policies implementation enabling intelligent routing

System Overview

User

1.User Request Service

3.Heavy load

2. Load analysis

4.Trigger Event 5.Request / Transmit

status 7.Redirect

Loading: CPU, Memory….

6. Light load

43

44

SDN Operation

Balance Monitor

SLA Management

CSLA Scheduling

Resource Allocation

In-Cloud

Data Collection

Performance Analysis

Balance Trigger

Data Transmission

1. Transmit cloud status

2.Transmit the result

3. Trigger the event

4.Transmit cloud’s status &

trigger event

7.Transmit the parameters

8.Transmit the SLA information

9.Balancing the routers’ loading

5.Request the other clouds’ statuses

6.Transmit the information

If there is no appropriate route, it will trigger the event to balance trigger

Task

Sequence Diagram of Load Balancing Module

45

The Concept of System Operation & Architecture

46

Testbed Environment

47

SDN Controller

Cloud A

Cloud D

OFS1

OFS5 OFS3

OFS4

OFS2

Cloud E

Cloud C

Cloud B

Cloud B

Schematic Diagram

48

Cloud A Loading Analysis

49

Cloud B Loading Analysis

50

Throughput Analysis

51

Link Utilization

• Introduction

• SDN Industry Overview

• SDN Development Challenge

• Cloud Computing with SDN Networking

• Inter-Cloud Computing with SDN Networking

• Conclusion

52

53

54

55

56