DevOps Yourself
Improve your Go To Market strategy
What is DevOps ?
Increase your ROI
Release more rapidly
Solution : the DevOps Pattern
Let's have an exemple
Glossary
Cloud orchestator, enable the user to deploy an application without worrring about the infrastructure or the ressource management.
Additional layer for the cloud orchestrator that gives the application a management interface with analitics, allows collaboration and has several additional software to be implemented to answer your need.
Computing support that changes the paradigme of deploying an application. Do not be restricted by the infrastructure of your cloud supplier, set your needs and let the algorithm optimize them.
Click on the images to check out the presentation in video
The concrete comparison
Time consumming tasks
Traditionnal IT Ops
-
Communication (i.e. meetings, writing emails, planning) - 7.2 hours
-
Firefighting - 4.8 hours
-
Automating repetitive tasks - 4.6 hours
Make the two teams meet regularly to agree on the project issues and work on the solutions together
-
Automated deployment
-
Continuous delivery & deployment
-
Infrastructure upgrades
-
Cloud portability
-
Works with your favorite DevOps tool chain
-
Integrates with your favorite monitoring tools
Final punch
A concrete example
Alien4Cloud is an Application Lifecycle enabler, associated with Cloudify the Cloud orchestrator, they make a perfect tool for the team willing to use a Devops Methodology.
“The relationship between dev and ops in a company is defined by the release process. You will understand the relationship if you examine this process.”
- Patrick Debois, father of the DevOps movement.
Plan-Do-Check-Act
ITIL
AGILE
SCRUM
Lean Management
Phone Call
Conferences
Old School DevOps Theory
DevOps
-
Automating repetitive tasks - 5.3 hours
-
Communication (i.e. meetings, writing emails, planning) - 5.1 hours
-
Infrastructure improvements - 4.8 hours
Management, Failure and release
DevOps
Traditionnal IT Ops
-
only 1 in 8 respondents have fully-automated processes. Nearly one-third do it manually
-
Apps deployed during weekday working hours 51% of the time, with all staff on hand in case there is a fire to fight. In 16% of cases, deployments happen during weekend nights
-
Around 75% of respondents rely on manual processes to recover from a release failure, which adds an increased risk of human error to an urgent recovery process.
-
DevOps oriented teams release apps in half as much time as
Traditional IT Ops teams (average time per release: 36 min vs. 85 min, median: 15 min vs. 30 min).
-
Puppet (40%) and Chef (31%) take the lead for popular infrastructure configuration tools
-
DevOps oriented teams are nearly 2x more likely to recover from a failure in less than 10 minutes
