Network Virtualisation Reference architecture and ecosystem · Network Virtualisation Reference...
Transcript of Network Virtualisation Reference architecture and ecosystem · Network Virtualisation Reference...
DISCOVER, DISRUPT, DELIVER
A future-proof network architecture requires distributing data plane
intensive functions and centralising control plane ones
v v
COTS HW
LOCAL PoPs REGIONAL DATA CENTRES
Control Plane can be
Centralised
Data Plane must be
Distributed
OS + Hypervisor
MPLS/SDN/Optical
Infrastructure
Service Domain
Network Domain
CDN Video
P-CSCF
EPC BRAS
CG-NAT DPI
SDP CSFB
IMS
DHCP PCRF
DNS UDB
COTS HW
OS + Hypervisor
MPLS/SDN/Optical
SRVCC
HW and SW
decoupling
HW and SW
decoupling
GGSN
PE
Security
NGIN
M/SMSC
There will be two kinds of Virtualized Network
Infrastructure: local PoPs and regional Data Centres
DISCOVER, DISRUPT, DELIVER
Network Virtualisation is not Cloud Computing
The network differs from the computing environment in 2 key factors:
Data plane workloads
(which are huge!)
Network requires shape
(+ E2E interconnection)
NEED OF HIGH AND
PREDICTABLE PERFORMANCE
(as with current equipment)
GLOBAL NETWORK VIEW IS
REQUIRED FOR MANAGEMENT
1
2
…which are big challenges for vanilla cloud computing
…and most of industry is offering to Telcos just IT based
cloud products as network virtualization environments
DISCOVER, DISRUPT, DELIVER
ETSI NFV ISG has generated a reference architecture for
ensuring interoperability and carrier grade performance
Management environment
Execution environment
Virtual
Machines
Network
Functions
Network
Scenarios
Commodity HW
OS + Hypervisor
Commodity Switching
infrastructure
Virtualised
Infrastructure
Manager
VNF Manager Virtual
Network
Functions
Orchestrator
Legacy
OSS/BSS
DISCOVER, DISRUPT, DELIVER
High and predictable performance is not an issue (e.g.
vCPE, vCG-NAT, vBRAS…) as long as you know how!
@Cloud VM
Bare Metal
Acceptable performance
Bare Metal
VM @Cloud
GAP
x10
Bare Metal
VM @vPoP
EX
EC
UT
ION
MA
NA
GE
ME
NT
EX
EC
UT
ION
MA
NA
GE
ME
NT
What defensive
Industry says
What can be achieved
doing things well(*)
80 Gbps per COTS blade
(*) ETSI NFV Work Item “NFV Performance & Portability Best Practises”: DGS/NFV-PER001 Current version: v0.0.7 (stable draft – 15/10/2013)
Telefónica is rapporteur of the draft, as well as chair of Performance and Portability Expert Group
DISCOVER, DISRUPT, DELIVER
x86 technology evolves faster than ASIC
@vPOP
VM
Bare Metal
Bare Metal
VM
@Cloud
Bare Metal VM
EX
EC
UT
ION
MA
NA
GE
ME
NT
EX
EC
UT
ION
MA
NA
GE
ME
NT
Sandy Bridge (2011) Ivy Bridge (2013)
80 Gbps per COTS blade
Bare Metal
VM @Cloud
EX
EC
UT
ION
MA
NA
GE
ME
NT
Westmere (2010)
VM • Support for translations in memory R/W
from I/O (large pages)
BARE METAL • Direct PCIe connection to the processor
• Direct cache access for I/O
• Large pages support for I/O
VM • Support for translations in memory R/W
from CPU (small and large pages)
• Support for translations in memory R/W
from I/O (only small pages)
• Support of NICs in passthrough
DISCOVER, DISRUPT, DELIVER
A more detailed HW visibility is needed…
CLOUD COMPUTING VIEW
MEMORY I/O device
CPU
Core Core Core Core
Core Core Core Core
CPU Core Core
Core Core
CPU Core Core
Core Core
QPI
I/O
device
I/O
device I/O
device
I/O
device
ME
MO
RY
ME
MO
RY
I/O device
NETWORK VIRTUALISATION VIEW Minimise QPI usage
Max. cache sharing
Min. mem. translations Polling mode drivers
Full assigment to process
DISCOVER, DISRUPT, DELIVER
… while server configuration does not add bottlenecks
CLOUD COMPUTING NETWORK VIRTUALISATION
Hardware
OS + Hypervisor
Virtual HW
SW libs OS
Virtual machine 1
Virtual HW
SW libs OS
Virtual machine N …
Virtual
Apps
Virtual
Network
Functions
Virtual
Apps
Virtual
Network
Functions
Hardware
OS + Hypervisor
Virtual HW
OS
Virtual machine 1 Virtual machine N …
Virtual
Apps
Virtual
Apps
Virtual HW
OS
UPSTREAM
TRAFFIC
DOWNSTREAM
TRAFFIC
TRAFFIC BYPASSED
DATA
PLANE IS
MANAGED
DIRECTLY
DISCOVER, DISRUPT, DELIVER
If ignored, “equivalent” deployments would lead to
completely different behaviours!
Random mapping is
FAR FROM LINE RATE
Correct mapping allows
LINE RATE
x2.5
Random mapping leads
to UNPREDICTABILITY
DISCOVER, DISRUPT, DELIVER
Industry’s best practices are being set…
Based on the previous results, a formal list of
recommendations aimed at a “telco datacentre” has
been issued.
A formal list of features to be included in the templates
for orchestration has been elaborated.
Both are collected in ETSI NFV Work Item
“NFV Performance & Portability Best Practises”:
• DGS/NFV-PER001 Current version: v0.0.7 (stable draft – 15/10/2013)
• Telefónica is rapporteur of the draft, as well as chair of Performance
and Portability Expert Group.
DISCOVER, DISRUPT, DELIVER
… but more work is needed on closing the gaps and
getting the industry focused on providing real value
Commodity HW
OS + Hypervisor
Commodity
Switching
infrastructure
Virtualised
Infrastructure
Manager
VNF Manager
Virtual Network
Functions
Orchestrator
Legacy OSS/BSS
Current
State of the
Art is good
enough (if
properly
arranged)
ADD VALUE
HERE:
Industry
should focus
on providing
differential
VNFs and
Network
Orchestration
ADD VALUE
HERE: Industry
should focus on
providing
differential
VNFs. Credible
ROADMAP
needed!!
Network Virtualisation Infrastructure and its Management should
become COMMODITY Network Virtualisation Infrastructure and its Management should
become COMMODITY
Work is
needed in
Open Source
to AVOID
proliferation
of VERTICAL
SOLUTIONS
DISCOVER, DISRUPT, DELIVER 12
OUR NEXT STEP:
Network Virtualisation Reference Lab @ Telefónica
NFVO
Proper HW &
Hypervisor
config
ADD VALUE
HERE: Network
Orchestration
on top of
Carrier-grade
OpenStack
VNFs
ADD VALUE HERE:
Simplest integration
NFVI VIM = OpenStack++
OFC++
BASELINE
TECHNOLOGIES
ECOSYSTEM
ECOSYSTEM
Add your
logo here We want your logo here
Carrier-grade
OpenStack
going to
upstream
development
DISCOVER, DISRUPT, DELIVER
Step 1 (2013-2014) Step 2 (2015-2016) Step 3 (2016- ….)
Home environment
simplification
Single IP Edge
Network
Intelligence
rationalisation
Core simplification
and centralisation
IP and photonic
coordination
Transport
provisioning
simplification
vEPC
vDHCP
vCPE
Real Time Network
Analytics
SDN Orchestrator
PCE Net OS: joint
orchestration of network
resources
vBRAS Unified IP Edge
Local Data
Centre
Regional
Data
Centre
Infrastructure
orchestration
vIMS vSDP
vDPI
vCG-NAT vPE vGGSN
vDNS vUDB
vPCRF
vSTB
It is key to decide what to virtualize first…
To introduce gradually and smoothly these changes in
our network