Open Source for the Open Network© 2017 TM Forum | 1 Open Source for the Open Network: A new...

© 2017 TM Forum | 1

Open Source for

the Open Network:A new paradigm needs

a new approach

Laurent Leboucher, Orange

Eyal Felstaine, Amdocs CTO

16 May, 2017

© 2017 TM Forum | 22

The network operating system

© 2017 TM Forum | 3

A ubiquitous network operating system for service providers

What is at stake?

▪ To adopt the speed and scale of the Web Platform Industry

Resilience and scalability through Cloud Native Network Applications

…not from bottom-up duplicated hardware based equipment

Get all the benefits from Moore’s law with commodity hardware

Agile delivery of network software releases

▪ To automate resource management and minimize human interventions

▪ To foster an open industrial ecosystem:

No vendor lock-in (no EMS)

Open to all VNF vendors

Ubiquity and interoperability between service providers

© 2017 TM Forum | 4

A new foundation which will disrupt “vertically integrated OSS/BSS silos”

Network

operating

system

Service (CFS) ordering

Performance Management

Service inventory

Service problem management

Activation and configuration

Usage Management

Service qualification

Service test managment

Customer Platform

Product & Offer Platform

Software Network Service Factory Platform

Distributed Infrastucture as a Service (IaaS)

Network Physical Factories

Design FrameworkRun-time framework: orchestration, control

Analytics

Syste

ms o

f e

nga

ge

me

nt

Syste

ms o

f e

nga

ge

me

nt

© 2017 TM Forum | 5

Network Operating System: key principles

1. Joint Agile Delivery 3. Closed Loop2. Cloud Native Automation

Product Service

ResourceReceipts

Policies

Run-time framework: orchestration, control Analytics

IaaS

controller

Network

controller

Application

controller

Batch Real-time

Telemetry

Incubation

Validation

Collaboration

Vendor Software

Product

Recipes

Policies

VNF components

From 18 months to 6 days

Design framework

Master Service

Orchestrator

© 2017 TM Forum | 66

Why open source?

© 2017 TM Forum | 7

Operator’s hurdle to new service introduction

Service design

VNF testing: automation

script in sand box

Get VNF Package

VNF Certification

Lab

VNF modification

and enrichment

VNF distribution to catalog

Service approval process

Start

Running service E2E in

sand box

Service distribution to

catalog

En

gin

eering

© 2017 TM Forum | 8

Opera

tions

End?

Performance Monitoring

Service Provisioning

Ongoing Updates/ Upgrades

Troubleshooting

Network

Configuration

Maintenance

© 2017 TM Forum | 9

Troubleshooting NFV issue

Proprietary/

closed source

Massively deployed

open source

© 2017 TM Forum | 10

– with closed source

Troubleshooting an NFV issue

VNF vendor CSP in production1. Automation script

doesn’t run

2. Operations notifies

engineering

3. Engineering notifies VNF

vendor tech support

4. Tech support discusses

with product manager

5. VNF product manager

discusses with

orchestrator product

manager

6. Development starts

on both sides

7. Testing

8. F2F meeting to

triangulate the issue

Operations

Engineering

1Product

management

Development

Testing

Tech support

88

6

7

Product

management

Development

Testing

Tech support

6

7

4

3

5

8

5

Proprietary/closed

code orchestrator

25

© 2017 TM Forum | 11

Open source

Orchestrator

1. Automation script

doesn’t run

2. Due to automation

script problem,

Operations notifies

engineering

3. Engineering notifies

VNF Vendor tech support

4. VNF vendor contributes

code in order to fix

the problem

Operations

2

1

3

44

– with open source


5

VNF vendor CSP in production

Engineering

© 2017 TM Forum | 12

Operations

Engineering

Troubleshooting an NFV issue – with open source

DevOps

Development & Operations

VNF vendorOpen source

OrchestratorCSP in production

code

test

deploy

© 2017 TM Forum | 13


Proprietary/closed source

Massively deployed open source

Open source accelerates the speed of innovation

Open source

Orchestrator

Operations

2

1

3

44

5


Engineering


Operations

Engineering

1Product

management

Development

Testing

Tech support

88

6

7

Product

management

Development

Testing

Tech support

6

7

4

3

5

8

5

25

Proprietary/closed

code orchestrator

© 2017 TM Forum | 15

Zoom in on ONAP (Open Network Automation Platform) & OpenECOMP

E-Services Big Data BSS OSS

Dispatch, ticketing,

fundamental planning etc.

Orchestration engine

Adapters (J2EE)

Request decomp. and recipe selection

API Request Handler MSO

Network Adapters Application Adapters

Service Logic Interpreter

Engineering Rules and Inventory

Controllers

Real-time collector Bath collector

Analytic Applications

Streaming framework

Events Pub/Sub

APIs

DCAE

AAI

EntitlementsActive/available

Inventory Management

Resource/service topology

Topology Visualization

Reporting

Manual action

Dashboard

OpenECOMPOA&M

External Data Movement and APIs

Storage Compute NetworkingVNFs/

Applications

Managed Environment

Design studio

Resource onboarding

Certification studio

Policy editor

Policy rules

Conflict identification

Policy CreationService Design

and Creation

Policy StorageCatalog

ProductServiceResource

Process Library

TemplatesRecipes and eng. rules

OpenECOMP Portal

Operation

functionsDesign functions

Workflow/engineering rules and policy

distribution (metadata artifacts/recipes)

OpenECOMP

Controller

Operational

Management

Framework

(OMF)

Common services: logging, data movement, access control and internal APIs

Legend

Design-time framework

Run-time execution framework

© 2017 TM Forum | 16

Why ONAP?

▪ Holistic

▪ Metadata-driven

▪ Policy-driven

▪ Enforces a very open ecosystem:

open source with large momentum

▪ Mature

+ECOMP

Platinum Members

Silver Members

© 2017 TM Forum | 18

Orange/Amdocs project phases

Initial vCPE for residential architecture & models, platform set-up1

2

3

4

Telemetry, monitoring

Automation, policies

vCPE for Residential complete architecture

© 2017 TM Forum | 19

Amdocs & Orange decided to join ONAP as Platinum members

▪ Amdocs NFV/SDN transformation requires a massive shift in operating model – few vendors or few operators

can successfully drive this change, need a community approach

Amdocs has already contributed and will continue to contribute in key areas of the “Platform” to reduce service specific code in the platform (i.e. increase service velocity)

Service providers and VNF vendors needed ONE standard way of onboarding, instantiating and operating to get cost of the equation – we believe ONAP provides a holistic approach

▪ Orange possible contributions to ONAP ONAP installer

CI/CD environment

Containerized VNFs

VNF guidelines (standardized onboarding process)

Hybrid management (service with physical and virtual resources)

AppC genericity assessment

DCAE generic applications

Micro services on top of ONAP towards “OSS” and “BSS,” starting with service ordering

Open Source for the Open Network© 2017 TM Forum | 1 Open Source for the Open Network: A new...

Documents

Transcript of Open Source for the Open Network© 2017 TM Forum | 1 Open Source for the Open Network: A new...