My Definition of DevOps
https://www.flickr.com/photos/geishabot/

My Definition of DevOps

DevOps has been a nebulous word in the IT world for the past few years. It now seems to have settled into the new job title for a systems administrator that also has to handle application deployments.

I don't have a problem with people using the term that way. However, if all we do is rebrand the Sys Admin as a DevOps, then I think we lose the essence of what the DevOps movement is trying to capture. DevOps also has to be about the improvement to our processes as well.

My definition of DevOps is:

DevOps is achieved when the processes for managing the dependencies between code and infrastructure are natural and automated.

You can see that I’ve defined the word DevOps to be an achievable state, and not a person or adjective.

Since it’s a short definition, I’ll highlight two points:

Natural

Natural means there is an expected interaction between code and the infrastructure beneath it that is planned for in the software development lifecycle.

If a new release of the software has a dependency that must be installed via a system package at the OS level, that should be easily accommodated.

A developer shouldn’t be chasing down a sys admin after a QA deployment fails because the package wasn’t installed on that environment. Whether it’s push-based by the developer, or pull-based with the sys admin asking for requirements, it needs to be a normal, scheduled step in the software development lifecycle.

Automated

The interaction between code and it’s underlying infrastructure must be automated or else it is not reproducible.

In the example above, once the developer has communicated the system dependency to a DevOps engineer, the developer should never have to worry about that dependency not being met in any environment.

Conclusion

Although DevOps involves new tools and changing job responsibilities, I hope that the ideas in my definition stick with the DevOps movement. Those core concepts are what will make DevOps have lasting impact, and not become yet another temporary trend.

-----------------------------------------------------------------

This article first appeared on: http://www.codeswimming.com/devops/my-definition-of-devops.html

Ya man it is a state...Alot of culture and mindsets need massaging to get there...

Like
Reply

To view or add a comment, sign in

More articles by Kevin Day

  • Make Technology Decisions in 5 Easy Steps

    Making technology decisions can be difficult. If you’re a software company today, you have seemingly endless options…

    1 Comment
  • Why Test-Driven Infrastructure (TDI) is Important

    It is my belief that any company that generates revenue from software should use Test-Driven Infrastructure principles…

Others also viewed

Explore content categories