DevOps - Wikipedia EN. DevOps (a portmanteau of development and operations) is a software development method that stresses communication, collaboration and integration between software developers and information technology (IT) operations professionals.[1][2] DevOps is a response to the interdependence of software development and IT operations.
It aims to help an organization rapidly produce software products and services.[3][4][5][6][7] Companies with very frequent releases may require a DevOps awareness or orientation program. Flickr developed a DevOps approach to support a business requirement of ten deployments per day;[8] this daily deployment cycle would be much higher at organizations producing multi-focus or multi-function applications. This is referred to as continuous deployment[9] or continuous delivery [10] and is frequently associated with the lean startup methodology.[11] Working groups, professional associations and blogs have formed on the topic since 2009.[6][12][13] About[edit] See also[edit] What Is This Devops Thing, Anyway? What problems are we trying to solve?
Let's face it - where we are right now sucks. In the IT industry, or perhaps to be more specific, in the software industry, particularly in the web-enabled sphere, there's a tacit assumption that projects will run late, and when they're delivered (if they’re ever delivered), they will underperform, and not deliver well against investment. It's a wonder any of us have a job at all! Let’s have a look at some of the common problems we experience in the software world today. Fear of change Once an application is delivered, the business tends to be tremendously afraid of change. Risky deployments Another symptom of the malaise is the concept of the ‘risky deployment’. It works on my machine! A common situation we experience is one in which a problem manifests itself once the site is live. However, this is frequently meaningless.
Siloisation How does Devops help? Breaking this down a bit - one of the key statements there is ‘sysadmin coders’. How to get involved. What is DevOps not? I’ve spent the last two weeks at conferences, and for some reason people keep assuming that I work in operations.
I can kind of understand why, but it’s also started a number of conversations about DevOps, and the complete misunderstanding of the term. It seems that DevOps is a confusing movement for people, and lots of people are assuming that some of the practices that might come with organisations embracing DevOps are themselves what make you DevOps. Defining what devops is can be hard, so instead I thought I’d feature a few of the things that devops isn’t. “I’ve renamed our Ops team the DevOps team” This is not DevOps, you’ve renamed your operations team, but that is all!
“But our devops team run puppet/chef/CFEngine to manage their systems” This is not devops, this is just ops using new tools. “We split our ops team into Infrastructure and DevOps. Congratulations! “Ok, so we got rid of our ops team, and our devs have root now” This is not just not devops, but it’s pretty damn stupid.