Friday, September 26, 2014

The Cloudcast #163 - Evolution of CoreOS

Topic 1 - We spoke with Brandon Phillips (CTO) about a year ago, at LinuxCon in NOLA, and you were just coming out after some funding. Now things are closer to beta and GA. Lots of projects and activities has emerged since then. What’s been the company focus for the last 12 months?

Topic 2 - There are potentially a number of systems that can be involved with a CoreOS environment - etcd, systemd, fleet, Docker, etc. Help us understand how to think about that logic stack or interaction - OS, Container, Clustering, Scheduling, etc.

Topic 3 - People still struggle with the concept of DevOps and who does what - or what tools align to what. So with things like etcd, systemd, fleet doing a bunch of deployment and operational functions, do you see those being more in the domain of an operations team vs. other elements (eg, CoreOS, Docker, the apps) being the domain of the Dev team?

Topic 4 - CoreOS has a unique updating mechanism (OS-as-a-Service; Managed Linux). Explain how it works and how people operationalize around live updates.

Topic 5 - Docker has DockerHub, for managing Docker images. CoreOS has Enterprise Registry. What are the differences?

Topic 6 - While CoreOS is a Linux distribution, it feels like it’s entirely focused on Linux for Cloud environments (less packaging, more operations and scaling), not like what Redhat or Ubuntu focus on. Do you think that’s a valid way of looking at CoreOS? Is this a more modern “LAMP” stack that’s getting built?

Topic 7 - Do we eventually see CoreOS involved in distributed devices - Internet of Things?