3 minute read

As with most issues of the newsletter I’ve included a few links to new tools. I always appreciate it when along with the tool itself I find a blog post explaining the context. Why something was written and by whom, and snapshot of the first release, is always of interest. If you release a new tool, remember to write a blog post too.


Downtime can be expensive. Download the Incident Management Buyer’s Guide to learn what your DevOps team can do about it. Get your copy here:


A Tale of Two Pipelines: To DevOps or Not to DevOps

Join this webinar to see two pipelines in work environments where people are running around putting out fires, pointing fingers, siloed, and losing sleep vs. teams with highly optimized communications, well defined roles, and common understood goals. You’ll take away insights on key pipeline factors that plague traditional delivery pipelines, and major practices that have significant impacts when leveraging a DevOps culture and Continuous Delivery Pipeline.


The combination of BigQuery and the GitHub archive make for a fantastic research tool. This post uncovers how Docker is being used, by looking at Dockerfiles in nearly 300,000 GitHub projects.

All of the videos from the recent Monitorama conference are now available. Combined with the previous events that’s 135 videos covering everything you ever wanted to know about monitoring.

Devops conversations can sometimes focus on the barriers between development and operations, but sometimes forget other silos within those separate organisations. A good post about silos within the development org.

When learning how to secure applications it’s useful to have an insecure application with known vulnerabilities to learn from. Bad Dockerfile is a known insecure Dockerfile, useful for testing tools or learning more about container image security.

An informative story for anyone exploring chaos engineering approaches to building resilient systems. EC2, Systemd, ECS and more services combine to provide hard-to-simulate failures.

I’m also interested in academic research into various devops topics and happy to help when I can. This survey is aimed at investigating how applications should be designed to enable and better support continuous delivery practices.

A good post on why it’s crazy to be dismissive of existing applications and existing infrastructure running an organisation when talking about moving to cloud services or more modern architectures.

A good discussion of one of the tenets of mircoservices, that of being independently deployable.

A quick look at the current state of image signing for containers. Discussion of different approaches, why signing is useful and what some of the tools are doing today.

Message queues are powerful tools for various tasks, but using them well can be challenging. This post is a good introduction to publish/subscribe architectures and some of the challenges of real time data processing with queues.

A nice, step-by-step look at using Google Cloud to setup a Jenkins based pipeline used to deploy a simple web application to Kubernetes, running in GKE.

A simple example of writing a chat bot for Slack to act as a deployment tool. The power covers some of the pros for deploying via chat, but I do which it talked about some of the downsides and issues too.


Is Chef more to you than a character on South Park? Find new DevOps opportunities on Hired.


Devopsdays Berlin is coming up later this year on November 16th and 17th. The organisers are on the lookout for sponsors and speakers, so get your submissions in before the 1st of September.


Terraform is an increasingly common tool for describing cloud infrastructure in code, but using it in teams requires some sharing of state. Enter Terragrunt, an open source service you can run to support locking and sharing state between users.

An interesting approach to creating an Apt package repository on S3, using Lambda to build the package index automatically when you upload new packages.

Skopeo is a command line utility for various operations on container images and image repositories. The main feature is the ability to explore image and layer metadata without pulling the filesystem portion.

Downtime can be expensive. Download the Incident Management Buyer’s Guide to learn what your DevOps team can do about it. Get your copy here: