Group items tagged

The DevOps team is "a growing group of people practicing a new way of combining development and system administration for more speed, quality, revenues and fun."

I've been interviewing candidates for a DevOps opening that Interactive Intelligence has available and I keep getting asked by candidates, 'What does DevOps mean to you?' If you were to google 'What is devops?' you'll find pages and pages of blogs and articles answering just that. I've read a few of them but I still find myself struggling to give a clear answer. I think the trouble with anwering this question is that people generally expect a 2-3 sentence answer and it's difficult to encapsulate all my thoughts on the subject that concisely. Another issue is that when I'm talking about DevOps, I feel like my attempts at explaining it come off as if it's some magical, fundamental, paradigm shift that exploded onto the scene and if followed will lead to peace on earth and an end to all hunger.

Devops is still a new topic for lots of people, and this introduction is a nice place to start. It provides a bit of the history, along with explaining Devops with a focus on culture, automation, measurement and sharing.

DevOps: A culture where people, regardless of title or background, work together to imagine, develop, deploy and operate a system.

During the Devopsdays in Hambourg, one of the most recuring discussion was about "packaging vs non-packaging, when and what?" I won't try to convince people on what do do when, neither will I say I have the absolute best solution, this post just illustrates the solution I implemented with @zipkid. Some points aren't finished yet, not implemented... or we have not yet decided which direction to follow.

The Shutl engineering team has been operating with a DevOps mentality for over two years. We started by rebuilding our infrastructure under Chef and embedding our operations engineers into our agile product development process. We made great progress and saw a big improvement in delivery and quality as all team members were responsible for getting things live and ensuring their long-term maintainability. But… we still had a silo. Only a few of our team were doing the lion's share of the work when it came to maintaining our infrastructure, and on-call duties were shared by just a small number of people. Over the past six months, we've changed that. So, rather than extol the virtues of this approach - there are plenty of articles doing that! - we thought we'd share some of the steps we took to make every engineer a DevOps engineer.

What follows is a countdown of the people whom, if you pay attention to today, will supply you with practical knowledge, wisdom even, that you can put to work in the real world of IT as early as tomorrow.

Have you ever felt like people were conspiring to make DevOps fail? They probably had good intentions but they just made DevOps more difficult than it should be. What if it was actually intentional? The resistance gets organized…