Mechanisms for the Automated Setup of Software …...Mechanisms for the Automated Setup of Software-Defined Networks Diederich Wermser, Jannis Ohms, Olaf Gebauer (Ostfalia Hochschule)

Mechanisms for the Automated Setup of

Software-Defined Networks

Diederich Wermser, Jannis Ohms, Olaf Gebauer (Ostfalia Hochschule)

Sven-Ove Wähling (Netzlink Informationstechnik GmbH)

21. VDE/ITG Fachtagung „Mobilkommunikation“

11.-12.05.2016 – Osnabrück

ZIM - INAASCA - Integrated Network-as-a-Service Solution as Part of Cloud IT Application Portfolio

Technologies and Partner•OpenStandard Communication Protocols

•SDN – Software Defined Networks, OpenFlow, OpenStack

•Internet of Things (IoT), Industrie 4.0, OPC UA

•NGN: IMS (IP Multimedia Subsystem)

•Voice over IP (VoIP), Unified Communications (UC)

•Session Initiation Protocol (SIP), Presence Service

•Web RealTime Communication (WebRTC)

•All-IP Mobil Communication, LTE

•Critical Communications, TETRA – LTE

•Soft-PBX: SipXecs, OpenUC, Asterisk, FreeSWITCH

•Workflow-Integration of RTC

•Quality-of-Service-Mechanisms (QoS) for RTC

•IntServ, DiffServ, MPLS, IPv6

•Routing, Load Balancing, NAT

•Analysis of „VoIP-Readiness“, Security in VoIP-Systems

•Test of IP-based Communication Systems

•Conformity Tests, TTCN-3

•Interoperability Tests, Stress Tests

•Development / Integration of OpenStandard Network Elements

•Contributions to Open Source Projects

Inhalt

•Motivation

•Automated Setup in NaaS context

•Requirements of Automated Bootstrapping

•Alternative Configuration Protocols

•Architecture for the Configuration Point

•Future Work

319.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück

Cloud computing makes IT applications efficiently!

And the networks?

Complete networks automatically set up from the cloud?

First establishment of network elements according plug'n'play manner?

Standardized network configuration via a customer assigned NaaS server?


Cloud-Layer nach der ITU-T

519.05.16

Quelle: ITU-T, „Focus Group on Cloud Computing, Part 5: Cloud Security, Version 1.0,“ 2012.

21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück

Automated Setup in NaaS Context


Cloud Shop

Network-Offer(NaaS-Control)

Datacenter

...

IT-Application-Offer(SaaS/CaaS-Control)

VoIPERP

Customer Specific NaaS-ServerCPS

Virtual Tenant LAN WANCustomer Location

LAN

Cloud IT-Application

ERP = Enterprise Ressource PlanningVoIP = Voice over IPCPS = Cyber Physical Systems



WAN

SDN-Controller

Datacenter

Northbound-IF

Southbound-IF

SDN-Switch Router Applicationserver Client

Customer Location

Openflow Configuration Protocol

SDN-Controller(Client)

Northbound-IF

SDN-Application

Southbound-IF

Integrated Cloud Service Control

IT-Service Control

Configuration Point

SDN-Application

IT

RTC

...

NaaS-Server


19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 8

Preparation

Server-on-state

Cloud-DashboardSaaSSDN-Apps

Cloud-Datacenter Customer-Area

Phase NaaS-Server

Order

Kunde Customer Site

Selection of SaaS and NaaS-Services

Offer (Including Exact Cost)

Verification

Creation of a logical Network Diagram

Order

Setting up the Tenant

Delivery of Equipment

Installation & Cabling

Bootstrapping of SDN-Switches

Setting up the Tenant

Configuration of the SDN-Apps

Pairing

Setting up Proactive Flows

Service Provision Using Proactive Flows

Requirements of Automated Bootstrapping

9

To be able to automate the initial setup of the SDN infrastructure, the respective

protocols must fulfill the following set of requirements:

•A protocol should work out of the box•Implies that the protocol is enabled by default

•Implies that the protocol does not need any additional manual configuration to function

•A protocol should be vendor agnostic•Network elements of different vendors should be interoperable in a heterogeneous scenario

•This avoids the possibility for vendor lock-ins

•A protocol should be an open standard•Easily to implement

•benefits the development of software libraries and APIs

•A variety of switches should support the protocol, this includes virtual and physical

switches

•Manual work should only include the cabling•can be done by nearly anyone


Alternative Configuration Protocols

10

Importan

ceO

F

-

C

o

n

fi

g

SSH Z

T

P

Seriell N

E

T

C

O

N

F

15 - KO - -

K

O

-

60,00% -

K

O

-

- KO -

Vendor support 6 1 Rarely supported 1

0

Standard 4 only

implemented by

bare metal

systems or in

premium

hardware

1

0

Standard 1

0

Widely supported

Useable for

bootstrapping

KO N Needs an IP

address the

availability of

DHCP is not

defined

N Needs an IP

address the

availability of

DHCP is not

defined

J Combination of

DHCP and

TFTP

specifically

designed for the

boot strapping

N Needs

manuell

wiring

N Needs an IP

address the

availability of DHCP

is not defined

Standardisation 3 1

0

ONF Standard 3 Depends on the

used NOS

5 Depends on the

used NOS

2 Depends on

the used

NOS

8 Depends on the

used NOS

License Cost 3 1

0

None 1

0

None 1

0

None 1

0

None 1

0

None

Cost of implementation 3 2 High 4 Medium 7 Medium 1 High 1 High19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück



WAN

SDN-Controller

Datacenter

Northbound-IF

Southbound-IF

SDN-Switch Router Applicationserver Client

Customer Location

Openflow Configuration Protocol

SDN-Controller(Client)

Northbound-IF

SDN-Application

Southbound-IF

Integrated Cloud Service Control

IT-Service Control

Configuration Point

SDN-Application

IT

RTC

...

NaaS-Server

Alternative Configuration Protocols


Powering on the SDN-Switches

IP-Configuration

Switch configuration

Registration on the SDN-Controller

Topology detection

Openflow configuration

Server-on-state

SDN-SwitchConfiguration Point

Hello

DHCP-Request

Registration on the SDN-Controller

OFDP-Request

OFDP-Response

Topology Update

OpenFlow Configuration (Reactive & Proactive)

SDN-Controller

Cloud-Datacenter Customer-Location LAN

Phase NaaS-Server

Pre-loading Config-Files

DHCP-Reply

TFTP-Request

TFTP-Reply

Initial Setup of Static Flows

Architecture for the Configuration Point


Hardware

OS (Linux)

CP-ApplicationTFTP-Deamon- z.B.: Ironic ?

- (verfügbar über Paketverwaltung)

Configuration Point (CP)

DHCP-Deamon- z.B.: Ironic ?

- (verfügbar über Paketverwaltung)

Legende:

Bereits verfügbar Nicht verfügbar

Architecture for the Configuration Application


Configuration Point

REST-APIFilesystem

Etc.

XSD validation

MarshallingLogical

validation

Configuration-

Processor

TFTPD /DHCPD

Configuration.xml

Vendor-specific

Non-vendor specific

Future Work


●Consideration of the 5G SDN Core Network Concepts–Methods for Management and Configuration of Data Plane Elements [e.g. 1]

–Interrelations of Concepts

–Integration of SDN-based WAN-as-a-Service Offerings expected within next years

●Analysis of OpenStack as XaaS/NaaS-Implementation Platform –Integration of NaaS-Concepts in Ironic?

–Proof of Concept Implementation of SDN Apps for CaaS (VoIP) and CPS

●Analysis of Interrelation with OpenStack-based Application-oriented

Frameworks like FIWARE

[1] Jose Costa-Requena et al., SDN and NFV integration in generalized mobile network architecture, 2015 European Conference on

Networks and Communications (EuCNC), IEEE 2015.

Mechanisms for the Automated Setup of

Software-Defined Networks

Diederich Wermser, Jannis Ohms, Olaf Gebauer(Ostfalia Hochschule)

Sven-Ove Wähling (Netzlink Informationstechnik GmbH)

21. VDE/ITG Fachtagung „Mobilkommunikation“

11.-12.05.2016 – OsnabrückDiscussion…

ZIM - INAASCA - Integrated Network-as-a-Service Solution as Part of Cloud IT Application Portfolio

Documents

Mechanisms for the Automated Setup of Software …...Mechanisms for the Automated Setup of Software-Defined Networks Diederich Wermser, Jannis Ohms, Olaf Gebauer (Ostfalia Hochschule)