containers: four things to consider
TRANSCRIPT
@bridgetkromhout
Containers: four things to consider
@bridgetkromhout
lives: Minneapolis,
Minnesota
works: Pivotal
podcasts: Arrested DevOps
organizes: devopsdays
Bridget Kromhout
@bridgetkromhout
@bridgetkromhout
Four things about containers…
1.They aren’t new… but are different.
@bridgetkromhout
1979 (Version 7)1982 (BSD)
20042000
chroot FreeBSD jails Solaris Zones LXC
2008
A Brief History of Containers, Part 1 (before docker era)
@bridgetkromhout
A Brief History of Containers, Part 2 (docker common era)
2011
Cloud Foundry
2013
Docker
2014
Rocket (later rkt)
@bridgetkromhout
Four things about containers…
1.They aren’t new… but are different. 2.They aren’t just for development.
@bridgetkromhout
containing dramas
(docker in prod since Oct 2013)
@bridgetkromhout
Prod & Dev both benefit
consistent development repeatable deployment
@bridgetkromhout
Four things about containers…
1.They aren’t new… but are different. 2.They aren’t just for development. 3.They require rethinking our architecture.
@bridgetkromhout
Image credit: James Ernest
@bridgetkromhout
Autoscaling
Packer
AMI
EC2 Instances
Jenkins
GitHub
Chef
AMI factory
@bridgetkromhout
@bridgetkromhout
beware image chaos
@bridgetkromhout
Container Orchestration & Scheduling
@bridgetkromhout
Run containers on your public cloud of choice…
@bridgetkromhout
Four things about containers…
1.They aren’t new. 2.They aren’t just for development. 3.They require rethinking our architecture.
4.We can’t ignore them.
@bridgetkromhout
Unikernels: the next thing?
@bridgetkromhout
“It’s not necessary to change.
Survival is not mandatory.”
—W. Edwards Deming
@bridgetkromhout
docker run kitten
@bridgetkromhout
opencontainers.org
tl;dr:
open source & open standards drive adoption
@bridgetkromhout
discussion time