Here is a list of three major types of elasticity that I have implemented / experienced so far. I'm also setting up a unit and functional testing environment that will re-utilize some of our architecture.
There can be friction between the various ways agile teams work, and it seems that the root of the conflict between agile and continuous delivery is the approach to making software "ready for release."
The first in a news series of blog posts by DevOps godfather, Patrick DuBois, will look at the integration and options within Nagios with reference to his infrastructure at Atlassian, where they must monitor about 10,000 websites.
Maven doesn’t like it when you use different verison numbers to the Maven standard format. I’m not “Maven bashing”, it’s just that this particular problem doesn’t have quite the elegant solution I was looking for. I do appreciate Maven, honestly.
If you're already using Vagrant to manage your VirtualBox VMs, then you probably have realized already how annoying is to keep the VBox guest additions up to date in your VMs. We'll help you fix this issue...
Here's a quick rundown of 6 types of monitoring for your infrastructure. Yes, there are six, and a few that you might not have thought of.
Joe Miller needed a simple mechanism to build native packages on the relevant platforms, ie: .deb's on debian and .rpm on redhat/centos. He ended up using a combination of Vagrant and some homegrown tools such as Bunchr.
The general best practice is to add an additional element for each service tier, also know as N+1 redundancy. This approach is straight forward, but many people would actually be surprised by how often these schemes fail.
I’m using Cobbler and Puppet to automate the creation of VMs on my laptop for testing/staging purposes so I thought I’d blog about it here. The aim is to use Cobbler to setup the base operating system and install puppet, then let Puppet take over and install and configure the rest of the system.
When the term NoOps was coined by Forrester last April it stirred up a lot of controversy online, especially in the DevOps camp. The discussion has been ongoing since then with no resolution. What I’m gonna argue is that except for the random troll, everybody is working toward the same goal and the problem is terminology.
A development team’s infrastructure - development and QA environments, CI servers, SCM servers, etc. - are indisputably business critical, but rarely given the kind of monitoring attention that production environments are. This is a missed opportunity, not only to ensure the continuity of development work, but also to gain valuable insight.
Gitosis-ng — it’s gitosis with some new features to help users work with the git server. Mainly implemented with commands sent via ssh. Here's what you can do with it.
I just setup a Graphite server on Ubuntu 12.04 (Precise). Here are some instructions for getting it all working (using Apache as web server).
It's a simple feature, but it can save a bunch of time. You could also setup a handler set specifically for metrics and another set for notifications. In the case of metrics, you could easily ship metrics to multiple systems – Graphite, Librato, Cube, etc. And adding a new system would be as simple as creating the handler and adding it to the handler set.
I want to give individuals access to the experiences that gave me good judgement today. Not just reading about them, because that’s not how I learn, but by getting hit in the stomach at 2am by them.
Andrew Phillips takes on a tricky VirtualBox problem where the DHCP server sometimes, under as-yet-undetermined circumstances, fails to allocate an IP address to the NAT interface. See how his solution works here...
It must have been at least five years ago, when Puppet was getting popular, that the author first ran into someone terrified of losing his job because of automation. However, what also history suggests is that resourceful and competent engineers will always have a job.
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...