|
For my personnal use case (and there's others) I'm using rundeck to launch chef on nodes (one solution on many). If a run ends in error it's marked as failed and I can relaunch on failed nodes easily. I do use rundeck for specific 'need now' run, for the rest I rely on a crontab job launching chef with a report/error handler which report back to a dashboard the updated resources, and some other specific needs (attributes accessed in our namespace, GAV of artifact deployed from nexus on this machine, cookbook version used, etc.) I do keep hope we can open source it on github one day. There's a lot of way to do this, which one is the good for you depends a lot of your interest of a run result and how you want to act on failure. My 2 cents on this subject, hope it will help. Le 2015-03-23 12:43, michael david mosier a écrit : Thank you everyone for helping me with naming conventions. I have another question. Again I am fairly new to this so I may have just not learned how this works yet. If someone has 1000 nodes. Going to each machine and running chef-client doesn't feel like it's the best way to do things. I know on the enterprise side they have a push type plugin. I also know with knife I can force a push to all the nodes. The problem I see with this is you may need to write an error handler into a recipe so you will know that something that was just updated on the node errored out. If your on each machine you can see on the screen if it errored out when you run chef-client but remotely I am not sure how to handle catching errors. I was thinking since there are two built in error handlers maybe I could write a script that would email me whenever an error occurs but that may mean that each node has to have send-mail running. 1. How do you all deal with updating multiple nodes without SSHing to each and running chef-client 2. How do you all deal with error handling. Thank yo so much Michael D. Mosier Systems Guy University Of Texas Astro Physics
|
Archive powered by MHonArc 2.6.16.