fast lane to the market: only through end-to-end service … · 2018. 1. 4. · fast lane to the...
TRANSCRIPT
Fast Lane to the Market: Only Through End-to-end Service OrchestrationStefan WalravenCo-founder & CEO of Inmanta
© Inmanta NV 2017 – All rights reserved.
2
11.6 s* Jon Jenkins, Amazon.com – Velocity 2011
Every
Amazon deploys new software to production*
More Mind-blowing Numbers
• Changes to production every 11.6 seconds (Amazon, May 2011)
• +50M deployments annually to dev, testing and production hosts (Amazon, November 2014)
• On average 3 new features per day released on AWS (Amazon, December 2016)
• +100 new products per year (Google)
• 4 000 deployments per day (Netflix, March 2016)
3
Speedy Release Cycles
▪Major source of competitive advantage
▪ Continuous innovation
▪ But people get used to this speed…
▪Where is the average enterprise?
4
Speed & Innovation
?Example: Telecom
5
Example: Telecom
▪ Long innovation cycles:
• 12 to 18 months development cycle
• Up to 90 days service deployment time
▪ Expensive and unscalable appliance-based solutions
▪ Complex manual and proprietary systems interfaces
6
How To Achieve
▪ Faster
▪More flexible delivery & management of services?
▪With less failures
7
End-to-end Service Orchestration
Inmanta End-to-End Service Orchestrator
8
What is End-to-end Service Orchestration?
▪ Automating & streamlining the execution of a workflow or process *
▪ “arranging and coordination of automated tasks” **
▪ “automated arrangement, coordination, and management of computer systems, middleware, and services” ***
▪ Example:• Provisioning consists of multiple tasks and involves multiple systems
9
What is End-to-end Service Orchestration?
▪ Full service delivered to customer• Can be internal customer
▪ >> single server• Application server
• Database
• Network
• Security
• Monitoring
• …
10
3 Dimensions of End-to-end
11
Multi-domain
Multi-layer
Multi-domain
▪ Services• Span over multiple domains
• Across providers, vendors and technologies
▪ Goal:• Deploy end-to-end changes
in a reliable and structured way
• Guarantee consistency across domains
12
Multi-domain
Multi-layer
Example: Telecom
ETSI NFV (1 domain) MEF LSO (multi-domain)
13
Source: SDxCentral
Multi-layer
▪Multiple layers of abstraction• Domain-specific
➢multiple levels of orchestration
▪ Cf. architecture design
▪ Goal:• Reuse & manageability
• Monitoring & analytics
14
Multi-domain
Multi-layer
End-user Service/App Orchestration
NFV Orchestration
VNF Management
Element Management / Config Mgmt
Network Orchestration
(Virtual) Infrastructure Management
Typical Orchestrators: 1 Layer
▪Where to position the orchestration layer?
15
Resource level
Service level
Orchestrationlevel
Abstraction gap to bridge
Abstraction gap to bridge
Step 1 Step 2 Step n
Script Script Script
Defines abstraction level
Typical Orchestrators: 1 Layer
▪ In reality
16
Resource level
Service level
Orchestrationlevel
Abstraction gap to bridge
Abstraction gap to bridge
Step 1
Step 2
Step n
Provision VM
Create config file
Call Service API
Multi-layer Orchestration
▪Maintain architectural abstractions in configuration model
17
Resource level
Service level
Orchestrationlevel 1
Step 1 Step 2 Step 3
Orchestrationlevel 2
St. 1.1 Call Service API
St. 1.2 St. 2.1
Orchestrationlevel …
Full Service lifecycle
▪Not just provisioning and deployment
▪ Goal:• Agile service
development
• Policy- or intent-driven
18
Multi-domain
Multi-layer
Test & ReleaseProvision & Deploy
DecommissionMonitor
Manage & Operate
Design & On-boarding
How To Apply in Your Organization
▪No single orchestrator to automate and manage all aspects• Hierarchy of orchestrators
(or traditional management systems) foro Different domains
o Different abstraction levels
• E.g. Kubernetes for container orchestration
▪ 1 overarching orchestrator to rule them all• Glue everything together
• Keep holistic overview
• Bridge gap to underpinning abstraction layers / orchestrators
• Ensure end-to-end consistency
19
Conclusion
▪ Customers expect instant delivery of value-added services• Pressure to deploy faster and to stay head of competition
▪ Traditional approaches fail to deliver agility and scalability
▪ End-to-end service orchestration• automates and manages the entire operational process
• abstracts away much of the underpinning complexity & heterogeneity
• ensure much faster delivery
• improve flexibility and reliability
20
