Seth Goings, ReadyTalk

1. Running a Benevolent
Puppet Regime
@sethgoings

5. Puppet
Regime?

6. Benevolent
Puppet
Regime?

7. Puppet
Regime?

8. a system that is directed by an outside
authority that leads to hardships on those
governed

9. Benevolent
Puppet
Regime?

10. a system that is directed by an outside
authority that leads to improved operations
on those governed

11. a system that is directed by an outside
authority that leads to improved operations
on those governed
People Computers

13. 80
40

14. hundreds
thousands

17. Ol’ Perly

24. … but …

26. … won’t allow Puppet on his machine
because it will totally destroy his glorious
dotfiles ...

27. … why change what is working just fine? ...

28. 2 years ago...

29. Which statement best describes
your ability to work on Puppet
modules?

30. I try to avoid working on Puppet modules.

31. I can add new Puppet modules to support a
new feature or add functionality for a related
story and I am familiar with how to test
Puppet modules.

32. I try to avoid working on Puppet modules.

34. I can read Puppet code and generally figure
out what a Puppet module is supposed to do.

35. Survey Quotes

36. I don’t use Puppet

37. Are the currently used Puppet modules
available in a repository for viewing and/or
editing by any team member?
I wasn't aware that I had access ...

38. I feel like our Puppet modules are guarded. I
am happy and able to contribute but don't
feel like there is a culture that supports this.

41. What do you do when you run into
issues with Puppet?

42. I say nothing and hope someone else will
run into the problem and fix it later.

43. I investigate and resolve the issue myself
using online documentation or other
resources.

44. I file a Jira issue with steps to reproduce the problem.

45. I ask a subject matter expert for assistance.

47. Survey Quotes

48. I've never had to do anything with Puppet.
I do know that Puppet has never worked on
my dev environment and when I asked for
help people ran away from me.

49. … also Puppet attacked and killed my family.

50. I like the idea of Puppet, but I have no idea
how to get started or how it works. I can
blow through the examples and tutorials
online, but I have no idea how to contribute
or improve our internal Puppet infrastructure.

51. 2 years ago...

52. It’s not Puppet’s fault
it’s how we’re using Puppet
or how we’ve built our modules

54. How long does it take to set up a new
machine for any engineer?
(have hardware, need OS and packages installed required
for their duties)
A. 1 hour (10 points)
B. 1 day (5 points)
C. 1 week (1 point)
D. > 1 week (0 points)

55. How long does it take to fulfill a normal
priority request from someone to install a
service on every one of your machines
(including production)?
A. 1 hour (10 points)
B. 1 day (5 points)
C. 1 week (1 point)
D. > 1 week (0 points)

56. How long does it take to fulfill an
emergency request from someone to install
a service on every one of your machines
(including production)?
A. 1 hour (10 points)
B. 1 day (5 points)
C. 1 week (1 point)
D. > 1 week (0 points)

57. Who contributes to the advancement of
your infrastructure via Puppet?
A. everyone (10 points)
B. the team that owns it (5 points)
C. the person who owns it (1 point)
D. no one (0 points)

58. 35 - 40 = Killin’ it. (why aren’t you up here?)
20 - 34 = It’s not your first Puppet show, is it?
5 - 19 = You’re average!
0 - 4 = Did you pass math class?

60. People could help but “can’t”

62. Low Involvement

63. People who know how to
maintain/advance Puppet are too
tied up in fixing problems

65. Strained Group

66. Puppet is perceived as something that
gets in the way / is inconvenient

69. Processes and Team Subverted

71. Low
Involve

72. StrainedGroup
Low
Involve

73. Process Subverted
Low
Involve
StrainedGroup

75. Hard work will not
ensure quality

76. Best efforts will not
ensure quality

77. Gadgets
computers or
investment in
machinery
will not ensure quality

78. It is not enough to do
your best;
you must know what to
do
and then do your best.

79. Puppet
Regime?

80. a system that is directed by an outside
authority that leads to hardships on those
governed

81. Benevolent
Puppet
Regime?

82. a system that is directed by an outside
authority that leads to improved operations
on those governed

83. a system that is directed by an outside
authority that leads to improved operations
on those governed
People Computers

87. Commit to Collaboration

88. Who contributes to the advancement of
your infrastructure via Puppet?

89. Low Involvement

90. Commit to Collaboration

95. Commit to Collaboration

98. Commit to Collaboration

99. Low Involvement

101. Automate Authority

102. How long does it take to fulfill a request
someone to install a service on every one of
your machines (including production)?

103. Strained Group

107. Automate Authority

113. github.com/puppetlabs/beaker

114. ---
provisioner:
name: puppet_apply
manifests_path: test/manifests
manifest: site.pp
modules_path: local
hiera_data_path: test/hieradata
puppet_test: true
platforms:
- name: debian-7.8-64-puppet
driver_plugin: vagrant
driver_config:
box: puppetlabs/debian-7.8-64-puppet
box_url: puppetlabs/debian-7.8-64-puppet
suites:
- name: default
- name: kitchen_dev
- name: postgres
- name: docker_ship
- name: java

115. platforms:
- name: debian-7.8-64-puppet
driver_plugin: vagrant
driver_config:
box: puppetlabs/debian-7.8-64-puppet
box_url: puppetlabs/debian-7.8-64-puppet

116. provisioner:
name: puppet_apply
manifests_path: test/manifests
manifest: site.pp
modules_path: local
hiera_data_path: test/hieradata
puppet_test: true

117. suites:
- name: postgres

118. describe "Postgres Packages" do
pg_packages = %w[
postgresql-9.2
postgresql-client-9.2
postgresql-contrib-9.2
postgresql-9.2-pgextwlist
]
...

119. describe "Postgres Packages" do
...
pg_packages.each do |pkg|
it "#{pkg} is installed" do
expect(package(pkg)).to
be_installed
end
end
end

122. Strained Group

123. Automate Authority

124. How long does it take to fulfill a request
someone to install a service on every one of
your machines (including production)?

126. Rebuild Ruthlessly

127. How long does it take to set up a new
machine for any engineer?
(have hardware, need OS and packages installed required
for their duties)

128. Strained Group

130. Processes and Team Subverted

132. How long does it take to fulfill a request
someone to install a service on every one of
your machines (including production)?

135. Kif Kroker:
Captain, may I have a word with you?
Captain Zapp Brannigan:
No.

136. Kif Kroker:
It's an emergency, sir.
Captain Zapp Brannigan:
Come back when it's a catastrophe.

137. [ loud rumbling ]

138. Captain Zapp Brannigan:
Oh, very well.

151. - hosts: localhost
tasks:
...
- hosts: build_slaves
serial: 2
roles:
...
- jenkins-slave
tasks:
...

152. - name: get jenkins cli jar
local_action: get_url
url="https://<jenkins>/jnlpJars/jenkins-cli.jar"
dest="{{ jenkins_cli }}"
run_once: true

153. - name: put Jenkins slave offline
- name: wait for Jenkins slave to become idle
- name: initiate Foreman build
- name: restart server
- name: verify server is dead
- name: wait for server to come back alive
- name: launch Jenkins slave
- name: put Jenkins slave online

154. - name: put Jenkins slave offline
- name: wait for Jenkins slave to become idle
- name: initiate Foreman build
- name: restart server
- name: verify server is dead
- name: wait for server to come back alive
- name: launch Jenkins slave
- name: put Jenkins slave online

155. - name: put Jenkins slave offline
- name: wait for Jenkins slave to become idle
- name: initiate Foreman build
- name: restart server
- name: verify server is dead
- name: wait for server to come back alive
- name: launch Jenkins slave
- name: put Jenkins slave online

156. - name: put Jenkins slave offline
- name: wait for Jenkins slave to become idle
- name: initiate Foreman build
- name: restart server
- name: verify server is dead
- name: wait for server to come back alive
- name: launch Jenkins slave
- name: put Jenkins slave online

157. - name: put Jenkins slave offline
- name: wait for Jenkins slave to become idle
- name: initiate Foreman build
- name: restart server
- name: verify server is dead
- name: wait for server to come back alive
- name: launch Jenkins slave
- name: put Jenkins slave online

158. - name: put Jenkins slave offline
- name: wait for Jenkins slave to become idle
- name: initiate Foreman build
- name: restart server
- name: verify server is dead
- name: wait for server to come back alive
- name: launch Jenkins slave
- name: put Jenkins slave online

159. - name: put Jenkins slave offline
- name: wait for Jenkins slave to become idle
- name: initiate Foreman build
- name: restart server
- name: verify server is dead
- name: wait for server to come back alive
- name: launch Jenkins slave
- name: put Jenkins slave online

160. - name: put Jenkins slave offline
- name: wait for Jenkins slave to become idle
- name: initiate Foreman build
- name: restart server
- name: verify server is dead
- name: wait for server to come back alive
- name: launch Jenkins slave
- name: put Jenkins slave online

169. Rebuild Ruthlessly

170. Strained Group

171. Processes and Team Subverted

172. … and …

174. Preseed
Problems

175. Approx
Problems

176. Initial
Puppet
Run
Problems

177. A few weeks ago...

178. I rebuilt my development environment
today
by myself
without any problems!

179. I rebuilt my development environment
today
by myself
without any problems!

180. I rebuilt my development environment
today
by myself
without any problems!

181. Just yesterday...

182. No
Jenkins
user?

183. When I realized what was happening,
I had a small heart attack

184. You may have saved a HUGE
headache from happening tomorrow.
Thanks!

185. Rebuild Ruthlessly

186. Puppet
Regime

187. a system that is directed by an outside
authority that leads to hardships on those
governed

188. Process Subverted
Low
Involve
StrainedGroup

190. Benevolent
Puppet
Regime

191. a system that is directed by an outside
authority that leads to improved operations
on those governed
People Computers

192. H
igh
Involve

193. H
igh
Involve
PerformantTeam

194. H
igh
Involve
Rewarding Process
PerformantTeam

197. Commit to Collaboration

198. Automate Authority

199. Rebuild Ruthlessly

201. @sethgoings
seth.goings@readytalk.com