IBBT Template Proposal

Download Report

Transcript IBBT Template Proposal

Deploying Network Function Virtualization
Experiments on the Virtual Wall
Outline
PART 1: THEORY
Introduction to NFV, SDN and SFC
PART 2: HANDS ON
Introduction to: Fed4FIRE, Virtual Wall and jFed
Experimental setup
Practical Work
Network Function Virtualization (NFV)
Problem
-
180
160
Continuously increasing user
140
requirements: more data, rapidly
120
changing services
Exabytes per month
1 exabyte = 1 000 000 000 gigabytes
100
-
1
-
2
Networks with proprietary
equipment
Increased CAPEX and OPEX
80
Global IP Traffic Trends
60
Source: Cisco VNI Global IP Traffic Forecast, 2014–2019. May 2015.
40
2014
2015
2016
2017
2018
2019
Increased competition amoung
each other and from O-T-T
providers
Limited possibility to raise
subscription fees
Continuous reduction in ARPU, PROFITABILITY
13 Operators Call for Action
http://portal.etsi.org/NFV/NFV_White_Paper.pdf
October 2012
A joint operator call for the Telecom and IT industry to take
advantage of advances in virtualization to increase service
agility, network flexibility and reduce CAPEX and OPEX
ETSI responds to Call
November 2012
-
AT&T, BT, Deutsche Telekom, Orange, Telecom Italia, Telefonica and
Verizon selected the European Telecommunications Standards Institute
(ETSI) to be the home of the Industry Specification Group for NFV
-
Now 240 individual companies including 37 of the world’s major service
providers as well as representatives from both telecoms and IT vendors
-
1st Phase of work ended at end of 2014, 11 documents: architectural
framework, descriptions of the infrastructure, management and
orchestration, security and trust, resilience and service quality metrics.
http://www.etsi.org/news-events/news/864-2015-01-press-etsi-network-functions-virtualisation-completes-first-phase-of-work
So, what is NFV ?
http://portal.etsi.org/NFV/NFV_White_Paper.pdf
Leverage advances in virtualization to decouple network functions from Hardware
NFV Concept
Anticipated Benefits
1-
Reduced capital expenses (CAPEX)
-
Due to economies of scale and more efficient use of resources
(scale up/down),
2-
Reduced operation expenses (OPEX)
-
3-
Power/energy, space, update/upgrade/maintenance
Flexible, faster deployment, reducing time to market
-
Minimizing typical operator innovation cycle. Automated, standard
deployment
Some examples: Customer Premises Equipment
External Networks
External Networks
Evolved Packet Core
Evolved Packet Core (EPC)
Data Centers
VNFs
P-GW
P-GW
PCRF
PCRF
MME
S-GW
MME
S-GW
Access Network
(E-UTRAN)
eNodeB
eNodeB
User Equipment
Access Network
(E-UTRAN)
eNodeB
eNodeB
User Equipment
NFV Reference Architecture
2
Virtual Network Functions
VNF 1
3
NFV
Management &
VNF 3
...
VNF N
Network Function Virtualization Infrastructure
Virtual Resources
Computing, Storage, Network Resources
Orchestration
(NFV MANO)
VNF 2
1
Physical Resources
Computing, Storage, Network Resources
A lot of progress, yet many challenges
- Automated Chaining of functions to create end-to-end services
- Inter-operability
- Management and Orchestration
- Efficient resource allocation
- Standardization
- Architectural design
- Information and data modeling
- Energy efficiency
- Performance
NFV
- Chain
functions
- Evaluate
performance
- Model
services,
functions
Service Function Chaining (SFC)
SFC provides the ability to set up an ordered list of a Service Functions (e.g. firewall,
DPI, etc.) which a set of packets should traverse
Virtual Network Functions
CLOUD
DHCP
C
L
A
S
S
I
F
I
E
R
NAT
Firewall
Transport
...
Parental
Controls
Software Defined Networking (SDN)
SDN Definition
Adapted from SDN Central (SDN usecases)
SDN Benefits
Adapted from SDN Central (SDN usecases)
Traditional vs Software defined Networks
Network/Business
Applications
Load
Balancing
Routing
MAC
Learning
APIs
Application Layer
Network Services
SDN
Controller
Traditional Network:
Distributed Control and
Middleboxes (e.g.
Firewall, Intrusion
Detection, etc.)
Control Layer
Forwarding
Switches
Infrastructure Layer
Interface
e.g.
Openflow
Controller
OpenFlow protocol
OpenFlow Switch
OpenFlow Interface
Flow Table(s)
Dropped
OpenFlow table entries
Match Fields Priority Counters
Instructions
Timeouts Cookie Flags
1. Write Metadata
2. Goto Flow Table
3. Write action(s) to action set
1. Output: Send packet to specified port
2. Drop
3. Set-Queue: Assign packet to specified queue
4. Set-Field: Modify packet header field(s)
5. Change-TTL
Ingress
port
Packet
header fields
Pipeline
Metadata
Decouples network functions from
equipment: Leads to agility,
reduced CAPEX and OPEX
Creates network abstractions to
enable faster innovation, network
flexibility and holistic management
Networking Abstraction
Service/Function Abstraction
Automation
NFV
Isolation
Mainly Telecom
service providers
Multiple Control Protocols
(e.g OpenFlow, SNMP)
Agility
SDN
Mainly networking software
and hardware vendors
OpenFlow
NFV and SDN are highly related and complimentary, combining them
may lead to greater value. BUT they are not dependent on each other
SDN-based Virtual Network Function Chaining
Controller
Firewall
NAT
DHCP
Parental Controls
Architectural overview of the SFC
configuration process
Personalized Services
Service Consumption
Service Function Chains
SFC Configuration
Virtual Infrastructure (VNFs)
jFed Embedding
Physical Infrastructure (Virtual Wall)
22
Network Function Implementation
 Software-based Click Functions
 Bandwidth Shaper
Src
BandwidthShaper
Sink
DelayShaper
Sink
IPClassifier
Sink
 Delay Shaper
Src
 Firewall
Src
 TCP monitoring
Src
IPClassifier (tcp,-)
Queue
Sink
IPPrint
23
Network Function Implementation
 Load Balancer
Src
IPClassifier
Queue
Sink
RoundRobinIPMapper
 IPv6/IPv4 translation
Src
ProtocolTranslator64
Sink
Src
ProtocolTranslator46
Sink
24
Virtual Network Infrastructure Topology
Open vSwitch
Click kernel
25
SFC Configuration Tool
Can be configured
to run any Network
Function in
Software using CLI
26
SFC Configuration Tool
 JavaScript-based front-end
 Automatically configured using topology information
from geni-get
 GUI for interconnecting functions
 Translating connections to SFC
(client1 -> click1 -> server1)
 Python-based SDN controller and back-end
 Listening to GUI messages over HTTP
 Translating SFC to OVS-ofctl commands
 Installing and managing OVS configurations
27
Advanced JFed features
 Download & install scripts for OVS node
 Specific image for click nodes
 Python controller using geni-get and ovs-ofctl
28