Profile cover photo
Profile photo
The shortest path to better software.
The shortest path to better software.

Puppet's posts

Post has attachment
If you know Puppet, you know we have a great admiration for dogs. It’s a delight coming to work with awesome people every day, but we also have an extra perk: getting to pet our doggy friends in our London, Belfast, Seattle, and Portland offices. Whether wagging their tails, begging for treats, or being generally adored, it’s a joy to be surrounded by our furry colleagues.

But let’s get real: In our industry, cats rule supreme. In fact, cats rule the internet. So in honor of International Cat Day on 8 August, we're offering you an extra 5 percent discount when you register for PuppetConf 2017. That's on top of our 20 percent early bird discount, which ends at midnight (Pacific Time) on *Thursday 10 August*.

The early bird catches the worm, but it's the cat that catches the bird. So get your 25 percent discount 8–10 August, and then thank the purring companion on your lap (or laptop, as the case may be).

To get the 25 percent discount, register and enter code meow at — then join us at PuppetConf 2017, 10–12 October in San Francisco, California for two-plus days of hands-on learning, collaboration and fun with all your Puppet friends.

Post has attachment
+Gareth Rushgrove writes: The tooling around container metadata continues to grow, and the new Manifesto tool from +Aqua Security ( fills a useful niche. This post shows how to use Manifesto with Lumogon ( to store information about the contents of your Docker images alongside the images themselves on Docker Hub.

Manifesto is a new tool from the folks at Aqua Security that allows users to store and query metadata for Docker images using only Docker Hub. This metadata can be any information that you want to store about an image post-build — especially useful where labels are not quite sufficient.

Lumogon is a new tool from Puppet that can inspect your container-based applications, producing reports on all sorts of metadata — from labels on the container to software installed in the image.

Read this post for more information about Manifesto and Lumogon, and how to use them together.

Post has attachment
Lisa Gregory writes: PuppetConf offers awesome keynotes, sessions (and so much more!) for practitioners — but don’t forget to invite the IT leaders in your organization. For the third consecutive year, PuppetConf will feature an [IT Leader track]( focused on emerging trends in IT, plus real-world stories of digital transformation, the future of DevOps, security and compliance, and journeys to the cloud. The IT Leader track is ideal for executives, managers and other people responsible for leading transformations within their organizations.

A lineup of expert presenters and panelists will cover:

How organizations are enabling digital transformation.
Successes and lessons learned from organizations that have adopted DevOps practices.
Approaches to ensuring security and compliance without sacrificing agility.
Strategies for moving to the cloud, achieving portability, and shifting to microservices.
Practical tips for CIOs and IT leaders seeking to build high-impact teams.

Post has attachment
Rick Monro writes: Without investment in a positive user experience, all the effort is left to the poor person sitting in front of a screen, wondering how they are going to get their work done. At Puppet, the principles of user-centered design are paramount. Humans are going to be using what we build, so it’s humans we work hard to design for.

You really don’t have to look too far anywhere in the world to see huge technical and engineering accomplishments diminished by a lack of real provision for end users. Think of the parking machine that requires you to stare at it for two minutes before you finally understand which button to push first. Or maybe the banking app that left you fumbling around for a simple way to set up a new transfer.

What helps us design for humans is the fact that so many of the people who work at Puppet are themselves current or former users of the product. That said, we try not to make the mistake of relying just on the knowledge inside the business to generate insights.

That's because when engineers build things for other engineers, it can be very easy to assume everyone is a power user. To avoid this kind of friction, we consult directly, regularly and systematically with Puppet customers and users. The insights we gain this way feed directly into improving our products.

Providing a platform and associated tools for others to build on is a fascinating challenge. We call it the Puppet developer experience (PDE). It’s not just a name; it’s a commitment on our part to provide those developing on the Puppet platform with the best possible experience. We dedicate whole teams of product owners, engineers and UX architects to this goal. If we get it right, people using Puppet will be able to finish their tasks more quickly, achieve their goals more effectively, and get on with the rest of their work.

So how does this look in practice? A good way to show you is to describe the work we've been doing recently on the Puppet Development Kit (PDK), which is designed to help you create Puppet modules more easily. (Note: This hasn't been released yet, but we'll be releasing it soon. Watch this space!)

Post has attachment
+Padmashree Koneti writes:
I can’t tell you how many times I have heard technology professionals say that they are “trying this agile thing out,” and that they think of their organization as “small ‘a’ agile but not capital ‘A’ agile.” These are organizations that are hoping to institute change by instituting rituals: two-week cycles for producing stuff; estimating work in hours; talking about continuous delivery and continuous integration; propping up a Raspberry Pi in their environments to watch builds; and conducting standard agile ceremonies. But an organization can check all those boxes and still not be agile.

Common pitfalls include:

* You conduct retrospectives, but your teams don’t feel safe enough to talk about the elephant in the room (an issue that blocks you from delivering on a task or feature) because they worry about political boundaries — or fear retribution.
* Your team is holding on to old ways of doing things because they are worried that automating old release engineering practices may make their jobs unnecessary.
* Your team does not feel empowered enough to implement continuous improvement, and allows huge blockers to persist. This lowers morale and increases attrition, particularly of good people.
* Progress reporting to leadership is not rooted in transparency and continuous improvement, and your middle managers feel like they have to brush problems under the carpet to make status reports look good.
* Your leadership has an affinity for bright and shiny objects, constantly launching new initiatives and remaining blind to incomplete work or technical debt.
* You feel stuck with leadership guidance that attempts to dictate scope, schedule and resources, and it’s unclear how you are empowered to address tradeoffs.

Post has attachment
+Michael Stahnke writes: A few weeks ago, with Sysadmin Day approaching, we asked ourselves, "What does it even mean to be a sysadmin in 2017?" Luckily, Puppet is a company filled with system administrators and folks who once were system administrators, so everybody here is passionate about making the lives of system administers better. Nigel Kersten, our chief technical strategist, and I decided to ask our folks for their insights. You'll find some interesting points of view from Puppet employees in this blog post.

As we often say around Puppet, every business is powered by software operations. Succeeding as a business relies on how well the organization can develop, deliver and manage software, so everyone involved with software has to align with the goals and strategy of the business.

Reflecting this shift, the role of the system administrator has changed, not only in nomenclature, but in terms of what responsibilities fall to the infrastructure layer. This doesn’t mean the classic definition of a system administrator has gone away; it means that today, the role is a superset of what was already an ill-defined and daunting job description.

The way software flows through and powers the company is now seen as a competitive advantage. Many system admins are in charge of bit flow, testing pipelines, delivery mechanisms, and error rates on production services. However, they still have to be able to take care of that legacy application in the corner.

Post has attachment
+David Lutterkort writes: Whether you’re new to containers or a seasoned veteran, you’ve probably come to realize that actually operating container-based infrastructure can quickly become unwieldy, particularly at scale. At scale, and over time, some of the subtleties around containers can trip you up and make operations harder than they need to be.

In this blog post, I highlight some of the common challenges with container configuration, and ways you can use Puppet to overcome them. We have come to think of configuration management as being concerned with low-level tasks like installing packages, maintaining configuration files, and ensuring services are running — all things that do not seem to be terribly useful for containers. But these examples are really just manifestations of the larger problem that configuration management addresses: managing the changes to infrastructure over time and at scale.

Post has attachment
+Matthew Girdharry writes: We’re really looking forward to being at the F5 [Agility 2017]( conference in Chicago (1 - 2 August at the Chicago Hilton). Since I joined a little over two years ago, +F5 is a name that keeps reverberating within Puppet — for example, our customers asking, "When can we get more of that Puppet-F5 goodness?" I think it’s safe to say that we’ve been wanting to work more closely with F5 for quite a while.

Well, now Puppet and F5 are formally partnering to provide key modules so our customers can accelerate their application deployments. With F5 as an [Advanced Technology partner](, we’ve been working hard to further our automation capabilities within F5’s enterprise-grade application services and in the application deployment process. So today, Puppet can provision and manage F5's BIG-IP platform and most of the LTM module, too. Plus there's more to come.

Modern IT organizations rely on automation frameworks like Puppet to increase the velocity of application deployments, and improve time to value for the business. Once deployed, however, it can be a complex challenge to keep the application fast, secure and highly available. As the market leader for intelligent traffic management, F5 gives operation teams the ability to quickly mitigate issues that threaten network performance, without compromising the speed of software delivery. And Puppet's automated configuration management platform makes it easy to deliver software securely and reliably, every time.

Stop by and see us at the Puppet kiosk in the Solution Expo. We’ll be delighted to talk with you about what we have available today, and what we plan to deliver in the near future.

Post has attachment
Glenn Sarti writes: The Puppet PowerShell module is one of the most popular modules for Windows administrators on the Puppet Forge. How popular, you ask?

* 2014 - 7,762 downloads
* 2015 - 79,241 downloads
* 2016 - 10,476,787 downloads!!

One reason for the large increase in downloads is the speed improvements we made to the module. (Of course, it was also the first new version for a while, and much anticipated.) In this blog post, I'll walk through the improvements we made to the PowerShell module, and how we increased its speed.

Post has attachment
+Verne Lindner writes: One of Puppet’s core features is its ability to maintain your infrastructure in exactly the state you define for it. Describe the configurations you want in a Puppet manifest just one time, and Puppet will apply and maintain those settings for as long as you wish.

This ability to automate configuration management offers you significant advantages when it comes to security, because automated configuration management lets you broadly enforce system rules, plus get an automatically generated audit trail so you can report on compliance.

This only works, however, for resources you manage with Puppet. What happens if you need to make sure that none of your nodes are running a vulnerable package, and you manage that particular package on only a portion of the affected nodes? For all its power, Puppet cannot maintain enforcement of a configuration on any package that you haven't explicitly told Puppet to manage.

Puppet can, however, report on these packages, as long as a Puppet agent is installed on the node hosting the package. In this blog post, I’ll show you how Puppet Enterprise’s reporting tools can help you track and manage package vulnerabilities, even on nodes where you aren’t managing the vulnerable package with Puppet.
Wait while more posts are being loaded