Book Image

DevOps Paradox

By : Viktor Farcic
Book Image

DevOps Paradox

By: Viktor Farcic

Overview of this book

DevOps promises to break down silos, uniting organizations to deliver high quality output in a cross-functional way. In reality it often results in confusion and new silos: pockets of DevOps practitioners fight the status quo, senior decision-makers demand DevOps paint jobs without committing to true change. Even a clear definition of what DevOps is remains elusive. In DevOps Paradox, top DevOps consultants, industry leaders, and founders reveal their own approaches to all aspects of DevOps implementation and operation. Surround yourself with expert DevOps advisors. Viktor Farcic draws on experts from across the industry to discuss how to introduce DevOps to chaotic organizations, align incentives between teams, and make use of the latest tools and techniques. With each expert offering their own opinions on what DevOps is and how to make it work, you will be able to form your own informed view of the importance and value of DevOps as we enter a new decade. If you want to see how real DevOps experts address the challenges and resolve the paradoxes, this book is for you.
Table of Contents (21 chapters)
20
Index
21
Packt

The hype around containers

Viktor Farcic: Speaking of technology, all the hype over the last couple of years has been about containers. How do you see that fitting into this whole picture?

Kohsuke Kawaguchi: When I worked at Sun Microsystems, we had our own operating system there called Solaris. I remember an internal conference where they talked about this thing called Solaris Zones. They would say, "Oh, we can split the user space into different portions, and we can allocate different CPU sizes, RAM, and so on to them. They will be like a different set of computers with virtually zero overhead." So now, looking back, I can see that what they were doing was actually putting in place the building blocks of what became containers.

The Solaris guys must have designed this feature, fully aware of the impact it can create. But it had zero traction. There were a number of other similar examples. The thing that I took away from Solaris is that we, as open source engineers, often tend to...