Four Pillars of Orchestration : Architecture for Lifecycle …...Carl Moberg Technology Director,...

Carl Moberg Technology Director, NFV May 4, 2016

CKN Webinar Series One : Orchestration Across Multiple Domains

Four Pillars of Orchestration : Architecture for Lifecycle Service Automation

2 © 2014 Cisco and/or its affiliates. All rights reserved.

•  Architecture for Lifecycle Service Automation •  Four Pillars of Orchestration

•  Pillar 1 : Orchestration Across Multiple Domains

•  Customer Use Case : Softbank

•  Demo

•  Resources

•  Q & A

Agenda


Architecture for Lifecycle Service Automation

Event Management Alarm and Fault Customer Portals Order Management

Orchestration Reference Architecture

Orchestrated Assurance

Orchestrated Fulfillment

NFV Orchestration

OSS

Orchestration

Network


Why Automate?

Execution at the speed of software

!  Agility, DevOps, NFV, SDN, new services platforms

Rapidly changing business models

!  Cloud services, virtualization, programmable networks

!  New ecosystems and value chains

!  OTT co-opetition

Changing customer behavior and new

expectations

!  Everything on demand !  New services with a press

of a button

All of this requires successful, flexible automation. But complexity has destroyed many automation initiatives.


The Four Pillars of Orchestration

Orchestration Across Multiple Domains

1

State Convergence

2

Orchestrated Assurance

3

Data Models and Data Model Mapping

4

Foundation for Full Lifecycle Service Automation


•  Networks are physical, virtual, interfaced through SDN controllers, NFV Orchestrators, or traditional means (CLI)

•  Revenue not driven from creating VMs or configuring SDN applications — but end-to-end services

Design the Service You Sell

End$to$End'Service'Orchestration

NFV Network'Configuration Applications

Assurance

SDN


NFV Management & Orchestration

NFV-O (NFV Orch.)

Virtual Infra Manager

EMS 1 EMS 3 EMS 2

On-

Vi

What about NFV Orchestration ?

VNF-M (VNF

Managers)

VNF-M (VNF

Manager)F Managers)

OSS / BSS

NFVI

Hardware Resources

Compute Network Storage

EMS 1 EMS 3 EMS 2

Nf-Vi Virtualization Layer

Virtual Compute Virtual Network Virtual Storage

Vn-Nf


NFV Management & Orchestration

NFV-O (NFV Orch.)

Virtual Infra Manager

EMS 1 EMS 3 EMS 2

On-

Vi

What about NFV Orchestration ?

VNF-M (VNF

Managers)

VNF-M (VNF

Manager)F Managers)

OSS / BSS

NFVI

Hardware Resources

Compute Network Storage

EMS 1 EMS 3 EMS 2

Nf-Vi Virtualization Layer

Virtual Compute Virtual Network Virtual Storage

Vn-Nf

Application Lifecycle

Service Lifecycle


NFV Service – Necessary, but not Sufficient

ETSI NFV services

Network service: •  A set of VNFs with optional

VNF forwarding graphs •  Configuration of VNF is out of

scope •  Examples: Deploying vEPC

•  Spans several Network Elements

•  One Network Element supports multiple services instances.

•  Examples: E-Line, VPN, VOIP connection, 4G mobile data

“Service Provider” Services

TM Forum Phrases •  Readiness: NFV Service •  Fulfillment: Service Provider Service

is a subset of


Example Scenario Virtual Service Chain


NSO

Example Scenario: Virtual Service Chain

NFVI VIM

VNFM

NFVO Service Activation

Order Management

PNF


NSO

Example Scenario: Virtual Service Chain The Create Operation

NFVI VIM

VNFM


Order Management

PNF

Step #1: Onboarding •  RFS Service •  VNFDs and NSDs •  …in catalog


NSO


NFVI VIM

VNFM


Order Management

PNF

Step #2: Order Arrives •  From OM according to

RFS service model (instantiate)

•  Order spans physical end-points, but also virtual router and firewall

•  NSO starts a transaction


NSO


NFVI VIM

VNFM


Order Management

PNF

Step #3: Stateful Convergence •  NSO decomposes operation into

required actions: 1.  Configure PNFs 2.  Deploy and stitch VNFs

(FW and vRouter) according to NSD and VNFDs

3.  Configure VNFs •  Close transaction on success

vFW vRtr


NSO

Example Scenario: Virtual Service Chain The Delete Operation

NFVI VIM

VNFM


Order Management

PNF

•  Order comes in to remove service •  NSO decomposes operation:

1.  Remove NSR and associated VNFRs and destroy VNFs

2.  Clean up configuration on PNFs


NSO

Example Scenario: Virtual Service Chain The Update Operation

NFVI VIM

VNFM


Order Management

PNF

•  Order comes in to remove firewall service from chain

•  NSO decomposes operation: 1.  Replace running NSR with

new, smaller NSD instance including new VLDs

2.  Update configuration on vRouter

3.  Update configuration on PNFs

vRtr


Customer Use Case: Softbank


•  VPN Plus cloud-based security services for SMBs and Enterprises

•  Virtualized Cloud Services: PE Routing, VPN Termination, Firewall, Web Filtering, Remote Access, Secure Proxy, HTTP Virus Check, Email Security

Overview


Orchestration Overview

DC #1

VTS

vCenter ESXi

Cluster VMs PNF Device

Pool

VNFs

DC #2

ESXi Cluster VMs

PNF Device Pool

VNFs

Internet

VTS

vCenter

Tail-f NSO


Orchestration Architecture

OSS Systems

Assurance Info

Tail-f NSO

VTS NED vCenter NED NEDs

Web Portal

YANG Service Model

VTS vCenter

dvSwitch VM

vSphere

Multi-Vendor PNF/VNF

“Un-managed” Day-0 configuration only

• Validation

• Resource Reservation - VRFs

- IP Subnets

- Dedicated/Shared PNF

• Topology - L2 Segments

- vCenter Port Groups

• VNF Instantiation

• PNF/VNF Configuration throughout service lifecycle

Fulfillment request Orchestration Steps


Demo


NSO 4.1.2

Demo Environment

NFVI OpenStack

Cisco ESC


Order Management (that’s me)

IOS-XR vASA CSRv


•  Cisco NSO and ESC www.cisco.com/go/nso

•  Editorial Resources on LR

Resources


•  Four Pillars of Orchestration, Webinar Series 2: “State Convergence”

To register, go to www.ciscoknowledgenetwork.com

Coming in July….


Q&A

Date post:	24-Sep-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

Four Pillars of Orchestration : Architecture for Lifecycle …...Carl Moberg Technology Director,...

Documents