DevOps Is No Replacement for Ops
Join the DZone community and get the full member experience.Join For Free
devops is gaining traction according to a study at the end of 2012 by puppet labs . their study concluded that devops adoption within companies grew by 26% year over year. devops is still misunderstood and has tremendous room for greater adoption still but let’s be clear about one very important thing: devops is not a replacement for operations!
if you’re not as well versed in the term devops as you want to be i suggest you read my “ devops scares me ” series.
worst developer on the planet
the real question in my mind is where do you draw the line between dev and ops. before you get upset and start yelling that dev and ops should collaborate and not have lines between them let me explain. if developers are to take on more aspects of operations, and operations personnel are to work more closely with developers, what are the duties that can be shared and what are the duties that must be held separate?
to illustrate this point i’ll use myself as an example. i am a battle hardened operations guy. i know how get servers racked, stacked, cabled, loaded, partitioned, secured, tuned, monitored, etc… what i don’t know how to do is write code. simply put, i’m probably the worst developer on the planet. i would never trust myself to write code in any language to run a business. now in this particular case it comes down to the fact that i simply don’t currently posses the proper skills to be a developer but that’s exactly my point. in order for devops to succeed there needs to be a clear delineation of duties where expertise can be developed and applied.
operations is a mix of implementing standard processes, planning for the future, and sometimes working feverishly to try and solve problems that are impacting the business. just like writing good code, providing good operational support takes experience. there are many areas where you need to develop expertise and you shouldn’t just start doing operations stuff unless you have some experience and a peer review of your work plan.
you do have a work plan don’t you? a work plan could be something as formal as a change control ( itil would be good to read about) or something as informal as a set of steps written on a bar napkin (hopefully not, but it’s possible). the point is that you need a plan and you need someone to review your plan to see if it makes sense. here are some of the things you need to consider when creating your plan:
- implementation process – what are you going to actually do?
- test plan – how will you be able to tell if everything is working properly after you implement your change?
- backout process – how do you revert back if things don’t go right?
- impacted application – what application are you actually working on?
- dependent application(s) – what applications are dependent upon the application you are changing?
the point i’m trying to make here is that devops does not change the fact that well defined operations processes and practices are what keep companies it departments working smoothly. adopting devops doesn’t mean that you can revert back to the days of the wild west and just run around making changes however you see fit. if you are going to adopt devops as a philosophy within your organization you need to blend the best of what each practice has to offer and figure out how to combine the practices in a manner that best meets your organizations requirements and goals.
bad operations decisions can cost companies a lot of money and significant reputation damage in a short period of time. bad code written by inexperienced developers can have the same effect but can be detected before causing impact. did someone just release new code for your application to production without testing it properly? find the application problems and bad code before they find you by trying appdynamics for free today .
Published at DZone with permission of Jim Hirschauer, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.