I never thought we'd be hearing those words from Jez Humble, an advocate for Agility at ThoughtWorks, but here is the point he's trying to make...
Infrastructure is hard to build. This is true when putting together compute clusters, or when dealing with roads or power lines. Typically this involves both increases in operating expenses and capital expenses, and a small mistake can be quite costly.
Build Flow enables us to define an upper level flow item to manage job orchestration and link up rules, using a dedicated DSL. Learn to harness this awesome plugin.
Log messages are destined to end up in a log file … are they really? When you search megabytes of logs file for a clue what went wrong, or when you want to generate some statistics, you realize that this calls for proper tooling. In logFaces I’ve found a tool that I’m using happily for more than two years now.
As an initiative to get developers, sysadmins, and testers working together to increase the speed of delivering high quality software changes, a key challenge devops must address is trust. Sysadmins simply don’t trust developers to hand them production ready code.
For the last 5 weeks or so I’ve been working with puppet every day to automate the configuration of various nodes in our stack and my most interesting observation so far is that you really need to keep your discipline when doing this type of work. Here are 3 ways to do it...
Once we have good metrics and a good set of monitoring systems on top of them, we can be much more aggressive in pushing out changes due to the fact that this style of monitoring gives us a very effective early warning system with regards to bugs or breakages that have been introduced.
Developers are driven by getting new features out the door. Operations, being charged with keeping things running, wants to avoid change. RISK is a 4-letter word keeping them apart.
Once you’ve been working with Jenkins and uberSVN for a while, you may find yourself in a situation where you have several jobs that need to run in a specific order. How do you implement a complicated setup?
Everyone knows the C-I-A triad for information security: security is about protecting the Confidentiality, Integrity and Availability of systems and data. In a recent post, Warren Axelrod argues that Availability is the most important of these factors for security. I don't agree...
Hosted applications need to be upgraded regularly. Configuration changes are regularly needed to tweak the environment so that it runs efficiently and communicates properly with other systems. This requires some mix of command-line invocations, jumping between GUI screens, and editing text files.
The result is a unique snowflake - good for a ski resort, bad for a data center.
Here we will highlight some of the measures that were necessary to further operationalize the system for production use. As our environment receives anywhere from 2,000 to 6,000 log messages per minute (with occasional peaks to 40,000!)
A recent question on Twitter prompted me to write a quick blog post about managing cron jobs. As more and more people want to automate provisioning and deployment of web applications some, maybe previously manually managed, items come into the fold.
Terraform is a flexible tool made available under the Apache 2.0 license that makes it easy to define, instantiate and manage environments. Terraform integrates with existing cloud providers. Today, Amazon EC2 and VMWare vSphere are supported.
"Once IT decides to focus on speed, two obstacles get in the way: security and governance." This is important. Manage security without it becoming an impediment.
The Unix philosophy is a noble idea, but even Unix doesn’t follow it too closely. "Write programs that do one thing and do it well." is one point in the philosophy that is especially strained.
Facebook engineer Doug Beaver shares in a W3 mailing post why Facebook endorses SPDY. He highlights cross-browser support as well as the ability to speed up communication between geographically distant web servers.
One I get asked quite a lot is: "How do you configure GlassFish to receive notifications/alerts/messages on important log entries?". Seems to be a good topic to blog about.
There are a number of books that influenced Kief Morris' thinking on Continuous Delivery. Here are his top 7.
We live in a world where we are already expected to know, where competence is assumed, but competence disappeared with craftsmanship to be replaced by production lines. Hierarchical management dug the nail in the coffin as the goal became moving up to the next job rather than getting good at the one you’re in.
At Devopsdays I listened to a lot of smart people saying smart things. And to some people saying things that sounded smart, but really weren’t. It was especially confusing when you heard both of these kinds of things from the same person.
Ten of the best books from the Deathray Research bibliography. Guaranteed to make you smarter about software engineering and the world. Inspired by the book, "This Will Make You Smarter", and my teenage son, who said today “All books are self-help books”. Couldn’t agree more.
At DevOpsDays Mountain View I was lucky enough to get some time with Michael Rembetsy, Director of Engineering and Operations at Etsy, which manages to be PCI-DSS compliant while practicing continuous deployment. In this short interview, he describes how they do it.
I recently ran into the situation in which I couldn’t get PKA to work when SSHing into my Ubuntu server. I hope this article helps somebody out. It was driving me bonkers.
Somewhere along the way our industry shifted this discussion into a tools discussion & now the amount of noise out there about “DevOps tools” is magnitudes higher than any discussion about the real reason DevOps exists – to shift culture.