Openstack Enhancements to Support NFV Use Cases Steve Gordon, Red Hat Adrian Hoban, Intel Alan Kavanagh, Ericsson Agenda

OpenStack Enhancements to Support NFV Use Cases Steve Gordon, Red Hat Adrian Hoban, Intel Alan Kavanagh, Ericsson Agenda

o OpenStack Engagement Model for NFV

o Kilo Extensions for NFV

o Evolving the Cloud to Support NFV

2 OpenStack Engagement Model for NFV

How did we get here?

ETSI NFV ISG

●Decoder ring: oEuropean Telecommunication Standards Institute oNetwork Function Virtualization oIndustry Specification Group ●Putting the standards in standards body!

ETSI NFV ISG

●Phase 1: oConvergence on network operator requirements oIncluding applicable existing standards oDeveloping new requirements to stimulate innovation and open ecosystem of vendors

ETSI NFV ISG

●Phase 2: oGrow an interoperable VNF ecosystem oThoroughly specify reference points and requirements defined in Phase 1 oAchieve broader industry engagement oClarify how NFV intersects with SDN and related standards/industry/open source initiatives.

NFV ARCHITECTURE

Open Platform for NFV (OPNFV)

●Establishing open source reference platform including: oNFV Infrastructure (NFVI) oVirtual Infrastructure Management (VIM) ●Focused on: oConsistency, performance, interoperability between components. oWorking with existing upstream communities.

NFV ARCHITECTURE

Initial OPNFV Focus

Open Platform for NFV (OPNFV)

●Growing list of projects: oRequirements projects .E.g. Fault Management oIntegration and Testing projects .E.g. IPv6 enabled OPNFV oCollaborative Development projects .E.g. Software Fastpath Service Quality Metrics oDocumentation projects

Telco Working Group

●Mission: oIdentify Telco/NFV use cases oDefine and prioritize requirements internally oHarmonize inputs into OpenStack projects .Blueprint/patch creation, submission, and review. ●Move discussion closer to OpenStack projects.

OpenStack

●Large community of technical contributors in wide array of loosely governed projects. ●NFV requirements fall across many of these. ●Require buy in from these diverse groups of contributors.

OpenStack

●Most projects moving to “specification” process for approval of major changes ●Ingredients of a good specification: oProblem description incl. use cases oConcrete design proposal oSomeone to implement!

Working Together

Success!

Current State

●Overlap exists between various groups in: oMission oMembership oScope oActivities ●Navigating can be tough!

Working from both ends ●ETSI NFV ●OPNFV ●Telco Working Group ●OpenStack

Working from both ends ●ETSI NFV ●OPNFV ●Telco Working Group Merging of “Worlds” happens here! ●OpenStack

Kilo Extensions for NFV Based on OpenStack community contributions & collaborations

19 Non Uniform Memory Architecture (NUMA) o Memory Proximity o Performance and latency characteristics differ depending on the core a process is executing on and where the memory a process is accessing is located.

CORE CORE CORE CORE Application Process Processor Processor

Socket 0 Socket 1

Memory Memory CORE CORE CORE CORE Application Application Application Process Process Process Server Optimising placement for memory proximity enables greater performance & efficiency 20 Filter Extensions: NUMA o numa_topology_filter o Helps to co-locate CPU core allocations to a single socket (when possible) o Resource tracks core/socket consumption and filters to available subset of suitable platforms.

CORE CORE CORE CORE Application Process Processor Processor

Socket 0 Socket 1

Memory Memory CORE CORE CORE CORE Application Application Application Process Process Process Server Co-location helps with cache efficiency for faster inter-process data communication 21 Filter Extensions: NUMA o numa_topology_filter o Helps to co-locate CPU core allocations to a single socket (when possible) o Resource tracks core/socket consumption and filters to available subset of suitable platforms.

CORE CORE CORE CORE Application Application Process Process Processor Processor

Socket 0 Socket 1

Memory Memory CORE CORE CORE CORE Application Application Process Process Server Enables the OSes to allocate local memory for greater performance & efficiency 22 Filter Extensions: NUMA – I/O Awareness

o Adds ability to select the socket based on the I/O device requirement o E.g. What if you’d prefer network access on NIC B

CORE CORE CORE CORE Application Application Process Process Processor Processor

Socket 0 Socket 1

Memory Memory CORE CORE CORE CORE Application Application Process Process

NIC A NIC B Server

23 Filter Extensions: NUMA – I/O Awareness

o Adds ability to select the socket based on the I/O device requirement o E.g. What if you’d prefer/require network access on NIC B?

CORE CORE CORE CORE Application Application Process Process Processor Processor

Socket 0 Socket 1

Memory Memory CORE CORE CORE CORE Application Application Process Process

NIC A NIC B Server Enables improved I/O performance 24 Simultaneous Multi-Threading (SMT) w/o SMT SMT

• SMT o On Intel platforms, run 2 threads at the same time per core • Take advantage of wide execution engine o Keep it fed with multiple threads o Hide latency of a single thread

• Power efficient performance feature Time (proc. cycles) (proc. Time o Very low die area cost o Can provide significant performance benefit Note: Each depending on application box represents o Much more efficient than adding an entire core a processor execution unit

SMT enhances performance and energy efficiency

25 Simultaneous Multi-Threading (SMT)

o Sample Linux enumeration of cores

o Linux scheduler (in the host) manages work load (process) allocation to CPUs

pCPU 0 pCPU 4 pCPU 1 pCPU 5 pCPU 8 pCPU 12 pCPU 9 pCPU 13 Execution Unit Execution Unit Execution Unit Execution Unit Processor Processor Socket 0 Socket 1