Puppet customers across diverse industries share how DevOps principles and cultural shifts became catalysts for widespread automation adoption. Before embracing DevOps, many organizations faced departmental silos, communication gaps, and manual tasks that took up valuable time. Implementing Puppet fostered collaboration between developers and operations, creating a shared understanding of goals and challenges.
You can try Puppet Enterprise for free and see for yourself the difference that DevOps collaboration can make for your teams.
Customers Interviewed
Dan Spurling, Getty Images
Alex Harden, Veradigm
Peter Magnaye, FINRA
Martin Jackson, Walmart
Nate Loomis, Wells Fargo
Transcript
Dan Spurling [0:06] Within Getty, DevOps has been something that we have been focused on across our entire organization and Puppet and other tools have helped us remove lines or remove barriers between what has historically been an operations focused team and a development focused team. Working in the same tool and helping each other be successful with the same tool and the same capabilities allows people to cross fences and cross barriers, and work together to achieve a longer common objective.
Alex Harden [0:28] So our part of the organization tends to be very infrastructure focused. So, bringing DevOps into the conversation with Puppet has enabled us to not only break down some of the silos that exist within our infrastructure side of the organization, but also gives us the opportunity to collaborate with our customers who are the application owners, and it'll improve our service time and our ability to get new applications up and going for our shared customers.
Peter Magnaye [0:53] A traditional enterprise IT has many silos. And for us to be successful, we had to break down those silos and and make Puppet available to all the infrastructure teams and to enable their automation as well. Another thing is we were able to break down the application developer versus infrastructure engineer silo, and now application developers are also using Puppet to provision their infrastructure workloads in Amazon.
Martin Jackson [1:23] In many ways, Puppet kind of enforces that DevOps mentality that says, "this is the configuration that you're gonna have on this system." Puppet forces you to get into the room and to have that conversation with people and say, "this is what the kernel tunings are gonna look like. This is what the SIS controls are gonna be. This is what the u-limits are going to be set to. You can't set it this way and then set it this way somewhere else. You have to plan in advance and kind of layer what your configuration is gonna look like."
Martin Jackson [1:54] And the end result is that, generally, everybody's really happy with the result. It leads to a single model and a single deliverable, which is the server's desired configuration state.
Nate Loomis [2:12] DevOps to us has changed the way that we interact with the business. They used to have to understand much more of the technical details, but at this point, it's all abstracted.
Nate Loomis [2:17] And really, we get to have a conversation about the business using their terms, and talking to them about the experience that they want. And that allows us to, you know, raise the level of our conversation to their level, and it also allows us to be more nimble in how we respond to their needs, their initiatives.