From the Blogosphere
Dev in DevOps? | @DevOpsSummit #APM #DevOps #CD #Microservices
Seven benefits of adopting a DevOps approach
By: Kareen Kircher
Oct. 31, 2016 04:15 PM
DevOps is a term that comes full of controversy. A lot of people are on the bandwagon, while others are waiting for the term to jump the shark, and eventually go back to business as usual.
Regardless of where you are along the specturm of loving or hating the term DevOps, one thing is certain. More and more people are using it to describe a system administrator who uses scripts, or tools like, Chef, Puppet or Ansible, in order to provision infrastructure. There is also usually an expectation of being able to deliver this in 100% cloud, or hybrid cloud environments.
How Things Fall Apart
When things fall apart, the first thing to go are processes and methodologies. All of a sudden, all of those lofty goals get set aside, in order to respond to the latest emergency. What then, is the solution for building a DevOps culture, something that will serve you when things are running smoothly or you hit a snag?
Short of throwing a monitoring report over the wall to the Dev team, the system engineers can't do much to help developers and QA to replicate and troubleshoot an issue. God forbid that a production issue comes up, various teams end up working in silos, even though there may be a concerted effort to triage the issue.
On the other hand, try asking the average developer for a plan to improve network latency. You would rightly be met with the hairy eyeball. Why would you expect them to do this?
A Comprehensive Approach
The best advice I would give as you consider a journey into DevOps, is to take stock of where you are now. Are you willing to address the low-hanging fruit that has been making you inefficient for too long now? Take inventory from the top down, because a feedback loop will only succeed, if it doesn't need a lot of babysitting, each time a stakeholder wants to know what's going on.
Benefits of Adopting a DevOps Approach
How We Can Help
As someone who has occupied in the various hot seats that many of your staff occupies; I can understand their fears, frustrations, and reluctance. I also know how to weave their individual visions into a cohesive process that different constituencies can buy into. It takes more than words, more than creating a catchy phrase to name your team. You a plan, and someone experienced in implementing change, to help bring transformation your culture.
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week