NFV is "network function virtualization" and is a hot topic in virtualization and cloud infrastructure. This presentation walks through what NFV is and how the ManageIQ community could potentially integrate with various NFV implementations.
For more on ManageIQ, see http://manageiq.org/
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Â
Design Summit - NFV BoF - Dave Neary
1. NFV and ManageIQ
Dave Neary
Open Source and Standards, Red Hat
October 8, 2014
2. What is NFV?
“NFV is a network architecture concept that
proposes using IT virtualization related
technologies to virtualize entire classes of network
node functions into building blocks that may be
connected, or chained, together to create
communication services”
2 Dave Neary, Red Hat
Wikipedia:
http://en.wikipedia.org/wiki/Network_Functions_Virtualization
4. Lost in a sea of acronyms
CDN
NFV
CG-NAT
AAA
SBC
ETSI NFV ISG
IPSec
MANO
IMS
SLA
4 Dave Neary, Red Hat
VIM
EPC VNFi
DPI
vCPE MME
SGSN
PDN-GW
RNC
eNode B
QoE
BNG
VPN
HLR/HSS
OSS/BSS
BRAS
C-RAN
VNFs
5. No, really... what is NFV?
Telcos are replacing hardware with VMs
5 Dave Neary, Red Hat
6. Why do telcos care?
â—Ź Enables increased agility
â—Ź Market pressures are reducing margins and
increasing customer demand for new services
â—Ź Reduced CapEx
â—Ź Consolidation of custom H/W to industry-standard
servers
â—Ź Promise of reduced OpEx
6 Dave Neary, Red Hat
7. What is a network function?
7 Dave Neary, Red Hat
8. “Middleboxes”
â—Ź Act on data going through the network
â—Ź Examples: Load balancer, gateway, IDS, VPN
endpoint, NAT, firewall
â—Ź Not just telco stuff
8 Dave Neary, Red Hat
10. Top use-cases
â—Ź IMS, EPC, SDB: Cellular, telephone, TV, video
streaming, VoIP, 3G/4G data
● CPE: Customer Premises Equipment – telco
equipment on-site (set-top boxes)
â—Ź Many others to choose from!
10 Dave Neary, Red Hat
11. Network Function Virtualization reference architecture
NFV Management and
Orchestration
An implementation of a Network Function
that can be deployed on a Network
Functions Virtualisation Infrastructure (NFVI)
Service, VNF and Infrastructure catalogue
VNF EMS 2
VNF EMS 3
Vn-Nf
VNF EMS 1
VNF 1
Virtual
Computing
Virtual
Storage
Virtualisation Layer (Hypervisor)
Computing
Hardware
Vl-Ha
Storage
Hardware
Virtual
Network
Network
Hardware
Hardware resources
Or-Vnfm
VNF
Managers
VNF 2
Orchestrator
OSS/BSS
NFVI
VNF 3
Os-Ma
Se-Ma
Ve-Vnfm
Nf-Vi
Virtualised
Virtual
Infrastructure
Manager
Infrastructure
Manager
Or-Vi
Execution reference points Main NFV Other reference points reference points
The totality of all hardware and software
components which build up the
environment in which VNFs are deployed.
The NFV-Infrastructure can span across
several locations, e.g. places where data
centres are operated. The network providing
connectivity between these locations is
regarded to be part of the NFV-Infrastructure.
A functional block that manages the
Network Service (NS) lifecycle and
coordinates the management of NS lifecycle,
VNF lifecycle (supported by the VNFM) and
NFVI resources (supported by the VIM) to
ensure an optimized allocation of the
necessary resources and connectivity.
A functional block that is responsible for the
lifecycle management of VNF.
A functional block that is responsible for
controlling and managing the NFVI compute,
storage and network resources, usually
within one operator’s Infrastructure Domain
(e.g., NFVI-PoP).
17. ETSI
â—Ź ETSI NFV ISG = European Telecommunications
Standards Institute NFV Industry Standards Group
â—Ź Defines use-cases, terminology and interfaces for a
hypothetical NFV platform
â—Ź Started European, but most telcos, NEPs and many
software vendors have presence
â—Ź NFV white paper and use-cases seeded both
OPNFV and OpenStack NFV team
17 Dave Neary, Red Hat
18. OPNFV
â—Ź Linux Foundation hosted project
â—Ź Goal is to create a complete software stack for NFV
â—Ź Includes KVM, libvirt, Open vSwitch, DPDK,
OpenDaylight, OpenStack
â—Ź Dual goals:
● Technology gaps – write code where needed for NFV
● Upstream first – evangelise NFV to upstream
projects, ensure code is accepted
â—Ź Members include NEPs, telcos, software &
hardware vendors
18 Dave Neary, Red Hat
23. Orchestration in NFV (1)
â—Ź VM affinity and anti-affinity
â—Ź Putting VMs on the same ovs-dpdk enabled host
â—Ź HA VMs on different hosts
â—Ź CPU pinning, resource reservation
â—Ź Dedicate resources to certain VMs
â—Ź Network orchestration
â—Ź Monitoring network QoS, reacting to hot spots
â—Ź Matching VMs to hardware capability
â—Ź VMs needing SR-IOV support
23 Dave Neary, Red Hat
25. Orchestration in NFV (2)
â—Ź VNFs consist of multiple components
â—Ź Each with their own performance constraints
â—Ź NFV deployment includes multiple VNFs
25 Dave Neary, Red Hat
26. NFV is basically an orchestration problem
26 Dave Neary, Red Hat