multi-domain service orchestration and microservices architectures

Sponsored by:

Multi-domain Service Orchestration and Microservices architectures:

Solving the Transformation challenge

Sponsored By:

Sponsored by:

Today’s Presenters

Moderator Presenter

Caroline Chappell Recep OzdagPrincipal Analyst Senior DirectorNFV & Cloud Solution MarketingHeavy Reading BluePlanet,

a division of Ciena

Sponsored by:

Agenda

• Managing the virtualized network: transformation challenges

• The importance of self-sufficiency• The benefits of a microservices-based

management platform• The role of a multi domain service

orchestrator• Q&A

Sponsored by:

Transformation challenges

• Adjust network operations for the virtualized network: OSS/NFV MANO/SDN controller co-existence– Service orchestration vs multi-domain service

orchestration • Enable rapid service lifecycle management

automation – ‘DevOps’– Supporting network operations with DIY tools

• Reduce time and cost associated with service change– Microservices-based deployment

Sponsored by:

Emerging Multi Service Domain Orchestration architecture

Business Layer Orchestration

Multi-domain service orchestration

Local domain Service orchestration,

SDNC/existing OSS

Resource management(EMS)

Local domain Service orchestration

SDNC/existing OSS

Resource management(EMS)

Local domain Service orchestration

NFV MANO

Resource orchestrationMANO/OpenStack

Transport network

control loop

Access network

control loop

Cloud infrastructure control loop

Sponsored by:

Microservice architecture for speed and flexibility

Microservices is a software architecture style in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. These services are small, highly decoupled and focus on doing a small task,facilitating a modular approach to system-buildingSource: Wikipedia

• Becoming the standard for cloud native app development• Scalability and resilience properties • Can be deployed using containers• Components easily changed/replaced for rapid feature

innovation• Supports continuous integration• ‘Two pizza’ DevOps team rule• ‘SOA done right’

https://en.wikipedia.org/wiki/Architectural_pattern

https://en.wikipedia.org/wiki/Software_application

https://en.wikipedia.org/wiki/Process_(computing)

https://en.wikipedia.org/wiki/Language-independent_specification

https://en.wikipedia.org/wiki/Application_programming_interface

https://en.wikipedia.org/wiki/Service_(systems_architecture)

https://en.wikipedia.org/wiki/Coupling_(computer_programming)

https://en.wikipedia.org/wiki/Modularity

https://en.wikipedia.org/wiki/System

Sponsored by:

TMF Future Mode of Operation

• Microservice architecture, domain-driven design (DDD) and composability provide inspiration for the TMF’s future approach to managing the cloudified network

• TMF Future Mode of Operation (FMO) approach proposes that the network will be composed from “well-behaved” functions, each integrating with Operations, Applications, Security and Execution environments

PolicyWorkflow

(orchestration)Function

ManagementFunctions

(eg monitoring)

Application Functions

(business use)

SecurityFunctions

(eg access control)

EnvironmentFunctions

(eg infra resources)

Application Model

Security Model

Management ControlContinuum (MCC)

Model

InfrastructureModel

FMO component functional overview – TMF paper

Models will be derived from

multiple sources.

Recursion and composability are

key principles

Sponsored by:

Network IT power shift away from professional services

“If you go to the IT department to get things done, it’s astronomically expensive. The OSS people have to write requirements, then code and test, but they don’t understand the network. Give me the tools and I can rapidly

prototype what I want in a day. What I want from the OSS guys is an abstract view of the service and I’ll decide how to implement it.”

Network engineer, US cable operator

TOSCA

YANG

Multi-Domain Service Orchestration and Micro-Services Architecture

Recep Ozdag, Sr. Director of MarketingCiena Blue Planet Division

Solving the Transformation Challenge

Fundamentals of a Successful Transformation to SDN and NFV

Self-Sufficiency

Micro-Services & Open Source Technology

Multi-Domain Service Orchestration A B

Service Ordering and DeliveryService Planning

Weeks to Months

Network architect defines and programs physical and virtual resources using template to create new service offering

Customer orders new service via operator’s web portal

Minutes to Hours

Orchestration platform and/or controller instantiates and automatically configures the end-to-end service

Service is activated in real-time and available to the customer

Legacy OSS Limiting SDN and NFV Benefits

Legacy OSS is hard coded, no self-service

Pro-serv required for even simple changes

Time-to-market affected by rigid processes

Significant cost to update OSS

Slow OSS update with the same vendors

Model and Template-based Service Development Approach

InformationModel

Service A

DataModel

YANG

TOSCA

(Topology and Orchestration Specification for Cloud Applications)

E-LineService

MobileBackhaul

Service B

Service C

Model and Template-based Service Development Approach

Service AInformationModel

• BPMN is the global standard for process modeling

• End-to-end process flow

• Technical and business users

• Business/IT alignment

• Streamlines integration of SDN and NFV-based services with the OSS/BSS

• Simplified creation, integration, and operation

• Accelerate new product introduction

• Enables operational agility and improved time-to-market • DevOps style workflows and processes break the vendor lock-in cycle

CustomerPortal

Blue Planet: Delivering on Self-Sufficiency

LegacyNetwork

Software-Defined WAN

NFVCloud

Get Toke

n

vCPE

E-line

Github

Image

Run Heat

Template

Service

Chain

TOSCATemplate(s)



Self-Sufficiency


✔

Micro-Services Architecture

Monolithic

Vs.

• Function-specific software containers

• Common with Web 2.0 cloud players and others:

• Micro-service vs. monolithic approach:• Accelerated development

• More graceful scaling

• Streamlined feature enhancements

UIMicro-

services

ComponentMicro-

services

Blue Planet Core Platform

Service Analyze

r

PCE

• Tailored suites of micro-services enable Blue Planet to support different use cases

• SDN Management and Control

• NFV Service Orchestration

• Multi-Domain Service Orchestration

• Or, any mix of use cases

• Ala-carte customization enables a single platform to meet customer’s business and operational requirements

UIMicro-

services

ComponentMicro-

services

Blue Planet Core Platform

Distributed, Real-time

Event Processing

DevOps

Elastic Scale & High Availability

Seamless Open Source Integration for Webscale

Distributed HA

Database

Load Balancing

Deployment Configuration Monitoring

Logging

SDNController Web UI APIs

The Central Office Re-Architected As a Data Center (CORD)

• Brings the economics and agility of a cloud data center to the service provider central office

• Replaces the fragmented, proprietary infrastructure of the traditional CO with open, commoditized software and hardware building blocks

• Enables simpler, more frequent updates and changes• Rapid adoption of latest technology innovations, including 3rd party and open source

components

Blue Planet: Micro-Services Architecture and Integrated Open Source


Self-Sufficiency


✔

✔


OSS/BSS OSS/BSS OSS/BSS OSS/BSS OSS/BSS OSS/BSS

Recreates the Silos and Operational Inefficiencies of the Legacy Era

Limitations of 1st Gen SDN and NFV Solutions

• Multiple monolithic apps for individual vendor and technology domains

• Duplication of functions

• Legacy OSS/BSS lacks the programmability n

LegacyNetwork

SDN-Enabled WAN

NFVCloud

NMSWAN SDN

Controller

NFVO

DC SDN Controller

Data Center

• FCAPS• Inventory • Topology • ...

• FCAPS• Inventory• Topology• ...



Open APIsOSS/BSS OSS/BSS OSS/BSS OSS/BSS OSS/BSS OSS/BSS

Overcoming the Limitations with MDSO

••

••

• FCAPS• Inventory • Topology • ...




LegacyNetwork

NMS

SDN-Enabled WAN

WAN SDN

Controller

DC SDN Controller

Data Center

NFVCloud

NFVO

Multi-Domain Service Orchestration •

• Breaks down vendor and technology silos• Automates and SDN and NFV-based services from end-to-end

Multi-Domain Service OrchestrationMulti-Domain Service OrchestrationMulti-Domain Service OrchestrationMulti-Domain Service OrchestrationMulti-Domain Service Orchestration

Operationalizing SDN and NFV More Efficiently

Domain 2 Domain 1

NFV MANO

CO/PoP

Domain 3Domain 4Domain 5

SDN Controller

NMS

NFV MANO

SDN Controller

NMS/SDN Controller

Controller

VNF VNF

PCE KVM

GUI VMPolic

y

Serv

ice

Tem

plat

esU

-ser

vice

s

VNF VNF

VNF VNF

ESX

ONOS

PCE KVM

GUI vFWPolic

y

Analytics Analytics


Self-Sufficiency

Micro-Services & Open Source

✔

✔

Multi-Domain Service Orchestration

A B✔

• Operational agility• Time-to-market • Breaks vendor lock-in

• Simpler, more frequent updates• Rapid technology adoption and innovation

• Breaks down silos• Automate services

from end-to-end

Thank You