I’ve been using vagrant to build up labs for my work recently and it’s an awesome product. One small downside is the sheer amount of space that the new VMs were taking up on my laptop SSD (I’d been testing linked clones and hadn’t cleaned up after myself). As my whole lab build was in code, I felt rather pleased with myself that I could just bin the whole environment including any VMs and then just spin it up again afterwards.
I’m absolutely loving PowerShell DSC at the moment and we’re using it heavily for the automation and configuration of various products. One of the most recent tasks was to create a fully parameterised SQL build function for reusability across the company. All was going swimmingly until I ran into the following error when attempting to run my freshly parameterised DSC function: After a little bit of digging, I stumbled across a great blog post by Jacob Benson which had some nice troubleshooting steps (Link here).
A task that I’ve been working on recently is the automation of VM builds and post configuration using PowerShell and the PowerCLI module (Unfortunately we don’t have a configuration management tool to make our lives easier at the moment). Part of the post-build configuration is to run a bunch of commands on the newly built VMs. I could have used PowerCLI’s Invoke-VMScript command to achieve this however as all of the VMs were joining the domain and tools on some of the VM templates were out of date, I used PowerShell’s Invoke-Command.
Recently, I’ve been thinking about how I can use DevOps tools and processes to improve the way I do things and this has led me to completely revamp my blog. My existing Wordpress blog has now been replaced with a shiny new blog using Hugo - a static website engine, hosted on Github Pages and automated using the continuous integration tool AppVeyor. In this article, I’m going to go through a step-by-step guide on how I set everything up.