Embed Size (px)
Citation preview
Exploiting Cloud Technologies in Networks:
NFV and SDN
Andy Reid and Peter Willis
BT Research and Innovation
© British Telecommunications plc
Clarifying what we mean by:
SDN
• Separation of
– control plane logic/processing
– data plane header look up and
forwarding
• Motivation
– Development of new control
protocols without changing
hardware
– Centralised control and
optimisation of network capacity
– Improved scalability for datacentre
networking
NFV
• Separation of
– Software defining network function
logic
– Generic processor based
hardware
• Motivation
– Speed and operational efficiency
in deploying new services
– Exploitation of commodity
components from Cloud
technologies
– Decoupling development/supply of
network functions from
development/supply of hardware
© British Telecommunications plc
Issue 1: What is the operational model for a
development to a network?
Upgrading a network is like changing the engine
oil while driving along
Hip Replacement Surgery
• The patient must remain alive during
the operation
• Scope of operation is precise and
focussed
• Time is limited.
• Only attempted if really needed
Changing Engine Oil
• The car and engine are stopped and
idle during the operation.
• Context of operation can be broad
• full service, engine replacement
• Taking longer has little or no
consequence for the car and engine
• Carried out as a matter of routine
© British Telecommunications plc
Issue 2: Viability of network development by scale
and scope
Small scale Large scale
Narrow
scope
Wide
scope Impractical • too complex
• do not fit
‘surgery’ model
Not
worthwhile
• Example Scope Dimensions
• Number services
• Range of legacy
technologies
• Number of vendors
• Network interconnect
• OSS interworking
Big but simple
Co
mp
lex b
ut s
ma
ll
© British Telecommunications plc
Ground rules for introduction of SDN and NFV (or
anything else) into a network
1. Select a (small) part of the network for initial upgrade
– Make use of new service introduction
– Make use of growth capacity increments
2. Interwork with existing parts of the network as necessary
– This includes OSS/BSS
– Selection in (1) which minimises (2) is good
3. Architect the development so that it fits with the longer term
development roadmap
– Development only to meet initial need is normally bad
– Development with ‘universal’ ambition is normally bad
– Business justification for the longer term fit is often not easy to quantify
– This is often the hardest step
4. It’s a marathon made up from a large number of short sprints
– A continuous relay race
© British Telecommunications plc
BRAS
Firewall DPI
CDN
Tester/QoE monitor
WAN Acceleration Message
Router
Radio Network Controller
Carrier Grade NAT
Session Border Controller
Classical Network Appliance Approach
PE Router SGSN/GGSN
Fragmented non-commodity hardware.
Physical install per appliance per site.
Hardware development large barrier to entry
for new vendors constraining innovation &
competition.
Network functions Virtualisation Approach
Independent Software Vendors
Standard High Volume Ethernet Switches
Standard High Volume x86 Servers
Standard High Volume Storage
Orchestrated,
automatic &
remote install.
What is Network functions Virtualisation?
Adding Machine Typewriter Printing Press Fax Machine
Com
pe
titive
&
Inn
ova
tive
Eco
syste
m
Its a bit like...
© British Telecommunications plc
The Story So Far: What happened last year...
Standard high volume servers have sufficient
packet processing performance to cost
effectively virtualise network appliances. •The hypervisor need not be a bottleneck.
•LINUX need not be a bottleneck.
•TCO advantages are scenario specific but
expect significant benefits.
•Plus a significant reduction in energy
consumption.
© British Telecommunications plc
NFV Example: consolidation of customer
premises equipment
Steelhead
Sentry
M-3050
Proxy SG 600
nano|engine
+ =
+ =
+ =
+ =
+ =
+ =
BT config & mgmt
hardware & software bundle
developer BT managed service
1 x 2 Unit rack- mount server
+ =
hypervisor
+ =
+ =
+
tra
ditio
nal
NfV
IP697
Protects private network
from Internet-based threats
Comprehensive IPS pro-actively detects/ prevents worms, data leaks & attacks
Checks web content for malware & controls insecure channels (e.g. IM)
Monitors network devices to collect/ analyse/ filter routine or false alerts
Accelerates transfers by removing unnecessary or repeated data
Prioritises apps and manages less important traffic over the Internet
© British Telecommunications plc
Orchestration and Relationship with SDN
Infrastructure Network Domain
Hyper-
visor &
Compute
Domain
Hyper-
visor &
Compute
Domain
NVF
Orchestration
Infrastructure Network Service
• Orchestration and Infrastructure Network primary
communications parameters are network
addresses and services between addresses
• Orchestration only sees infrastructure network
service not network detail
• Common model for any infrastructure network
technology, not just SDN
© British Telecommunications plc
Inherent Provision for Evolutionary Interworking
Interworking between software and
hardware planes
SDN NFV
Interworking between vendors
SDN NFV
Interworking between networks
SDN NFV
Interworking with existing OSS
SDN NFV
© British Telecommunications plc
The scope of possible SDN development plans
Plan A
SDN only
Plan B
NFV+SDN
Plan C?
© British Telecommunications plc
THANK YOU
