Puppet Podcast

Cloud teams are drowning in an increasing, unsustainable volume of external events: cloud events, git events, monitoring alerts, tickets, incidents, and others. In response, engineers manually perform a disparate set of actions across various cloud providers, container platforms, CI/CD tools, config mgmt tools, and hundreds of other APIs. To make this better, some developers try to create their one-off automation tools or integration hubs, usually per team or project. Eric Sorenson and Melissa Sussmann discuss Puppet’s event-driven automation, Relay, and how it helps clean up the “DevOps Dumping Ground” in your environmentLearn moreWe’re building the future of DevOps automation with Relay. Join the launch here Relay Launch

Puppet's developer experience has been through a lot of growing pains. Many of us learned Puppet before the PDK existed, when the state of the art was SSHing into a Puppet master, manually making a module's directory structure, and cracking open Vim to edit our manifests. Some of us still do that; old habits die hard. But the point is that the barrier to entry used to be really high, and it didn't have to be. James Pogran is a Puppet developer on a mission to change that and simplify the experience for practitioners of all levels. He's here to talk with us today about his work on the Puppet VS Code Extension.Learn moreInstall the Puppet VS Code Extension today!See more about the Puppet VS Code extensionGet started with the PDK today

In this podcast, Eric Sorenson and Melissa Sussmann will be exploring the challenges that DevOps engineers face in using cloud-native infrastructure and how Puppet can help with your deployments.Continuous deployment is essential to the growing cloud-native space, especially in the case of containerization. Everyone we’ve interviewed is looking to adopt cloud-native technologies, but they face significant challenges in adopting containers, microservices, and serverless infrastructure for even simple cloud-native applications.Project Nebula provides automation that helps customers easily work on provisioning, rollbacks, application deployment, and notifications all through one tool. Nebula also provides teams with a platform for sharing workflows and best practices to build consistent and coherent deployments. It's our latest offering for teams that are adopting various cloud-native and serverless technologies and need to unify this heterogeneous toolset into a single, end-to-end deployment workflow.Sign up fo

Puppet’s Nigel Kersten and CircleCI’s Mike Stahnke go behind-the-scenes of the 2019 report to talk about the shift to a security-focused report and where they see these challenges heading and evolving. Learn more• Download the 2019 State of DevOps Report• Listen to: Doing the DevOps with Yasmin Rajabi and Nick Maludy

In today’s episode, we talk to Nick Maludy DevOps Manager at Encore Technologies. He shares his career journey going from a developer to managing teams and applying DevOps at scale.Doing the DevOps can be hard and transformation takes time, Nick shares insight on how his team has implemented changes and continues to improve over time. Learn what tools they used and what advice he has to help introduce DevOps into your teams. Mentioned in the episode:• Nick's twitter: @NickMaludy• Puppet's slack channel:  http://slack.puppet.com• Blogs resources: https://puppet.com/docs/bolt/latest/bolt.html• encore tech blog: https://encore.tech/blog/• S**t Gary Says: http://garylarizza.com/• Rob Nelson's blog: https://rnelson0.com/• Bolt hands-on lab: https://puppetlabs.github.io/bolt/

We’re covering a few DevOps parallels, data-driven diaper changing, and, apparently, Baby Shark.Taking care of a newborn is a gargantuan task for everyone involved. We invite one of our technologists to tell us more about how he and his partner are automating the rough manual tasks away to make more time for rest and peace of mind.Automating chunks of the newborn/baby experience is beyond software. It’s about taking out manual tasks to make more time for important things… like sleep.* Andrew Nhem is the managing editor at PuppetLearn more• Check out Dad Verb's YouTube Channel • Here's an overview of Dr. Karp's "Five S's for Soothing Babies"• If somehow you've made it through most of 2019 without listening to "Baby Shark"... (you're welcome)

Last month, we spent two and a half days in Budapest with some of our best community friends. I think the summary of Contributor Summit was the one common complaint I heard:"There was too much good content and it was really hard to decide between workshops!" said everybody.That's a really good problem to have and is the hallmark of a great experience. The key was in how the event was organized. Rather than tightly control the messaging, we simply asked our facilitators to build workshops that spoke to them and to just bring their best selves to the table ready to collaborate.This was part of our new focus on the community contributor experience. The whole Summit practically crackled with electricity and what felt like every attendee came up to tell me how productive it was for them. What are we covering?In this podcast, we talk about what made Contributor Summit special and some of the lessons we learned. We spoke with Tim Meusel, better known as bastelfreak, about the critical role that Vox Pupuli plays in o

Sometimes big challenges need to be tested and solved for at a much smaller scale. In this case, it’s the 1:87 model train scale with an interesting experiment coming out of Puppet.  Learn more about a new way to bring people together and automate with Bolt.On this episode, Engineers Cas, Ken, Jacob, and Managing Editor Andrew chat about “bolting” remote task orchestration and automation onto a HO-scale model train set. The vision: sending  Bolt plans to operate a model train at Puppet’s Portland headquarters.Hear how this cross-functional team solves for the automation of remote devices, navigating network security requirements, possibly provisioning containers, and (most importantly) building a fun project that brings people together.

You've probably heard that we've got a conference coming up soon. But have you also heard about the exciting additional events going on around Puppetize PDX? We're coming back home to Portland, and are super excited to show you some of our favorite parts of our city.We've added a few extra events into the Puppetize PDX agenda and in this podcast, we'll talk with a small handful of Puppet employees who're helping facilitate some of those experiences for you. They range from integral parts of the conference, like the Birds of a Feather discussion sessions that Gene is facilitating, to the technical extras, like the Bolt workshop and the Hackday, all the way to the unrelated-but-still-fun Puppet-sponsored Portland Marathon team and the informal pinball tournament at Ground Kontrol.Come along; we hope you enjoy the listen!*Ben Ford is a software engineer and developer advocate at Puppet.* Learn more• See the Ground Kontrol facilities.• See the Puppetize PDX agenda• Read about the Birds of a Feather format• Play w

In this podcast, Eric talks with Bryan Belanger from Fervid about working with Puppet in highly regulated compute environments. As a consultant for US Government agencies, Bryan's been working to get "Authority to Operate" for governmental cloud services, to speed up time to delivery and reduce compliance risk. The Puppet modules for STIG hardening, especially for Windows servers, let them build a baseline from existing systems and enforce that across the environment. We talk about the Forge, about Cloud, and about... Canada! Windows hardening module: https://forge.puppet.com/autostructure/harden_windows_server *Eric is a technical product manager at Puppet.*

I hope to see you in Budapest, 4-5 June.Contributor Summit is just around the corner and we can't wait to catch up with you. Budapest will be beautiful in June and we've got two days of workshops, collaboration, hacking, and discussions on the present and future of Puppet projects lined up for you. For some of you, this will be the first time we've met face to face, and that's pretty exciting!And don't forget, Project Month is going on right now, and you'll have the opportunity to present your work at Summit. Maybe you'll even attract some contributors to help you out!We realize that international travel might sound like it requires sacks of cash, but since hotel and food are so affordable in Budapest, the total cost of the trip might be far less than you expect. Try a few searches on your favorite travel website to see for yourself!Don't forget to show up the evening before for the Vox Pupuli pinball party! More Info:• Contributor Summit• CS Project Month• Vox Pupuli pinball party *Ben Ford is a developer ad

Vox Pupuli has long been the backbone of the open source Puppet community. But as often happens when a group is so capable and ubiquitous, sometimes the work done by individuals in the group goes unsung. In this episode, Eric and Hunter tell the story of their own involvement in the group and share some fun historical stories.Today's musical intro was recorded by Eric Putnam.*Ben Ford is a developer advocate at Puppet.*

One of Puppet’s big strengths is declarative automation – you model the desired end state of your infrastructure and Puppet does the hard work of enforcing it. This concept is quite powerful and has become the industry standard for configuration management. But sometimes your workflow doesn't quite fit into that pattern. Sometimes you really do need to deploy point-in-time changes, or mix imperative and declarative approaches together in a single workflow.With Bolt, we've learned from the lessons of Puppet and used those to design the next generation of infrastructure automation. Listen as Eric Sorenson and Yasmin Rajabi explain the tools of the future.The music in this episode is part of a live performance Eric Sorenson, Puppet Director of Product, prepared for Volt Divers. The full track is available here*Ben Ford is a developer advocate at Puppet.*

It seems like every day is another paradigm shift anymore. SaaS, PaaS, configuration management, cloud native, immutable infrastructure, serverless, and so on. But one has to ask, what do we lose by always chasing the bleeding edge? Information hiding, API contracts, and other ways of abstracting away implementation details are all part of solid system architecture. Are there patterns from yesterday that we should continue applying towards the new ways of working today and tomorrow?George Pandzik (@DevOpsFables) thinks so, and he's here to talk about patterns that he doesn't think should be lost to the sands of time.*Ben Ford is a developer advocate at Puppet.*

We're all familiar with Puppet's main forte; that of managing configuration for computers, servers, cloud instances, etc. But as with any tool, community members often… color outside the lines.Carrying on with our community spotlight series, this episode highlights one of those unusual usages. Corey Osman started this project by using Puppet to manage tiny IoT devices but ended up building a whole management framework out of Puppet and Bolt technologies. Let's get started and hear his story.Today's musical intro was recorded by Manny, a software engineer on our hosted services team.*Ben Ford is a developer advocate at Puppet.*

We're kicking off 2019 with a bang and a series of spotlights on notable community members and their achievements. We've got some great shows lined up for you, from useful development tools, to community experiences, to lessons we could learn from the history of computing. Let's get started today with Corey Osman of Portland, Oregon who's built a command line REPL. This quick screencast shows some of the capabilities of the tool:A REPL, or command-line shell, allows you to interactively work within Puppet and see what effect each line of code you write will have. Rather than trying to understand an entire system at once, you can drop into the shell and try out a language construct or see how a variable will be interpolated. For even greater understanding, you can add breakpoints to your Puppet code so you can stop compilation at a known spot and inspect your variables or see what classes have been declared.Today