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

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 3 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?

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 4 Cloud-Layer nach der ITU-T

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

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 5 Automated Setup in NaaS Context

Cloud Shop IT-Application-Offer Network-Offer (SaaS/CaaS-Control) (NaaS-Control)

Datacenter

ERP VoIP Customer Specific ... CPS NaaS-Server

Cloud IT-Application

ERP = Enterprise Ressource Planning VoIP = Voice over IP Customer Location CPS = Cyber Physical Systems Virtual Tenant LAN WAN LAN

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 6 Automated Setup in NaaS Context

Datacenter WAN Customer Location Integrated Cloud Service SDN-Application Control Northbound-IF NaaS-Server Configuration SDN-Controller IT- Point (Client) Service SDN-Application Southbound-IF Control Northbound-IF SDN-Controller Southbound-IF IT

RTC

...

SDN-Switch Router Applicationserver Client

Openflow Configuration Protocol

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 7 Automated Setup in NaaS Context

Cloud-Datacenter Customer-Area

Phase NaaS-Server SDN-Apps SaaS Cloud-Dashboard Kunde Customer Site

Selection of SaaS and NaaS-Services Verification Order Creation of a logical Network Diagram Offer (Including Exact Cost) Order

Setting up the Tenant Setting up the Tenant Configuration of the SDN-Apps

Pairing Preparation Delivery of Equipment Installation & Cabling Bootstrapping of SDN-Switches Service Provision Using Proactive Flows Setting up Proactive Flows

Server-on-state

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 8 Requirements of Automated Bootstrapping 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

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 9 Alternative Configuration Protocols

Importan O SSH Z Seriell N ce F T E - P T C C o O n N fi F g 15 - KO - - 60,00% - - KO - K K O O - -

Vendor support 6 1 Rarely supported 1 Standard 4 only 1 Standard 1 Widely supported 0 implemented by 0 0 bare metal systems or in premium hardware Useable for KO N Needs an IP N Needs an IP J Combination of N Needs N Needs an IP bootstrapping address the address the DHCP and manuell address the availability of availability of TFTP wiring availability of DHCP DHCP is not DHCP is not specifically is not defined defined defined designed for the boot strapping Standardisation 3 1 ONF Standard 3 Depends on the 5 Depends on the 2 Depends on 8 Depends on the 0 used NOS used NOS the used used NOS NOS License Cost 3 1 None 1 None 1 None 1 None 1 None 0 0 0 0 0 19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 10 Cost of implementation 3 2 High 4 Medium 7 Medium 1 High 1 High Automated Setup in NaaS Context

RTC

...

SDN-Switch Router Applicationserver Client

Openflow Configuration Protocol

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

Cloud-Datacenter Customer-Location LAN

Phase NaaS-Server SDN-Controller Configuration Point SDN-Switch

Hello Pre-loading Config-Files

Powering on the SDN- Switches

DHCP-Request

IP-Configuration DHCP-Reply

TFTP-Request

Switch configuration TFTP-Reply

Registration on the SDN- Registration on the SDN-Controller Controller OFDP-Request Topology detection OFDP-Response Topology Update

Openflow configuration OpenFlow Configuration (Reactive & Proactive)

Initial Setup of Static Flows Server-on-state

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 12 Architecture for the Configuration Point

Configuration Point (CP)

TFTP-Deamon DHCP-Deamon CP-Application - z.B.: Ironic ? - z.B.: Ironic ? - (verfügbar über - (verfügbar über Paketverwaltung) Paketverwaltung)

OS (Linux)

Hardware

Legende: Bereits verfügbar Nicht verfügbar

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 13 Architecture for the Configuration Application

Configuration Point

REST-API Configurati XSD Logical TFTPD / Filesystem Marshalling on- validation validation DHCPD Etc. Processor

Configuration.xml

Vendor-specific

Non-vendor specific

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 14 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.

19.05.16 21. VDE/ITG Fachtagung „Mobilkommunikation“ 11.-12.05.2016 – Osnabrück 15 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“ Discussion… 11.-12.05.2016 – Osnabrück

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