DevOps stems from the idea that developers and operations should work more closely together – communicating, knowledge sharing, and collaborating to increase the quality of the systems that we build and operate.
Rsync has a simple protocol that replicates a directory (one or more) on a single server to other servers. This can be achieved in two different methods...
It’s in vogue right now to claim that there’s no such thing as a DevOps team or warn about certain kinds of teams that brand themselves DevOps but are not. Jez Humble’s doing it. Patrick Debois has made similar noises in the past.
In case you missed them last week, here's a roundup of noteworthy IT ops links, including Firefox's new approach to page load, 61 countries that can't be easily cut off from the web, and a hack that leverages Amazon's Silk browser for backdoor cloud computing.
While I’m collecting Devops Protocols which highlight healthy patterns in your organization, let’s take a quick look at the opposite: Devops anti-patterns. Would you be able to spot the warning signs when your team starts to slip in the wrong direction?
I’ve spent most of the last decade working on problems in build, deployment and release management. While automation has been a focus of mine, the hard part in these domains have always been around dependency management.
I get easily tired of doing the same thing over and over again, and will, wherever possible, script or automate it to make life easier for myself. This could be in the form of a lightweight webapp/REST api for stuff, or in this case, I used Jenkins.
Enter the real world: Your network is disconnected. DNS goes downs. Your HTTP hooks and downloads stall. Interprocess communication hangs. Here is an example how to create timeouts and notifications in a shell script.
An outstanding issue is how to get changed config data (JSON) to the nodes in a production stack that need it. Here's a brain-dump of the choices, without mentioning specific languages.
We figured that we could learn a thing or two about continuous delivery from Facebook, so we reached out to Chuck Rossi, Facebook’s first release engineer and the head of their release engineering team.
A few weeks ago Jez Humble wrote a blog post titled “There’s no such thing as a ‘DevOps team.’” Here are some thoughts about the article and what a DevOps team actually is.
I’ve been spending a bit of time recently pushing a few Puppet modules to the Forge. I started doing it as a bit of an experiment, to find out what I liked and what worked and I decided to writeup a few opinions.
So you have your executable web application in JAR with bundled Tomcat (make sure to read that one first). However there are these annoying Tomcat logs at the beginning, independent from our application logs and not customizable
I’ve heard quite a bit about the “G-WAN Application Server” over the past few weeks. Initially it was a Serverfault question that left me thinking “WTF.”
Often when inspecting an UNIX server as a sysadmin you need to find and kill a (hung) process running with a certain command line arguments.
FitNesse is a lightweight testing framework that is meant to implement integration testing in a highly collaborative way, which makes it very suitable to be used within agile software projects. With Jenkins and Maven it is quite easy to trigger the execution of FitNesse integration tests automatically.
It’s day 4 of our first agile ITOps sprint and so far it’s pretty much going to script. Our estimation of how much work we would be able to get through is looking roughly in the right ballpark.
Today we started day 1 of our first ever ITOps sprint. This all came about because we needed a way of working out our productivity on “project tasks”, as well as learning how to triage our interruptions a bit better.
The idea is to get the simplest implementation of a pipeline in place, prioritizing a fully working skeleton that stretches across the full path to production over a fully featured, final-design functionality for each stage of the pipeline.
Imagine you want to introduce automated configuration management to your organization. You’ve read all the books and even visited a great conference where you heard a lot of success stories. “It’s really time to get our servers under control” you think. But how do you get started?
One important issue that comes up when undertaking a configuration management effort is how to design “the schema” for configuration management data. There are a couple of general and complementary approaches you need to know about if you’re working on this.
Here are 10 tips for teams and those who manage, administer or simply organise teams. Of course, if you are a self-managing team you should all read this list.
By default CentOS minimal install does not come with pre-configured network, here’s how to make it work.
Today, I will focus on the mix of Capistrano / Webistrano. Both of the packages are ruby on rails based, and can be easily installed using gems.
Git’s distributed approach makes it easy to push to a dedicated “deploy” branch which is being automatically fetched, but would that be possible with TFS as well?