VNF & Performance: A practical approach Luc Provoost Engineering Manager, Network Product Group Intel Corporation
SDN and NFV are Forces of Change One Application Per System Many Applications Per Virtual System Compute Application Applications and Services DEFINE the System Application A APP A APP B Application B APP C Network Application VM Manager Resource Pools Storage Application STORAGE Traditional Hardware TRANSFORMING NETWORKING AND STORAGE Abstracting the Hardware NETWORK COMPUTE Abstracting the Infrastructure 2
But Barriers Remain Open Standards and Source TRANSFORMING NETWORKING AND STORAGE Commercial Grade Solutions Deployments with TCO Business Case 3
Intel is Investing to ACCELERATE the Transformation Industry Consortia Intel ONP Reference Architecture Advance Gaps in Open Source and Standards Intel Network Builders Deliver Open Reference Designs Enable Open Ecosystem on IA Collaborate on Trials and Deployments TRANSFORMING NETWORKING AND STORAGE Telecom Cloud Enterprise *Other brands and names are the property of their respective owners 4
Intel is Investing to Accelerate the Transformation Advance Open Source and Standards TRANSFORMING NETWORKING AND STORAGE Industry Consortia Intel ONP Reference Architecture Intel Network Builders Telecom Cloud Enterprise *Other brands and names are the property of their respective owners 5
Advancing Open Source AND Standards to Solve Problems TRANSFORMING NETWORKING AND STORAGE Network Virtualization Intelligent Workload Placement (EPA) Policy VXLAN, Geneve OpenStack OpenDaylight Service Chaining NSH Virtual Switching Open vswitch L2/L3 Data Plane Performance *Other brands and names are the property of their respective owners DPDK 6
Advancing Open Source AND Standards to EVOLVE SOLUTIONS Network Virtualization Intelligent Workload Placement (EPA) Policy OpenStack OpenDaylight Service Chaining NSH Virtual Switching Open vswitch L2/L3 Data Plane Performance Service Assurance TRANSFORMING NETWORKING AND STORAGE VXLAN, Geneve *Other brands and names are the property of their respective owners DPDK GAP Today at node and network level 7
SERVICE ASSURANCE THE CHALLENGE AT THE MULTI Provisioning TENANT NODE Deploy Time Run Time What is the NFV compute and switching performance capacity required of the node? Am I getting specified performance without interference from noisy neighbors? Alarm Time vapp What do I do when my CPU/disk/memory/ switch runs hot? TRANSFORMING NETWORKING AND STORAGE Linux Services vfw Can I detect when a VNF image has been altered? vce Router KVM - vswitch Compute Node *Other brands and names are the property of their respective owners Run Time Is my virtual switch performing? 8
Integrating THEM INTO A SOLUTION BECOMES THE NEXT CHALLENGE TRANSFORMING NETWORKING AND STORAGE Network Virtualization Intelligent Workload Placement (EPA) Policy VXLAN, Geneve OpenStack OpenDaylight Service Chaining NSH Virtual Switching Open vswitch L2/L3 Data Plane Performance Service Assurance *Other brands and names are the property of their respective owners DPDK Service Assurance POC 9
Industry Consortia Intel is Investing to Lead the Transformation Intel ONP Reference Architecture Intel Network Builders Deliver Open Reference Designs Telecom Cloud Enterprise TRANSFORMING NETWORKING AND STORAGE *Other brands and names are the property of their respective owners 10
Intel Open Network Reference Architecture What is Intel ONP? Open Source Software Stack Based on ETSI-NFV Reference Architecture OpenStack Cloud OS OpenDaylight Controller Optimized server architecture for SDN/NFV in Telco, Enterprise and Cloud DPDK Accelerated Open vswitch Linux Fedora OS KVM Hypervisor Intel QuickAssist Technology Drivers Intel Ethernet Drivers:10 & 40 GbE Industry Standard High Volume Server Intel Xeon Intel Communications Chipset 89xx Series Intel Atom Reference Architecture that integrates hardware and open source software ingredients Intel Ethernet Controllers Vehicle to accelerate development and to showcase solutions for SDN/NFV based on IA Reference Architecture delivered quarterly on 01.org in the form of: Reference open source software Reference Architecture & Benchmark Guides Benchmark Test Report It is not a commercial product
Intel ONP Server is Aligned to OPNFV Intel ONP server Software Stack based on Open Source and Open Standards Contributions Industry Standard Server based on Intel Architecture Output Intel ONP Server contributes to and consumes OPNFV output to create an industry-standard open source platform optimized on IA *Other brands and names are the property of their respective owners 12
Intel ONP Server Program Step #2: Build ONP software stack INTEGRATE Contribute based on customer use-cases INTEGRATE Step #1: ONP Software ONP Software Step #3: Validate and benchmark Step #4: Deliver Intel ONP Reference Architecture *Other brands and names are the property of their respective owners 13
Industry Consortia Intel is Investing to Lead the Transformation Intel ONP Reference Architecture Intel Network Builders Enable Open Ecosystem on IA Telecom Cloud Enterprise TRANSFORMING NETWORKING AND STORAGE *Other brands and names are the property of their respective owners 14
Intel Network Builders : networkbuilders.intel.com Software Defined Networking (SDN) Telecom Cloud Enterprise Network Function Virtualization (NFV) >170 members 7 Service Providers TRANSFORMING NETWORKING AND STORAGE *Other brands and names are the property of their respective owners 15
Intel Network Builders Foundation partners end users Growing an ecosystem 30 partners in use in public POCs, trials, and deployments Build early end customer interest 11 with Network Builders Summits 1300 attendees 60 33 20 webinars delivered podcasts published 30 solutions briefs, partners optimized on whitepapers, and Intel open source reference architectures on contributions networkbuilders.intel.com Point Ecosystem Solutions Optimization on Intel Technologies & Market Awareness 16
Intel is Investing to ACCELERATE the Transformation Collaborate on Trials and Deployments TRANSFORMING NETWORKING AND STORAGE Industry Consortia Intel ONP Reference Architecture Intel Network Builders Telecom Cloud Enterprise *Other brands and names are the property of their respective owners 17
WORKING WITH END USERS : MWC 2015 E2e NFV architecture Cloud and NFV Are Different Especially for data/bearer plane processing Enhanced Platform Features Crucial Capabilities' Must Be Exposed (Descriptors) at VNF Deployment Time 23 Mpps (40G) v 270 Kbps TRANSFORMING NETWORKING AND STORAGE *Other brands and names are the property of their respective owners 18
The shift to SDN/NFV is underway But some barriers remain TRANSFORMING NETWORKING AND STORAGE Open Source and Open Standards are vital to releasing the value the transformation Intel is partnering with Service Providers and partners to accelerate the network transformation 19
Revenue Model Characterization, Modeling, TCO TCO Model Performance Model Benchmarking: A formal procedure for performance characterization for purposes of comparison Characterization Test system Test automation System Under Test B A Traffic generation OVS Node A Dimensioning Model C Characterization Tools D OVS Node B OpenFlow Switch NFVI instrumentation TRANSFORMING NETWORKING AND STORAGE Performance Measurement PROX ( Processing Execution Engine) System under Test SW Traffic generation Performance Measurements Instrumentation DATS (Dataplane Automated Testing System) Test automation & test report generation 20
PROX Task assignment through configuration System under Test Also for test generation and measurements Performance measurements Throughput and latency Per core, per port TRANSFORMING NETWORKING AND STORAGE
Dataplane Automated Testing System Soft Switch Dataplane traffic PROX (gen) DAT S Tester TRANSFORMING NETWORKING AND STORAGE Out-of-band DATS control & data PROX (workloads) VM Operating SUT System
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Increasing complexity Forwarding (change MAC address) 3. Measuring impact of modified cache line Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing 5. Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) 8. Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 23
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Increasing complexity Forwarding (change MAC address) 3. Measuring impact of modified cache line Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing 5. Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) 8. Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 24
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Forwarding (change MAC address) Measuring impact of modified cache line 3. Increasing complexity Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing 5. Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) 8. Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 25
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Increasing complexity Forwarding (change MAC address) 3. Measuring impact of modified cache line Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing 5. Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) 8. Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 26
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Increasing complexity Forwarding (change MAC address) 3. Measuring impact of modified cache line Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. 5. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) 8. Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 27
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Increasing complexity Forwarding (change MAC address) 3. Measuring impact of modified cache line Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. 5. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) 8. Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 28
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Increasing complexity Forwarding (change MAC address) 3. Measuring impact of modified cache line Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. 5. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) 8. Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 29
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Increasing complexity Forwarding (change MAC address) 3. Measuring impact of modified cache line Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. 5. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. 8. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 30
Test Cases 1. forwarding (no touch) Requirements: Needs back to back connection (through wires or through switch config) 2. Increasing complexity Forwarding (change MAC address) 3. Measuring impact of modified cache line Requirements: switches configured (if any) in sync with PROX config files. MPLS (un)tagging, modifying packet length 4. 5. Measuring impact of doing some protocol manipulation and changing packet length 5-tuple based load balancing Measuring impact of having DPI and table look up in the flow, using DPDK features (cuckoo hash) Access Control List (ACL) 6. Measuring impact of having DPI and packet filtering in the flow Flow Buffering 7. 8. Measuring impact of large numbers of buffered packets, stressing cache and memory bandwidth Border Network Gateway (BNG) Common VNF in NFV *PE use-cases BNG with QoS Common VNF with compute bound feature (QoS) Network Platforms Group 31
Legal Disclaimer INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined". Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information. The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or go to: http://www.intel.com/design/literature.htm [Add any code names from previous pages] and other code names featured are used internally within Intel to identify products that are in development and not yet publicly announced for release. Customers, licensees and other third parties are not authorized by Intel to use code names in advertising, promotion or marketing of any product or services and any such use of Intel's internal code names is at the sole risk of the user. Intel, [Add words with TM or R from previous pages..ie Xeon,, etc] and the Intel logo are trademarks of Intel Corporation in the United States and other countries. Other names and brands may be claimed as the property of others. Copyright 2014 Intel Corporation. 33