This presentation discusses Enea's contributions and offerings related to OPNFV and NFV. Some key points: - Enea was involved in early work bringing up OPNFV architectures on ARM hardware and demonstrating reference platforms. - Enea hosts a multi-vendor NFV lab compliant with OPNFV specifications and participates in the OPNFV Armband project to support ARM. - Enea's NFV portfolio includes an OPNFV-based virtualization platform, VNF/PNF platform, high performance dataplane software, guest operating systems, and a VNF management platform. - Going forward, Enea aims to focus on areas like hardening OPNFV releases

1. Enea – OPNFV vision,
contributions and offerings
OPNFV Summit 2016
Ulf Bragnell, Director Product Management

2. NFV is more than the
datacenter…
Servers
Mix of servers and
purpose built HW
Purpose built HW
Modified from http://portal.etsi.org/NFV/NFV_White_Paper2.pdf
Datacenter (DC)
Network Edge
Access, Premise
Central Office (CO)
Point of Presence (PoP)
Metro Edge

3. NFVi fragmentation
 Commercial platforms
tend to be focused on
one or two types of
deployment
 Implicit dependencies
on commercial HW is
beginning to appear
 Separate ecosystems
forming for each vendor
 Very few have the
development muscle or
incentive to deliver a
cross network platform
Vendor A
Vendor C Vendor B
Vendor D
Modified from http://portal.etsi.org/NFV/NFV_White_Paper2.pdf

4. Modified from http://portal.etsi.org/NFV/NFV_White_Paper2.pdf
Why open source NFVi?
 OPNFV is a collaboration between
many different vendors
 Each have their own agenda but
are using OPNFV as the method
to implement it
 OPNFV is One ecosystem that can
address all main use cases
 Software vendor independence
 OPNFV is One platform that
supports multiple hardware
architectures
 Hardware vendor independence
OPNFV tomorrow
OPNFV today

5. Why deploy NFV at the edge?
 Every location is not connected via 10Gbps fiber
 Some applications are sensitive to latency
 Others are not optimal in a central location
 Residential pCPEs still needed in some cases
 L3 processing
 IPsec protection of L2TP for PPP
 OS and apps
 Residential/Enterprise vCPEs enables
differentiation through new services
 Orchestration and service chaining is key to
make this work
 Not all usecases are the same – cost vs. power

6. Why ARM for NFV?
 Choice
 Many vendors to select from or build
your own
 Cost
 ARM SoC are cheaper, lower power and
typically more integrated
 Software compatibility
 Same processor core means same VNF
runs on multiple hardware platforms
Edge Local office Cloud datacenter

7. Enea NFV contributions
and offerings

8. Some of Enea’s NFV contributions…
 Enea did the initial bring up of the OPNFV
architecture for ARM hardware in H1 2015
 Enea presented together with ARM the first
“reference” platform corresponding to
OPNFV’s “Arno” release in Q2 2015
 Enea demonstrated together with ARM a first
“multi-vendor” demo of the OPNFV
architecture at the ARM Partner Meeting in Q3
2015.
 Enea was one of the founding participants of
the ARM Band project in OPNFV in Q3 2015
 Enea launched in Q4 2015 the world’s first
ARM-based NFV lab compliant with the
“Pharos” specification from OPNFV
 Enea has brought up the “Brahmaputra”
release of OPNFV on ARM hardware
 Enea today hosts a multi-vendor NFV lab with
6 pods

9. OPNFV Armband Project
 Add support for ARM Architecture-based
servers in OPNFV
 Drive population of ARM-based servers in
OPNFV Labs
 Work with upstream community to release
OPNFV on multi-architecture

10. OPNFV demos
Virtual
Network
Virtual
Storage
Virtual
Computing
VIRTUALIZATION LAYER
Hardware Resources
NFVI VIM
Hardware Resources
VNF 1 VNF 3VNF 2
DPI
ServerClient Firewall
Client
(scp&http get)
Firewall
DPI settings
openstack
dashboard

11. OPNFV demos
Cavium ThunderX
48 core ARMv8
NXP LS2085
8 core ARMv8
Broadcom NS2
4 core ARMv8
Data Center
Central Office
vCPE
The same demo runs on different ARM devices
4, 8 and 48 core ARMv8!

12. Strong ecosystem a success factor
Partners Community memberships

13. NIC Hardware
NGINX worker
process
NGINX worker
process
NGINX worker
process
Kernel TCP/IP
NGINX – OFP TCP/IP integration
• Avoid context switches
• Avoid locks
• Streamlined packet path
• Better scalability, throughput
and latency
Context
switch
Locks
Packet flows
NGINX
worker
process
NGINX
worker
process
NGINX
worker
process
NIC Hardware
OFP BSD Socket API
PKT IO API
OFP TCP/IP stack library
ODP/DPDK
RX/TX
queues
RX/TX
queues
RX/TX
queues
Standard TCP/IP OFP TCP/IP

14. Current Projects and Portfolio today
 Enea NFV Lab
 Public OPNFV “Pharos” lab pods
 Multi-vendor hardware
 OPNFV-Based Virtualization Platform ”COSNOS” 1
 OPNFV based with multi-vendor HW/SW support
 “Enea Linux” carrier-grade host OS
 VNF/PNF Platform
 ”Enea Element” VNF/PNF Platform
 ”OpenFastPath” 2 high performance IP dataplane
 ”Enea Linux” and “Enea OSE” 2 carrier-grade guest OS
 VNF Management Platform ”Enea ElementCenter”
 Platform for VNF 2 and Network Management
 Model-based with support for NETCONF and YANG
 Expert Services
 OPNFV deployment, VNF validation/optimization/deployment
OpenFastPath 2
High
Performance
Dataplane
Enea
Linux + OSE 2
Guest
OS
Enea
Element
VNF/PNF
Platform
Commercial off-the-shelf (COTS) Hardware
Enea COSNOS
OPNFV-Based Virtualization Platform
Enea ElementCenter
VNF Management 2
Network Management
1 Carrier-grade Open Source Network Operating System (COSNOS)
2 Not available or integrated yet
Enea NFV Lab
Enea Linux

15. Enea NFV next steps…
 Hardening of OPNFV releases – High availability and resilience
 Performance optimization – NFVi and VNF level leveraging HW acceleration
 Edge usecases – Containers vs. VMs, Jailhouse vs. KVM etc.
 Security – How do we secure the NFV platform leveraging OPNFV and HW acceleration
 NFVi and VNF test lab based on Pharos – Environment to test and validate NFVi components and VNFs
 Orchestration – what makes sense to work with/engage in for the distributed NFV case

16. Call to action

17. United we stand, divided we fall…
 Work together to enable critical NFV components - vSwitch, IPsec, Guest acceleration, Containers etc
 Collaborate on performance benchmarks – Pharos and OPNFV test project is enablers
 More contributions needed in OPNFV Armband – benefits the whole ecosystem
 Engage directly with service providers and operators – understand their REAL usecases
 Go beyond high level demos to real PoC – could (should?) be multivendor

18. Thank You
F o r a d d i t i o n a l i n f o r m a t i o n o n E n e a , p l e a s e v i s i t
w w w. e n e a . c o m