cloudify nfv orchestrator for optimal performance
TRANSCRIPT
NFV Orchestration for Optimal Performance
Hello ThereArthur Berezin
Director of product - Cloudify, GigaSpaces
Sivan BarzilyDirector of product NFV - GigaSpaces
Agenda◇ The Challenge Data intensive VNFs
◇ The Environment DPA and EPA
◇ The Missing Link Smart Orchestration
◇ Introducing Cloudify
◇ Tying It All Together Use Case
The Challenge
NFV Orchestration Requirements
Performance◇ Placement and
configuration ◇ Mixed, Multiple
SLA sensitive workloads
◇ Fine-tune Hypervisor, OS and other bottlenecks
Scalability◇ VNF placement
vs. VM placement◇ Dynamic VNF
scaling in and out ◇ Maintain
Throughput and SLA as VNF scales
Predictability◇ VNF Descriptors
- NFV-O + VIM - Platform Policy
Enforcement and Telemetry
◇ Fine grain resource requests
And More..◇ High
Infrastructure Utilization
◇ Service Function Chaining (SFC)
◇ OSS/BSS Interaction
◇ PNFV Integration
The Environment
DPA◇ NFVI Level◇ CPU pinning◇ NUMA◇ DPDK◇ SR-IOV◇ And more…
◇ VIM level◇ Recognizes and
configures platform and infrastructure
◇ Enables “asking” for the right resources
EPA
FOR OPTIMIZED VNF PERFORMANCE, ENVIRONMENT AWARE ORCHESTRATION IS REQUIRED
?
The Missing LinkEnvironment Aware Orchestration
Introducing CloudifyPure-Play Orchestrator based on TOSCA
APIsAutomation *-as-a-Service
Awareness Reaction to Self
Software-Defined-Operator
APIsAutomation *-as-a-Service
The Reality
VNFs Are (Very) Complex
◇ Multi-Tiers◇ Load balanced◇ Strict HW / Placement ◇ NUMA, DPDK, SR/IOV,
Affinity / Anti-Affinity◇ Firewalls, networks,
storage, ◇ Often hard wired◇ Day 1? and day 2?◇ Scaling, Healing, elasticity?
Service Chains More So..Add Their Own 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” -Unknown
WHAT IFYou could orchestrate and manage any VNF the same way?
Orchestrating VNF Blueprints with TOSCA
Topology Workflow Policy
(Topology Orchestration Specification for Cloud Applications)
VM
Container
VNF BlueprintVM
Container
Bono
VM
Sprout Homer
HostedOn ConnectedTo
Network A Network B
Subnet Subnet
Node Type: VM
ConnectedTo
VM
Container
VNF BlueprintVM
Container
Bono
VM
Sprout Homer
HostedOn ConnectedTo
Network A Network B
Subnet Subnet
Node Type: VM
ConnectedTo
◇ YAML Blueprint◇ Resources
(Modules, Receipts, YANG, Scripts, Others)
VNFBlueprint(TOSCA)
InfrastructurePlugins
ContainerPlugins
Conf. MgmtPlugins
● Provision● Configure● Monitor● Manage Monitoring &
Alarming
VNFBlueprint(TOSCA)
InfraPlugins
ContainerPlugins
Conf MgmtPlugins
● Provision● Configure● Monitor● Manage Monitoring &
Alarming
Cloudify Key Aspects
Open Source
Open Source is key to drive innovation and create superb quality software. No more monolithic vendor tied monsters.
Open Standard
Open standard and vendor neutral language based on the TOSCA Spec for describing VNFs and forwarding graphs.
Future Proof
Be ready for what’s coming and leverage new emerging Technologies and tools.
“It is not the strongest of the species that survives, It is the one that is most adaptable to change.” -Charles Darwin
HowCloudify Fits in ETSI NFV ?
Orchestrator
VNF Manager
Tying It All Together
Requirements:● SR-IOV● DPDK● etc
VNFD
EPA Enabled VIM
NFVO
Exposing Platform Capabilities
NFVI
Use Cases
OPNFV Functest vIMS
Why Cloudify?◇ Will provision resources on any cloud ◇ Standards based (TOSCA)◇ Smart placement◇ Will handle monitoring, log collection,
healing and scaling of your deployment
◇ Will allow you to mix containerized and non containerized pieces
◇ It Works!
References ◇ Cloudify community portal:
http://getcloudify.org
◇ NFV related posts at the Cloudify blog: http://getcloudify.org/tags/NFV/
◇ Demo Video: https://youtu.be/84gEy6Vvc0E
◇ Cloudify ClearWater https://github.com/Orange-OpenSource/opnfv-cloudify-clearwater
