Here are the slides from Nick Lewis' PuppetConf 2016 presentation called Closing the Loop: Direct Change Control with Puppet. Watch the videos at https://www.youtube.com/playlist?list=PLV86BgbREluVjwwt-9UL8u2Uy8xnzpIqa

1. Closing the Loop:
Direct Change Control
with Puppet
Nick Lewis
@nick_lewis
nick@puppet.com
"A Mad Tea Party" (CC BY-NC-SA 2.0) by Justin in SD

2. Hello!
Nick Lewis
@nick_lewis
nick@puppet.com

3. "shinkansen" (CC BY-SA 2.0) by twicepix

4. Artisanal, hand-crafted bits
• Fast
• For a while
• Wildly unsafe
• Impossible to track

5. #!/usr/bin/bash

7. o o o o o o o
?

8. ?

9. Enter: Puppet!

10. 💡
💡
💡

11. Nodes have a desired state,
which is periodically updated and reinforced.

12. Nodes have a desired state,
which is periodically updated and reinforced.

13. 💡
💡
💡

14. Direct Change

16. puppet job run --nodes foo.example.com,bar.example.com,baz.example.com
puppet job run --query 'inventory { facts.osfamily = "Debian" }'
puppet job run --query 'resources { type = "Service" and title = "httpd" }'

17. inventory { facts.osfamily = "Debian"
and resources { type = "Service" and title = "httpd" }
limit 3 }
nodes { last_report_status = "failed" }
catalogs { ! code_id = "urn:puppet:code-id:1:a393e1b;production" }

19. 💡💡
💡
Orchestrator

20. 💡💡
💡
Orchestrator

21. Direct Change
• The way to make change with Puppet
• Up to 10k nodes now, scale-out later
• Runs from your laptop

22. Client Tools
• puppet job
• puppet access
• puppet code
• puppet query

23. Future Work
• UI improvements
• Smarter puppet run throttling
• Open source tooling

24. Futurer Work
• Asynchronous enforcement
• Automatic change
• Devices, non-root agents

25. Questions?
Direct Puppet and Application Management for the Puppet Platform
Ryan Coleman
Friday, 1:30 pm @ Terrace Salon (track 6)