Management’s role in DevOps: orchestrating the why

Donkey teamwork What’s the point of it all? Why are we doing this? These questions pop up frequently in IT teams where the reason for doing your daily activities — like churning through tickets, whizzing up builds, or “doing the DevOps” — seems only that someone, somewhere told you to do it. If you’re in this situation — you have no idea how your activities are helping your organization make money — you should stop and find out quickly what your company’s goals and strategies are to make sure you’re not wasting time.

Will OpenStack, Kubernetes, Or Mesos Control Future Clusters?

“When Apple moved to bare metal with Mesos, one of the big reasons why they did it was, first, they did not need the virtual machines and, second, they got a big performance improvement. The virtualization tax that we often talk about is very real and for Apple it was on the order of 30 percent. Removing it meant Apple could run Siri jobs 30 percent faster, which is a really big deal.

Philips | Case Study | Pivotal

“Provisioning applications that required manual steps and operations that used to take weeks or months, can now take minutes or even less in order to stage and provision new applications.” Philips | Case Study | Pivotal

Axel Springer | Case Study | Pivotal

“Together, the teams were able to reduce deployment times from 14 hours to 14 minutes, facilitated by Pivotal Cloud Foundry’s integration with Jenkins and Gradle build systems. Since this pilot, Pivotal Cloud Foundry has had zero downtime. It is being maintained by just two operators, using their preferred tools: Logstash, DataDog and PagerDuty. Furthermore, it runs in Axel Springer’s chosen datacenter on European soil.” Axel Springer | Case Study | Pivotal