Fewer tools but an awful lot to read this week, including a few short books available for free online. If you skip everything else or just skim the outlines I’d definitely read the first article in full. Then read it again and think about how it applies to our domain of fast moving technology, and more importantly how we avoid the need for too much devops archaeology in the future.
Devops Weekly is sponsored by Brightbox Cloud - launch cloud servers in multiple UK datacentres in seconds…
This first article doesn’t appear to have anything to do with devops. It’s about institutional memory, engineering archaeology, documentation and document management. It’s about a chemical engineering plant. But I bet most people can read this and see it either in their past or future when it comes to the computer system we build.
A Platform as a Service is generally made up of quite a few interesting moving parts. This free book (available online or to download) covers some of the dotcloud details, but much of the software discussed is open source. Some good low level resource management and file system stuff.
Nice write-up of continuous deployment from an individual developers perspective. I particularly liked the like “The real secret to the success of continuous deployment is that code is pushed before it’s done”.
Anyone running real life systems will get reports of errors from users or the code itself at some point, and not all error reports are useful (to put it politely). This post covers a manifesto for error reporting, with several good tips worth considering next time you write error handling code.
Chef 11 has some awesome new features, but unless you’ve been following along closely you might have some work to do to resolve some breaking changes. Here’s a good walk though of a few of the gotchas that should see you on Chef 11 in no time.
Logging is a source of lots of interesting and useful information, but getting the right setup for you can take time. Here’s five simple steps to make your application logging better.
Armatures is a new community project from Puppetlabs which aims to provide a way for people to suggest proposals to enhance or add features to Puppet or something in the Puppet ecosystem. It’s just a GitHub repo and the first armature documents the process to follow to make proposals. Interesting idea.
A few videos from the recent San Francisco Metrics meetup featuring a Sensu talk by Nick Stielau (Pantheon) and Jeremy Carroll (Pinterest) and an OpenTSDB talk by Benoit Sigoure (Arista Networks) & Jonathan Creasy (Box).
Sphonic is looking for a passionate and skilled UK based, Operations Engineer. We are fast growing startup and are planning significant global growth over the next year. We are commited to delivering scalable solutions in the cloud over a SAAS model. You should be on the line between developer and sysadmin, delivering infrastructure through automation, and monitoring as the foundation of responsive infrastructure. If you’re a hybrid of sysadmin and a developer, with a depth of understanding of how the latest technology can deliver at scale, and can help shape a startup company, then go and help them build it. Simply send your CV and cover letter to apply.
State are looking for a Lead DevOps Architect to join a young but fast-moving startup in west London. Think about the goal of connecting the world’s opinions and you’ll get some idea of the scale of the ambition, and take a look at some of the people involved at https://state.com/about/people. If you’re an advocate of code-as-configuration, automation, continuous delivery, expert with AWS and Puppet or Chef and have managed rapidly scaling consumer web environments please get in touch.
Puppetconf is back, this time in San Francisco on August 22nd and 23rd. Early bird tickets, call for proposals and sponsorship opportunities all available now.
As vagrant becomes more and more useful and powerful you can spend too long typing in those commands. Fear not, here is a much improved set of scripts for bash completion for vagrant.
Slaughter is a configuration management system written in Perl, with a pretty comprehensive set of documentation. it was inspired by CFEngine, with the supplied primitives being very similar, but with the client-server model replaced by a more flexible system of transports.