The march of Devopsdays through Europe continues with Paris this last week so several bits of related content. With Austin, Berlin, Mountain View and Amsterdam coming up in the next month or so expect lots of good quality new content from those too.
Devops Weekly is sponsored by Brightbox Cloud - launch cloud servers in multiple UK datacentres in seconds…
I wasn’t going to include this, as I wrote it, but a few people bugged me to do so. I work for the UK Government and as part of transforming how IT works we’re writing a service design manual which now has a section on devops. If someone claims you’re just making this devops think up then happily point them to an official Government page on the subject.
Devops is all about organisational culture, so it’s great to see a short ebook released on this very subject. “Building a DevOps Culture” is free too if you provide your name and email address.
Epic set of notes on all of the sessions from Devopsdays Paris. Includes notes on some of the question and answer sessions too which you won’t find in the slides.
Great presentation about troubleshooting complex systems based on quite a bit of research about the Air France 447 disaster. Lots on communication, interface design, understanding responsibilities, blame, alerting strategies and more. Good example of looking to other disciplines for things we can learn about web operations.
Slides from one of the ignite talks at Devopsdays Paris, from Patrick Debois, entitled “what if devops was invented by coca-cola”.
More slides from Devopsdays Paris. This deck is called How devops improved my dev, and is a developers viewpoint on why devops is important. Note the first two slides are intentionally blank, just keep going.
If you’re a RedHat or Centos user interested in OpenStack then RDO might be just the think. It provides tools to get started quickly, claiming 3 steps and 15 minutes to get up and running. It’s also a community forum for questions specific to running things on RHEL.
A new post in a series on organisational change. This one covers how to measure team success. It pulls together various bits of thinking on the subject and asks some good questions about measuring business objectives rather than more easily defined team ones.
If you decide to go down the software as a service route for your monitoring tools then there are lots of choices. Here’s a curated list of different options available for logging, alerting, metrics and full stack monitoring options.
Fizzgig is a tool for writing fast unit tests for puppet. It uses the rspec matchers from rspec-puppet but takes the approach of on making catalogue compilation explicit. So rather than compiling the entire catalogue it just compiles the unit you’re interested in.
Puppet cleaner provides a number of utilities to clean up Puppet source code according to the Puppet language style guide. As well as transforming the source code it can also provide a diff of changes that it intends to make.