Here are the slides from Chris Barker and Deepak Giridharagopal's PuppetConf 2016 presentation called Docker, Mesos, Kubernetes and...Puppet? Don't Panic!. Watch the videos at https://www.youtube.com/playlist?list=PLV86BgbREluVjwwt-9UL8u2Uy8xnzpIqa

1. Project Blueshift
Deepak Giridharagopal
CTO & Chief Architect @ Puppet
PuppetConf 2016

2. @grim_radical

3. The way we build systems
today will not be the way we
build systems tomorrow.
deepak / @grim_radical / #puppetconf 2016

4. Now is a great time for
those who build & manage
systems!
deepak / @grim_radical / #puppetconf 2016

5. Bare metal, virtual machines,
containers, job schedulers,
infrastructure APIs, service
discovery, dynamic
configuration, cloud functions,
unikernels…
deepak / @grim_radical / #puppetconf 2016

6. What can the systems of the
past & present teach us about
how to manage stuff in the
future?
deepak / @grim_radical / #puppetconf 2016

7. What is configuration
management?
No, seriously, what is it?
deepak / @grim_radical / #puppetconf 2016

9. deepak / @grim_radical / #puppetconf 2016

10. Identification
Control
Status accounting
Verification and audit
deepak / @grim_radical / #puppetconf 2016
thanks @garethr!

11. To properly manage a system,
you must understand & control
the inputs to that system, over
time.
deepak / @grim_radical / #puppetconf 2016
I mean "system" in the abstract sense. stay with me, people!

12. Example:
Files vs. Packages
deepak / @grim_radical / #puppetconf 2016

13. Example:
AWS autoscaling group
deepak / @grim_radical / #puppetconf 2016

14. Example:
etcd key/value pairs
deepak / @grim_radical / #puppetconf 2016

15. The nature of your systems’
inputs may change along with
your tech, but they’re still there
and they’re your problem.
deepak / @grim_radical / #puppetconf 2016

16. There’s more to running a farm
than the dilemma of pets vs.
cattle.
(n.b. I hate this analogy)
deepak / @grim_radical / #puppetconf 2016

17. There’s more to running The
Empire than the dilemma of
Jango Fett vs. clone troopers
(thanks @brianb!)
deepak / @grim_radical / #puppetconf 2016

18. New technology eliminates
some management problems,
but creates some new ones.
Just like all software, ever.
deepak / @grim_radical / #puppetconf 2016

19. There is no future with fewer
servers.
deepak / @grim_radical / #puppetconf 2016
note: I mean server in the SRE sense

20. If you’re going to put all your
eggs in one basket, you need to
take expert care of that basket.
deepak / @grim_radical / #puppetconf 2016

21. The future is not evenly
distributed.
deepak / @grim_radical / #puppetconf 2016

22. Unified tooling across
physical, virtual,
containerized, cloud, etc.
infrastructure is a big deal!
deepak / @grim_radical / #puppetconf 2016

23. Puppet is a bridge to the future.

24. Project Blueshift:
Use Puppet to provide and
manage next generation
software in a simple, reliable,
and consistent way.
deepak / @grim_radical / #puppetconf 2016

25. (without introducing more risk)
Docker module

26. (without introducing more risk)
Configure Docker
class { 'docker':
tcp_bind => 'tcp://127.0.0.1:4243',
socket_bind => 'unix:///var/run/docker.sock',
version => '1.11',
dns => '8.8.8.8',
}

27. (without introducing more risk)
Run Docker containers
docker::run { 'helloworld':
image => 'ubuntu:precise',
command => '/bin/sh -c "while true; do echo hello world
}

28. (without introducing more risk)
Manage networks
docker_network { 'my-net':
ensure => present,
driver => 'overlay',
subnet => '192.168.1.0/24',
gateway => '192.168.1.1',
ip_range => '192.168.1.4/32',
}

29. (without introducing more risk)
Setup UCP
class { 'docker_ucp':
controller => true,
version => '1.0.0',
tracking => false,
swarm_scheduler => 'binpack',
preserve_certs => true,
docker_socket_path => '/var/run/docker.sock',
license_file => '/etc/docker/subscription.lic',
}

30. (without introducing more risk)
Real world case studies

31. (without introducing more risk)
Read the book

32. (without introducing more risk)
puppet-in-docker

33. (without introducing more risk)
Docker Hub

34. (without introducing more risk)
Run Puppet in Docker
$ docker run --net puppet
--name puppet
--hostname puppet
puppet/puppetserver

35. (without introducing more risk)
Develop on Windows

36. (without introducing more risk)
Launch with Compose
version: '2'
services:
puppet:
container_name: puppet
hostname: puppet
image: puppet/puppetserver
ports:
- 8140
volumes:
- ./code:/etc/puppetlabs/code/

37. (without introducing more risk)
puppetlabs-image_build

38. Building Docker images with Puppet
should be as simple as building them
with docker build

39. (without introducing more risk)
Building with Puppet
$ ls
Puppetfile manifests
$ puppet docker build
--image-name garethr/someimage

40. (without introducing more risk)
Kubernetes module

41. (without introducing more risk)
Puppet has a long history of making
software deployment easier and more
reliable… I'm really excited to see Puppet
enabling their customers to seamlessly
adopt new technology like containers and
Kubernetes while maintaining a consistent,
familiar experience for production quality
software deployment.
Brendan Burns, cofounder, Kubernetes

42. (without introducing more risk)
Model K8S resources
kubernetes_pod { 'sample-pod':
ensure => present,
metadata => {
namespace => 'default',
},
spec => {
containers => [{
name => 'container-name',
image => 'nginx',
}],
},
}

43. (without introducing more risk)
Create abstractions
controller_service_pair { 'frontend':
app => 'guestbook',
role => 'php-redis',
tier => 'frontend',
port => 80,
image => 'gcr.io/google_samples/gb-frontend:v3',
replicas => 3,
service_type => 'LoadBalancer',
}

44. (without introducing more risk)
Official blog post

45. (without introducing more risk)
Extending to OpenShift

46. Minimal OS’s

47. (without introducing more risk)(without introducing more risk)
VMware Photon OS

48. (without introducing more risk)
CoreOS ecosystem

49. (without introducing more risk)
Mesos support

50. (without introducing more risk)
Consul integration

51. (without introducing more risk)
Rancher
class { 'docker': }
class { 'rancher::server': }
class { 'rancher':
registration_url => http://127.0.0.1:8080/v1/sc
agent_address => $::ipaddress_eth1,
}

52. (without introducing more risk)
$ puppet resource rkt_pod
rkt_pod { 'c8ecd9ae':
ensure => 'exited',
app => 'hello',
image_name => 'hello',
}
Rkt

53. (without introducing more risk)
Find out more about Puppet as
the bridge to the future with
Project Blueshift at
https://puppet.com/product/managed-technology/blueshift

54. Modern infrastructure track
"The challenges with container
configuration" —David Lutterkort, Thurs 2:30P
"Running puppet software in
Docker containers" —Gareth Rushgrove, Fri 1:30P
deepak / @grim_radical / #puppetconf 2016

55. (without introducing more risk)