Do you author plans for Puppet Enterprise? Looking for ways to improve them? Read on! The Puppet Plan language allows a variety of methods to pick targets. In this article we will explore two of these methods (TargetSpec parameters and PuppetDB queries) and how plan authors can employ the latter to: Note: the following examples assume that you are running against targets that have the Puppet agent installed.
Everyone wants to automate security. Traditionally, though, doing so has been challenging because setting up security automation tools required a specialized set of skills that no one engineer at a company possesses. It’s time to change this state of affairs by democratizing security automation. Here’s why and how.
IT is not a technology cost, it’s a human resource cost! This is a fundamental concept MSPs need to keep in mind when they are looking at their businesses, but one many smaller MSPs tend to overlook. Think about it; for every business you’re supporting as an MSP, you’re doing so to ensure their IT infrastructure has stability of operation and is optimized to maximize staff productivity.
In my time as a systems engineer in the insurance industry, I learned a lot about compliance programs and the challenges that organizations face to ensure infrastructure is compliant. Audits were time-consuming and handoffs between security, compliance, and infrastructure operations teams were always challenging.
From my previous blog, I’m going to continue the list of five things you can do to improve your technical service delivery to your customers (if you didn’t read the last post, you can catch up on what you missed here (link)). In the following three points, I focus on the role automation can play.
