Intel Software Adrenaline

Implementing SDN and NFV with Intel® Architecture

Issue link:

Contents of this Issue


Page 7 of 7

PART II: IMPLEMENTING SDN AND NFV WITH INTEL® ARCHITECTURE Trusted compute pool example ACCELERATING SDN NETWORK DEVELOPMENT Earlier, it was suggested that if OpenStack provided more information about the special hardware capabilities of individual nodes, network operators could more easily take advantage of these capabilities. For instance, users of cloud services requiring maximum protection for sensitive data may request their applications run in a trusted compute pool; hence, the aforementioned modification to OpenStack may be employed: This paper proposes a set of hardware and software components that could be used to develop an entire SDN and NFV-based network. In addition, Intel is making two reference designs available to reduce the development time and effort required to design physical and virtual switches. This solution was made possible by two fundamental innovations, the Intel DPDK and the ONS API, which accelerate packet forwarding, and create a common API between physical and virtual switches, respectively. With the objective of advancing SDN further, Intel is working with other companies and standards bodies to drive greater intelligence, capability and standardization into SDN/NFV APIs, thus enabling operators to more fully utilize their network resources. Step 1: Glance, which manages and administers VM images, is requested to load an application in a trusted compute pool. Glance broadcasts, "This VM image must be run in a trusted compute pool." Step 2: Nova, which creates VMs, identifies the platforms in the node layer with trusted execution technology and broadcasts, "Here is a node with that capability." Step 3: Another Nova module then performs the necessary matchmaking to ensure the VM image is loaded onto a platform in the trusted compute pool. For more information about Intel® solutions for networking and communications, visit For more details about the orchestration layer and newly approved enhancements to OpenStack, see Part III of this series titled, "SDN Orchestration Layer Implementation Considerations." 1Source: "Software-Defined Networking: The New Norm for Networks," ONF White Paper, April 13, 2012, pg. 7, 11, 8, 2 Source: 3 Source: 4Source: 5 Source: 6 Source: 7 Performance estimates are based on internal Intel analysis and are provided for informational purposes only. 8 9 Performance tests and ratings are measured using specific computer systems and/or components and reflect the approximate performance of Intel® products as measured by those tests. Any difference in system hardware or software design or configuration may affect actual performance. Buyers should consult other sources of information to evaluate the performance of systems or components they are considering purchasing. For more information on performance tests and on the performance of Intel products, visit See for more information. 10 Intel® Virtualization Technology (Intel® VT) requires a computer system with an enabled Intel® processor, BIOS, virtual machine monitor (VMM), and for some uses, certain platform software enabled for it. Functionality, performance, or other benefits will vary depending on hardware and software configurations and may require a BIOS update. Software applications may not be compatible with all operating systems. Please check with your application vendor. Source: OpenStack web site, 11 Source: "OpenStack Folsom Architecture," by Ken Pepple, 12 Copyright © 2013 Intel Corporation. All rights reserved. Intel, the Intel logo, and Atom are trademarks of Intel Corporation in the United States and/or other countries. *Other names and brands may be claimed as the property of others. Printed in USA 0413/MS/TM/PDF Please Recycle 328848-001US

Articles in this issue

Links on this page

view archives of Intel Software Adrenaline - Implementing SDN and NFV with Intel® Architecture