Is Orchestration the Next Big
Thing in DevOps?
Nati Shalom
CTO & Founder GigaSpaces
@natishalom
DevOps
Through the
Car Industry
Analogy
The Biggest
Revolution?
Gasoline Engine
Sports Car
Model T Assembly Line
“You can choose any
color you want as
long as its black...”
- Henry
Ford
Transformed
the Entire
Industry
• Automobile enters
the mass market
• 10x more cars a day
• 4 months pay to
buy a car
How is this Relevant to DevOps?
DevOps is the Industrialization of IT
IT Pre DevOps IT Post DevOps
DevOps is all
about...
• Releasing new
features and
products faster
and at scale
• 1000s of updates
per day is typical
What’s Changed?
It seems like everything
BUT the kitchen sink is
software defined these
days.
You were
saying?
Everything is Software Defined
We Can Automate Everything
Configuration Networking
Compute
The Missing Piece in the Puzzle
The Missing Piece In the Puzzle?The Missing Piece in the Puzzle…
Software
Defined
Operator
Human vs Software Operator
• Human Operator • Software Operator
Input:
DSL
Execute:
API
Input:
Email, Docs
Execute:
GUI, CLI
Control:
Policy Engine
Control:
Monitoring, SMS
The Impact of Human Error
14
80%
of outages impacting mission-critical services
will be caused by people and process issues
50%
of those outages will be caused by
change/configuration/release integration and
hand-off issues
Orchestration = Software
Operation
Typical Orchestration Model
TOSCA: A Standard Blueprint
Apache Server DB Server
NodeJS
NodeCeller
MongoDB
TOSCA-like Example
• App Network
• App Subnet
• App Port
• Security Group
• Apache Floating IP
• Router Gateway
• Data Network
• Data Subnet
• Data Port
• Security Group
Router
Monitoring, Logging CI
Network View
Topology View
TOSCA-like Blueprint
Real Life
Example
(HP Print)
• 30 HP Helion Public Cloud accounts
• 500+compute instances
• 1400 Peak deployments per day
• 100+compute instances per
management cluster
• 100xdevelopers doing
deployments in a consistent fashion
• <2HMove from HP Helion Public
Cloud tenant to a fully provisioned and
deployed service
Orchestrating Networks and Apps
Send
Metrics
Execute
Policy
Feedback
Correlate
with
Historical
Events
Real Time
Analytics
Deploy
Fail-
over
Scale
Real Time Analytics Cloud Infrastructure
Intelligent Orchestration
Next: Intelligent Orchestration
11111111111
Historical Data
000000000
11111111111
000000000
11111111111
000000000
Does this Mark the End of IT
Operations?
Ops in a
DevOps
World
Apps & Ops
speaks the
same
language
Ops can
deliver real
value –
ensuring that
SLAs are met
More control
Over the
Environment
The Demand For DevOps..
Orchestration Is the Next Big Thing
• Code Example
• getcloudify.org
TOSCA-like Example
Thank You
Nati Shalom
@natishalom

Is Orchestration the Next Big Thing in DevOps

Editor's Notes

  • #6 http://corporate.ford.com/news-center/press-releases-detail/677-5-dollar-a-day
  • #15 A recent Gartner study projected that through 2015, “80 percent of outages impacting mission-critical services will be caused by people and process issues, and more than 50 percent of those outages will be caused by change, configuration, release integration, and handoff issues.[2].” (Ronni J. Colville and George Spafford, “Configuration Management for Virtual and Cloud Infrastructures”)
  • #29 http://www.cloudcomputing-news.net/blog-hub/2013/sep/10/the-challenge-of-predicting-enterprise-cloud-computing-growth/ 83% of enterprises face significant roadblocks that hold them back from moving beyond cost reduction to faster time-to-market and better orchestration of their businesses. Respondents mentioned that politics, budget, time and staff are the main sources of roadblocks to getting more value out of their cloud computing investments. The majority of these roadblocks are not related to IT.  They include lack of clarity regarding organization and budget (37%), resistance to change (16%) and lack of trust (visibility and reliability) (15%).  The following graphic illustrates the enterprise cloud journey as defined in TheInfoPro Wave 5 Cloud Computing Study.