PuppetConf 2017

Distelli recently joined the Puppet family to make application delivery seamless no matter what the application runs on—VMs or containerized applications running in on-premise environments, public or private clouds, and Kubernetes clusters. Automation has changed how we deliver software, and we’ve come a long way from the days of developers throwing code over the wall to operations. But we’re still in the early stages in this long arc of automation progress. Together, Distelli and Puppet are unifying operations and development workflows so teams can iterate faster and ship sooner. Join this session to learn:

• How to deploy traditional software and containers to any on-premise, cloud environment, or Kubernetes clusters.


• How Distelli lets you know who did what when. Find out who checked in the code that failed a deploy.


• Use Distelli to promote and approve deployments.


• Build Docker images from any repo and push to the container registry of your choice


• How Puppet will integrate with Distelli and what we’re planning next.

Adding Windows servers to a Puppet instance can feel like a daunting task, even more so when you already have a large number of Linux servers in Puppet already. Learn how Walmart integrated their Windows servers into Puppet Enterprise. We’ll discuss not only why we chose Puppet over other tools, but why and how we still use tools like DSC, SCCM and GPOs. We’ll also go over the successes and pitfalls we had along the way in using Puppet on Windows, onboarding other teams, and evangelizing our team’s vision to others.

The expectations and responsibilities for a modern operations team are high. Today, ops is expected to build and design delivery pipelines, have continuous statistic collection as a part of their monitoring services, and complement the development process with continuous integration and delivery practices, all while still maintaining critical back-office applications that most wouldn’t wish upon their enemies. How did it get that way? What separates the operations teams that lead from the ones who react? To dig in, we’ll consider a reactive team mired in fire-fighting and incapable of making headway, then watch as change that betters the team’s output and perception throughout the organization is slowly introduced. We’ll cover root-cause analysis efforts, bringing pain forward, experimentation, shifting left on quality, and selling automation and DevOps practices to management. This talk will not focus on tools, but rather procedural and cultural improvements that highlight the journey operations has undergone, and how we can prepare for the future.

I have a two-year-old daughter who adores Dr. Seuss. And as I was reading Cat in the Hat for the 214th time, I realized Dr. Seuss had it all figured out. His words are odd. The cadence confusing. But there’s a gem hidden in all his children’s rhymes. You see, Dr. Seuss would have made an excellent engineer. Because great code isn’t about choosing the perfect method name or building out 95% test coverage. All that is great, but it doesn’t make great code. YOU DO. It likely never feels that way. There’s a rhythm to software development that goes something like this: 1. “Easy. I’ve got this.” 2. “Uhhh, maybe not.” 3. “HALP! I have no idea what the f*ck I’m doing.” 4. “How did I not think of that before?!” 5. “I AM A GOD.” This process is okay if you’re comfortable having a mild psychotic break every sprint. I’m not. We’re going about it all wrong. Putting ourselves — our egos — above our code. No judgement. I do it too. We’re human. It’s okay. But I think we can bypass our egos and the emotional ups and downs it produces. This talk will focus on common pitfalls along the development lifecycle and distill Dr. Seuss’s excellent advice into concise steps developers can take before they write a single line of code. Examples include: * Overcoming imposter syndrome. Well, keeping it under control. * Finding a support group outside of work. Mentors to provide honest feedback about your growth and peers to support you. * Creating a collaborative culture at your job. Celebrating successes, embracing failures. Letting go of the need to be "right." In the words of Dr. Seuss: You have brains in your head. You have feet in your shoes. You can steer yourself any direction you choose. You’re on your own. And you know what you know. And YOU are the guy who’ll decide where to go.