2. “DevOps is an approach to collapse the barrier between the Development and the Infrastructure (or
Operations) Team”.
The dependency between the Development and the Infra Team is a common scenario in any real
time Project. More than the “dependency” its the “time” that’s the “worry factor”.
Request for a VM – CentOS, Oracle 11i,
4gb RAM, 250gb free space
Min 4-6 weeks with Approvals, Procuring
Licence and finally handing over
Time is the Biggest Worry Factor – With Agile Mode 4-6
weeks waiting time is COSTLY
3. • Fear of Change - application being brittle and vulnerable might break or go down
• Risky Deployments - pray and push the code quietly to PROD and get a sense of relief
• Developer Mindset – “It works fine on my system”
• Isolation and Splitting of Teams - divides the Team into “us and them”
• Battle between SysAdmin and developers
4. • Based on the activities, being performed, at a very high level it might look as if, “this is what the
sysadmin does!!”. But the answer is NO. There are a lot of other things done by the DevOps.
• There is a nice article that talks about this Debate DevOps vs SysAdmin.
DevOps SysAdmin
6. • Eliminate risk of change
• Enable live user tests and data-driven design choices
• Self-service deployments through tools and automation
• Monitoring made easy
• Infrastructure Renaissance
• Agile SysAdmin
• Infrastructure Coders
• SysAdmin Coders
7. • Requesting for a VM or generating a VM on the fly dynamically. To facilitate this a GUI can be
made available to a Developer :
• Once the above details are filled a Manifest File is created to spin-off a VM on the fly
• Similarly for replicating multiple cloned server open source tools like Puppet, Chef can be used. In
case of Puppet, a declarative scripting or coding is required for cloning multiple servers
9. • Time-to-value is much shorter because IT cycle time is greatly reduced
• Software features are released more quickly and regularly
• Releases are stable and predictable
• Faster implementation and better quality
• Reduce and eliminate wasteful deliveries
• Collaboration between your development and IT operations teams
• Easy and faster access to new features and business functionalities
• Accept changes in smaller, granular and manageable portions
• Less disruptive upgrades -> take less time -> low cost -> require fewer resources
• Better visibility of the features for the next release
• Better change management in the environment
10. • ”The DevOps movement is characterized by people with a multidisciplinary skill set - people who are
comfortable with infrastructure and configuration, but also happy to roll up their sleeves, write tests, debug,
and ship features”
• “This, of course, has a positive effect on the bottom line - better reliability and availability, happier clients,
faster time to market, and more time to focus the team's energy on core business rather than wasteful
administration and firefighting”
• Another important thing to note “DevOps is a not a Technology Problem, it’s a Business Problem”
PN : Quotes are from one of the articles mentioned in the Reference Links Slide
11. For most of the slide contents the following Links were used as Bible :
• What Is This Devops Thing, Anyway?
• The Rise of DevOps
• Wikipedia on DevOps
• http://dev2ops.org/blog/2010/2/22/what-is-devops.html
• DevOps 101
• http://theagileadmin.com/what-is-devops/
• http://www.slideshare.net/adrianco
• http://perfcap.blogspot.in/2012/03/ops-devops-and-noops-at-netflix.html
• http://www.slideshare.net/geekle/devops-5348895
• http://www.slideshare.net/gheavyside/devops-at-accu-2012
• http://www.slideshare.net/jweiss/infrastructure-automation-withchef
• http://www.slideshare.net/carlossg/from-dev-to-devops-fosdem-2012
• http://www.slideshare.net/launchany/getting-started-with-heroku