If you are starting to use Puppet or Chef, you must have Vagrant! Check it out!
James Betteley was invited to go along to the Facebook offices in London this week. What he learned was the secrets and tools behind their engineering and automated testing, all while enjoying some beer and pizza.
This article contains methods that a ThoughtWorks engineer is trying out to keep their Chef codebases (and the infrastructure they control) in shape:
I just found out about a really interesting open source tool that could support DevOps processes in an even greater capacity than the multi-tool stacks that are currently in place at many shops. Check out some concise details about this new tech...
There was no client library to query a Munin server. There's PyMunin or python-munin which helped with the development of Munin plugins, but nothing to access the munin-node and retrieve its data. So Julien Danjou wrote PyMuninCli.
This post shows code examples in Python (2.7) for sending data to Graphite. Try it out!
We've practiced continuous deployment for 2 years. You know how many complaints we've had about a cruddy user experience due to frequent deployments? Zero. Here's how we do things...
Automated management of infrastructure is vital for delivering highly effective IT services. But although there are plenty of tools available to help implement automation, it’s still common to see operations teams manually installing and managing their servers, which leads to a high-maintenance infrastructure, which soaks up the team’s time on firefighting and other reactive tasks. Here are some recommendations...
It's been pretty exciting to see the number of folks getting involved with Sensu lately, as judging by the increased activity on the #sensu channel on Freenode. One of the most common questions is how to integrate Sensu and Graphite. In this article I'll cover two approaches for pushing metrics from Sensu to Graphite.
How do you help the teams bring the entire product together on a periodic basis, regardless of their technical practices? If you look at the comments from the last post, you can see that continuous integration is a real problem for any number of reasons.
Graphite consists of a storage backend and a web-based visualization frontend. Client applications send streams of numeric time-series data to the Graphite backend (called carbon), where it gets stored in fixed-size database files similar in design to RRD. The web frontend provides 2 distinct user interfaces for visualizing this data in graphs as well as a simple URL-based API for direct graph generation.
At Okta, we’ve gone through many iterations of using Jenkins to build and test our software. We use a number of tools to make sure our code works properly, and we like to have Jenkins manage these. The list would be familiar to anyone using the Java environment; PMD, Cobertura, unit and functional tests with JUnit, Selenium tests with testNG, and also some more exotic tools like BURP Security scanner, MogoTest, and SLAMD.
It's bad when people try to fit today’s understanding of what works into a word, which is defined into perpetuity. The real win in all of this is collaboration. Collaboration between departments, between companies, and across the world of Web Operations experts and novices.
In a previous post, Kief Morris glibly said that 'SLAs represent waste that an organization has identified and formalized.' Reader 'Kenfin' commented on the post, rightly calling me out to provide alternatives. So here they are...
Following is a categorized list of tools that Ranjib Dey has learned/used as a sysadmin and DevOps dude at ThoughtWorks while maintaining their distributed infrastructure, setting up private cloud installations, and in many different client gigs.
The DevOps google group recently discussed the perception of DevOps followers as folks who are users, developers, and fans of chef, puppet, and similar tools. Most people on the group agreed that this perception cannot become reality for DevOps to succeed as a movement.
Some interesting insider info was released this week about the Facebook deployment process. I've compiled a TL;DR version here. The information comes straight from Chuck Rossi, the head of Facebook's release engineering team.
I’ve seen so many threads over the last few weeks about who should do what, why, and what you should do about it if you don’t conform. I don’t get it. Ops is a team in a company – there are lots of types of companies. Companies typically have a few goals:
Hear about the interesting discussion around third party build dependencies such as unit testing frameworks, database versioning tools and other command line executables in your build. The topic of these discussions has been about where these dependencies should be located, inside your project, or installed on your build server.
The Continuous Delivery toolmakers over at UrbanCode released two significant upgrades to their toolsets for helping companies follow the DevOps philosophy - a new version for uDeploy, for release automation, and and an upgrade to Anthill Pro, their Continuous Delivery pipline platform.
When DevOps Days in Austin, TX was announced a couple of months ago, the event was sold out the day after it was announced and had a waitlist of over 100. So the organizers at DevOps Days decided to stream some of the key sessions live! (a move which Google also made after I/O sold out in minutes) So without further adieu, here is the embedded stream of DevOps Days 2012 Austin.
There have been numerous and rapid improvements in operations tools in the last 10 years but when it comes to monitoring we’re still pretty much stuck on the same tools we’ve been using since the late-90s. Learn how open source contributors are finally trying to change this.
Generally when it comes understanding the very basis of how the internet functions using DNS, most of these very same experienced developers haven’t got a clue. I wrote this post to hopefully help pay back some of the awesome karma they have earned helping me over the years, by teaching them something in return. Lets learn about DNS.
At ThoughtWorks, they use chef not only for configuration management but also for provisioning instances. This post by a ThoughtWorks DevOps-er showcases how Chef can be used from any script if you have an API client configured.
At the community's urging, Dominica DeGrandis (David J. Anderson & Associates) ran the first ever Kanban class focused on it's application to DevOps.