View
1.665
Download
0
Category
Tags:
Preview:
DESCRIPTION
DevOps processes (such as continuous deployment and delivery) often involve writing many custom scripts that are triggered by the build system. With that approach, it is relatively hard to trace the deployment process and troubleshoot when something goes wrong. Additionally, custom scripts are often not written in an easily understood manner. In this session we will walk through specific DevOps workflows (such as install, update, etc) using Riemann as the framework in subject and see the steps required to automate those processes. We will also discuss how Cloudify uses Riemann to provide simple execution and monitoring of those workflow processes. We will share how one customer, PaddyPower, was able to leverage Cloudify to transition their traditional IT into a DevOps environment, bridging the gap betwe
Citation preview
Is Orchestration the Next Big Thing in DevOps?
Nati ShalomCTO & 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 NetworkingCompute
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: APIInput:
Email, DocsExecute: 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
NodeCellerMongoDB
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
• 100x developers doing deployments in a consistent fashion
• <2H Move 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
1111
1111
111
Historical Data
0000
0000
011
1111
1111
100
0000
000
1111
1111
111
0000
0000
0
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
Recommended