Group items tagged

"I have worked in environments where reacting was the "normal" way to approach issues and being proactive was just a waste of time... *facepalm* The seemingly simple idea of changing the workplace culture from reactive to proactive was hard to pitch, let alone implement on my own. 18 months ago, I knew there was a better way of doing things and I was determined to find something. I had been watching developers implement Agile Development processes with great envy and I was starting to see concepts that would have great outcomes if adopted in a traditional operations environment. Finally having something tangible to explore I started looking into Agile Operations, which led me DevOps. Lurking in the shadows for a while, I digested as much as I could of the DevOps movement. I thought it was  time to talk to some of the developers and get them on board. 6 months on and here we are... "

Although Puppet Enterprise gives you the wonderful tools to automate your Linux administration, you still cannot deploy a server with a single command. With the following script, you can. Why is this so cool? When, for instance, a new Tomcat server is needed, I create a DNS entry for that server and give a single command and get some coffee. Before it has cooled down enough to drink, the developer has his Tomcat-app deployed and the server is operational. (It takes about 8 minutes to get from scratch to a fully operational server.)

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.

Until recently I was not able to clearly articulate what DevOps is. Then one day, when trying to describe what we are building at Nirmata to an investor, I said something to the effect of, "its all about enabling developers to perform operations, using automation". That made sense to them; and, I've since started using the following definition for DevOps: Developers doing Operations using Automation

"Microsoft provides virtual machine disk images to facilitate website testing in multiple versions of IE, regardless of the host operating system. With a single command, you can have IE6, IE7, IE8, IE9 and IE10 running in separate virtual machines."

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

Kibana is an open source (MIT License), browser based interface to Logstash and ElasticSearch. Once you have those in place, Kibana is a breeze to install and configure (really, I swear). And as you'll see below, none too hard to operate. Check out the screenshots for an idea of what Kibana is all about.

DevOps is evolving from what started as little more than a rally cry, into a culture for continuous delivery of IT services. As more pieces of the puzzle fall into place, we understand that DevOps is primarily a matter of human collaboration -- assisted, but not encompassed by, certain tools and technologies. This essay is my take on DevOps, and why I think it is about embracing distributed, autonomous operational methods that support scalable human-computer processes.

DevOps is een reactie op de onderlinge afhankelijkheid van software development (Dev) en operations (Ops). De spreekwoordelijke muurtjes tussen de Dev en Ops afdeling bestaan niet meer binnen DevOps. De implementatie van DevOps resulteert in een versnelling van de ' time to market' en een verhoging van de kwaliteit van delivery. DevOps gaat een stap verder in de richting die met Agile werken al is ingezet. Waar bij Agile werken frequent werkende software met de meeste toegevoegde waarde wordt opgeleverd, gaat DevOps nog een stap verder door de applicatie delivery te versnellen.

A path to DevOps When Lara Hogan asked Bridget Kroumhout (on stage, at Velocity), "So, how did you get tricked into operations?" it was funny, but it got Kroumhout thinking. It's a question she's been asked before, and has sometimes been at a loss for an answer since she didn't follow a plan originally. Kroumhout now offers a plan-a wonderfully thoughtful and pragmatic set of resources beginning with culture (e.g., if you work in tech for even a little while, you'll notice that you have a lot of social and economic privilege, no matter your demographic identity, because you have more choices in your work and life than do many of your fellow humans), tools, education, community, and how to launch your career. Even if you're already well established, this is worth a read if only to rekindle your fire.

We wrote back in August about 3 "litmus test" questions about #DevOps in your organisation. We'd like to add 3 more questions that focus on the more operational aspects of DevOps.

We have a variety of tutorial videos all related to DevOps. Our goal is to make the lives of SysAdmins everywhere easier by helping them use the tools that developers have been using for a long time, as well as helping developers realize how to solve some of the issues that Operations has traditionally had to deal with. If you have any comments or suggestions, please let us know!

Arrested DevOps is hosted by Matt Stratton, Trevor Hess, and Bridget Kromhout. ADO is the podcast that helps you achieve understanding, develop good practices, and operate your team and business for maximum DevOps awesomeness.