four%pillarsof%orchestration:%% …€¦ · architecture%for%lifecycle%service%automation...
TRANSCRIPT
Carl MobergTechnology Director, NFVSeptember 7, 2016
CKN Webinar Series #3: Orchestrated Assurance
Four Pillars of Orchestration: Architecture for Service Lifecycle Automation
• Architecture for Lifecycle Service Automation• Four Pillars of Orchestration • Pillar 3: Orchestrated Assurance• Demo• Resources • Q&A
Agenda
Architecture for Lifecycle Service Automation
Event ManagementAlarm and FaultCustomer PortalsOrder Management
Orchestration Reference Architecture
OrchestratedAssurance
OrchestratedFulfillment
NFVOrchestration
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 andvalue chains
§ OTT co-opetition
Changing customer behavior and new expectations
§ Everything on demand§ New services with a pressof 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
Background #1
Background #2
Background #3
• Not customer and service centric
Challenges Summary
• Fear the great mapping machine
• Connect fulfilment and assurance
Where we need to go
Software-defined testing and assurance in network
Orchestrator
ServiceConfiguration
Fulfilment(Configuration)
Fulfilment(Testing)
Assurance(SLA, Trblsh)
Automated Automated Automated
Metro&and&Access WAN Data&CenterCPE
ServiceHealth
Orchestrated Assurance – Moving Parts
OrchestratedAssurance
OrchestratedAssurance
Orchestrated Assurance
Top-down Service KPI and SLA Monitoring
Bottom-up Service Topology, Service
Impact
Is the customer happy?
What is broken?
Technologies
Overall Model Structure
YANG Model Definition Example Values
SLA Acceptable, Good
Actions Activation/Bandwidth Test
Service Status Operational States
Service KPI Loss, Latency, Jitter
VM Templates vFW, vProbe
Service Configuration AS-number, endpoints
L3 VPN
End-point• KPI values• Actions
Network SLA
Video SLA• KPI Thresholds• ES Thresholds• SLA Thresholds
NSD
VNFD
vProbevPEvFW
Activation testsStart SLA monitoring
Mapping to Model Tree
Principles by Example
Example Service: MPLS L3 VPN w Service Chain
CE
vPEvFW
CE
PE
P P
PP
MPLS VPN: SDN Component
CE
vPEvFW
CE
PE
P P
PP
MANO Service (NS, NSD, NSR)
VNF VNF
MANO VLD/VLDR (SDN)
Service'Orchestration'Spans'Multiple'Domains
3
Resource-facing Service
Orchestrated Assurance
CE
vPEvFW
CE
PE
P P
PP
vProbe
Service SLA’s / KPI’s
Service Impact
Orchestrator dynamically:- Maintains service KPI probes- Maintains service topology
OrchestratedAssurance
3
Demo ScenarioVirtual Service Chain
• Cisco NSO and ESCwww.cisco.com/go/nso
• Editorial Resources on LR
Resources
• Four Pillars of Orchestration, Webinar Series 4: “Data Models and Data Model Mapping”
To register, go to www.ciscoknowledgenetwork.com
Coming in September….
Q&A
Background
Software-definedtesting andassurance
Orchestrator
Service Health
ServiceConfig
Fulfilment(Configuration)
Fulfilment(Testing)
Assurance(SLA, Trblsh)
Automated Automated Automated
• Technology trends driving customer expectations, especially network virtualization, have made service design and delivery vastly more complex
• Move from:• Complex service interdependencies • Hard-coded integration
• Towards:• Services viewed as atomic functions that can be assembled and disassembled in myriad of ways, on demand
• Automated, repeatable, reliable, end-to-end service orchestration
Change Agents?