mon 2-4 leymann

8/13/2019 Mon 2-4 Leymann

http://slidepdf.com/reader/full/mon-2-4-leymann 1/14

An SDN based Network Architecture

for Service Providers

Nicolai Leymann, Deutsche Telekom AG

[email protected]



SDN Based Network Architecture.

Agenda.

1. Principles, Motivation and Limitations

2. Use Cases

3. Architecture Blueprint

4. Summary

11/19/2013– public– Leymann/SDN & NFV Architecture 2




Principles.

1. Make sure that you have a clear understanding on SDN, NFV and friends and don’t

believe what vendors are promising

2. One integrated strategy for Software Defined Networking, Network Function

Virtualization, Service Chaining and Data Center deployments.

3. Virtualization of network functions on data center hardware should be the standard

model when introducing new technologies.

4. Implement open interfaces to ensure programmability of thenetwork fabric but don’t limit to a specific protocol or standard.

5. SDN enables different level of network control. Most attractive use cases for IP flow-level

control (e.g. OpenFlow) are at the network edge, e.g. service chaining.

6. Accelerate the efforts to implement network aware end to end service orchestration ofservices and resources for optimal placement.

7. Use standardized and common data center technologies and processes to implement

network functions.

8. Use in case of clear benefits, not because it’s a fancy new technology.

Strategy N

e t w o r k F u n c t i o n

V

i r t u a l i z a t i o n

D a t a C e n t

e r

S o f t w a r e D e f

i n e d

N e t w o r

k i n g





Impact Analyses.





Remove Limits of Existing Models.

Vendor dependencies

restricts development.

Scalability limits are

restricting growth.

Complexity limits

development and

and hindersflexibility.

SDN & NFV

Paradigms

Universal API:

Standardized API as common base for development of

network services and applications.

Central Control Plane:

Universal access for controlling

activities within the network

remove

limits of

existing

models

Abstraction:Separation of Forwarding and

Control Plane

Remove dependencies between

hardware and implementation.

Programmability:

Network and services can be

programmed




Standard x86 based

hardware with flexibleand elastic resource

provisioning

(computing

performance,

throughput, …)

Data Center

Separated control

/data planes withstandardized south

and northbound

interfaces to control

traffic. Decoupling of

life cycles.

SDN

NFV

1


Bringing Everything Together.

23

Virtualization ofnetwork functionaliy

(e.g. PPP termination,

Firewalling, Parental

Control)

NFV1

23 Virtualized

Data

Center

SDN


„Sweet

Spot“

End-to-End Use Case

(orchestration of NFV services in

a Data Center). NFV can be seen

as a use case of combining

virtualization in DC and Software

Defined Networking.




Key Aspects.

Decoupling of Control Plane and Data Plane.

Application are steering the traffic and are interacting with the forwarding nodes.

Flexible Control of all network functionality (not focused on forwarding).

Moving forward towards a „NOS“ – Network Operating System.

Network Functions (like firewalling) are running on a virtualized infrastructure. Use of standard data center (based on x86 based hardware) for all services.

Complex functionality for subset of services/customers not on every network node.

Respond on changing requests via horizontal scaling.

Use of standard x86 based server and abstraction of physical infrastructure. Use of a common resource pool.

Decoupling of hardware and application life cycles.

Simplification and automation of provisioning processes for Cloud services.

Opex & Capex savings through lower energy & maintenance costs.

Software

DefinedNetworking

Virtualization(Data Center)

NetworkFunction

Virtualization





Use Case: Classification, Steering and Service Chaining.

Peering

IP Backbone

LERLER

Data

Center

BNG

Redirect

Need to dynamically classify

and steer traffic based on

customer demands towards

Data Center

Data Center implements

service chaining (e.g. traffic

scrubbing and analyses)

Traffic classification andsteering part of Service

Chaining architecture

End-to-End Orchestration needsto take distributedclassification and redirection

into account

RemarksDynamic Traffic Steering and Service Chaining

Firewall

Scrubber

Antivirus

Analyses

Customer





Architecture Blueprint (1 of 2).

NetworkVirtualized Data Center

Hypervisor (KVM)

VM VMVM VMAPP

OSVMAPP

OSVMAPP

OS

Compute Storage Network

OpenStack Services

API

GlanceNova NeutronSwift

Infrastruktur

Install&

ConfigSys

Hypervisor (KVM)

VMVMVM VMVMVMVMVMVM VMAPP

OSVMAPP

OSVMAPP

OSVMAPP

OSVMVMAPPAPP

OSOSVMAPP

OSVMVMAPPAPP

OSOSVMAPP

OSVMVMAPPAPP

OSOS

ComputeCompute StorageStorage NetworkNetwork

OpenStack Services

APIAPI

GlanceGlanceNovaNova NeutronNeutronSwiftSwift

Infrastruktur

Install&

ConfigSys

Infrastruktur

Install&

ConfigSys

Orchestration

APP APP APP APP

Abstraction Layer

Controller

Adapter Adapter Adapter

Orchestration

End-to-End Orchestration

Controller





Architecture Blueprint (2 of 2).

All services are virtualized

Standardized elastic and scalable data center(s) for allservices

Single (small number) of standized interfaces – north

and southbound

The Bright Future

Abstraction layer needs to take

non virtualized hardware into

account

Integration of legacy software and hardware (fortransition period) necessary

Abstraction

Not everything can be virtualized

Legacy hardware not going to disappear in short term

Service specific Data Centers in deployment and needto be migrated

large „zoo“ of different control planes and interfaces

Reality

End-to-End Orchestration of services and network

(including connectivity) View on network and services (and network services in

DC) crossing (todays) organizational borders

Orchestration

Architecture Blueprint





Success Factors.

Common vision

from IT and NT.

Open minded discussion and flexibility are key factors for success. Architecture and strategyshould be seen as enablers for future networks and services.

Take organizational

impact into account

Not religious on

protocols and

solutions.

Move as much as

possible to new

architecture.

Clear path towards

Virtualization.

Factors for Success





Summary.

Higher flexibility for network and service deployments (faster „time to market“) Possibility to provide services end-to-end and ..

Interact with the underlying network through a single orchestration

Industry still in „gold rush mood“, many promises

Many players, many interpretations of SDN

Impact not only on technology level but also on organizational structures

Technologies like SDN and NFV are enablers for new services and more flexibility

Network evolution towards a software based/centric approach

Paradigm shift within IT industry (vendors, telcos, …)

Evolution

Opportunities

Challenges


mon 2-4 leymann

Documents