NFV Orchestration for Optimal Performance...NFV Orchestration Requirements Performance Placement and...
Transcript of NFV Orchestration for Optimal Performance...NFV Orchestration Requirements Performance Placement and...
NFV Or chest r at ion forOpt imal Per f or mance
Hello Ther eDeWayne Filppi
Architect- GigaSpaces
Vadim SukhomlinovSDN/NFV Application Engineer – Intel
Agenda◇The Challenge Da ta intensive
VN Fs
◇The Environment DPA a nd EPA
◇The Missing Link S ma rt O rchestra tion
◇Introducing TOSCA, ARIA, and Cloudify
The Challenge
NFV Or chest r at ion Requir ements
Performance◇ Placement and
configura tion ◇ Mixed, Multiple
S LA sensitive workloa ds
◇ Fine -tune H ypervisor, O S a nd other bottlenecks
Scalability◇ VNF placement
vs . VM pla cement◇ Dynamic VNF
sca ling in a nd out ◇ Maintain
Throughput a nd S LA a s VN F sca les
And More..◇ High
Infra structure Utiliza tion
◇ Service Function Cha ining (S FC)
◇ O S S / B S S Intera ction
◇ PNFV Integration
The Env ir onment
DPA◇ NFVI Level◇ CPU pinning◇ NUMA◇ DPDK◇ S R -IO V◇ And more…
◇ VIM level◇ Recognizes and
configures pla tform a nd infra structure
◇ Enables “asking” for the right resources
E PA
FOR OPTIMIZED VNF PERFORMANCE, ENVIRONMENT AWARE ORCHESTRATION IS REQUIRED
?
Requir ements on NFV in f r as tr uctur e
◇Some differences to generic IT:• Determinism and performance
• Small packet processing
• Real -time, la tency (< 10μs for CPE a nd a ccess functions), jitter
• A v a i l a b i l i t y ( d e t e c t f a i l e d V M s i n < 1 s a n d a utoresta rt, recover host fa ilures)
• Regulatory, geolocation (incl. geo redundancy)
• Accelerate VM migration in planned ma intena nce
• HW acceleration cards
• A d v a n c e d m a n a g e m e n t ( O S S / B S S )
VM1 VM2 VM3
Orchestration service aware
platform aware
Hypervisor
CPU ChipsetSwitchSilicon
NICSilicon Linux+Apps
EPA for demanding applications recognizesand configures platform/infrastructure
Source: Telefonica, May 2015
Ser ver ar chitectur e and w or k load placem en t
core15
core14
core13
core12
core11
core10
core9
core8
core7
core6
core5
core4
core3
core2
core1
core0
socket 0
core15
core14
core13
core12
core11
core10
core9
core8
core7
core6
core5
core4
core3
core2
core1
core0
socket 1
QPI
PCIe PCIe
NIC0 NIC1 NIC0 NIC110G
10G
10G
10G
10G
10G
10G
10G
memory memory
huge page
huge page
huge page
huge page
huge page
huge page
huge page
huge page
Legend:
Good placement
Bad placement
Key Enhanced Plat f or m A w ar en es s f eatur es
◇Example platform features for N FV da ta pla neworkloa ds:• S R -IO V
• Huge Pages
• NUMA
• vCPU pinning to cores
• CPU model, instructions, Last Level Ca che
• vSwitch
• Real Time
• Trusted Execution Technology
• …
◇Cumulative performance impact on Intel® Da ta Pla ne Performa nce Demonstra tors from pla tform optimiza tions
as % of 10Gb/s
Source: Intel white paper QoS in BRAS with Linux and IA, August 2014
13Source: Telefonica, May 2015
EPA at Resour ce Or chest r at ion
15
• N FV R esource O rchestra tor needs to understa nd wha t is required to support ea ch VM
• R equests fa cilities from the releva nt VIM , which then a lloca tes logica l a nd physica l resources from a ma na ged pool
Servers & hypervisor
Resource Orchestration
Virtual Network Function
VM
VM
VM
VM
Infrastructure as a Service
VIMCloud/SDN
OpenStack* (E PA ) Featur es
16
Non-Uniform Memory Architecture (NUMA) CPU & memory configuration (co-located memory and socket)
NUMA I/O Device locality configuration (co-located PCI device and socketa)
CPU Pinning
Huge Page Support (2MB/1GB)
I/O Pass-through (Full PCIe pass-through of the I/O device to the guest)
I/O Pass-through (Virtual Function (SR-IOV) pass-through of the I/O device to the guest)
Intel ® Quick Assist Technology
Intel® TXT (Trusted platform)
HW offload API for RRC (Ruby Rapids)
Intel® AES-NI, AVX, SSE4.2, RD RAND (Instruction Set Extensions)
CPU Model (explicit model match for planned, or better for the future)
CPU llc (cache size)
vSwitches (type, capability) - OVS specified, with or without either DPDK/HWOA
LLC utilization
CPU ddio (direct i/o) - bios has to turn it on, DPDK makes use of it
CAT (cache allocation)
Example EPA listbenefit/use cases EPA feature HP ProLiant w Niantic NICsavoid vSwitch bottleneck I/O Pass-through (Full PCIe pass-through of the I/O device to the guest) yes
avoid vSwitch bottleneckI/O Pass-through (Virtual Function (SR-IOV) pass-through of the I/O device to the guest) yes
connect NIC cache and memory CPU ddio (direct i/o) -bios has to turn it on, DPDK makes use of it yes (in BIOS settings)
memory close to vCPUNon-Uniform Memory Architecture (NUMA) CPU & Memory configuration (co-located memory and socket) yes
IO close to vCPU NUMA I/O Device Locality configuration (co-located PCI device and socket) yeshost OS scheduler doesn't move VMs CPU Pinning yesrequirement for DPDK packet processing performance Huge Page Support (2MB/1GB) yescorrect VM placement AES-NI, AVX, SSE4.2, RD RAND (Instruction Set Extensions) yesmin compute performance CPU Model (explicit model match for planned, or better for the Future) yesmin compute performance CPU Last Level Cache (cache size) yes
min vSwitch features/performancevSwitches (type, capability) -OVS specified, with or without either DPDK/HWOA yes
virtualization latency/jitter real time hypervisor yes (needs BIOS settings)
trusted boot (trusted compute pools, geolocation) Trusted eXecution Technology yes
EPA Conf igur at ion
18
* Other names and brands may be claimed as the property of others
Descriptor withEnhanced Platform Awareness (EPA)
requirements
Example descr iptor w ith E PA r equir em en ts
The M issing LinkEnvironment Awa re O rchestra tion
VNFs Ar e (Ver y) Complex◇ Multi -Tiers◇ L o a d b a l a n c e d◇ Strict HW / Placement ◇ NUMA, DPDK, SR/IOV,
Affinity / Anti-Affinity◇ Firewalls, networks,
stora ge, ◇ Often hard wired◇ D a y 1 ? a n d d a y 2 ?◇ Scaling, Healing, elasticity?
Ser v ice Chains Mor e So..Add Their O wn Complexities : ◇ Forwarding Graphs(dynamic?) ◇ Complex Environments ◇ Cutting Edge and Legacy in same
environment◇ Multiple geographic locations◇ Complex policies and SLA
requirements
“ The only constant is change”-
Unknow n
WHAT IFYou could orchestra te a nd ma na ge a ny VN F the sa me wa y?
Or chest r at ing VNF B luepr in ts w ith T OS C A
Topology W orkflow Policy
(Topology O rchestra tion S pecifica tion for C loud Applica tions)
VM
C on tain er
T OS C A M odels Deploy m en ts A s A N ode G r aph: T he B luepr in t
V M
C on tain er
VNF
VM
VNF VNF
HostedOn ConnectedTo
Netw or k A Netw or k B
Subnet Subnet
Node Type: VM
Relationship: ConnectedTo
TOSCA Models Ar e In ter pr eted by W or k f low s
• “Install” workflow
V M
V N F
V M
C on tain er
V N F
S er v er
V N FN etw or k
S ubn et
1
2
4
3
4 4
5
<Placem en t/ A f f in ity >
Flow Graph
Creation
TOSCA Policies
• Asynchronous Post Deployment Actions• Detect node failure and heal• Detect capacity threshold and scale• Any other automated as y n c capability
TOSCA Requir ements & C apabilities
• Enables abstract specifications• P l a t f o r m / C l o u d / V I M i n d e p e n d e n t• Example: rather than specify OS Image,
s pecif y m in im um OS V er s ion• Example: specify VNF host provides SR - IOV .
VNF Topology V M
C on tain er
node.js
VM
Tomcat
Old- School Java App
VM
MongoDB
Hosted on
Connected-to
Node Type: Container
◇ Types, Nodes and Interfaces◇ Inputs and Outputs◇ Relationships◇ Requirements and Capabilities
VM
C on tain er
V N F B luepr in tV M
C on tain er
Bono (edge pr oxy)
VM
Spr out (SIP r outer )
Homer (xm l stor e)
HostedOn ConnectedTo
Netw or k A Netw or k B
Subnet Subnet
Node Type: VM
ConnectedTo
VM
C on tain er
V N F B luepr in tV M
C on tain er
Bono
VM
Spr out Homer
HostedOn ConnectedTo
Netw or k A Netw or k B
Subnet Subnet
Node Type: VM
ConnectedTo
◇ YAML Blueprint◇ Resources
(M odules , YAN G, S cripts , O thers)
In t r oducing Cloudif yPure-Pla y O rchestra tor ba sed on TO S CA
VNFBlueprint(TOSCA)
Infra structurePlugins
Conta inerPlugins
Conf. M gmtPlugins
● Provision● Configure● Monitor● Manage
Monitoring &Alarming
VNFBlueprint(TOSCA)
InfraPlugins
Conta inerPlugins
Conf M gmtPlugins
● Provision● Configure● Monitor● Manage
Monitoring &Alarming
Cloudif y Key Aspects
Open SourceOpen S our ce is k ey todr iv e in n ov ation an dcr eate s uper b qualitys of tw ar e. N o m or em on olithic v en dortied m on s ter s .
Open StandardOpen s tan dar d an dv en dor n eutr allan guage bas ed onthe T OS C A S pec f ordes cr ibin g V N Fs an df or w ar din g gr aphs .
Future ProofB e r eady f or w hat’scom in g an d lev er agen ew em er gin gT echn ologies an dtools .
“It is not the st r ongest of the species that sur v ives, It is the one that is most adaptable to change.”
- Char les Dar w in
HowCloudif yFit s in ETSI NFV ?
Orchestrator
VNF Manager
Ty ing It All Together
Requirements:● SR-IOV● DPDK● etc
VNFD
EPA Enabled VIM
NFVO
Exposing Platform Capabilities
NFVI
What Is ARIA?◇ Embeddable TOSCA orchestration Engine
■ TOSCA Parser and Execution Engine○ Python Library and CLI
■ Common Plugins ◇ Set of examples for Enterprise and NFV ◇ Open Source◇ Open Governance
■ Apache Software Foundation◇ www.Aria TO S CA.org
TOSCA Orchestration Engine Library
Apache Software Foundation Project
OASIS TOSCADefines and Refines
TOSCA SPEC
PlatformConsumes ARIA Library for TOSCA
orchestration capabilities
OPEN-OConsumes ARIA library for TOSCA
orchestration capabilities and Multi-VIM
ARIA
ARIA
TackerConsumes ARIA library as Tacker Orchestration Plugin for TOSCA
capabilities and Multi-VIM supportARIA
MuranoConsumes ARIA library as orchestrator Plugin for TOSCA capabilities and Multi-
VIM supportARIA
Mist.IOConsumes ARIA library as orchestrator Plugin for TOSCA capabilities and Multi-
VIM supportARIA
Use Cases
Spec
Gigaspaces & In tel◇ A r i a a n d O p e n-O initia tive◇ NFV Sales Collaboration◇ Joint Effort to test VNFs on EPA hardware
Refer ences ◇ Cloudify community portal:
http://getcloudify.org
◇ NFV related posts at the Cloudify blog: http://getcloudify.org/ta gs/N FV/
◇ Demo Video: https ://youtu.be/84gEy6Vvc0E
◇ Cloudify ClearWater https ://github.com/O ra nge-O penS ource/opnfv-cloudify-clea rwa ter
Thank YouQuestions?Find us a t:
◇ Twitter @CloudifySource◇ email info@ giga spa ces .com