Book Image

DevOps Culture and Practice with OpenShift

By : Tim Beattie, Mike Hepburn, Noel O'Connor, Donal Spring, Ilaria Doria
Book Image

DevOps Culture and Practice with OpenShift

By: Tim Beattie, Mike Hepburn, Noel O'Connor, Donal Spring, Ilaria Doria

Overview of this book

DevOps Culture and Practice with OpenShift features many different real-world practices - some people-related, some process-related, some technology-related - to facilitate successful DevOps, and in turn OpenShift, adoption within your organization. It introduces many DevOps concepts and tools to connect culture and practice through a continuous loop of discovery, pivots, and delivery underpinned by a foundation of collaboration and software engineering. Containers and container-centric application lifecycle management are now an industry standard, and OpenShift has a leading position in a flourishing market of enterprise Kubernetes-based product offerings. DevOps Culture and Practice with OpenShift provides a roadmap for building empowered product teams within your organization. This guide brings together lean, agile, design thinking, DevOps, culture, facilitation, and hands-on technical enablement all in one book. Through a combination of real-world stories, a practical case study, facilitation guides, and technical implementation details, DevOps Culture and Practice with OpenShift provides tools and techniques to build a DevOps culture within your organization on Red Hat's OpenShift Container Platform.
Table of Contents (30 chapters)
Free Chapter
2
Section 1: Practices Make Perfect
6
Section 2: Establishing the Foundation
11
Section 3: Discover It
15
Section 4: Prioritize It
17
Section 5: Deliver It
20
Section 6: Build It, Run It, Own It
24
Section 7: Improve It, Sustain It
27
Index
Appendix B – Additional Learning Resources

Developer Workflows

Git is a version control system (VCS) created by Linus Torvalds (author of the Linux kernel) to track changes in source code and easily manage these changes across many file types and developers. Git differs from other VCS in that it is decentralized. This means that unlike, for example, Subversion (svn), each developer retains a complete copy of the source code locally when they check it out. Locally, each developer has a copy of all the history and can rewind or fast forward to different versions as they need to. An engineer makes their changes and applies those changes as a delta on top of another's work. This is known as a commit. Git can be conceptualized as a tree, with a trunk of these changes or commits on top of each other. Branches can spring out from the trunk as independent pieces of functionality, or work that is not ready can be merged back to the trunk. Once something is committed to Git, it is forever in the history and can always be found ...