High-level agenda

Here’s a general look at the Puppetize PDX agenda. Get a sense of when keynotes, sessions, trainings, and exhibitor hall will happen.

  • Sun, 6 Oct: Training: Getting Started with Puppet, Training: Puppet Practitioner
  • Mon, 7 Oct: Training: Getting Started with Puppet, Training: Puppet Practitioner
  • Tues, 8 Oct: Training: Getting Started with Puppet, Training: Puppet Practitioner, Bolt Workshop, Hackathon, Reception & Exhibits
  • Wed, 9 Oct: Breakfast and registration, Keynotes, Sessions, Exhibitor Hall, Party
  • Thurs, 10 Oct: Breakfast, Keynotes, Sessions, Exhibitor Hall

What will we cover?

Join our automation, infrastructure provisioning, delivery, and DevOps experts for best practices, knowledge sharing, and stories from the field. We’ll cover a variety of themes, including:

  • Infrastructure automation: orchestrate tasks, plans, and enforce state for your infrastructure no matter where it lives
  • Security: hear stories and best practices around eliminating vulnerabilities and ensuring rock-solid compliance
  • Infrastructure provisioning and code delivery: Whether infrastructure or applications, hear stories and practices on continuously delivering code for the modern enterprise.

Pre-Conference Events (Optional)


Date: 6-8 October
Time: 9am - 4pm 

Location: The Heathman Hotel

(Paid event) Attending training at Puppetize PDX gives you the opportunity to learn from experienced instructors and get hands-on so you can level-up your skills and make the most of your Puppet implementation.

We suggest New Puppet users and beginners select the: "Getting Started with Puppet" track, while those with advanced Puppet experience pick the: "Puppet Practitioner" track. More Info.

Seats are limited and only available to Puppetize PDX attendees.  Training costs $2400. ($2160 until June 15th) 

Note: Training will be held at the Heathman Hotel, a 10-minute walk from the Pupppetize PDX conference venue, the Waterfront Marriott. 

Bolt Workshop

Date: 8 October
Time: 12:30 - 4:30pm

Location: Conference Venue, Portland Marriott Downtown Waterfront

Space is Limited! Free to Puppetize PDX attendees.

Want to get hands-on with Bolt? In this half-day workshop, we'll start with the basics—running bolt commands, building an inventory file, running scripts and turning those scripts into tasks. Then we'll put it all together and write a task plan. Seats are limited and only available to Puppetize PDX attendees. 

NOTE: This workshop is running at the same time as the hackathon and overlaps with the last day of training. 

Puppet Hackathon

Date: 8 October
Time: 10:00- 4:30 pm (You don't need to stay the entire time!) 

Location: Puppet HQ

Space is Limited! Free to Puppetize PDX attendees.

Whether you're interested in contributing to Puppet, or already a Puppet contributor, the Puppet Hackathon is a great way to engage with the Puppet team, contributors and users. Join us for a half day of hacking at Puppet headquarters. Seats are limited and only available to Puppetize PDX attendees. 

NOTE: This workshop is running at the same time as the Bolt workshop and overlaps with the last day of training. 

Welcome Reception

Date: 8 October
Time: 4:30 - 6pm

Location: Conference Venue, Portland Marriott Downtown Waterfront


Mingle with fellow attendees and enjoy snacks and beverages while exploring the exhibitor hall. 

A Selection of Confirmed Talks, 9-10 October

Bolt Best Practices

Lucy Wyman - Puppet - Software Engineer

There are many ways to deploy an apache server, but which one is the right way? How can users get the most out of Bolt, without so much heavy lifting? This talk will cover best practices and insider tips for developing Bolt content and working with the task runner. We'll talk about making your plans and tasks shareable, using Bolt's builtin content and features, pitfalls to avoid, and best practices for writing robust code. You'll finish the session with concrete "do's" and "don'ts", as well as more general koans for improving your infrastructure automation. What's the right way to skin a cat? Come find out!

DevOps in a Containerized World

Martin Alfke - example42 GmbH - CEO

DevOps describes the culture of communication and collaboration between IT Development and IT Operations (and other) departments. Usually, this covers system setup, application deployment and all the surrounding tools like CI, metrics and alerting. A core element has always been IT automation using configuration management and CI/CD. But how do we do DevOps in a containerized world? Do we still need configuration management? Is there still collaboration possible? Or are containers the DevOps killer?

Windows Security, Compliance, and Patching

Matthew Stone - Puppet - Senior Sales Engineer

With infrastructure as code and configuration management becoming more commonplace in the Windows ecosystem, many questions remain or have arisen around how security, compliance and patching work in a world full of clouds and pipelines. In this talk, I'll discuss some of the challenges around defining what security, compliance and patching processes look like in your organizations and how you can use various tools and processes to deliver fully provisioned and secured systems that can meet your company's compliance requirements.

Puppet Server and Containers: A Multi-tenancy Deployment

David Moreno-García - CERN - DevOps Engineer

The CERN IT infrastructure consists of more than 40000 Puppet-managed virtual and physical machines. All the Puppet catalogs are served by a shared pool of almost 200 Puppet Servers regardless of the organisational unit from which the requests come. This deployment might lead to security risks as the number of nodes and personnel writing Puppet code increases.

The Configuration Team, as part of the IT department at CERN, is exploring ways to configure a multi-tenancy enabled Puppet Server deployment minimising the performance impact for users and the resource usage.

This talk serves as a follow up of the bits presented in PuppetConf 2017, unveiling the alternatives considered, the implementation details and the results obtained so far.

I Know What You did Last Puppet Run

Elizabeth Plumb - Datadog - Solutions Engineer

Knowing how our apps are performing is a constant need. But when you're using a tool who's job it is to enforce a configuration, you need to watch how those runs influence performance. If you're not associating your Puppet runs with your environment's performance, you're missing a big piece of the picture!

In this talk, I'll show you the why and how of:

  • Integrating Puppet with Datadog to see the impact your Puppet runs have on your nodes
  • Overlay Puppet runs on top system / application performance metrics to see how your nodes handled the change.
  • Surface Puppet metrics like average run time, resources skipped/failed/out of sync, and number of resources changed across your entire infrastructure.

Deep-Dive: Cloud-Native Masterless Puppet, with Bolt and PuppetDB

Craig Watson - ForgeRock - Senior Systems Engineer

Building, managing and scaling a Puppet master in a largely ephemeral cloud environment can be quite a daunting prospect, with certificate management, node lifecycles and the usual high-availability points to consider.

In this session, we will deep-dive into how ForgeRock’s IT team are using masterless Puppet together with Bolt and PuppetDB to create a truly elastic cloud-native Puppet environment.

This approach has enabled us to scale out our infrastructure in the cloud from a standing start with minimal ongoing engineering overhead, and it can help you too!

Continuous Delivery for PE – Design and Roadmap

Cat Rayburn, Carl Caum - Puppet - User Experience Designer, Product Manager

In this talk, Cat and Carl will discuss the challenges IT organizations face when accelerating their velocity and coordinating across teams, all while trying to keep the lights on. You will learn how Continuous Delivery for Puppet Enterprise helps to address these challenges and get a glimpse of upcoming features in our infrastructure continuous delivery solution.

Cloud-Native Puppet: Config Management in 2020 and Beyond

Eric Sorenson - Puppet - Technical Product Manager

What role does configuration management have in containerized and cloud-native infrastructure? How does Puppet work with modern cloud platforms like Kubernetes? Is there a way out of the maze of YAML we've trapped ourselves in? In this session, Eric will walk through Puppet's perspective on the evolution of infrastructure platforms and the changes to our tools and processes that are necessary to adapt to the landscape of today – and tomorrow.

Bolt Internals Deep Dive

Alex Dreyer - Puppet - Senior Principal Software Engineer

Curious how Bolt handles different types of connections or how it interacts with the Puppet language? Want to learn more about how the plugin extension points work? This talk will cover how Bolt itself is structured and how we develop new features. This is a great introduction for those who would like to contribute to Bolt or are just curious about how the pieces fit together. 

PE Deep(er) Dive

Yasmin Rajabi - Puppet - Senior Product Manager

The latest release of Puppet Enterprise is out! This talk will provide an overview of the new features, common use cases, and a demo of the new functionality.

Automate, Analyze, and React using Data Driven Decisions

Domnick Eger - Splunk - Senior DevOps Practitioner

Puppet Bolt + Splunk can bring the power of Investigation, Triage, and Collaboration with the ability to make data-driven decisions to deliver real-time insights into your environment. These details can help you build a better understand your whole situation by taking an agentless approach in operations, security, and development. We are going to show you a few examples of this and how you can fix things on demand or by utilizing alert actions to remediate issues quickly.

ITIL is Dead, Long Live ITIL (in Spirit)

David Alexander - Puppet - Principal Sales Engineer, APJ

In spite of all hope to the contrary, the spirit of ITIL lives on in thousands of organizations around the globe, and seems to be a blocker for DevOps in one way or another in many of these. So what are some of the things we can do within an ITIL framework to move towards a DevOps utopia? In this talk, we will consider how small changes can create big improvements without significantly impacting risk, and how you can start automating towards the future right now.

Multi-Node Acceptance Tests for Fun and Profit

Trevor Vaughan - Onyx Point, Inc. - VP Engineering 

This session will walk through the mysterious task of getting Beaker running in PDK and present a multi-node acceptance test using the puppetlabs-ntp module.

The presentation hopes to promote an understanding of the following:

  • Why acceptance testing is important
  • Why multi-node acceptance tests are important
  • A minimal-fuss method for getting Beaker running via rake tasks and PDK

Security & Compliance at Scale with Automation

Bill Tang - Puppet - Senior Product Manager

While manually hardening a single or a small handful of servers is doable, automation is not a nice to have but a must to securing 1000s of servers consistently and at scale.

Automated Patching with Bolt

Nick Maludy - Encore Technologies - DevOps Manager

If patch management is a problem in your infrastructure, then this talk is for you. This talk will walk through our journey to automate the patch management of our infrastructure. Details will be shared about our architecture, phased approach and implementation. We will also showcase our new Puppet module that can be used as a framework for patch management with Bolt and Puppet.

Puppet Developer Tools: Litmus and PDK

TP Honey - Puppet - Principal Engineer

Using litmus as a development tool / acceptance test runner for puppet modules

I Am Unit Tests (And So Can You!)

Tray Torrance - Twitter - Sr. Site Reliability Engineer

Puppet's history has included many testing tools & frameworks. This talk will provide a brief history of Puppet testing frameworks from `cucumber-puppet` to today's `PDK` and `Litmus`. Its primary focus will be using the modern tools and using them effectively -- giving consideration to proprietary and open source use cases. In addition to understanding which testing tools to use when attendees will leave with a better understanding of how to match their Puppet testing strategy to their specific needs.

AntiPatterns in Configuration Management: Treating Infrastructure as Code

Allee Clark - Oscar Health - Site Reliability Engineer

What are configuration management best practices? For answers to these questions and more, join us on a tour of SREs’ journey through our migration from one Linux Kernel version to the next. We’ll get a brief overview of our configuration management design. How we refactored our legacy code for the future to scale our infrastructure. How we took this opportunity to improve our configuration code review process to increase shared responsibility throughout our engineering organization.

DevOps Performance from a Different Data Set

Michael Stahnke - CircleCI - VP Platform

What can you learn about DevOps and software delivery practices by looking at data from a platform with more than 300,000 developers, 25,000 organizations and 25+ million builds per month? I wanted to find out. As an author of State of DevOps Report in 2018, I was very interested in this new data set from a large SaaS developer platform. What items pop out from the data? Are they different than what is seen through surveys where responders opt-in to participating, vs being aggregated through platform usage? Additionally, does the data validate assertions from State of DevOps Reports of years past about batch sizes, trunk development, and team size?

I’ll cover a view into anonymized team data to share insights, behaviors, and metrics that help teams build better software, faster from millions of builds and look into characteristics of success that we can measure through our data. Then I’ll overlay that onto what we’ve found through survey data and point confirmed actions that improve delivery flow, and open up some counter points to what we’ve seen so far.

Transforming DevOps Processes and Culture through Consistent Iteration and Cross-team Empathy

Chris Leicester - Puppet - Software Engineer

We often think of DevOps CI/CD as a complete, 100% automated solution for our entire infrastructure management process, but this perception causes many teams to give up before they get started. While this may appear to be a CI/CD hurdle, it is actually a cultural hurdle. The key to implementing CI/CD is continuous improvement, and more often than not, that improvement must start at the cultural level.

DevOps teams often get lost in the magnitude of overhauling their entire infrastructure automation and end up at a standstill. Drawing from the principles of CI/CD itself, we will move past this mindset and explore the following human-first solutions to technologically complex problems.

Destroying the notion of the “all-or-nothing” approach to automation. “Our infrastructure is too complex to automate”: Codifying your end-to-end process to reveal your “Human Pipeline”. Low hanging fruit: Where to begin converting manual tasks into automated tasks by observing the Theory of Constraints. Furthering efficiency: Developing intra-team empathy to promote collaboration and reduce cross-team bottlenecks. Progress over perfection: The value of celebrating iterative, consistent successes, and applying what you’ve learned to the next iteration.

Automated Testing the Easy Way

Dylan Ratcliffe - Puppet - Senior Professional Services Engineer

Test all of your code without writing any actual tests using Onceover! This session will cover how to get 100% test coverage over your Puppet code with very little effort and no coding required, regardless of whether you are just starting out or have so much code you've given up on ever testing it all.

Scaling Puppet Infrastructure with Multi-Tenancy and Self-Service by Design

Jerry Yu -  HERE Technologies - Manager, Systems Engineering

Frank Branham - HERE Technologies - Lead Systems Engineer

We recently iterated our Puppet infrastructure and arrived at an architecture that enables multi-tenancy and self-service. With this talk, we'll state our problem and architecture design objectives, describe restraints/resources, outline how we select and/or adopt specific software tools to assemble our tool chain, and share our joys and woes solutioning to overcome integration and automation challenges and organizational constraints.

Chat Ops giving DevOps a Turbo Boost

Mithran Naiker -  Transurban - CTO

Scott Brown -   Transurban - Head of Infrastructure Operations and Service Assurance

When onboarding staff, how long does it take organisations to realise someone who is effective at their job once all onboarding is done? At Transurban this is a day zero activity for us, chat ops has given us a way to use our toolset by just using English. We will cover what we've done with Puppet, Webex, ServiceNow and Chatops to effectively lower the barrier to learning new skills and complete simple tasks across the business.

Scaling Configuration Management through Inventories

Alex Zbarcea -  Fannie Mae - DevOps Engineer III

The more supply chain principles apply to IT, the better. A good monitoring of the inventory allows an efficient and secure management of the supply chain. How do principles of the traditional Supply Chain (in Manufacturing) help scaling, when dealing with heterogeneous infrastructure (physical/VMs and cloud), multiple OS-es, package managers, services, and multiple teams managing these altogether in Puppet ? Join in exploring some patterns and lessons learned from managing a +10K nodes Puppet infrastructure within a highly regulated industry.

Puppetizing the Pain Out of Patching

Tony Green - Katana 1 - DevOps practice lead

Description coming soon. 

TBD - Additional sessions will be announced soon!

Coming soon.