From Puppet templates to troubleshooting, writing custom types and getting up and running quickly— you'll learn about it at PuppetConf 2016 in San Diego. Learn more and register at https://puppet.com/puppetconf/.

1. t
Track Overview:
Inside Puppet
A deep dive into all things Puppet
19 - 21 October
San Diego

2. Up and Running With Puppet
Enterprise in 45 Minutes or Less!
Many of us have heard about configuration management tools and
the ecosystem of services and products that Puppet has. Some of
us are unsure how to write Puppet code, identify key features in the
product, or even navigate the console. Even fewer of us know how
to get up and running immediately with Puppet Enterprise.
In this session, we will show beginners and Puppet Enterprise
newbies how to install PE and manage key resources in less than
an hour. We'll cover the basics of Puppet code, using the GUI and
leveraging the Forge for future module development. You will leave
with the confidence you need to start managing resources today.
2
Thursday, October 20 | 11:15 am
Bryan Wood
Grace Andrews
Inside Puppet
Technical Solutions Engineer, Puppet
Technical Solutions Engineer, Puppet

3. Puppet Troubleshooting
How to diagnose Puppet infrastructure and code issues. In
this session I'll introduce some troubleshooting methods for
verifying your Puppet infrastructure is working as intended. I'll
show how to use API endpoints to find problems with your
system. We'll examine X.509 certificates and troubleshoot
common Certificate Authority issues. I will also show how
to use Ruby Pry to interact with puppet server during
catalog compilation.
3
Thursday, October 20 | 1:30 pm
Thomas Uphill
Inside Puppet
DevOps Engineer, Wells Fargo

4. Turning Pain Into Gain:
A Unit Testing Story
Puppet is integral to Box's infrastructure, serving many purposes.
Use of Puppet grew organically, resulting in a large monolith of
fragile spaghetti code. When we needed CI, this code was in an
untestable state. Out of the box, rspec-puppet didn't work. Rather
than continuing to rely only on manual testing or rewriting our code
into proper modules, roles, and profiles, we made the unit testing
system work with our spaghetti code. Our open-source
rspec-puppet extensions enabled us to add coverage for our
monolith, and can help others achieve the same. This session
covers Box's journey to a fully-featured Puppet CI. We discuss the
importance of unit testing, show it's possible to improve testing
practices, present solutions to roadblocks we encountered, and
share workflows we created.
4
Thursday, October 20 | 2:30 pm
Jordan Moldow
Nadeem Ahmad
Inside Puppet
Software Engineer, Box
Software Engineer, Box

5. Writing Custom Types to Manage
Web-Based Applications
Atlassian's Build Engineering team is responsible for the build
infrastructure that hundreds of developers rely on to perform thousands
of builds that upload hundreds of thousands of build artifacts a day. The
services behind this infrastructure, including Bamboo and Nexus, are
provisioned and configured using Puppet. To manage the configuration
of Bamboo and Nexus more effectively and with less disruption, the
Build Engineering team has created its own custom Puppet types and
providers to manage these applications through their REST APIs. Since
publishing, these modules have been downloaded tens of thousands of
times and received contributions from the community. This presentation
walks the audience through the design and development custom
Puppet types and providers.
5
Thursday, October 20 | 3:45 pm
Tim Cinel
Inside Puppet
DevOps Engineer, Atlassian

6. Deconfiguration Management:
Making Puppet Clean Up
Its Own Mess
You accidentally deployed the wrong thing. Or you deployed the right
thing, but now it's cruft and you want it gone. Puppet is an elegant tool
for placing and assembling infrastructure, but what happens when it's
time to disassemble? This talk will cover Yelp's experience using
Puppet for automatic deconfiguration management, and how we can
confidently make statements about both what our infrastructure _is_,
and what it _is not_, without requiring extra Puppet code. We will
consider how to do this with many of the resource types we use from
day to day, including the simplest ones (files), more complex
(cronjobs), and the fiendish (monitoring checks, system packages).
6
Thursday, October 20 | 4:45 pm
Josh Snyder
Inside Puppet
Site Reliability Engineer, Yelp

7. Friday, October 21 | 11:15 am
Martin Alfke
Moving From Exec to Types
and Providers
We want to automate this application rollout and
configuration by using Puppet DSL." The task is clear, the
tool is clear. But how to proceed? Installation is delivered as
tarball, configuration is done by running cli commands. This
talk will give an overview on how we started using commands
within exec resources, the difficulties and problems that rose
up, and the process of moving to Types and Providers.
7
Inside Puppet
CEO & Co-Founder, example42 GmbH

8. Puppet Templates
Writing templates greatly simplifies management of configuration files
in Puppet. This talk covers all of the templating options available in
Puppet as well as when and how to use them (and when to use
Augeas). We will validate and render ERB, EPP, and inline templates,
and see how to integrate complicated strings and variables from
throughout Puppet including referencing Hiera. Attendees will leave
ready to confidently and quickly choose the right formats for each
config file as well as be prepared to build and modify their own
well-structured templates.
8
Friday, October 21 | 1:30 pm
Sally Lehman
Inside Puppet
Production Engineer, Auth0

9. High Availability for Puppet
This session will be an overview of highly available
components that can be deployed with Puppet
Enterprise. It will focus on some of the current Beta
support in PuppetDB as well as tips and tricks from the
professional services department. The session will cover
field solutions ( both supported and unsupported ) that
allow architectures to be designed that align with different
levels of high availability across the services that support
running puppet on agent nodes during an outage of your
primary puppet infrastructure.
9
Friday, October 21 | 2:30 pm
Zack Smith
Russ Mull
Inside Puppet
Senior Software Engineer, Puppet
Principal Professional Services Engineer, Puppet

10. Want to explore more PuppetConf
sessions?
View our full agenda and other tracks at
puppet.com/puppetconf

11. t
Inside Puppet:
Speakers
A deep dive into all things Puppet
19 - 21 October
San Diego

12. Grace Andrews
Technical Solutions Engineer, Puppet
Grace Andrews is a Technical Solutions Engineer at Puppet, a
dog-lover, and an avid weight lifter. She has a background in
the social sciences and is passionate about empathetic
technologies and open source software. She's been
strengthening her command line skills and learning everything
she can about Puppet Enterprise as a member of the Technical
Solutions Engineering team. As a TSE, she has conducted
webinars, contributed to the TSE demo environment, and
engaged with customers to help them see the value of Puppet.
Prior to Puppet, Grace spent several years as the co-founder at
GraphAlchemist -- creating data visualizations and data
analytics solutions for various organizations.

13. Bryan Wood
Technical Solutions Engineer, Puppet
Thomas has given several tutorials on Puppet at LISA and
has spoken at PuppetConf and Puppet Camps. He has
published four books on Puppet, including Mastering
Puppet. He is co-organizer of the Seattle PUG and is also a
Board member of LOPSA (lopsa.org). He also helps run the
local LOPSA meetup in Seattle, SASAG. He is a long time
Linux Administrator with an RHCA from RedHat. When not
making terrible Dad jokes he enjoys watching panel shows
and browsing r/justrolledintotheshop. You can find his blog
at ramblings.narrabilis.com.

14. Thomas Uphill
DevOps Engineer, Wells Fargo
Thomas has given several tutorials on Puppet at LISA and
has spoken at PuppetConf and Puppet Camps. He has
published four books on Puppet, including Mastering
Puppet. He is co-organizer of the Seattle PUG and is also a
Board member of LOPSA (lopsa.org). He also helps run the
local LOPSA meetup in Seattle, SASAG. He is a long time
Linux Administrator with an RHCA from RedHat. When not
making terrible Dad jokes he enjoys watching panel shows
and browsing r/justrolledintotheshop. You can find his blog
at ramblings.narrabilis.com.

15. Nadeem Ahmad
Software Engineer, Box
Nadeem Ahmad is a Software Engineer on the Ops Platform
team at Box. Nadeem is originally from Toronto, Canada and
graduated from the University of Waterloo in 2014. As part of
the Ops Platform team, he champions Puppet best practices
at Box and owns the Puppet unit testing pipeline. When he is
not working with Puppet, he spends most of his time
automating various infrastructure workflows. Nadeem has
experience writing code in PHP, Java, C#, and Python and is
passionate about open-source software, writing clean code,
and continuous integration/continuous delivery. When not in
front of a computer, you will often find Nadeem watching
some kind of sporting event.

16. Jordan Moldow
Software Engineer, Box
Jordan Moldow is a Software Engineer on Box’s Desktop
team. After earning MIT BS degrees in CSE and mathematics
in 2014, Jordan moved to California to join Box. He writes
Python for Desktop clients and CI infrastructure, and Puppet
for build machines. After a call to tackle Puppet tech debt,
Jordan volunteered with Ops to set up a unit testing
framework. Jordan is passionate about free software, clean
software/interface design, and teaching. He’s contributed to
multiple projects, teaches high school students through
Learning Unlimited, and leads Box code walkthroughs.
Jordan consistently makes the effort to become well versed
in the best practices, and often the source, of the tools he
uses. His teammates consider him to be very knowledgeable
in Python, Puppet, and Git.

17. Tim Cinel
DevOps Engineer, Atlassian
Tim has been an infrastructure nerd in Atlassian's Build
Engineering team for more than two years. The Build Eng
team is responsible for running the many services
responsible for building, testing, and deploying software that
Atlassians are working on on every day. In order to develop,
test and deploy changes to the Build Engineering
infrastructure, Tim get to use a combination of neato tools
like Puppet, Terraform and Packer. Tinkering with
infrastructure that runs thousands of builds simultaneously is
something that makes Tim excited. A bit too excited.
Unfortunately, Tim's self-appointed nickname, "Build
Whisperer", has not caught on. Not yet, anyway.

18. Josh Snyder
Site Reliability Engineer, Yelp
Josh is a site reliability engineer for Yelp, currently working
on Eat24. A veteran infrastructurer, he works on everything
from load-balancers to deployment to metrics collection, but
his biggest focus is stateful services: datastores, of both the
SQL and NoSQL variety. He likes designing foundational
systems that serve their functions reliably and silently. To
that end, he is always rounding out sharp corners of
infrastructure, and crafting new functionality to be as
maintainable as possible. You may have seen him present
before at Percona Live, Velocity NY, or MySQL Connect.

19. Martin Alfke
CEO & Co-Founder, example42 GmbH
Martin has been working with Puppet since 2007. In 2015 he
co-founded example42 GmbH located in Berlin/Germany. He
is official Puppet Certified Instructor and Puppet Certified
Consultant and co-author of "Puppet 4 Essential" book. In
earlier times he would have said that he is a System
Engineer. Nowadays he prefers the name Infrastructure
Engineer. The main difference is within the tools: a System
Engineer uses SSH to log in and fix a problem; the
Infrastructure Engineer repairs his automation.

20. Sally Lehman
Production Engineer, Auth0
I grew up in various small towns in Oregon and Washington,
and am now semi-nomadic, spending time in California,
Arizona, and Tennessee. My first computer experiences were
with EMACs, MS-DOS, and Ski Free when I was < 5 years
old, and people have been trying to get me off my computer,
with limited success, ever since. I have a wonderful husband
named Brandon and a tiny Italian Greyhound named Sudo.
At Auth0, I am a Production Engineer. I focus on monitoring
and availability as well as config management for highly
scalable and available infrastructure. My favorite movie is
Office Space and I make a mean Tiramisu.

21. Zack Smith
Principal Professional Services Engineer, Puppet
Zack has been a Professional Services engineer for the last
4.5 year at Puppet. He was the original author of the puppet
advanced course and is currently consulting with some of the
larger customers at Puppet. Before that he was a consultant
for 10 years doing custom script development and various
installation/integration and migration projects for multiple
vendors. He has a very cute dog named "Freyja".

22. Russ Mull
Senior Software Engineer, Puppet
Russell works on PuppetDB and HA at Puppet. He's into
Clojure, guitars, and ways to make everything conflict-free.

23. t
Get on the path
to a better future
Join us 19-21 October in San Diego
Register now
Summer Savings:
Save $240 until 15 September
puppetconf.com