Transcript Why NFV - Meetup

NFV on OpenStack
Telco case study
Shay Naeh
Copyright © GigaSpaces 2014. All rights reserved.
The Move to NFV
Orchestration
Becomes a
Central Piece
Why NFV
•
•
•
•
Implementing network functionality on COTS (i.e. Intel)
Reduced TCO, no vendor lock-in
Unified manageability
High Availability
– N+1 compute pools
– Multi zone, multi region, multi cloud
– Less human error, continues monitoring, automated tasks
• Multi cloud (openstack, EC2)
• Orchestration
• Auto Scaling
– Elastic scaling
• Self Hilling
Why NFV
• Modularity vs. Monolitic
– Improved abstraction and functional modularity
• Agile DevOps
– Improved agility
• Open source
– Stops single vendor silos
• Last but not least – Monitoring
– KPIs
– Feedback loop
– Analytics
Hardware components replaced by
NFV
• Automatic deployment of virtual
functions
– Virtual appliances:
• vRouter
• vFW, vLB
– Virtual Subsystems:
• IMS, CDN, EPC
– https://wiki.openstack.org/wiki/Teams/NFV
OPERATOR INFRASTRUCTURE
EPC
APN
FW
DPI
P-CF
NAT
Mobile
Network
IMS OFFERING
SBC
APN
Core
P-CF
VoLTE or
RCS/MMTEL
SMARTPHONE WEB SERVICE
Mobile
Device
PGW
Proxy
LB
APN
FW
NAT
Internet
VIDEO SERVICE
Vid Op
DPI
APN
FW
NAT
www.softwaretelco.com
OTT Video
SERVICE FUNCTION CHAIN EXAMPLES
Middleboxes via VNF /
VNFC Forwarding Graphs
(Package)
APN: Access Point Name
LB: Load Balancer
FW: Firewall
SBC: Session Border Controller
Core: IMS Core Components
P-CF: Policy & Charging Functions
Vid-Op: Video Optimizer
NAT: Network Address Translator
EPC: Evolved Packet Core
Proxy: Web Proxy
DPI: Deep Packet Inspection
Why OpenStack
•
•
•
•
•
•
•
•
•
•
•
Available & free
Open source
Economics of OTT and Telco standards (CPU, storage, network)
Large community, momentum, contribution
Carrier grade? Not yet, but soon…
High availability & resiliency
Resource allocation & optimization
Service continuity
Every large Telco (Evaluates and plan to move to Openstack)
OVS, SDN, etc
https://www.openstack.org/summit/openstack-summit-atlanta2014/session-videos/presentation/openstack-as-the-key-engine-ofnfv
Cloud for NFV – 4 Components
Application
Orchestration
Hardware
IAAS
Deployment & Orchestration
– Tosca/Heat based configuration
• Standard language
• Portable
– Dependencies
• In one NVF service deployment
• In multiple NFVs
– Self healing
– Auto scaling
– Analytics & feedback
–…
Example: “Intelligent Orchestration”
Send
Metrics
Real Time
Analytics
000000000
11111111111
000000000
11111111111
000000000
11111111111
Real Time Analytics
Cloud Infrastructure
Correlate
with
Historical
Events
Execute
Policy
Scale
Failover
Deploy
Feedback
Historical Data
Intelligent Orchestration
Network & Application Orchestration
• App Network
• App Subnet
• App Port
• Security Group
• Apache Floating IP
• Router Gateway
•
•
•
•
Data Network
Data Subnet
Data Port
Security Group
Apache Server
DB Server
NodeJS
MongoDB
Router
NodeCeller
Monitoring, Logging CI
Topology Driven Monitoring
What Do We See Here?
Host
App module
connection
Middleware
Custom Metrics
TOSCA –
The Glue for
Putting all This
Together
Application
Topologies
Workflows
Policies
TOSCA (Like) Blueprint
Host
Middleware
module: DB
Use Bash for
configuration and
life cycle
management
TOSCA (Like) Blueprint
Middleware module:
node JS Server
App module: node JS
connection
NFV Demo: Video Streaming Service
Clients
Load Gen
(3000 , 200)
vLB
Video
streaming
vVideo Stremer