Is Your Network Ready for Telco Cloud?

December 07, 2016

CENGN Summit 2016

Agenda

What is the goal of moving to a telco cloud (smart infrastructure)?

What are the challenges of telco cloud?

What are the key architectural and business decisions?

Juniper’s POV on the key architecture for telco cloud

Drivers of accelerating change….

ENTERPRISES ADOPT A

“CLOUD FIRST” STRATEGY

%86

LANS BECOME ON-RAMPS TO CLOUD APPS OVER WAN

%90

INCREASE IN CONNECTIONS FROM MOBILE/ IOT DEVICES

B>25

VIDEO TRAFFIC DOMINATES

INCREASE IN SECURITY RISK

%27

of workloads will be processed by cloud

data centers by 2019

of enterprise traffic becomes N-S

connected devices, growing 10%/yr, by 2020 (46% M2M)

of all IP traffic will be video by 2020

of corporate data traffic will bypass perimeter security

by 2021

82%

IoT/ S

MA

RT E

DG

EM

OB

ILE/ F

IXED

EN

TER

PR

ISES

IOT / M2MNew Apps

Cloudify cell Sites, CO, POPs to run low latency/high performance VNFs and IOT/M2M workloads

5G Mobile/ FWA Services

…

Enterprise ServicesNetwork & Security Services

Why is now the right time for Telco Cloud?Inline edge services

scaled to demand

Multi-tenancy and cloud scale drives cost savings , SLAs, and agility

Wireless access

Virtualization for 5G cell densification

Caching and latency for video, VR/AR

Massive number of devices

Low latency for actionable analytics, control loops

Element / Device Mgmt

System / Services Abstractions

Human Middleware

Proprietary Vendor Lock-in

Intelligent Policy Automation

Intelligence is moving to higher layers

Higher value conversations with customers

Influence new buying centers at customer

Allows Automation and Analytics – (for both

Underlay & Overlay)

Ability to solve higher impact business

problems for customers

OpenSource provides an important

defensible differentiation

Interoperability with different products offers

an insertion strategy

Easier to attach low-differentiated hardware

TRADITIONAL NETWORKS CLOUD NETWORKS

Why does a customer care?

Open-Source & Interoperable

Ecosystem

KEY PROPERTIES

Openstack (Neutron / Extensions)

IP or MPLS

Transport

BGP L3VPN,

BGP EVPN

MPLS, VXLANService

Overlays

1. Physical distribution of cloud resources close to consumer and business customers

2. Enables applications to have:1. Low Latency2. High Availability/ SLA3. High network throughput/

minimize network choke points

3. Seamless Integration of DC and WAN technologies leveraging existing network and operational procedures.

WAN/METRO

BGP (Control Plane)MPLS (Service)

MPLS (Transport)

DC Fabric

BGP / OSPF (Control Plane)IP (Transport)

+

DC Overlays

MPLS, VXLAN, IP, GRE, etc.

+

NETWORK BLOCKS TELCO CLOUD

What is the Telco Cloud?

WAN

WAN

WAN

WAN

WAN

~50-250

~250-1000

> 1000

METRO

METRO

Physical

Network

Functions

ManagementController & Operations

Management

x86 x86 x86

Switch Switch

VNF VNF VNF

Purpose-built hardware + integrated software

Customers chose integrated solutions for performance, simplicity, and ease of use

Disaggregation of physical infrastructure - the networking stack is now divided among scale-out infrastructure

Management software ensures the various cloud components operate seamlessly

Geographic distribution of clouds raises operational complexity and need for automation

Need to predict failures and respond quickly

Challenges of Telco cloud transformationLEGACY: SCALE-UP

INTEGRATED SYSTEMSFUTURE: SCALE-OUT, TELCO CLOUD ARCHITECTURE

Challenges of Telco cloud transformation

• Migrate from appliances to scale-out cloud architectures

• Disaggregated vNFs/ centralized orchestration

• Cloud operations automation/ devops skills

• Costs of migration, including double bubble

• Making it all work together seamlessly, with similar SLAs, with greater agility, and lower overall costs

APIs, Automation

Stat mux gains; n x svcs

Micro services

SDN control / data plane

separation (e.g. CUPS)

Performance optimized

KEY CHALLENGES

SCALE-UP APPLIANCES

V1.0: INTEGRATED DISAGGREGATED

V2.0: CLOUD NATIVE/

SCALE-OUT

Time

Serv

ice

Ag

ility

Tota

l Co

st o

f Se

rvic

e

HW & SW independence

Cost-optimized HW

SW purchasing model

Legos - build ahead of

demand

= time to deployment of new services/ technology

What are the key architectural and business decisions in defining/ adopting the Telco cloud?

Is it deployable?

Is it manageable/ serviceable?

Is it better than the way we do it

today?

Does it reduce cost? Increase

revenue?

Can it coexist or leverage with what I have today (e.g. support brownfield)?

Are there specific compelling applications or services that can benefit from it (e.g. green field)?

Can I effectively manage the cloud and cloud services and keep them running at cloud scale, with

high SLA? Can I effectively manage it when it breaks?

Does it create flexibility to easily service, upgrade, and migrate to new services over time

Is it more flexible/agile?

Does it offer better performance/scale/capacity?

Is it more secure?

Is it less expensive to build/operate/consume?

What statistical multiplexing gains can be achieved?

What types of business models are achievable (subscription, pay per use, perpetual, unit based…)

such that costs are well aligned with usage?

Data Plane Acceleration (DPDK, SmartNIC)

VNF 1 VNF 2 VNF 3

Virtualisation Layer

Virtual

Computing

Virtual

Storage

Virtual

Network

Computing

Hardware

Storage

Hardware

Network

Hardware

vSRX vNF(s)

Contrail

vRouter

QFX, MX,

MFX

OpenStack, KVM

vMX

Virtual StorageVirtual

Computing

Juniper NFV Stack

VNF ManagersVNF Managers

OSS/BSS

Service, VNF, and

Infrastructure Description

NFVI

Vi-Ha

NFV Management and Orchestration

Os-Ma

Se-Ma

Ve-Vnfm

Nf-Vi

NFV Orchestrator

VNF Manager

Virtualised Infrastructure

Manager

Contrail Service Orchestration

Contrail Cloud Platform

Contrail Networking +

OpenStack/ Kubernetes

Scalable End-To-

End Solution

Open Framework

Simplified Service

Creation

Automated Service

Delivery

Security designed in

Cloud Operations Automation

VNF

ARCHITECTURE TENETS

Juniper Networks acquires Appformix

ANALYTICS/ MACHINE LEARNING

STATE-DRIVEN ORCHESTRATION

DYNAMIC PERFORMANCE OPTIMIZATION

REAL-TIME MONITORING &

VISIBILITY

Appformix, as part of the Contrail suite, is designed to provide public, private and telco cloud operators in both OpenStackand Kubernetes environments a smarter, automatic, and agile operational experience at lower total costs.

Architecture for Cloud-delivered CPE Services

Low end

Mid range

Ingegrated

High End

CP

E H

ard

war

e

CPE Software Services

Basic SD-WAN Adv. SD-WAN,

FW, WAN Opt+ Ent.

Routing+ Switching

MPLSBBLTE

Private Cloud

Public CloudPE/GW Cloud Services

Public Cloud

Orchestration

Controller & Orchestration

GW

GW

Managed Access

Internet Access

3a

3b

42

1

• Modular, easily portable SW services and flexible service placement• Enterprise WAN Controller & Orchestration• Ability to seamlessly integrate into existing services at scale

Cloud PoP/DC

https://youtu.be/-pXGCIyDApo

Aggregate Switches

(CSO)Contrail Service

Orchestrator

Network Service DesignerCSO Self Care

Portal

Admin Portal

Services

Internet

Kiosk

Phone

Retail

Surveillance

TV

Smart CityServices (SP3)Service

Provider 2 (SP2)

Service Provider 1 (SP1)

Pilot project in Ottawa

Data Utility Controller (DUC)

Operator View

SP1 View

SP2 View

SP3 View

DUC PortalCPE

CPE

Customer PremisesEquipment (CPE)

Customer n

Customer 1

Customer 2CPE

Payload SwitchesVirtual Network Elements (VNE)

Industrial

Consumer and

Home

Healthcare

Retail

Public Safety

Transportation

Contrail CloudSmart City Services

Juniper & CENGN: Smart City Infrastructure

Summary and key takeaways

• Transition to cloud / wireless has created the right timing for telcocloud (smart infrastructure)

• Architecture choices matter

• Ability to scale and operate the cloud at scale matters

• Build the cloud like a platform – designed for secure operation at scale

Thank you

AUTOMATION

SCALABILITY

Applications are built for five 9’s or six 9s availability

Infrastructure can help them do that but cloud native applications have the resiliency built in

Separate fault domains and make them smalller

INTEROPERABILITY

Better Operability with historical and real time analytics information

Application and Network state for rich diagnostics, reporting, and power operational tools

Smart apps need this information to be make smart choices

Agile DevOps approach

Automate everything

Irregularity is the enemy, simplicity is king

Applications and infrastructure must be able to scale out (almost infinitely) and scale in

elastically

Pets vs cattle mindset shift required

AVAILABILITY

With multi-vendor physical infrastructure for investment protection

Use of standard protocols and open source

All components abstracted out through APIs allowing for interoperability with different

OSS/BSS/orchestration systems

ANALYTICS

Guiding principles of the cloud

Contrail key tenets

Use standard protocols for multi-vendor system integration(BGP, XMPP, OVSDB, …)

Support 3rd Party / Multi-vendor NF out-of-the-box(Technology alliance partners VNF validation, enable svc chaining using routing …)

Support both virtual and physical (installed base)(VNF + PNF, Bare Metal Server integration…)

Open-source product(Contrail Networking, OpenStack …)

Leverage Hardware Offload wherever possible(Offload to NIC, Smart NICs, etc. …)