Using Monitoring & Configuration Management to restart services.

2,010 views
1,957 views

Published on

These are the slides from a talk I gave to the Large Scale Production Engineering group in November 2011. The talk is on how to tie Nagios and Puppet together so that puppet can rectify problems detected by Nagios.

Published in: Technology, Design
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,010
On SlideShare
0
From Embeds
0
Number of Embeds
1,057
Actions
Shares
0
Downloads
10
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Using Monitoring & Configuration Management to restart services.

  1. 1. Combining Monitoring and CM to restart services. Greg Retkowski Operations Engineer, OnLive
  2. 2. Whats in it for me?● Itll free you up from firefighting● Itll react faster than a human can● Its a hedge against technical debt
  3. 3. Required Tools● NAGIOS● Puppet
  4. 4. High Level Diagram
  5. 5. Our Puppet Apache Class
  6. 6. Nagios service.cfg
  7. 7. Nagios commands.cfg
  8. 8. Puppet auth.conf● Create an empty namespaceauth.conf● Add this to your auth.conf:
  9. 9. Puppet puppet.conf
  10. 10. Testing the puppet agent● puppetd –listen –verbose –no-daemonize –no- client –fqdn `hostname`
  11. 11. Invoking puppetrun● puppetrun -a –host FQDN
  12. 12. The handle_puppetrun.sh script
  13. 13. Bringing it all together
  14. 14. Resourceshttp://www.rage.net/lspe

×