1. Open Source for NFV MANO
James Crawshaw, Senior Analyst, Heavy Reading
2. 1. Why Open Source for NFV?
2. Open Source for NFV MANO
3. Open Source MANO
4. ECOMP
5. Open-O
6. Conclusions
Agenda
3. 1) Why Open Source for NFV?
Source: thenewstack.io
Source: ETSI
4. SDOs and Open Source
Source: Heavy Reading. Legend – blue = open source, red = SDO or consortium
Interoperability
ATIS
MEF
OPNFV
OSS
TMForum
OpenNMS, Drools
NFVO - Orchestration
Open-O, Open Source Mano, ECOMP
VNFM - Control
ONOS, OpenDaylight, ONF
VIM - Infrastructure
3GPP
OpenStack, OpenFlow, Cloudstack
Architecture
ETSI
5. Open source complimentary to SDOs
• Open source initiatives are more nimble and less consensus
driven than SDOs
• Multiple open source solutions might be developed to
address the same problem which can cause confusion
• The market decides which one works best and it becomes a
de facto standard – survival of the fittest
7. Key open source NFV projects
• OpenDaylight – Around 30 projects including (1) network applications, orchestration and
services; (2) controller platform; (3) southbound interfaces & protocols such as netconf or
OpenFlow plugins; (4) data plane elements such as OpenFlow-enabled devices or Open
vSwitches. Supported by the Linux Foundation.
• OPNFV (Open Platform for NFV) – a framework for software development covering NFV
Infrastructure, Virtualized Infrastructure Management, and APIs to other NFV elements.
• OpenStack – Nova (compute) provisions/manages large networks of VMs; Neutron
(networking) provides pluggable, scalable, API-driven network and IP management; Swift
provides object storage and Cinder provides block storage.
• ONOS – Open Network Operating System is an open source community hosted by the Linux
Foundation which aims to create a SDN operating system for communications service
providers.
• ONF (Open Networking Foundation) – inherited the OpenFlow protocol/API (used as VIM)
from Stanford University. Led by Facebook, DT, AT&T, Microsoft, Google, NTT, Verizon.
8. • Which open source initiative do you think is
most important for the success of NFV?
– OPNFV
– OpenStack
– Open source MANO (OSM, ECOMP & Open-O)
– Other (please specify)
Question poll 1
10. Open Warfare - May the Best MANO Win
Source: Heavy Reading.
Open Source MANO ECOMP OPEN-O
Hosted by ETSI NFV AT&T / Linux Foundation Linux Foundation
Operator support Bell Mobility, BT, Portugal
Telecom, Sprint, Telefonica,
Telenor
AT&T, Orange Business
Services
China Mobile, China Telecom
Key vendor members ADVA Optical, Canonical,
Comptel, Intel, Ixia, Mirantis,
Procera, Red Hat, RIFT.io,
Sandvine, Technicolor, Viavi
Ericsson, GigaSpaces, Huawei,
Intel, ZTE
Other vendor participants Brocade, Netcracker,
Netrounds, Radcom, VMWare
Amdocs, Radcom Canonical, Red Hat
Lines of code 0.3m 8.5m 2.1m
Commits 412 n/a 2,674
Contributors 51 n/a 86
Downloads 803 n/a n/a
11. 3) Open Source MANO
Initial OSM architecture (release 0)
Source: Open Source MANO
13. 4) ECOMP
• ECOMP = Enhanced Control, Orchestration,
Management and Policy
• 2 years of development and 8m lines of code
• Working with Linux Foundation to make open source
project from 1Q17
• So far the only operator to join AT&T in publicly
supporting ECOMP is Orange Business Services
20. • All three open source MANO initiatives claim
to have a broader scope than ETSI NFV MANO
• All claim to support brownfield environments
• How you integrate with existing OSS/BSS is
unclear
• Time will tell which solution/s become/s the
de facto standard/s
6) Conclusions
21. • Which of the three open source MANO
initiatives discussed today do you think will
prove the most popular over time?
– OSM
– ECOMP
– Open-O
Question poll 2