The evolution of DevOps culture: sessions from Puppetize PDX
In the timeline of modern technological evolution, DevOps is a relatively old concept, dating all the way back to 2008. And while “DevOps” may be the most overused buzzword of the last decade, it has remained relevant largely because of what it stands for. Its culture-first ethos and the underlying principles of collaboration, communication, and sharing are good guidelines for cross-functional work — no matter what those functions might be.
But as more organizations move toward containerization and CI/CD, does the traditional notion of DevOps hold up? Are the core cultural tenets still useful, or are they incompatible with the shifting landscape? These themes emerged at our Puppetize PDX user conference in October. Check out the following talks for perspectives on the application and evolution of DevOps culture.
DevOps in a containerized world
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 of 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 collaboration still possible? Or are containers the DevOps killer?
In this session, Martin Alfke, CEO at example42 GmbH, discusses the role of DevOps in a containerized world.
Transforming DevOps culture
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.
Puppet software engineer Chris Leicester draws on the principles of CI/CD to demonstrate how human-first solutions can be used to solve technologically complex problems.
Expanding the circle of trust: Onboarding new Puppet developers
DevOps at Walmart is an extension of the company’s mission that everyone shares the responsibility for serving customers. Configuration management is at the core of Walmart’s DevOps effort — getting everyone to agree on what infrastructure looks like and how it should run in service of Walmart’s mission.
Martin Jackson, distinguished systems engineer at Walmart, shares how Walmart has on-boarded and enabled 77 developers from all areas of the organization. Their investment has paid off as their first and second generation of developers have moved on to new teams to mentor other new developers on using Puppet for their DevOps efforts.