Intel Open Network Platform Server (Release 1.3) Release Notes

Transcription

1 (Release 1.3) Revision 1.1 February 2015

2 Revision History Date Revision Description February 19, Updated for release of 1.3 of Intel Network Platform Server 1.3 December 15, Initial release (Intel public) 2

3 Contents 1.0 Introduction System Overview Release 1.3 Highlights Intel ONP Server Distribution Reference Architecture Environment Network Elements Compute Node Software Controller Node Software Reference Platform Hardware Functionality Highlights New Functionality Contributed and Collaborated in Open Source Project by Intel Release 1.3 Limitations Installation Instructions Node SW

4 Note: This page is intentionally left blank. 4

5 1.0 Introduction This document describes Release 1.3 of Intel Open Network Platform Server (Intel ONP Server). Intel ONP Server is a platform-level reference architecture designed to make it easier for software and hardware vendors, and service providers to develop and deploy software-defined networking (SDN) and network function virtualization (NFV) solutions. The deployment of this reference architecture is done mainly using DevStack, which, although it does not make the deployment production ready, provides the developer a good option to experiment with Intel s software and hardware stack. Intel ONP Server defines hardware and software that together provide a framework to deliver the many benefits of Intel architecture to SDN and NFV. The underlying foundation of this reference architecture is comprised of IA-based standard high volume servers. The software stack is based on Open Source software originated by Open Standard communities (e.g., Open vswitch, DPDK, OpenDaylight, OpenStack, and KVM). Intel is working closely with these communities and contributing to the evolution and advancement of these open standard projects. Intel ONP Server provides a SDN/NFV reference solution that defines three main network elements: networking nodes, OpenDaylight controller, and OpenStack manager. An SDN/NFV lab environment comprised of those network elements is the setting for ONP Server software integration, customer use case validation, and the execution of benchmark performance testing. This document describes the main capabilities contributed by Intel to the Open Source community projects and integrated into Intel ONP Server, Release 1.3, as well as major solution gaps. It also provides a snapshot of the benchmark performance tests results as gathered for Intel ONP Server Release 1.3. Note: Intel has decided to increase investment in the Open vswitch community project focusing on DPDK and advancing hardware acceleration starting with Release System Overview 2.1 Release 1.3 Highlights Intel ONP Server, Release 1.3, introduces the following new capabilities: Integration with the following latest Open Source software releases: Upgraded to Openstack Juno Upgraded to OpenDaylight Helium-SR1.1 Support for the following: Note: Fedora 21 (server version) Real-time Linux kernel (v rt28) installation Intel Ethernet Controller XL710 4x10 GbE (code named Fortville) Intel Ethernet Controller XL710 4x10 GbE was tested with the Intel FTLX8571D3BCV-IT, AFBR-703sDZ-IN2 850nm SFPs, and dual Xeon processor E v3 server platform. Section 3.1 and Section 3.2 describe in detail the software enhancements in Release

6 2.2 Intel ONP Server Distribution Intel ONP Server, Release 1.3, is delivered in the form of two documents. Access to the documentation is under: Intel ONP Servers Release 1.3 Software. The following are the two main deliverables: Intel ONP Server Reference Architecture Guide This document provides instructions on how to build Intel ONP Server software, set the functionality test environment, and perform the tests. Intel ONP Benchmark Performance Test Report This document provides descriptions of benchmark tests and performance test results. 2.3 Reference Architecture Environment Figure 1. Intel ONP Server Node View Figure 2. Intel ONP Server Test and Validation Environment 6

7 2.4 Network Elements Compute Node Software Software Fedora 21 x86_64 (server version) Linux* Real-Time Kernel DPDK Compute (regular OVS and OVS with DPDKD-netdev): Open vswitch (OVS) Libvirt fc21.x86_64 QEMU-KVM fc21.x86_64 Intel QuickAssist Technology (QATmux.L tar.gz and icp_qat_netkey.l tar.gz) Notes Underlying system-level OS; based on the fc21.x86_64 kernel Real-Time Linux Kernel rt28 (This is a baseline in order to give real time aspects to the compute mode.) Software libraries used to significantly accelerate packet processing, increasing throughput and scalability Includes support for OVS with DPDK-netdev Toolkit and API used by QEMU-KVM to manage virtual machines and OpenStack to manage the compute resources of the host. - Open Source machine emulator and virtualizer - Includes KVM to enable hardware accelerations in Intel platforms Hardware-based acceleration and communication mechanisms for services, such as encryption/decryption and compression/decompression Controller Node Software The following table shows the controller node software components that were used during the testing of VNF components vips, vbng and non-uniform memory access (NUMA) placement, and SR-IOV passthrough for OpenStack. Software Fedora 21 x86_64 (server version) OpenStack* Juno (together with Intel patches openstack-ovs-dpdk- 911.zip) Controller: Open vswitch git3282e51 Notes Underlying system OS. Upgraded to the fc21.x86_64 kernel - OpenStack, related tools, and Intel patches for building and managing clouds - Includes DevStack shell script for automating development-environment builds Includes support for OVS with DPDK-netdev The following table shows the controller node software components that were used during the testing of OpenDaylight. Note: OpenDaylight Helium does not support the native Java version on Fedora 21. Fedora 20 x86_64 Software OpenStack* Juno (together with Intel patches openstack-ovs-dpdk- 911.zip) Controller: OpenvSwitch git3282e51 (OVS) OpenDaylight* Helium SR1.1 Notes Underlying system OS, upgraded to the fc20.x86_64 kernel - OpenStack, related tools, and Intel patches for building and managing clouds - Includes DevStack shell script for automating development-environment builds Includes support for OVS with DPDK-netdev OpenDaylight functioning as OpenStack Neutron ML2 mechanism driver for OVS 7

8 2.4.3 Reference Platform Hardware Ivy Bridge-based Platform Platform Processors Description Intel Server Board 2U 8x3.5 SATA 2x750W 2xHS Rails Intel R2308GZ4GC Intel Xeon Processor Series E v2 LGA2011, 2.8 GHz, 25 MB, 115 W, 10 cores Notes Grizzly Pass Xeon DP Server (2 CPU sockets) 240 GB, SSD 2.5, SATA 6 GB/s Intel Wolfsville SSDSC2BB240G401 DC S3500 Series Supports SR-IOV (Formerly code named Ivy Bridge) Socket-R (EP), 10 Core, 2.8 GHz, 115 W, 2.5 M per core LLC, 8.0 GT/s QPI, DDR3-1867, HT, turbo Long product availability Cores 10 physical cores/cpu 20 hyper-threaded cores per CPU for a total of 40 cores Memory NICs (Niantic) BIOS Quick Assist Technology 8 GB, 1600 Reg ECC, 1.5 V DDR3 Kingston KVR16R11S4/8I Romley 2x Intel Gigabit Ethernet Controller SE5C600.86B Release Date: 08/22/2013 BIOS Revision: 4.6 Intel Communications Chipset 8950 (Coleto Creek) 64 GB RAM (8 x 8 GB) NICs are on socket zero. (3 PCIe slots available on socket 0) Supports SR-IOV Intel Virtualization Technology for directed I/O (Intel VT-d), enabled only Walnut Hill PCIe card 1xColeto Creek Supports SR-IOV Haswell-based Platforms Platform Description Intel Server Board S2600WTT 1100W power supply Notes Wildcat Pass Xeon DP Server (2 CPU sockets) 120 GB SSD 2.5in SATA 6GB/s Intel Wolfsville SSDSC2BB120G4, supports SR-IOV Processors Intel Xeon Processor Series E V3, 2.6 GHz, 25 MB 145 W, 14 cores (Formerly code-named Haswell) 14 cores, 2.60 GHz, 145 W, 3.5 M per core LLC, 9.6 GT/s QPI, DDR4-1600/1866/2133 Cores 14 physical cores/cpu 28 hyper-threaded cores per CPU for 56 total cores Memory 8 GB DDR4 RDIMM Crucial CT8G4RFS GB RAM (8 x 8 GB) NICs (XL710) BIOS Quick Assist Technology Intel Ethernet Controller XL710 4x10 GbE tested with Intel FTLX8571D3BCV- IT and Intel AFBR-703sDZ-IN2 850nm SFPs GRNDSDP1.86B.0038.R Release Date: 09/04/2014 Intel Communications Chipset 8950 (Coleto Creek) (code-named Fortville) NICs on socket zero Intel Virtualization Technology for Directed I/O (Intel VT-d) enabled only for SR-IOV PCI pass-through tests, hyperthreading enabled, but disabled for benchmark testing. Walnut Hill PCIe card 1xColeto Creek, supports SR-IOV 8

9 Platform Description Intel Server Board S2600WTT 1100W power supply Notes Wildcat Pass Xeon DP Server (2 CPU sockets) 120 GB SSD 2.5in SATA 6 GB/s Intel Wolfsville SSDSC2BB120G4. Supports SR-IOV Processors Intel Dual Xeon Processor Series E v3, 2.3 GHz, 45 MB 145 W, 18 cores (Formerly code-named Haswell) 18 cores, 2.3 GHz, 145 W, 45 MB total cache per processor, 9.6 GT/s QPI, DDR4-1600/ 1866/2133 Cores 18 physical cores/cpu 36 hyper-threaded cores per CPU for 72 total cores Memory 8 GB DDR4 RDIMM Crucial CT8G4RFS GB RAM (8x8 GB) NICs (XL710) Intel Ethernet Controller XL710 4x10 GbE tested with Intel FTLX8571D3BCV-IT and Intel AFBR-703sDZ-IN2 850nm SFPs (code-named Fortville) NICs on socket zero BIOS SE5C610.86B Intel Virtualization Technology for Directed I/O (Intel VT-d) enabled only for SR-IOV PCI pass-through tests, hyperthreading enabled, but disabled for benchmark testing. Quick Assist Technology Intel Communications Chipset 8950 (Coleto Creek) Walnut Hill PCIe card 1xColeto Creek, supports SR-IOV 3.0 Functionality Highlights 3.1 New Functionality Contributed and Collaborated in Open Source Project by Intel This section provides a summary of the new software features. No. Open Software ONP Release ONP System Capability Description 1. OpenStack 1.3 Rebase to Openstack Full Juno release notes can be found at the following: Compatibility with DPDK and OVS with DPDK-netdev 2. OpenDaylight 1.3 Helium-SR 1.1 support. Full OpenDayLight release notes can be found at the following SR1_Combined_Release_Notes 3. Integration Scripts 1.3 The CPUs of the VM now match the architecture of the physical CPU. 1.3 Handle infrastructures with and without proxy server presence 4. Fedora Support integration of DPDK 1.7.1, regular Open vswitch (OVS)/OVS with DPDK-netdev, OpenStack Juno on Fedora 21 OS 5. Real-Time Kernel 1.3 Support for installation of real-time kernel v rt28 9

10 3.2 Release 1.3 Limitations This section provides a summary of release limitations. No. Open Software Limitations 1. DPDK When OpenStack is compiled on OVS with DPDK-netdev compute node, an error is observed: :57: Unloading any existing DPDK UIO module :57: Loading DPDK UIO module :57: insmod: ERROR: could not insert module /opt/stack/dpdkv1.7.1/x86_64-ivshmem-linuxapp-gcc/kmod/igb_uio.ko: Unknown symbol in module :57: ## ERROR: Could not load kmod/igb_uio.ko. Workaround: <root> modprobe uio <root> lsmod <stack> cd devstack <stack>./unstack.sh <stack> FORCE=yes./stack.sh 2. After stack compilation is successful on the controller and compute nodes, log in to OpenStack UI to spawn VM, an error is observed: Failed to connect to server (code 1006). Workaround: sudo iptables -F 3. DPDK The DPDK driver for XL710 will fail to load when the platform has more than 64 logical cores. 4. ODL interop with OpenStack The interoperability between Openstack and Opendaylight is unstable. On some occasions, Openstack tenant network may not function properly 5. vips use case On some occasions, the vips does not route packets between two networks on a specific hardware configuration (i.e., Wildcat Pass server with Fortville network adapter). 4.0 Installation Instructions This section provides a high-level description of the installation process. Note: For details, see the README file referenced below. 4.1 Node SW Instructions: 1. Download the Intel ONP Server, Release 1.2 Scripts tarball from: -onp-servers The bundle contains the following files: README A file with detailed information on how to use the scripts to deploy the controller and compute nodes prepare_system.sh A script to do the initial system configuration and pull the right updates from the Fedora repos prepare_stack.sh A wrapper to DevStack scripts onps_config The main configuration file with the necessary setup parameters 10

11 onps_config_stand_alone_compute a version of onps_config that sets up a standalone compute node without any controllers involved. local.conf-ovdk-controller A DevStack template configuration file DO NOT modify. local.conf-ovdk-compute A DevStack template configuration file DO NOT modify. 2. Plan ahead to decide what hosts you are going to use and what host interfaces will belong to management and/or the data plane network. 3. Install a fresh Fedora 20 installation on each host, and install the tarball on each host. 4. Untar the tarball and confirm the above described files are present. 5. Manually edit the onps_server configuration file on each host based on the planned role of that host (controller/node), type of interfaces, type of vswitch desired, etc. 6. Execute prepare_system.sh and reboot. The script parses onps_server and prepares the system accordingly. 7. Execute prepare_stack.sh. The script will parse onps_server again and kick off DevStack in the background. After successfully completing steps 1 through 7 in all the hosts, a fully deployed set of compute and controller nodes should be available. Note: This set of scripts and configuration files is intended for evaluation and facilitation purposes only. 11

12 LEGAL By using this document, in addition to any agreements you have with Intel, you accept the terms set forth below. You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. 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. Software and workloads used in performance tests may have been optimized for performance only on Intel microprocessors. Performance tests, such as SYSmark and MobileMark, are measured using specific computer systems, components, software, operations and functions. Any change to any of those factors may cause the results to vary. You should consult other information and performance tests to assist you in fully evaluating your contemplated purchases, including the performance of that product when combined with other products. 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. Intel technologies may require enabled hardware, specific software, or services activation. Check with your system manufacturer or retailer. Tests document performance of components on a particular test, in specific systems. Differences in hardware, software, or configuration will affect actual performance. Consult other sources of information to evaluate performance as you consider your purchase. For more complete information about performance and benchmark results, visit All products, computer systems, dates and figures specified are preliminary based on current expectations, and are subject to change without notice. Results have been estimated or simulated using internal Intel analysis or architecture simulation or modeling, and provided to you for informational purposes. Any differences in your system hardware, software or configuration may affect your actual performance. No computer system can be absolutely secure. Intel does not assume any liability for lost or stolen data or systems or any damages resulting from such losses. Intel does not control or audit third-party web sites referenced in this document. You should visit the referenced web site and confirm whether referenced data are accurate. Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights Intel Corporation. All rights reserved. Intel, the Intel logo, Core, Xeon and others are trademarks of Intel Corporation in the U.S. and/or other countries. *Other names and brands may be claimed as the property of others. 11