Harnessing Kubernetes – Cloud Foundry Container Runtime

November 13, 2017

A few weeks ago I attended Cloud Foundry summit Europe 2017 held in Basel, Switzerland.  One of the more interesting topics that came up was the “Cloud Foundry Container Runtime,” an effort formerly known as “Kubo.”

Kubo, which comes from “Kubernetes on Bosh,” was created jointly by Pivotal and Google in order to provide a simple way to deploy and operate production-ready Kubernetes clusters on premise and in the cloud.  Back in June, the Kubo code was donated to the Linux Foundation as an open source project.

To learn more about Cloud Foundry Container Runtime (nee Kubo) and the larger context it fits within I sat down with Ian Andrews, Vice President of Products at Pivotal.  Armed with only a pen and paper Ian provides an overview of the container runtime and explains how it differs from the Cloud Foundry application runtime, as well as which workloads are most appropriate for each.

Ian ends by walking us through the recently announced, Pivotal Container Service (PKS) that VMware and Pivotal worked on together with help from the Google cloud team (PKS is based on the Cloud Foundry container runtime with extra goodies thrown in).

Time markers

  • 00:00 –07:25      Intro/background: How Kubo came about and how it and Cloud Foundry (CF) elastic runtime were renamed “Cloud Foundry container runtime” and “Cloud Foundry application run time”
  • 07:25 – 24:00      Sketches out the CF architecture.  From there he goes through each of the two components that sit on top of BOSH:   CF container runtime and CF application run time.  He then compares the two runtimes
  • 24:00 – 28:55      Goes through Pivotal’s implementation of the above: Pivotal Cloud Foundry and Pivotal Container Service.

Extra-credit reading

  • Take Kubernetes, and bish bash BOSH, you’ve got Container Runtime – The Register
  • Cloud Foundry Morphs Kubo into Container Runtime – sdxcentral
  • VMware teams up with Pivotal, Google Cloud on new container service – ZDNet
  • Google, VMware and Pivotal team for on-premises Kubernetes – The Register
  • Choosing the Right Tool for Your App Modernization Project – VMware | Blogs

Pau for now…


Digital Transformation: The Perils and the Keys to Success

November 2, 2016

The week before last Dell EMC held its first Dell EMC World here in Austin.  The event was full of keynotes, breakouts and Dell EMC and partner booths.  On the expo floor a stage was set up where partners and various Dell EMC employees, from Michael Dell on down, were interviewed as a part of Dell EMC World Live.

I was fortunate enough to participate in two of the live sessions, one about speeding up app development for the digital enterprise, and the one embedded below.  The session below was entitled “Stop Hitting Yourself. Tips for Succeeding at Digital Transformation” and featured Richard Seroter and Michael Cote of Pivotal as well as myself.

Check it out

Some of the ground Cote, Richard and I cover

  • How Uber delivered a Digital-transformation wakeup call to ordinary enterprises
  • Evolving your business to being a software-enabled business
  • It’s not about software for software’s sake, it’s about developing a more intimate relationship with the customer
  • The last 20 years for IT has been about driving efficiencies rather than improving the customer relationship
  • Moving from silos to platforms
  • Often support will come from the CEO down and the developers up but it’s the those in the middle who have the toughest time

Extra-credit reading

Pau for now…


The coming donkey apocalypse — DevOps Days Austin

June 1, 2015

After a bit of a gap I’m continuing the my series from DevOps Days Austin.  After Damon Edwards kicked off the event, Michael Cote of Pivotal took the stage.  Cote presented “The coming donkey apocalypse — what happens when Devops goes mainstream.”

Take a listen (you can find his slides below):

Some of the ground that Cote covers:

  • What DevOps as a community needs to focus on next to expand
  • Unicorns (eg Uber and Netflix), Horses (eg top banks) and Donkeys (mainstream organizations)
  • 3 key areas of DevOps to focus on today
    1. Culture and process
    2. Supporting legacy code
    3. Tools and technology

Interviews on tap:

  • Cameron Haight – Gartner
  • John Willis – Docker
  • Paul Read – Release Engineering Approaches

Extra Credit reading

Pau for now…


%d bloggers like this: