Puppet

Edit: I’ve edited this post a few times since it was originally written in November, but now everything’s all dandy and working I thought I’d republish it as a new post! Testing Puppet on Windows So as someone who’s been doing way more work on Windows recently, I’ve become super interested in how to do systems acceptance testing on Windows. I ended up pairing with Liam at the Contributor Summit at Config Management Camp 2015 about this, as Liam’s behind a lot of the original work to get cygwin-less Beaker working for testing. Go read his blog posts over on the OpenTable, he knows way more about the background than I do! ...

I’ve noticed half of my posts on this blog have been about me fiddling with my blog. I like to tinker, and something like this blog which I actually have to maintain solo gives me an opportunity to try new technologies. Like docker for example! Docker’s something I’ve had some basic understanding about for a while. I’ve used it for testing, and I’ve got a vague idea how it works, but there were so many things to understand to get anything working. Just like a lot of new technologies, there’s a lot of plugins, tools and extensions to understand to figure out whats going on. Do I use Swarm or Kubernetes? ...

So I originally set up this blog way, way back in 2013. I’d been using Octopress and a Github hosted page. But it made it look like every other Jekyll blog out there. I had attended TwilioCon 2013, and Hannah Wolfe gave a presentation on Ghost. It sounded pretty cool, and DigitalOcean had just created a Ghost image to play around with. So I booted one up and it worked pretty well! The problem was, since it was an image, it was pretty annoying to maintain. I was stuck with Ghost 0.3 for a while. I remember looking into how hard it would be to automate with Puppet, but the only Ghost module on the forge at the time wasn’t working for me. So I put it in my to-do pile to automate with Puppet, and left it. ...

Header image: https://flic.kr/p/7Lx9Kk As someone who’s started out in dev and ended up falling into ops, a lot of my approaches are heavily influenced by what I cut my teeth on early on. Since I started out development Ruby and Rails, I learnt a lot about Test Driven Development. In fact, even before I did Rails, I was working a little on cuke4duke, a JVM Cucumber package. I’m a big fan of using TDD when writing Puppet code, as I think it really helps with my workflow and brings a lot of advantages. ...

Every 3-4 months, Puppetlabs has a Triage-a-thon. It’s a cool opertunity to get your hands dirty looking at the puppet source code, help fix some outstanding issues and generally help out the community. Everyone jumps on IRC, and you can fish through the Puppetlabs Jira and find out what you can fix, and sometimes just do a bit of janitor-ing removing old tickets that are resolved or nudging people for reviews and the like. ...