Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Closing the Loop:
Direct Change Control
with Puppet
Nick Lewis
@nick_lewis
nick@puppet.com
"A Mad Tea Party" (CC BY-NC-SA ...
Hello!
Nick Lewis
@nick_lewis
nick@puppet.com
"shinkansen" (CC BY-SA 2.0) by twicepix
Artisanal, hand-crafted bits
• Fast
• For a while
• Wildly unsafe
• Impossible to track
#!/usr/bin/bash
o o o o o o o
?
?
Enter: Puppet!
💡
💡
💡
Nodes have a desired state,
which is periodically updated and reinforced.
Nodes have a desired state,
which is periodically updated and reinforced.
💡
💡
💡
Direct Change
puppet job run --nodes foo.example.com,bar.example.com,baz.example.com
puppet job run --query 'inventory { facts.osfamily ...
inventory { facts.osfamily = "Debian"
and resources { type = "Service" and title = "httpd" }
limit 3 }
nodes { last_report...
💡💡
💡
Orchestrator
💡💡
💡
Orchestrator
Direct Change
• The way to make change with Puppet
• Up to 10k nodes now, scale-out later
• Runs from your laptop
Client Tools
• puppet job
• puppet access
• puppet code
• puppet query
Future Work
• UI improvements
• Smarter puppet run throttling
• Open source tooling
Futurer Work
• Asynchronous enforcement
• Automatic change
• Devices, non-root agents
Questions?
Direct Puppet and Application Management for the Puppet Platform
Ryan Coleman
Friday, 1:30 pm @ Terrace Salon (...
PuppetConf 2016: Closing the Loop: Direct Change Control with Puppet – Nick Lewis, Puppet
PuppetConf 2016: Closing the Loop: Direct Change Control with Puppet – Nick Lewis, Puppet
PuppetConf 2016: Closing the Loop: Direct Change Control with Puppet – Nick Lewis, Puppet
PuppetConf 2016: Closing the Loop: Direct Change Control with Puppet – Nick Lewis, Puppet
Upcoming SlideShare
Loading in …5
×

PuppetConf 2016: Closing the Loop: Direct Change Control with Puppet – Nick Lewis, Puppet

142 views

Published on

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

Published in: Technology
  • Be the first to comment

  • Be the first to like this

PuppetConf 2016: Closing the Loop: Direct Change Control with Puppet – Nick Lewis, Puppet

  1. 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. 2. Hello! Nick Lewis @nick_lewis nick@puppet.com
  3. 3. "shinkansen" (CC BY-SA 2.0) by twicepix
  4. 4. Artisanal, hand-crafted bits • Fast • For a while • Wildly unsafe • Impossible to track
  5. 5. #!/usr/bin/bash
  6. 6. o o o o o o o ?
  7. 7. ?
  8. 8. Enter: Puppet!
  9. 9. 💡 💡 💡
  10. 10. Nodes have a desired state, which is periodically updated and reinforced.
  11. 11. Nodes have a desired state, which is periodically updated and reinforced.
  12. 12. 💡 💡 💡
  13. 13. Direct Change
  14. 14. 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" }'
  15. 15. 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" }
  16. 16. 💡💡 💡 Orchestrator
  17. 17. 💡💡 💡 Orchestrator
  18. 18. Direct Change • The way to make change with Puppet • Up to 10k nodes now, scale-out later • Runs from your laptop
  19. 19. Client Tools • puppet job • puppet access • puppet code • puppet query
  20. 20. Future Work • UI improvements • Smarter puppet run throttling • Open source tooling
  21. 21. Futurer Work • Asynchronous enforcement • Automatic change • Devices, non-root agents
  22. 22. Questions? Direct Puppet and Application Management for the Puppet Platform Ryan Coleman Friday, 1:30 pm @ Terrace Salon (track 6)

×