Open Source and Cloud: Change Through Collaboration

Open source and cloud -
change through
collaboration
Martin Bäckström
Vice President & Head of Group Function Datacom, Ericsson
Ildikó Váncsa
Ericsson Openstack coordinator

OPNFV Summit 2015 | Public | © Ericsson AB 2015 | 2015-11-11
> Digital business shift & challenges
> Collaboration through OPNFV
> OPNFV and upstream
Content

> The Digital business shift &
challenges

The pace of change
1875 20001975
10
30
50 15 years
50 billion connected devices
25 years
5 billion connected people
100 years
1 billion connected places
20
40
Connections(billion)
2020

1G 2G 3G 4G 5G
Mobility generations

Evolution Towards 2020
1000x
Mobile Data
Volumes 10x-100x
Connected Devices
10x
Lower Latency
10x-100x
End-user Data Rates
10x
Battery Life for Low
Power Devices
Source: METIS
4G3G2G 5G

INDUSTRIAL INTERNET
Beyond Mobile Broadband
Broadband experience
everywhere anytime
Smart Transport
Infrastructure
and vehicles
Remote controlled
machines
Mass market
personalized
media and gaming
Human / machines
interaction
Meters, sensors,
“Massive MTC”
And much more!
New opportunities and flexibility for the unforeseen

One network – multiple industries
@
A common network platform with
dynamic and secure network slices
NFV & SDN an
enabler for network
slices
From vertical to
horizontal networks

Transforming existing
networks to support
Cloud services
Addressing Cloud
connectivity needs
Building and enable
Public Cloud offers
Evolving internal IT
environments to
leverage Cloud
Enterprise CloudCommercial CloudPrivate/IT CloudTelecom Cloud
Different clouds
Telco Network
Communication &
Messaging Enterprise & OTT Services
AccessSecurity
Collaboration
Media
Enterprise & Health
CMO & CFOCIOCTO
Operations & Business Support Systems
OSS
BSS
Business Driven
Technology Driven

Cloud, SDN & NFV: AUTOMATION
Forwarding Forwarding Forwarding
SDN
Cloud
SDN
Controller
Control
Virtualize network
functions
Virtualize and
scale the compute
and storage
infrastructure
Programmable
forwarding
network with a
centralized
control plane
Orchestration
Automate and
coordinate
Virtual
Infrastructure
Manager
NFV
VNF
Manager
Cross-Domain Orchestration

› Why OPNFV?
– Creating open source standard for telecom
virtualization
– Driving eco-system with competitive solution
offerings
– Optimizing cost of NFV deployments
› OPNFV is gaining global momentum as
the “open source standard” for NFV
industrialization.
› Ericsson is committed to drive stronger
operator leadership in OPNFV.
OPNFV: Creating the
NFV ECO-system

Operator nfv deployment
models
OPNFV establishes carrier-grade performance and interoperability among multiple open source components
Vendor X
Hardware
Virtualization
VNF VNF
A
Vendor N
Vendor X + Vendor Y
Hardware
Virt.
VNF
Virt.
VNF
B
Hardware
Virtualization
Vendor N
VNF VNF
Vendor X + Vendor Y
C
Hardware
Virtualization
Vendor M
Vendor N
VNF VNF
Vendor X + Vendor Y
D
Hardware
Virtualization
Vendor M
Many vendors + SI
VNFVNF
Vendor X + Vendor Y
E

Ericsson OPNFV Certification
program
› Dovetail project in OPNFV starting up
› Ericsson OPNFV Certification
– An Industry certification (industry
acknowledged and customer authorized)
– Certify vendors to the ETSI NFV standard
and OPNFV reference solution
– Validate multi-vendor inter-operability
compliance to relevant standards
– Benchmark full-stack performance
– Validate VNF portability to NFVI and NFVI
compliance to VNFs

> Collaboration through OPNFV

Standardization
› Sequential process
› Slightly different implementations
› Multiple standards for the same area
› Few parties involved in the decision

De facto
Standards
› Implementation driven
› Majority of users
› No formal agreement
› No documentation

OPNFV
› Bridge between traditional
standardization and implementation
› Parallel process
› Feedback loop

> OPNFV and Upstream

› Quality of Service (QoS)
–The term was defined in 1994 in the
field of telephony
› Same types of requirements
–High Availability & Resiliency
–Deterministic performance
–Security
–Manageability & Orchestration
› Different numbers
–“0” downtime…
Telecom vs IT

› High Availability
– 99.999% availability  5.26 minutes of
downtime per year
– OpenStack control services availability
– Instance availability
› Deterministic performance
– Reaction on load changes
› Security
– AAA
› Manageability and Orchestration
– Zero-downtime upgrade
– Virtualized Network Function (VNF)
provisioning
Telecom Grade
Requirements

› What is missing?
– Quality vs Quantity – new features or
stability?
– Focus
– Priorities
– Synchronization
› How to fill the gaps?
– Concentrated effort
– Working Groups in OpenStack
› Telco WG
› Product Management WG
Telecom Grade
OpenStack

› Industry focus on characteristics
–Stability
–Performance
–Scalability
–Security
› NFV beyond L2
–Telecom use cases
–L3-VPN
–SDN controller integration
Change
Viewpoint

Diversity in the Loop
Doctor
(Fault
Management)
NEC
NOKIAINTEL
DOCOMO
NEC
NOKIA DOCOMO

› For Telecom vendors and operators
› For new upstream contributors
› For standardization
› For OpenStack
Competence
build up

› Adapt to and drive changes
–Converging Telecom and
enterprise mind sets
–Way of working as a collection of
flexible processes
› Efficient standardization with
implementation focus
Go with the Flow
Change
Collaboration
Community

> Summary

Summary
› SDN, NFV and Cloud enable the vision “One network, Multiple
Industries”.
› Operators have chosen different approaches for NFV and Cloud
transformation.
› OPNFV is gaining global momentum as the “open source standard”
for NFV industrialization. Ericsson is committed to drive stronger
operator leadership in OPNFV.
› OPNFV adapts to and drives changes. It is a community
where telecom and enterprise mind sets converge.

Open Source and Cloud: Change Through Collaboration

More Related Content

What's hot

Viewers also liked

Similar to Open Source and Cloud: Change Through Collaboration

More from OPNFV

Recently uploaded

Open Source and Cloud: Change Through Collaboration