Sebastien Goasguen
Sebastien Goasguen built his first compute cluster in the late 90's when they were still called Beowulf clusters while working on his PhD; he has been working on making computing a utility since then. He has done research in grid computing and high performance computing and with the advent of virtualization moved to cloud computing in the mid 2000s. He is currently a Senior Open Source Solutions Architect at Citrix, where he works primarily on the Apache CloudStack project, helping develop the CloudStack ecosystem. Sebastien is a project management committee member (PMC) of CloudStack and Apache libcloud and a member of the Apache Software Foundation, he focuses on the cloud ecosystem and has contributed to dozens of open source project. He is currently writing the Docker Cookbook.
Set up Kubernetes with a Docker compose one-liner
Start exploring Kubernetes with minimal effort.
I had not looked at Kubernetes in over a month. It is a fast paced project so it is hard to keep up. If you have not looked at Kubernetes, it is roughly a cluster manager for containers. It takes a set of Docker hosts under management and schedules groups of containers in them. Kubernetes was open sourced by Google around June last year to bring all the Google knowledge of working with containers to us, a.k.a The people :) There are a lot of container schedulers or orchestrators if you wish out there, Citadel, Docker Swarm, Mesos with the Marathon framework, Cloud Foundry lattice etc. The Docker ecosystem is booming and our heads are spinning.
What I find very interesting with Kubernetes is the concept of replication controllers. Not only can you schedule groups of colocated containers together in a cluster, but you can also define replica sets. Say you have a container you want to scale up or down, you can define a replica controller and use it to resize the number of containers running. It is great for scaling when the load dictates it, but it is also great when you want to replace a container with a new image. Kubernetes also exposes a concept of services basically a way to expose a container application to all the hosts in your cluster as if it were running locally. Think the ambassador pattern of the early Docker days but on steroids.