v

NetworkAutomation Automation& Network Orchestration With with and Orchestration Carrier NFV Carrier SDN SDN & and NFV Caroline Chappell Senior Analyst Heavy Reading

OUR PANELISTS • Margaret Chiosi, Distinguished Network Architect, AT&T • Ralph Santitoro, Director of Strategic Market Development, Fujitsu • Nirav Modi, Director of Software Innovations, Cyan • Manish Gulyani, VP Product Marketing, Alcatel-Lucent • Prayson Pate, Chief Technologist, Overture Networks

www.lightreading.com

AGENDA • Operationalizing SDN and NFV: abstracting, automating, and orchestrating the network • Panel Discussion • Q&A

www.lightreading.com

SDN vs NFV

Function/ location separation

COTS hardware Vendor-independence

Initial focus on atomic network functions, but topology focus coming

Improved operational efficiency Standardized, open interfaces Dynamic chaining of network functions Centralized orchestration and management

Reduced power usage (elastic scalability)

SDN

NFV

Rapid service innovation

Control/ data plane separation

Consistent policy framework

Focus on network function connectivity (logical topologies)

Network Automation & Orchestration With Carrier SDN & NFV Ralph Santitoro Director of Strategic Market Development [email protected] October 2, 2013

Current OSS Landscape OSS Problem Statement  OSS’s have limited or no technology abstraction  Technology abstraction simplifies multi-vendor, multi-layer, multi-technology management

 Difficult and time consuming to innovate  Cost prohibitive to experiment with new types of services or customization of existing services

 Provisioned Networks  Limited Programmability and Service Elasticity

 Managed Network Functions  Limited Automation

Our Carrier’s cloud-centric OSSs must worldevolve requires to automation support this and newelasticity reality NFV and SDN Management Orchestration

(c) Copyright 2013 Fujitsu Network Communications, Inc. All Rights Reserved.

6

SDN Management Orchestration Model  In the Southbound direction (SDNC  NE/EMS)  Abstracts networking technology/protocol details from NetOS/SDN Controller  Provides vendor-independent programmability of network elements

 In the Northbound direction (SDNC Apps)  Provides network/service programmability (APIs) by software applications  Abstracts networking technology details from the applications

Apps

Apps

Apps

Apps

Northbound APIs (network/service abstraction)

Network OS/SDN Controller Southbound APIs (technology abstraction) OpenFlow

Network Element

TL1

Network Element

NFV and SDN Management Orchestration

SNMP

Network Element

XML

Web 2.0 RESTful APIs using, e.g., JSON representations, for Apps to program networks and services Software adapters for NetOS/SDNC to NE/EMS protocol translation

EMS

(c) Copyright 2013 Fujitsu Network Communications, Inc. All Rights Reserved.

7

NFV Management Orchestration Model ETSI NFV ISG (Work in Progress) OSS / BSS Virtual Network Functions VNF

VNF

VNF

VNF

Virtual Machines (VMs)

Network Function Virtualization Infrastructure (NFVI) Virtual Resources vCompute

vStorage

vNetwork

VNF and NFVI Management and Orchestration

Virtualization Layer (Hypervisor) Physical Resources Compute

Storage

Network

(c) Copyright 2013 Fujitsu Network Communications, Inc. AllComputing Rights Reserved. NFV Management & Orchestration following Cloud Model8 NFV and SDN Management Orchestration

Next Generation OSSs require Orchestration of Cloud Computing, SDN and NFV Management

Application Layer

Business Applications RESTful APIs

VNF Management and Orchestration

VM

Network/Service Abstraction

VNF VNF VNF VM VM VM

Virtualization (Hypervisor) vCompute

vStorage

NFV NFV and SDN Management Orchestration

vNetwork

Control Layer

Network Network Service Network Service Service

Network Services

Technology Abstraction OpenFlow

TL1

SNMP

Infrastructure Layer

SDN (c) Copyright 2013 Fujitsu Network Communications, Inc. All Rights Reserved.

9

Cyan Solutions

10

© 2013, CYAN, INC.

Reinventing the OSS  Network and DC are converging into a singular resource pool

 Elasticity previously only available in DCs is migrating to the networking space  Current OSSs not architected to deploy SDN technologies and NFV orchestration  Carrier-grade service requirements still need to be met  Service agility, service innovation as well as transformation of cost and operational models are drivers for change 

11

Existing systems not flexible, service introduction can take months

© 2013, CYAN, INC.

Network & Cloud Convergence Black, White and mostly Grey?  Majority of economically compelling NFs virtualized  Larger freedom of (re-)location  Consolidations

Provider B

Wholesale

Enterprise Provider A

Enterprise Data Center Residential Wireless Legend:

- Network functions as specialized physical NEs - Generic switch as physical NE

- Data Center providing NFV Infrastructure services

- Virtual network functions

12

© 2013, CYAN, INC.

The OSS Needs New Clothes Service Orchestration Cloud Orchestration

APIs

APIs

Cloud Services

Multi-Layer, Multi-Vendor NaaS

VNF Services

Controller

Controller

Controller

Access

13

NFV Orchestration

Network Orchestration

Metro

Core

© 2013, CYAN, INC.

Enabling SDN and NFV BSS/OSS

BSS/OSS

APIs

APIs

SDN/NFV Platform

NMS/EMS

NMS/EMS

NFV Infrastructure

CMS CMS CMS

14

SDN/NFV Platform

CMS CMS

© 2013, CYAN, INC.

Multi-Domain SDN/NFV Orchestration

15

© 2013, CYAN, INC.

NETWORK AUTOMATION & ORCHESTRATION WITH CARRIER SDN & NFV Manish Gulyani September 2013

NETWORK WANTS TO EMBRACE CLOUD FROM CONVENTIONAL INFRASTRUCTURE …

… TO A SOFTWARE DEFINED ENVIRONMENT

IPTV

MOBILE CORE

CDN

RNC/BSC

IMS

RNC/BSC

CDN IMS

EPC

OSS/BSS

EPC ENTERPRISE SERVICES

IPTV

ENTERPRISE SERVICES

SDM OSS/BSS

FULL AUTOMATION

RAPID PROGRAMMABILITY

18

IMPROVED EFFICIENCY

YOU NEED MORE THAN VIRTUALIZATION LEAN: AGILE & COST EFFECTIVE

FIT WITH SLAS AS REQUIRED

ECOSYSTEM

REAL TIME

99.9 to 99.999%

SECURITY

UNRESTRICTED NETWORKING

REGULATORY COMPLIANCE

19

CLOUD ORCHESTRATION & NETWORK AUTOMATION REQUIREMENTS TO CLOUDIFY THE NETWORK

VIRTUAL & NON-VIRTUAL BARE METAL & CONVENTIONAL SYSTEMS

app

RAPID ONBOARDING & AUTOMATED LIFECYCLE MANAGEMENT

E2E ASSURANCE & ANALYTICS

DYNAMIC CAPACITY MANAGEMENT AT SCALE

UNCONSTRAINED CONNECTIONS RESPECTING APPLICATION SECURITY & QoS 20

MUST FIT INTO AN OPEN CLOUD ENVIRONMENT

Cloud services & capabilities

IT services (PaaS, IaaS)

NFV applications

Application services (SaaS) Public clouds

Cloud intelligence & control

Cloud orchestration & automation

Network virtualization & automation

Hybrid clouds

Virtual private clouds

Open, distributed cloud infrastructure

Enterprise private clouds Customers

DEPLOY APPLICATIONS ON TOP OF ANY CLOUD H/W, OS OR NETWORK 21

PUTTING IT IN ACTION ADDING SIGNALING CAPACITY TO A VIRTUAL EPC

1

Cloud Mgr & Orchestrator

2

EPC Mgmt System

vMME recipe

5

Scenario After introduction of a set of small cells, the signaling traffic load is much greater than expected

Network Services Policy

3

SDN Controller

vMME Virtual Routing & Switching Native OS (Optional) Hypervisor Generic x86 Hardware Virtual Operating Environment

22

4

UNDERTAKING THE JOURNEY

LIFECYCLE

MATURITY LEVEL

AUTOMATION

CLOUD DC DEPLOYMENT EARLY VIRTUALIZATION

IMPLEMENTATION 23

FULL CLOUD OPERATION

Carrier Class Orchestration for SDN & NFV Prayson Pate Chief Technologist Overture Networks

OVERTURENETWORKS.COM

Carrier Orchestration is Different! Traditional orchestration (e.g. AWS CloudFormation) is focused on the data center.

26

Carrier Class Orchestration for SDN & NFV

Carrier SDN and NFV will be used to build carrier services across the network; orchestration must reflect additional requirements.

Resource Acquisition, Assignment & Span • In a data center, resources are all equivalent. • In an NFV network location matters • Span extends beyond data center to MEN and WAN Metro Datacenter Not just in here

All the same These resources are scarce, but lower latency

But also here Metro Network

Central Office Mini-Datacenter 27

Carrier Class Orchestration for SDN & NFV

Customer Site

Lifecycle and Work Flow • Critical to tie into higher-level systems • Could be OSS/BSS systems • Could be network applications • Programmable and transactional behavior on service activation • Reliability and status monitoring

28

Carrier Class Orchestration for SDN & NFV

Service Elasticity and Orchestrator Scalability • Services built using NFV must have VNF components that are elastic / horizontally scalable • Can’t be simple conversions of software to run on a server instead of an appliance

29

Carrier Class Orchestration for SDN & NFV

Orchestrator Multi-Tenancy • Wikipedia: “Multi-tenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple clientorganizations (tenants)” • Different from “virtualization where components are abstracted enabling each customer application to appear to run on a separate physical machine.” • Orchestrator multi-tenancy simplifies system design and integration into higher level systems.

30

Carrier Class Orchestration for SDN & NFV

Summary of Carrier Class Orchestration Aspect Resource Acquisition and Assignment Span of Control Lifecycle and Work Flow Service Assurance and Resilience

Data Center All resources are equivalent Within data center Controlled directly by user Coarse status monitoring

Elasticity, Scalability Current resources and Multi-tenancy are elastic 31

Carrier Class Orchestration for SDN & NFV

Carrier Class Location, latency and bandwidth matter Across metro area Tied into higher level systems Transactional behavior and fine status monitoring VNFs must be elastic and orchestrator multi-tenant

An Entrance to a Smarter Network

Thank You!

[email protected] OVERTURENETWORKS.COM

QUESTION 1 What do we mean by orchestration? Service orchestration? Resource cloud orchestration? Controller orchestration?

www.lightreading.com

QUESTION 2 What happens to legacy OSS? What is the migration path to SDN/NFV management approaches?

www.lightreading.com

QUESTION 3 What are the largest barriers to operationalizing SDN and NFV?

www.lightreading.com

QUESTION 4 Can SDN and NFV be introduced into legacy networks or should they support new services in a greenfield way?

www.lightreading.com

QUESTION 5 How much of the network can a single vendor realistically orchestrate? What are the specific standards needed here?

www.lightreading.com

QUESTION 6 How far should NFV management and orchestration follow the IT cloud management paradigm?

www.lightreading.com

QUESTION 7 What are the benefits of SDN/NFV network automation and orchestration?

www.lightreading.com

Q&A www.lightreading.com