PRESENTED BY:
@LIGHT_READING #SDOAUTOMATION
ORCHESTRATING THE LIFECYCLE OF NETWORK SERVICES
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
Panel
Ari Banerjee
VP Strategy
Netcracker
Steve Payne
VP Sales
Sedona Systems
Ian Bresnahan
CEO
Itential
Jose Manuel de Arce
OSS Manager
Telefonica
Ahmed El Sawaf
Network & Cloud
Senior Advisor
STC
Roy Silon
VP R&D
Atrinet
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
Outline
• Automating service design and deployment across test and
production networks brings new challenges for engineers and
operations staff.
• While these teams have historically acted independently, there is a
need for greater collaboration going forward and a need for new tools
to support their workflows.
• This panel will explore the challenges and opportunities of
orchestrating the complete lifecycle of network services from design to
retirement.
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
Orchestration Layers
PNFs VNFs
NFVI
Element Managers
Service Orchestration
Network Service Orchestration
Resource Orchestration
VNF Manager
ETSIMANO
Virtual Infrastructure Manager
Existing OSS
NFVO
e.g. E2E service like VoLTE
NS is built from interconnected VNFs and PNFs
NSO and RO are resource-oriented, application
agnostic, management functions and are not
intended to be implemented separately.
Source: Heavy Reading
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
ZSM Framework Architecture
Source: ETSI
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
Orchestration Taxonomy
Source: Network Service Orchestration: A Survey, IEEE (https://arxiv.org/pdf/1803.06596.pdf)
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
MEF LSO Framework & API Details
Source: MEF
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
VNF DevOps Lifecycle
Source: NFV Service Design & Operations: Saving the Sorcerer’s Apprentice, Heavy Reading
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
Orchestration, Automation & DevOps
Orchestrators & Controllers:
•Service lifecycle management (moves, adds, changes,
disconnects)
•Large-scale, dynamic changes enabled by model-based
approach
•Device agnostic management of services across the network
Orchestration
Automation System:
• Consolidation of scripting tools, orchestrators, & controllers into
single management plane
• Network Intent API capabilities for upstream services such as
CRM & IT Service Management
• Closed-loop automation leveraging monitoring, inventory,
telemetry, and analytics data within automation workflows
Automation
Scripts & DevOps Platforms:
• Large-scale changes, but rigid in the scope of each change
• Transition of scripts to DevOps platforms to increase reusability
• Standardized approach leveraging run books and vendor
specific modules
DevOps Tools
Source: Heavy Reading
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
Audience Question Poll
Which of the following best fits your view?
• I foresee a multi-layered approach to
orchestration with one end-to-end orchestrator
overseeing a number of domain specific
orchestrators
• I foresee a zoo of orchestrators from multiple
suppliers that require significant manual effort
to work in tandem and/or custom integration
• Too soon to say, too hard to tell
To vote please go to pollev.com/jamescrawsha760
P R E S E N T E D B Y :
@LIGHT_READING #CNGEUROPE
Panel
Ari Banerjee
VP Strategy
Netcracker
Steve Payne
VP Sales
Sedona Systems
Ian Bresnahan
CEO
Itential
Jose Manuel de Arce
OSS Manager
Telefonica
Ahmed El Sawaf
Network & Cloud
Senior Advisor
STC
Roy Silon
VP R&D
Atrinet

Orchestrating the lifecycle of network services

  • 1.
  • 2.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE Panel Ari Banerjee VP Strategy Netcracker Steve Payne VP Sales Sedona Systems Ian Bresnahan CEO Itential Jose Manuel de Arce OSS Manager Telefonica Ahmed El Sawaf Network & Cloud Senior Advisor STC Roy Silon VP R&D Atrinet
  • 3.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE Outline • Automating service design and deployment across test and production networks brings new challenges for engineers and operations staff. • While these teams have historically acted independently, there is a need for greater collaboration going forward and a need for new tools to support their workflows. • This panel will explore the challenges and opportunities of orchestrating the complete lifecycle of network services from design to retirement.
  • 4.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE Orchestration Layers PNFs VNFs NFVI Element Managers Service Orchestration Network Service Orchestration Resource Orchestration VNF Manager ETSIMANO Virtual Infrastructure Manager Existing OSS NFVO e.g. E2E service like VoLTE NS is built from interconnected VNFs and PNFs NSO and RO are resource-oriented, application agnostic, management functions and are not intended to be implemented separately. Source: Heavy Reading
  • 5.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE ZSM Framework Architecture Source: ETSI
  • 6.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE Orchestration Taxonomy Source: Network Service Orchestration: A Survey, IEEE (https://arxiv.org/pdf/1803.06596.pdf)
  • 7.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE MEF LSO Framework & API Details Source: MEF
  • 8.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE VNF DevOps Lifecycle Source: NFV Service Design & Operations: Saving the Sorcerer’s Apprentice, Heavy Reading
  • 9.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE Orchestration, Automation & DevOps Orchestrators & Controllers: •Service lifecycle management (moves, adds, changes, disconnects) •Large-scale, dynamic changes enabled by model-based approach •Device agnostic management of services across the network Orchestration Automation System: • Consolidation of scripting tools, orchestrators, & controllers into single management plane • Network Intent API capabilities for upstream services such as CRM & IT Service Management • Closed-loop automation leveraging monitoring, inventory, telemetry, and analytics data within automation workflows Automation Scripts & DevOps Platforms: • Large-scale changes, but rigid in the scope of each change • Transition of scripts to DevOps platforms to increase reusability • Standardized approach leveraging run books and vendor specific modules DevOps Tools Source: Heavy Reading
  • 10.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE Audience Question Poll Which of the following best fits your view? • I foresee a multi-layered approach to orchestration with one end-to-end orchestrator overseeing a number of domain specific orchestrators • I foresee a zoo of orchestrators from multiple suppliers that require significant manual effort to work in tandem and/or custom integration • Too soon to say, too hard to tell To vote please go to pollev.com/jamescrawsha760
  • 11.
    P R ES E N T E D B Y : @LIGHT_READING #CNGEUROPE Panel Ari Banerjee VP Strategy Netcracker Steve Payne VP Sales Sedona Systems Ian Bresnahan CEO Itential Jose Manuel de Arce OSS Manager Telefonica Ahmed El Sawaf Network & Cloud Senior Advisor STC Roy Silon VP R&D Atrinet